From: "D Webster" <dwebster78@home.com>
To: lartc@vger.kernel.org
Subject: [LARTC] Multiple Internet Interface Issue
Date: Mon, 09 Jul 2001 22:13:57 +0000 [thread overview]
Message-ID: <marc-lartc-99471686700854@msgid-missing> (raw)
[-- Attachment #1: Type: text/plain, Size: 1921 bytes --]
Okay, here's the deal, (diagram below)
I currently have 3 NIC's configured in my Linux server.
eth0 serving the home network
eth2 Cable modem to internet
ppp0 ADSL to internet (through eth1)
Connections can be established from eth0 (192.168.0.0/255)
and from eth2 (24.250.85.128/128). Because eth2
has the first default route.
However, ppp0 has a problem.
Traffic is received from ppp0 there is no return traffic through that
interface
unless the first default route is directing traffic through ppp0. Meaning
nothing goes out through eth2.
At this point, all I want is for connections able to be successfully
established through both internet interfaces (ppp0, eth2). In its present
state if someone tries to access any services(ping/telnet/ssh/etc.) via the
interface not setup as the default route, the connections timeout.
Network Diagram
Intranet Internet's
inet addr: 192.168.0.0 eth2 inet addr:
24.250.85.201
Bcast: 192.168.0.255 eth0 Bcast:
24.250.85.255
Mask: 255.255.255.0 Mask:
255.255.255.128
ppp0 inet
addr: 207.30.233.216
P-t-P: 207.30.233.1
Mask: 255.255.255.255
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
207.30.233.1 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0
#note: Is host
24.250.85.128 0.0.0.0 255.255.255.128 U 0 0 0 eth2
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
0.0.0.0 24.250.85.129 0.0.0.0 UG 0 0 0 eth2
#Default Route
0.0.0.0 207.30.233.1 0.0.0.0 UG 0 0 0 ppp0
#Default Route
Thanks for any help you can offer!
-Jon
[-- Attachment #2: winmail.dat --]
[-- Type: application/ms-tnef, Size: 5100 bytes --]
next reply other threads:[~2001-07-09 22:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-09 22:13 D Webster [this message]
2001-07-13 11:45 ` [LARTC] Multiple Internet Interface Issue D Webster
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-99471686700854@msgid-missing \
--to=dwebster78@home.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.