• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

OpenBSD post-install question

kag

Golden Member
I installed OpenBSD from an HTTP site and everything worked fine.

But now that I rebooted, the OpenBSD machine can't ping anything except its address... not the gateway or other computers in the network. And other machines on the network can't ping it either.

When I look at my /etc/hostname.xl0 well everything looks fine. The weird thing is that it downloaded all the packages perfectly and now it doesn't work. Am I missing something that I'm supposed to turn on???

Thanks
 
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33224
..........inet 127.0.0.1 netmask 0xff000000
..........inet6 ::1 prefixlen 128
..........inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4
xl0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
..........address: 00:10:5a:10:96:28
..........media: Ethernet 100baseTX full-duplex
..........status: no carrier
..........inet 192.168.1.3 netmask 0xffffff00 broadcast 192.168.1.255
..........inet6 fe80::210:5aff:fe10:9628%xl0 prefixlen 64 scopeid 0x1
pflog0: flags=0<> mtu 33224
pfsync0: flags=0<> mtu 2020
enc0: flags=0<> mtu 1536


Mmm "status: no carrier"


EDIT: forget it. I read it up on Google and while the router showed that the port was in use, I had to play with the network cable and got it working.
 
Originally posted by: kag
xl0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
..........address: 00:10:5a:10:96:28
..........media: Ethernet 100baseTX full-duplex
..........status: no carrier
..........inet 192.168.1.3 netmask 0xffffff00 broadcast 192.168.1.255
..........inet6 fe80::210:5aff:fe10:9628%xl0 prefixlen 64 scopeid 0x1
pflog0: flags=0<> mtu 33224
pfsync0: flags=0<> mtu 2020
enc0: flags=0<> mtu 1536

I think I got it right.

no carrier? weird. This is probably a stupid question, but is your network cable properly plugged in?

Some googling of "status: no carrier" (with quotes) produced this:
http://www.mail-archive.com/freebsd-net@freebsd.org/msg02023.html

There are a lot more results... maybe read through more of them if that one doesn't solve it.
 
Originally posted by: CTho9305
no carrier? weird. This is probably a stupid question, but is your network cable properly plugged in?
I edited my post while you were typing yours 🙂
Thanks though
 
My NIC might be dying. In one of the results by a Google search, the guy said that "status: no carrier" was a sign that his NIC was about to die.

I rebooted and I couldn't connect to the machine with PuTTY... and I could connect via HTTP but it took like 30 seconds to load a simple page.

I played with the cable again and it worked back. But this NIC has always given me problems (slowing down the connection of certain other computers on the network... like it was copying another computer's MAC address or something). I had to put it in my OpenBSD computer because the original NIC wasn't detected.
 
3com cards are generally crap. There is a note somewhere on the OpenBSD site (FAQ about choosing hardware I think) that 3com cards are overpriced junk. Intel cards are the best 10/100, if you can find them for reasonable prices. And there have been a couple of emails on the mailing lists about dc (tulip, generally linksys) problems, and I'm actually wondering if that was my problem and not a bad linksys card...

Anyways, I'd look at getting a better card. Intel cards are like $30 generally. Linksys cards usually work, but I'm liking them less and less lately. Realtek works, but really, it's crap. RhineII chipsets work (I use one), but again, it's crap. I only use it on a "slow" link.
 
3Com's might not be the best in terms of stability under high load, but they seem damn near indestructible, I don't think I've ever seen one go.
Well, actually I have, but that one was due to another component getting FUBAR'ed and taking the 3Com with it.
 
Back
Top