From: "Dave Miller" <dave@millerscomp.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Routing
Date: Sat, 07 Jul 2001 18:33:31 +0000 [thread overview]
Message-ID: <marc-lartc-99453086212698@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98373940416816@msgid-missing>
I'm not convinced yet that it won't work. Bellatlatic and Verizon are
actually on the same network. The ip addresses that we get through the two
accounts overlap sometimes. They will let us send email from a Verizon
account through a Bellatlantic connection and vise-versa. Do you have an
web address for the "src" hints to help me along. If it doesn't work -we so
be it. However, I still want to give it a try.
Thanks for all the help so far.
Dave
>
> On Fri, 6 Jul 2001, Dave Miller wrote:
>
> > Actually, both lines must use PPPOE - non static ip's (thanks Verizon
and
> > Bellatlantic), I had the Bellatlantic account before the merger, and now
> > have the second through Verizon. Doing a double pppoe is no big deal
thanks
> > to Roaring Penguin's software using the GUI that is available. If my
> > understanding is correct - if I could change the source address of all
the
> > packets going out through the 384 line to read what the pppoe address is
for
> > the 1.5mb line - should that not work? The rest of the world would see
the
> > source address as that of the 1.5 line instead of the 384 line. I just
> > don't know how to do that.
>
> Well, sorry, no. The upstream network may very well filter what it
considers
> 'foreign' source addresses from its net, thereby effectively blocking all
> your traffic. You can *try*, ofcourse, but I wouldn't be surprised if you
> cut off all your connectivity doing so.
>
> If you want to try: the 'src' hints for routes are followed, independent
of
> the interface you route out of.
>
> Doei, Arthur.
>
> --
> /\ / | arthurvl@sci.kun.nl | Work like you don't need the
money
> /__\ / | A friend is someone with whom | Love like you have never been
hurt
> / \/__ | you can dare to be yourself | Dance like there's nobody
watching
>
>
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO:
http://ds9a.nl/2.4Routing/
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
next prev parent reply other threads:[~2001-07-07 18:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-03 11:13 [LARTC] routing Spyros
2001-01-03 12:37 ` David
2001-01-05 12:25 ` Junus
2001-01-05 12:33 ` Junus
2001-07-06 14:03 ` [LARTC] Routing Dave Miller
2001-07-06 15:01 ` Arthur van Leeuwen
2001-07-06 15:18 ` Dave Miller
2001-07-07 6:33 ` Deepak singhal
2001-07-07 18:24 ` Arthur van Leeuwen
2001-07-07 18:33 ` Dave Miller [this message]
2001-07-07 18:37 ` Arthur van Leeuwen
2001-12-25 4:58 ` [LARTC] routing Daniel Wittenberg
2001-12-25 12:16 ` bert hubert
2002-10-30 12:57 ` [LARTC] Routing Jose Sebastiao Martins
2002-10-30 15:57 ` Martin A. Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-lartc-99453086212698@msgid-missing \
--to=dave@millerscomp.com \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.