All of lore.kernel.org
 help / color / mirror / Atom feed
From: tslayer@phatchicks.com
To: lartc@vger.kernel.org
Subject: [LARTC] Problem with 2 DSL lines
Date: Sat, 27 Apr 2002 02:34:25 +0000	[thread overview]
Message-ID: <marc-lartc-101987481920492@msgid-missing> (raw)

Hey..

I have 2 DSL lines both going into Linux.

I followed the HOWTO for Split Access at
http://lartc.org/HOWTO//cvs/2.4routing/html/x247.html#AEN251

I have the following:


I have 5 IPs on eth0 for DSL line #1.
I have 1 IP on eth2 for DSL line #2.


192.168.0.0/24 is my local lan.  I have iptables setup to SNAT to eth2 for
this local lan.

Everything seems to work great except if I want to access any of the IPs
on eth0 from the local lan.  I do a traceroute and it just hangs on the
1st hop.


The default is via the gateway of DSL line #2.

Any ideas?

Thanks...




_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

             reply	other threads:[~2002-04-27  2:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-27  2:34 tslayer [this message]
2002-04-28 15:06 ` [LARTC] Problem with 2 DSL lines tslayer
2002-05-01  1:53 ` tslayer

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-101987481920492@msgid-missing \
    --to=tslayer@phatchicks.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.