Re: [TCLUG:8792] Multiple Ethernet Woes

["Brian Ackermann" <brianj@subrad.com>]

On a beginning note....that command did not report an error...yet, pings to
that subnet remain unsuccessful...

-------------

[root@firewall /root]# ifconfig

eth0      Link encap:Ethernet  HWaddr 00:10:5A:97:E5:1A
          inet addr:205.218.57.25  Bcast:205.218.57.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:182717 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3323 errors:0 dropped:0 overruns:0 carrier:0
          collisions:1

eth1      Link encap:Ethernet  HWaddr 00:50:04:12:15:47
          inet addr:192.168.6.48  Bcast:192.168.6.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:180 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:3924  Metric:1
          RX packets:353 errors:0 dropped:0 overruns:0 frame:0
          TX packets:353 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0


[root@firewall /root]#

----------

Brian


----------
>From: Nate Carlson <natecars@infiniteloop.com>
>To: tclug-list@mn-linux.org
>Subject: Re: [TCLUG:8792] Multiple Ethernet Woes
>Date: Fri, Oct 1, 1999, 1:45 PM
>

> OK, it's supposed to automatically figure this stuff out.. but try:
>
> route add -net 192.168.6.0 netmask 255.255.255.0 gw 192.168.6.1 eth1
>
> that REALLY should work.  :)
>
> You know, that makes me suspicious..... dump ifconfig eth0 and ifconfig
> eth1 to the list.