|
OpenBSD Installation and Upgrading Installing and upgrading OpenBSD. |
|
Thread Tools | Display Modes |
|
|||
I can DHCP but after that...nada on the net
So I have a laptop with an re0 (Realtek 8101E). I plugged an ethernet cable in and ran dhclient. I got an address.
However, an attempt to ping the router results in all packets lost. in fact, I can't seem to go anywhere - ssh, etc. My dhcp'd address is 192.168.1.100 (as an example). netstat -rn -f inet shows 192.168.1.1 as the default gateway (that is the router and correct). The entry for 192.168.1.1 is link#1 aka re0. The entry: 192.168.1.1 (router MAC) is the one that increases in the Use column when I try to ping. I ran pfctl -d just to take pf out of the equation. re0 shows an lladdr of 00:00:00:00:00:00, which is unusual, and dmesg shows an "unknown ASIC". The dhcp'd address, netmask, broadcast, DNS, etc. are all correct. So I'm wondering if there is something I need to configure further to get networking working (this is my first attempt to set it up on this box and I'm a little rusty on OpenBSD networking). |
|
|||
Post the output of the ifconfig(8). Redact any public IP addresses displayed.
|
|
|||
Here is ifconfig -a:
Code:
lo0: flags=8149<UP,LOOPBACK,RUNNING,PROMISC,MULTICAST> mtu 33160 priority: 0 groups: lo inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 inet 127.0.0.1 netmask 0xff000000 re0: flags=28843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,NOINET6> mtu 1500 lladdr 00:00:00:00:00:00 priority: 0 groups: egress media: Ethernet autoselect (100baseTX full-duplex) status: active inet 192.168.1.100 netmask 0xffffff00 broadcast 192.168.1.255 iwn0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500 lladdr 78:92:9c:11:ab:f4 priority: 4 groups: wlan media: IEEE802.11 autoselect status: no network ieee80211: nwid "" enc0: flags=0<> priority: 0 groups: enc status: active pflog0: flags=141<UP,RUNNING,PROMISC> mtu 33160 priority: 0 groups: pflog Code:
Routing tables Internet: Destination Gateway Flags Refs Use Mtu Prio Iface default 192.168.1.1 UGS 0 0 - 8 re0 127/8 127.0.0.1 UGRS 0 0 33160 8 lo0 127.0.0.1 127.0.0.1 UH 0 0 33160 4 lo0 192.168.1/24 link#1 UC 1 0 - 4 re0 192.168.1.1 00:1c:10:3c:74:f7 UHLc 1 67 - 4 re0 192.168.1.100 127.0.0.1 UGHS 0 0 33160 8 lo0 224/4 127.0.0.1 URS 0 0 33160 8 lo0 |
|
|||
Quote:
http://www.daemonforums.org/showpost...83&postcount=9 |
|
|||
Actually, maybe I'm not sure what you mean by physical attachment layer - the chip in use (Realtek 8101E) is listed as supported on the re man page. Is there something more than this that's needed? Please forgive my ignorance.
|
|
||||
Thank you for the pointer!
Code:
re0 at pci1 dev 0 function 0 "Realtek 8101E" rev 0x05: unknown ASIC (0x4080), apic 4 int 16 (irq 11), address 00:00:00:00:00:00 ukphy0 at re0 phy 7: Generic IEEE 802.3u media interface, rev. 2: OUI 0x000732, model 0x0008 I found a short thread on the misc@ mailing list with a similar message, from 2007, which did not have any resolution noted: http://marc.info/?l=openbsd-misc&m=119866202617286&w=2 And a more recent comment regarding newer hardware and 4.9 -- again, without resolution: http://marc.info/?l=openbsd-misc&m=131408424000633&w=2 Please boot a RAMDISK kernel from a recent snapshot, as I advised, and see if -current supports your hardware. If so, you can move to -current and be fully supported. You might try setting your NIC's Ethernet MAC address to something other than all zeroes, perhaps that will circumvent the issue. This is done with ifconfig(8) and its lladdr option. |
|
||||
There are multiple chips in use. The "8101E" is Realtek's NIC controller chip. There is a second chip in the NIC, which communicates with the Ethernet network. In this case, it is an ASIC which OpenBSD 4.9 does not know about.
Because that NIC was able to communicate on the Ethernet for DHCP, it may be possible to assign a MAC address (also known as an Ethernet address) in order to permit point to point communication on your LAN. DHCP protocol is conducted via UDP broadcasts, not via specific device addresses. To test -current, as I've recommended:
|
|
|||
So here are the results of the tests you recommended (and thanks for that!):
So...looks like it's -current for me Thanks so much again for your help. |
|
||||
Quote:
If you've not read it, please review FAQ 5.1 as well on the flavors of OpenBSD and its development cycle, too, which will help you understand what you'll be running. Lastly, -current packages are made available from time to time on the major architectures, for our convenience. They are likely never going to be in exact sync with your particular -current system; most of the time if your current is within a few days or so of when those packages were built you can use them. But not always; especially when there are library bumps. Expect to have to build a port or two manually once in a while due to a package<>OS sync issue. |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
isc dhcp server | queshaw | OpenBSD Packages and Ports | 1 | 8th February 2011 11:09 AM |
W2K DHCP Issue | DrJ | Other OS | 4 | 25th May 2009 07:19 PM |
obtain 2 ips via dhcp | dextro | FreeBSD General | 2 | 6th February 2009 04:56 AM |
Obtaining multiple IPs from ISP via DHCP | dextro | General software and network | 15 | 9th January 2009 02:36 AM |
DHCP Server | WeakSauceIII | OpenBSD General | 1 | 25th September 2008 03:34 AM |