Basic routing usually notes that the routing system should have an
interface on each network/subnet that it's talking to. Usually, you would
have 2 interfaces, one pointing to the net, and one pointing to your local
network, which would point you at the dual NIC option, which you're trying
to avoid. The other option that should work, fairly well, is to have 2
IPs assigned to the eth0 interface...this way, there's an IP on the local
net, as well as the one assigned by AT&T. This is how I'd do it, if it
were my doing.
On Tue, 2 Jan 2001, Micah Yoder wrote:
> Mike Burger wrote:
> >
> > I'm assuming that you have your internal network numbered differently than
> > the external "internet" side of your Cable modem, yes?
>
> Internal network is 192.168.1.x. Server only has one IP, the one
> assigned by the ISP (AT&T @Home).
>
> > 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.
>
> Server is not bound to 192.x, but it does have a route that lets it
> reach 192.x through eth0. eth0 also is the default gateway to the
> Internet. here's what I have...
>
> on SERVER:
>
> eth0 Link encap:Ethernet HWaddr 00:10:4B:6B:3A:A1
> inet addr:65.4.56.167 Bcast:65.4.56.255 Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:9242 errors:0 dropped:0 overruns:0 frame:0
> TX packets:7981 errors:0 dropped:0 overruns:0 carrier:0
> collisions:265 txqueuelen:100
> Interrupt:9 Base
> address:0xec00
>
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use
> Iface
> c1306879-a.sale * 255.255.255.255 UH 0 0 0
> eth0
> 192.168.1.0 * 255.255.255.0 U 0 0 0
> eth0
> 65.4.56.0 * 255.255.255.0 U 0 0 0
> eth0
> 127.0.0.0 * 255.0.0.0 U 0 0 0
> lo
> default 65.4.56.1 0.0.0.0 UG 0 0 0
> eth0
>
> on CLIENT:
>
> eth0 Link encap:Ethernet HWaddr 00:50:DA:B7:DC:6B
> inet addr:192.168.1.5 Bcast:192.168.1.255 Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:3123 errors:0 dropped:0 overruns:0 frame:0
> TX packets:2275 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:100
> Interrupt:5 Base
> address:0x9800
>
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use
> Iface
> 192.168.1.5 * 255.255.255.255 UH 0 0 0
> eth0
> nova * 255.255.255.255 UH 0 0 0
> eth0
> 192.168.1.0 * 255.255.255.0 U 0 0 0
> eth0
> 127.0.0.0 * 255.0.0.0 U 0 0 0
> lo
> default nova 0.0.0.0 UG 0 0 0
> eth0
>
>
> > 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.
>
> No DHCP. Have a static address for now, but they promise we'll get DHCP
> "as soon as they get it working reliably." Wish they wouldn't bother.
>:-(
>
> > 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.
>
> I don't believe there's a difference in ifconfig output... after all
> there's only one IP for eth0 and it's always up. I've never noticed a
> difference anyway.
>
> Thanks!
>
>
>
> _______________________________________________
> Redhat-list mailing list
> [EMAIL PROTECTED]
> https://listman.redhat.com/mailman/listinfo/redhat-list
>
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
