|
OpenBSD Installation and Upgrading Installing and upgrading OpenBSD. |
|
Thread Tools | Display Modes |
|
|||
On OpenBSD, drivers are named after the vendor & chipset they support, rl(4) is for the cards based on the Realtek 8129/8130 chipset.
If your dmesg only shows a single rl0 device, then another driver is being used for the additional card. You can look through the dmesg, or with ifconfig(8) to find what cards are in your system. In your example, you state rl0 but create a file named hostname.rl1, perhaps that was a typo? |
|
|||
Welcome to our forums! I have separated your message from the original thread responded to, as we discourage hijacking.
Most members of these forums search through old threads for research. Keeping threads to a single subject makes this exercise significantly easier. Quote:
Quote:
|
|
||||
First off, welcome to daemonforums.org...
Second, Google is certainly a trusted source when it comes to Linux. The man pages on Linux tend to leave a lot to be desired...not so with OpenBSD (most BSD projects, for that matter, have superior man pages than Linux). You can "man -k <some_topic>" to get a list of man pages that discuss whatever topic you're looking for. That should be your first stop before consulting Google =) As for the second NIC, is it actually being recognized? You mention a single line from dmesg, but since you already have a NIC in the machine, is there a second dmesg line that matches the SMC 1244TX? If not (or it says "not configured" after it), your card doesn't have a driver and won't work until a driver is written for it. If it *IS* being recognized, what does ifconfig have pertaining to that card? And you're correct, hostname.* files are only used if the hardware is actually there.
__________________
Linux/Network-Security Engineer by Profession. OpenBSD user by choice. |
|
||||
thanks folks, progress report:
Quote:
I kept plugging away after I left this post. Here's where I got: I piped dmesg to a file and really looked through it. I had been just using |more to page through. I found that yes, the card was being recognized! Code:
dc0 at pci1 dev 11 function 0 "ADMtek AN983" rev 0x11: apic 2 int 23 (irq 9), address 00:50:bf:9f:0a:80 dc0: MII without any PHY! rl0 at pci1 dev 13 function 0 "Realtek 8139" rev 0x10: apic 2 int 17 (irq 10), address 00:0c:6e:0f:ab:51 rlphy0 at rl0 phy 0: RTL internal PHY my system hung. It hung badly enough that I had to cycle power. I had to boot from the install cd and mount the hard disc filesystem and then rename hostname.dc0 before it would boot. It would boot, but would hang as soon as the "starting network" came up. I just now tried again after I found the man pages for rl and for dc and made some changes. Any ideas GREATLY appreciated. TP in CO |
|
|||
I assume both interfaces were connected to the same subnet. Is this correct?
Likewise, the testing described has two cases:
|
|
|||
Quote:
|
|
||||
Quote:
Quote:
If that allows the dc device to work, I will have learned something--but it might be that I have learned that I need to find another pci card NIC to use as the 2nd one. |
|
||||
MII without any PHY!
Agree, MII without any PHY! seems like a pretty important factoid. I did some searching around, finding no obvious clues. I was hoping someone here might have an aha. But I ran out of time to do much more than post my message before my work week ended.
I may try to round up a different PCI NIC (though I did a fairly exhaustive search of the PC junk pile at my workplace--buying one seems crazy! but I'd really like to learn about what is going on. Thanks as always for the attention and help. When a solution is found I will post all details. |
|
||||
Monday morning tactics
Hey there. This morning first thing I went into CMOS setup and disabled the onboad NIC. Then I put in my SMT 1244TX PCI card (dc0) and started openBSD. The dc0 device appeared to be recognized properly; no 'MII without any PHY!' message, but at the very end of dmesg was 'watchdog timeout'. No connectivity either. After a little searching around I found one tip that moving the card to a different slot might help that problem.
I thought that sounded a little crazy, and I only saw one reference to that, but it seemed like an easy thing to try. Putting that card in a different slot did change things. Once again I got the 'MII without any PHY!' message, but no 'watchdog timeout'. Also no connectivity. I found another nic in another old PC in our boneyard. It's a DLink. That card hasn't got an effective modular connector retainer (when you plug in the 10-baseT connector it won't go 'click' and the cable can just be pulled out/fall out). This makes me less enthusiastic about using it as part of our enterprise firewall, but... It works. I tried it with the onboard nic still disabled and it came up fine and I have connectivity with it. So then I re-enabled the onboard nic. Once I did that the onboard nic had connectivity but not the DLink. I'm wondering if that could be simply because I have some of the other net config stuff wrong. Or whether it is because those two devices are conflicting with each other. New info... any ideas from you knowledgable folks out there would be appreciated as always! Tom in CO, USA |
|
||||
Quote:
sh /etc/netstart No change. I can ping rl0 (192.168.0.254) but cannot ping rl1 (192.168.1.249). For reference, here's the excerpt from my dmesg output pertaining to the two nics: Code:
... pci1 at ppb0 bus 1 rl0 at pci1 dev 11 function 0 "D-Link 530TX+" rev 0x10: apic 2 int 23 (irq 9), address 00:05:5d:4e:71:e3 rlphy0 at rl0 phy 0: RTL internal PHY rl1 at pci1 dev 13 function 0 "Realtek 8139" rev 0x10: apic 2 int 17 (irq 10), address 00:0c:6e:0f:ab:51 rlphy1 at rl1 phy 0: RTL internal PHY ... Code:
inet 192.168.0.254 255.255.255.0 NONE Code:
inet 192.168.1.249 255.255.255.0 NONE At this point I have pretty much written off the SMC 1244TX card even though it came new out of a box. Seems like it might just have basic problems with OpenBSD... TIA as always. Tom in CO |
|
||||
The output of $ ifconfig may be of assistance; it should show physical connectivity, or the lack thereof.
And where are you pinging these addresses from? The OpenBSD platform, or externally? If the latter, routing may be an issue. |
|
|||
Quote:
Quote:
Quote:
|
|
||||
Check your route tables ("netstat -nrf inet" or similar). If you have a blanket statement like:
192.168/16 link#2 <etc...> rl1 That could cause ALL 192.168 traffic to route through link#2. I've had this happen before, and it causes one NIC to appear to go "brain dead". If you can't put them on seperate IP blocks (i.e. put one on 10/8, and the other on 192.168/16 or 172.16/12), you'll have to hammer out your routing tables (something I've never messed with since I could always switch to an unused private block).
__________________
Linux/Network-Security Engineer by Profession. OpenBSD user by choice. |
|
||||
Nics are now working!
Quote:
So now I know that both Nics are working. Big milestone! I was hoping that I would be able to use the box to bridge to my internet gateway (our dsl modem/router), meaning that I could actually access the 'net through my OpenBSD box, serving as a bridge to the internet gateway, but it isn't working that way. The router/gateway address is 192.168.0.1. I am assuming that getting this to work will imply having the right configuration info in mygate, myname, and hosts, correct? Here are the contents of those files now: Code:
$ cat /etc/mygate 192.168.0.1 $ cat /etc/myname tincup.rmt0.com $ cat /etc/hosts # $OpenBSD: hosts,v 1.12 2009/03/10 00:42:13 deraadt Exp $ # # Host Database # # RFC 1918 specifies that these networks are "internal". # 10.0.0.0 10.255.255.255 # 172.16.0.0 172.31.255.255 # 192.168.0.0 192.168.255.255 # 127.0.0.1 localhost ::1 localhost 192.168.0.254 tincup.rmt0.com tincup 192.168.1.249 tincup0.rmt0.com tincup0 Thanks a million for the help so far folks. I'm making progress. My ultimate goal is to get pf (Packet Filter) running, which will pass all the traffic from our internal network to the DSL Modem/Router, filtering by port of course. I assume that the configuration will need to be working to make the machine a simple bridge first though. If you have a page that describes getting a pf-based firewall going once the nics are running properly, feel free to send me to that and I will get down to reading and experimenting. Or send me to a place where I can get data about basic net config. I've been reading man pages about myname, mygate, and hosts. Pretty clear, but as I follow them I don't seem to be getting the higher level stuff working. Thanks again! Good Monday so far! |
|
|||
Quote:
http://www.openbsd.org/faq/pf/index.html The PF User's Guide should be considered definitive. Likewise, the following may help as well: http://home.nuug.no/~peter/pf/ |
|
||||
Thanks
Quote:
I think this probably should be considered the conclusion of a thread in OpenBSD Installation and Upgrading called configuring second NIC. A few questions are left unanswered, most notably, what was wrong with the SMC 1244 TX pci NIC that I started with? It was not listed in the supported hardware for OpenBSD 4.9, which is a strong clue. It is recognized by the dc driver, but the 'MII without any PHY!' message suggests that there is some aspect of it that the driver doesn't like. R.I.P. SMC 1244 TX, you go back onto the shelf. Perhaps you will become useful at some other time. For now you are to be exiled to the island of misfit toys, the hardware boneyard. The DLink card will be doing the job. The cable will be duct-taped in place to keep it from falling out since the retention clip doesn't work. Any questions that arise I will be willing to address to the extent of my ability. Email is tpurvis at arkansasvalley dot net |
|
||||
Glad you got things working, Tom. And, I'm glad that you were able to identify the problem with connectivity was routing.
Speaking of routing.... For routing packets, which most firewalls do, don't forget to enable IP forwarding, as described in FAQ 6.2.7. Your OpenBSD platform won't be a router without it. |
|
||||
Thanks for the advice of IP Forwarding
Quote:
So I kept reading and saw about putting aliases in the hostname.rlX file(s), so I've been experimenting with that. Not sure I understand it though--actually pretty sure I don't understand it. And not allowing me to get to the internet gateway while identifying the OpenBSD box as the PC's default gateway. More reading... |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
It's necesary to use firmware configuring rum or zyd? | ximo | FreeBSD General | 7 | 8th July 2009 10:05 AM |
Configuring authpf freebsd | kasse | FreeBSD General | 0 | 7th February 2009 12:32 PM |
Help configuring pine | cssgalactic | FreeBSD General | 4 | 29th June 2008 11:50 PM |
Need Help Configuring Postfix | iainnitro | General software and network | 6 | 8th June 2008 04:55 AM |
Configuring VLANs under FreeBSD | Popof | FreeBSD General | 5 | 13th May 2008 04:08 PM |