I recently got a new disk and had a couple hundred GBs free and decided to give FreeBSD a try. After a couple of false starts trying to get it to boot from Grub, I finally got to a command line expecting to start the rest of the install from the net. Unfortunately it didn't appear to have any external connection.
I have an Atheros Killer E220x Gigabit ethernet interface and from the documentation it is supposed to be supported with the 'alc' driver.
which looks good to me.
works fine but
got no replies from the router.
which looks OK to me. There aren't any errors on either input or output and repeated tries give a slowly increasing number of Ipkts like I normally see on the network. If I issue a 'ping' command and look again, the Opkts count goes up by a reasonable number.
'dmesg' shows no errors.
If this were new hardware I would suspect maybe a network cable or router port failure but booting the system to either Linux or Windows the network connection is perfect.
Has anyone seen anything like this or have suggestions on what to try next?
I have an Atheros Killer E220x Gigabit ethernet interface and from the documentation it is supposed to be supported with the 'alc' driver.
ifconfig
gives:
Code:
alc0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=c319a<TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_MCAST,WOL_MAGIC,VLAN_HWTSO,LINKSTATE>
ether 74:d4:35:e7:6c:a3
inet 192.168.2.110 netmask 0xffffff00 broadcast 192.168.2.255
nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
ping 192.168.2.110
works fine but
ping 192.168.2.1
got no replies from the router.
netstat -i
gives:
Code:
Name Mtu Network Address Ipkts Ierrs Idrop Opkts Oerrs Coll
alc0 1500 <Link#1> 74:d4:35:e7:6c:a3 73 0 0 4 0 0
alc0 - 192.168.2.0/2 192.168.2.110 0 - - 3 - -
lo0 16384 <Link#2> lo0 456 0 0 456 0 0
lo0 - localhost localhost 228 - - 228 - -
lo0 - fe80::%lo0/64 fe80::1%lo0 0 - - 0 - -
lo0 - your-net localhost 228 - - 228 - -
#
'dmesg' shows no errors.
If this were new hardware I would suspect maybe a network cable or router port failure but booting the system to either Linux or Windows the network connection is perfect.
Has anyone seen anything like this or have suggestions on what to try next?