From: Glen Stewart glen_stewart@associate.com
To: lartc@vger.kernel.org
Subject: [LARTC] Relieving ISDN of web/ftp traffic via cable modem...
Date: Thu, 12 Oct 2000 21:11:45 +0000 [thread overview]
Message-ID: <marc-lartc-98373938216777@msgid-missing> (raw)
<PRE>Hi,
I have two identical NIC's installed in a Mandrake 7.1 system. One interface
is connected to ISDN and the other to a cable modem. The ISDN connection
serves web and mail.
I would like to relieve my ISDN connection of all personal web/ftp traffic
(from my browser and ftp client) by utilizing the bandwidth of the cable
modem on the 2nd interface. All web and mail traffic to the server on the
1st interface needs to continue as before.
After I activate the cable NIC in Linuxconf, I can ping my server with
another box using the cable address. Leaving it in this state (with IPV4
routing off) makes the mail server begin to "hold" mail for destinations on
the cable network. (uh-oh)
Next, I run "dhcdcd -R -h ______ eth1" which goes out and contacts the DHCP
server and assigns an IP address to the interface. After a few hours (with
no other tweaking) all my outbound traffic begins to flow across the cable
connection. It appears that mail is no longer being accepted on the eth0
interface. Running netstat -r shows the cable route as the 1st default route
before the eth0 default previously set. This isn't exactly what I was after
(-;
I've read dozens of FAQ's, but still don't know exactly how to tackle this
problem. The Linux Routing FAQ has wonderful explanations, but no sample
scenario close enough to mine (for me to understand).
Can someone offer some guidance?
Thanks!
</PRE>
next reply other threads:[~2000-10-12 21:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-12 21:11 Glen [this message]
2000-10-12 22:32 ` [LARTC] Relieving ISDN of web/ftp traffic via cable modem bert
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-98373938216777@msgid-missing \
--to=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.