I'm assuming that you have your internal network numbered differently than
the external "internet" side of your Cable modem, yes?

If so, you may need to check and make sure that both IPs are bound to the
server's NIC at the time you're having the problems.

Also, if you're using DHCP on the "internet" side, you could be running
into an issue of the lease running out on the DHCP supplied address, and
your system renewing that lease...the problem being that it may see the
secondary IP as also being a DHCP lease, and being unable to renew the
lease for the IP that is, for all intents and purposes, non-existent.

So...run ifconfig on the firewall box, when you're experiencing the
problem, and see if your system still sees the correct IPs for itself.

On Tue, 2 Jan 2001, Micah Yoder wrote:

> Just thought I'd try this one again...
>
> I'm masquerading a cable modem connection using a single ethernet card
> in the server.
>
> Most of the time, from the masq'd machine, either the entire Internet is
> reachable or none is.  But there have been a few times where some hosts
> are reachable and others aren't!
>
> Also, I can telnet from the masq'd box from the server and run ssh from
> there to the net.  No problems.  And I can browse with a remote display
> of Netscape from the server to the masq'd box.  No problems.
>
> When hosts are reachable, performance is great, though the ethernet hub
> does occasionally blink the "collision" light.
>
> MTU on both client and server ethernet cards is 1500.
>
> So I'm thinking it's *got* to be fixable without adding a second NIC to
> the server.  If packet collisions were the problem, why is performance
> fine when it works and why can I *always* get to the net fine via
> bouncing off the server?



_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list

Reply via email to