FYI: here is the output from ifconfig, arp -an, ipv4 routing tables while running the 5.1-RELEASE kernel. dc0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500 inet6 fe80::2c0:f0ff:fe48:7562%dc0 prefixlen 64 scopeid 0x1 inet 192.168.0.2 netmask 0xffffff00 broadcast 192.168.0.255 ether 00:c0:f0:48:75:62 media: Ethernet autoselect (100baseTX <full-duplex>) status: active ? (10.255.255.255) at ff:ff:ff:ff:ff:ff on vmnet1 permanent [ethernet] ? (192.168.0.0) at ff:ff:ff:ff:ff:ff on dc0 permanent [ethernet] ? (192.168.0.1) at 00:a0:c5:e6:58:00 on dc0 [ethernet] ? (192.168.0.253) at 00:06:25:54:2a:20 on dc0 [ethernet] ? (192.168.0.255) at ff:ff:ff:ff:ff:ff on dc0 permanent [ethernet] netstat -rn Routing tables Internet: Destination Gateway Flags Refs Use Netif Expire default 192.168.0.1 UGSc 8 0 dc0 10 link#4 UC 1 0 vmnet1 10.255.255.255 ff:ff:ff:ff:ff:ff UHLWb 2 58 vmnet1 127.0.0.1 127.0.0.1 UH 11 3250 lo0 192.168.0.0 ff:ff:ff:ff:ff:ff UHLWb 0 9 dc0 => 192.168.0 link#1 UC 4 0 dc0 192.168.0.1 00:a0:c5:e6:58:00 UHLW 9 8 dc0 332 192.168.0.2 127.0.0.1 UGHS 0 5 lo0 192.168.0.253 00:06:25:54:2a:20 UHLW 0 1 dc0 1057 192.168.0.255 ff:ff:ff:ff:ff:ff UHLWb 4 147 dc0 slave-mike wrote: > Follows is my arp table entries and interface while running a -current > kernel. > > My system can see the default gateway etc, and appears to be > transmitting packets (based on activity of hub lights), but does not > seem to be receiving them back or knowing they are received back beyond > the arp/rarp packets or it just plain eats them. :) > > 192.168.0.1 is my default gw > > I have tried both fxp0 and dc0. > I have tried both with and without vmnet being loaded. > > ? (10.255.255.255) at ff:ff:ff:ff:ff:ff on vmnet1 permanent [ethernet] > ? (192.168.0.0) at ff:ff:ff:ff:ff:ff on dc0 permanent [ethernet] > ? (192.168.0.1) at 00:a0:c5:e6:58:00 on dc0 [ethernet] > ? (192.168.0.253) at 00:06:25:54:2a:20 on dc0 [ethernet] > ? (192.168.0.255) at ff:ff:ff:ff:ff:ff on dc0 permanent [ethernet] > > dc0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500 > inet6 fe80::2c0:f0ff:fe48:7562%dc0 prefixlen 64 scopeid 0x1 > inet 192.168.0.2 netmask 0xffffff00 broadcast 192.168.0.255 > ether 00:c0:f0:48:75:62 > media: Ethernet autoselect (100baseTX <full-duplex>) > status: active > > > mjoyner wrote: > >> It works fine with a 5.1 kernel. >> >> Doug White wrote: >> >>> On Fri, 17 Oct 2003, mjoyner wrote: >>> >>> >>>> When I use a current kernel, my system will obtain an ip address via >>>> dhclient, but thereafter, it cannot see the network. >>>> >>>> I have tried switching ethernet cards. (used both a dc0 and an fxp0) >>>> Am currently using a 5.1-RELEASE kernel to have network access. >>>> >>>> Advice? >>> >>> >>> >>> >>> Perhaps your DHCP server is handing out bogus info? >>> >> >> _______________________________________________ >> freebsd-current_at_freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to >> "freebsd-current-unsubscribe_at_freebsd.org" > > > ------------------------------------------------------------------------ > > ? (10.255.255.255) at ff:ff:ff:ff:ff:ff on vmnet1 permanent [ethernet] > ? (192.168.0.0) at ff:ff:ff:ff:ff:ff on dc0 permanent [ethernet] > ? (192.168.0.1) at 00:a0:c5:e6:58:00 on dc0 [ethernet] > ? (192.168.0.253) at 00:06:25:54:2a:20 on dc0 [ethernet] > ? (192.168.0.255) at ff:ff:ff:ff:ff:ff on dc0 permanent [ethernet] > > dc0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500 > inet6 fe80::2c0:f0ff:fe48:7562%dc0 prefixlen 64 scopeid 0x1 > inet 192.168.0.2 netmask 0xffffff00 broadcast 192.168.0.255 > ether 00:c0:f0:48:75:62 > media: Ethernet autoselect (100baseTX <full-duplex>) > status: active >Received on Sat Oct 18 2003 - 20:40:39 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:25 UTC