Date: 12 May 2000 21:43:05 -0700 From: Harry Putnam <reader@newsguy.com> To: freebsd-questions@FreeBSD.ORG Subject: Initial network setup debug Message-ID: <m2ya5f2h7q.fsf@reader.ptw.com>
next in thread | raw e-mail | index | archive | help
Setup: New user of Release-4.0 NICs installed: PCI NE2000 clone 'RealTek RTL-8029 PCI Netgear Netgear FA 310TX PCI Preface to comments below: When first installing, at the screen provided to resolve any hardware conflicts. There were 8 conflicts. Every entry under the network menu was in conflict. I disabled them all. I did boot up once leaving the conflits in place and saw no difference. Have I effectively disabled networking? The 0S seems to find my cards here, but complains later about corrupt memory in one device (see note further down) From boot messages: May 12 00:34:04 reader /kernel: ed0: <NE2000 PCI Ethernet (RealTek 8029)> port 0xdc00-0xdc1f irq 9 at device 9.0 on pci0 May 12 00:34:04 reader /kernel: ed0: supplying EUI64: 00:00:e8:ff:fe:90:99:20 May 12 00:34:04 reader /kernel: ed0: address 00:00:e8:90:99:20, type NE2000 (16 bit) May 12 00:34:04 reader /kernel: dc0: <82c169 PNIC 10/100BaseTX> port 0xe000-0xe0ff mem 0xeb000000-0xeb0000ff irq 9 at device 10.0 on pci0 May 12 00:34:04 reader /kernel: dc0: Ethernet address: 00:a0:cc:59:6b:fc NOTE: dc0 up and ed0 shutdown Results of `netstat -nr' Routing tables Internet: Destination Gateway Flags Netif Expire default 209.144.117.114 UGSc dc0 127.0.0.1 127.0.0.1 UH lo0 209.144.117 link#2 UC dc0 => 209.144.117.113 0:a0:cc:59:6b:fc UHLW lo0 209.144.117.114 link#2 UHRLW dc0 => results of ifconfig dc0: dc0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 inet 209.144.117.113 netmask 0xffffff00 broadcast 209.144.117.255 inet6 fe80::2a0:ccff:fe59:6bfc%dc0 prefixlen 64 scopeid 0x2 ether 00:a0:cc:59:6b:fc media: autoselect (100baseTX) status: active supported media: autoselect 100baseTX <full-duplex> 100baseTX 10baseT/UTP <full-duplex> 10baseT/UTP none The above setup can ping the NIC card address 209.144.117.113 But not the gateway at my ISP .......114 Next I shut down dc0 and fired up ed0. NOTE: dc0 shut down ..ed0 up System logger gives these messages: May 12 18:20:42 reader /kernel: dc0: starting DAD for fe80:0002::02a0:ccff:fe59:6bfc May 12 18:20:43 reader /kernel: dc0: DAD complete for fe80:0002::02a0:ccff:fe59:6bfc - no duplicates found [HP ***NOTE*** below:] May 12 18:23:55 reader /kernel: ed0: NIC memory corrupt - invalid packet length 0 May 12 19:03:07 reader /kernel: ed0: starting DAD for fe80:0001::0200:e8ff:fe90:9920 May 12 19:03:09 reader /kernel: ed0: DAD complete for fe80:0001::0200:e8ff:fe90:9920 - no duplicates found Results of `netstat -nr': Routing tables Internet: Destination Gateway Flags Netif Expire default 209.144.117.114 UGSc dc0 127.0.0.1 127.0.0.1 UH lo0 I then set up a connection on ed0 ifconfig ed0 inet 209.144.117.113 netmask 255.255.255.0 Gateway is already setup. results of netstat -nr with new interface setup: Routing tables Internet: Destination Gateway Flags Netif Expire default 209.144.117.114 UGSc dc0 127.0.0.1 127.0.0.1 UH lo0 209.144.117 link#1 UC ed0 => 209.144.117.113 0:0:e8:90:99:20 UHLW lo0 209.144.117.114 0:e0:da:3:dd:0 UHLW ed0 1107 With dc0 down and this new interface on ed0, I can ping the nic and the gateway on the other end. But still not connected to the internet. Can't ping my nameserver. Resolv.conf looks like: domain ptw.com nameserver 209.144.112.4 Contents /etc/hosts 127.0.0.1 localhost.ptw.com localhost 209.144.117.113 reader.ptw.com. 192.168.x.x reader.local.lan reader 192.168.x.x satellite.local.lan satellite Where to from here? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?m2ya5f2h7q.fsf>