All of lore.kernel.org
 help / color / mirror / Atom feed
From: bert hubert ahu@ds9a.nl
To: lartc@vger.kernel.org
Subject: [LARTC] Relieving ISDN of web/ftp traffic via cable modem...
Date: Thu, 12 Oct 2000 22:32:53 +0000	[thread overview]
Message-ID: <marc-lartc-98373938216778@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98373938216777@msgid-missing>

<PRE>On Thu, Oct 12, 2000 at 05:11:45PM -0400, Glen Stewart wrote:

&gt;<i> I would like to relieve my ISDN connection of all personal web/ftp traffic 
</I>&gt;<i> (from my browser and ftp client) by utilizing the bandwidth of the cable 
</I>&gt;<i> modem on the 2nd interface.  All web and mail traffic to the server on the 
</I>&gt;<i> 1st interface needs to continue as before.
</I>
We've done somewhat the same thing here, works well.

&gt;<i> After I activate the cable NIC in Linuxconf, I can ping my server with 
</I>&gt;<i> another box using the cable address.  Leaving it in this state (with IPV4 
</I>&gt;<i> routing off) makes the mail server begin to &quot;hold&quot; mail for destinations on 
</I>&gt;<i> the cable network.  (uh-oh)
</I>
I think you need to draw a picture, and really understand what is happening.
Your problems so far seem to be IP Address related - for example, when you
activate the cable NIC, does it get an IP address? 

Investigate where routes are pointing, and understand what those routes
mean.

Your problems so far are too general for me to be of more assistance.

-- 
PowerDNS                     Versatile DNS Services  
Trilab                       The Technology People   
'SYN! .. SYN|ACK! .. ACK!' - the mating call of the internet


</PRE>

      reply	other threads:[~2000-10-12 22:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-12 21:11 [LARTC] Relieving ISDN of web/ftp traffic via cable modem Glen
2000-10-12 22:32 ` bert [this message]

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-98373938216778@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.