MediaOne and Linux (yet again)

Derek Atkins warlord at mit.edu
Wed Aug 12 11:52:36 EDT 1998


This output seems to imply that the card is up and running fine.  It
is certainly configured, and it is transmitting AND receiving
packets....  So, what is failing, now?  From your linux box you should
be able to ping other machines on 192.168.1.0, assuming they are setup
properly.

-derek

"Peter R. Breton" <prbreton at fandago.read.tasc.com> writes:

> 
> > Peter, you need to show us the output from "ifconfig" and "netstat -rn".
> > I would want to see the 2 lines in your boot rc files that show how
> > eth1 was handled.
> > 
> > I have usually been able to diagnose the net setup from that.
> > 
> > Have you taken the stuff out of the rc for eth0?  You could probably
> > hack that to fix up eth1.
> 
> 
> Here they is:
> 
> 1. The kernel detecting the cards:
> 
> 3c59x.c:v0.99E 5/12/98 Donald Becker
> http://cesdis.gsfc.nasa.gov/linux/drivers/vortex.html
> loading device 'eth0'...
> eth0: 3Com 3c905B Cyclone 100baseTx at 0xb800, 00:10:4b:98:e5:5a, IRQ 10
>   8K byte-wide RAM 5:3 Rx:Tx split, autoselect/NWay Autonegotiation
> interface.
>   Enabling bus-master transmits and whole-frame receives.
> loading device 'eth1'...
> eth1: 3Com 3c905B Cyclone 100baseTx at 0xb400, 00:10:4b:cd:0a:c7, IRQ 11
>   8K byte-wide RAM 5:3 Rx:Tx split, autoselect/NWay Autonegotiation
> interface.
>   Enabling bus-master transmits and whole-frame receives.
> 
> 2. Output of ifconfig
> 
> [root at pbreton network-scripts]# ifconfig
> lo        Link encap:Local Loopback  
>           inet addr:127.0.0.1  Bcast:127.255.255.255  Mask:255.0.0.0
>           EtherTalk Phase 2 addr:0/0
>           UP BROADCAST LOOPBACK RUNNING  MTU:3584  Metric:1
>           RX packets:87 errors:0 dropped:0 overruns:0
>           TX packets:87 errors:0 dropped:0 overruns:0
> 
> eth0      Link encap:Ethernet  HWaddr 00:10:4B:98:E5:5A
>           inet addr:24.128.89.183  Bcast:24.128.89.255 
> Mask:255.255.254.0
>           UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:2301 errors:0 dropped:0 overruns:0
>           TX packets:20 errors:0 dropped:0 overruns:0
>           Interrupt:10 Base address:0xb800 
> 
> eth1      Link encap:Ethernet  HWaddr 00:10:4B:CD:0A:C7
>           inet addr:192.168.1.1  Bcast:192.168.1.255  Mask:255.255.255.0
>           EtherTalk Phase 2 addr:65280/144
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:158 errors:0 dropped:0 overruns:0
>           TX packets:124 errors:0 dropped:0 overruns:0
>           Interrupt:11 Base address:0xb400 
> 
> 3. Routing tables
> 
> [root at pbreton network-scripts]# netstat -nr
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags   MSS Window  irtt
> Iface
> 192.168.1.3     0.0.0.0         255.255.255.255 UH     1500 0          0
> eth1
> 192.168.1.0     0.0.0.0         255.255.255.0   U      1500 0          0
> eth1
> 24.128.88.0     0.0.0.0         255.255.254.0   U      1500 0          0
> eth0
> 127.0.0.0       0.0.0.0         255.0.0.0       U      3584 0          0
> lo
> 0.0.0.0         24.128.88.1     0.0.0.0         G      1500 0          0
> eth0
> 
> 4. /etc/sysconfig/network-scripts files:
> 
> emacs at pbreton(4) [10:13:12]% cat ifcfg-eth0
> DEVICE=eth0
> IPADDR=
> NETMASK=
> ONBOOT=yes
> BOOTPROTO=dhcp
> USERCTL=no
> 
> emacs at pbreton(5) [10:13:17]% cat ifcfg-eth1
> DEVICE=eth1
> USERCTL=no
> ONBOOT=yes
> BOOTPROTO=none
> NETWORK=192.168.1.0
> BROADCAST=192.168.1.255
> NETMASK=255.255.255.0
> IPADDR=192.168.1.1
> 
> Any clues welcomed... right now I'm mystified, and am back to thinking
> that it may be the card after all.
> 
> 				Peter

-- 
       Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
       Member, MIT Student Information Processing Board  (SIPB)
       URL: http://web.mit.edu/warlord/    PP-ASEL-IA     N1NWH
       warlord at MIT.EDU                        PGP key available
***
Subcription/unsubscription/info requests: send e-mail with subject of
"subscribe", "unsubscribe", or "info" to discuss-request at blu.org



More information about the Discuss mailing list