Re: network interface not recognized on Intel S3420GPLC board
b0 at ehci0: USB revision 2.0 uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1 ppb1 at pci0 dev 28 function 0 vendor "Intel", unknown product 0x3b42 rev 0x05: apic 8 int 16 (irq 10) pci2 at ppb1 bus 2 ppb2 at pci0 dev 28 function 4 vendor "Intel", unknown product 0x3b4a rev 0x05 pci3 at ppb2 bus 3 em1 at pci3 dev 0 function 0 "Intel PRO/1000 MT (82574L)" rev 0x00: apic 8 int 16 (irq 10), address 00:15:17:ad:e4:20 ppb3 at pci0 dev 28 function 6 vendor "Intel", unknown product 0x3b4e rev 0x05 pci4 at ppb3 bus 4 vga1 at pci4 dev 0 function 0 "Matrox MGA G200e (ServerEngines)" rev 0x02 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) ppb4 at pci0 dev 28 function 7 vendor "Intel", unknown product 0x3b50 rev 0x05 pci5 at ppb4 bus 5 ehci1 at pci0 dev 29 function 0 vendor "Intel", unknown product 0x3b34 rev 0x05: apic 8 int 23 (irq 9) usb1 at ehci1: USB revision 2.0 uhub1 at usb1 "Intel EHCI root hub" rev 2.00/1.00 addr 1 ppb5 at pci0 dev 30 function 0 "Intel 82801BA Hub-to-PCI" rev 0xa5 pci6 at ppb5 bus 6 pcib0 at pci0 dev 31 function 0 vendor "Intel", unknown product 0x3b14 rev 0x05 pciide0 at pci0 dev 31 function 2 vendor "Intel", unknown product 0x3b20 rev 0x05: DMA (unsupported), channel 0 configured to native-PCI, channel 1 configured to native-PCI pciide0: using apic 8 int 18 (irq 11) for native-PCI interrupt wd0 at pciide0 channel 0 drive 0: wd0: 16-sector PIO, LBA48, 305245MB, 625142448 sectors pciide0: channel 1 ignored (not responding; disabled or no drives?) vendor "Intel", unknown product 0x3b30 (class serial bus subclass SMBus, rev 0x05) at pci0 dev 31 function 3 not configured pciide1 at pci0 dev 31 function 5 vendor "Intel", unknown product 0x3b26 rev 0x05: DMA (unsupported), channel 0 wired to native-PCI, channel 1 wired to native-PCI pciide1: using apic 8 int 22 (irq 5) for native-PCI interrupt pciide1: channel 0 ignored (not responding; disabled or no drives?) pciide1: channel 1 ignored (not responding; disabled or no drives?) isa0 at pcib0 isadma0 at isa0 com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo pckbc0 at isa0 port 0x60/5 kbc: cmd word write error pcppi0 at isa0 port 0x61 midi0 at pcppi0: spkr0 at pcppi0 npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16 mtrr: Pentium Pro MTRR support uhub2 at uhub0 port 1 "vendor 0x8087 product 0x0020" rev 2.00/0.00 addr 2 uhub3 at uhub1 port 1 "vendor 0x8087 product 0x0020" rev 2.00/0.00 addr 2 uhidev0 at uhub3 port 2 configuration 1 interface 0 "American Megatrends Inc. Virtual Keyboard and Mouse" rev 1.10/1.00 addr 3 uhidev0: iclass 3/1 ukbd0 at uhidev0: 8 modifier keys, 6 key codes wskbd0 at ukbd0 mux 1 wskbd0: connecting to wsdisplay0 uhidev1 at uhub3 port 2 configuration 1 interface 1 "American Megatrends Inc. Virtual Keyboard and Mouse" rev 1.10/1.00 addr 3 uhidev1: iclass 3/1 ums0 at uhidev1 ums0: X report 0x0002 not supported uhidev2 at uhub3 port 6 configuration 1 interface 0 "CHESEN PS2 to USB Converter" rev 1.10/0.10 addr 4 uhidev2: iclass 3/1 ukbd1 at uhidev2: 8 modifier keys, 6 key codes wskbd1 at ukbd1 mux 1 wskbd1: connecting to wsdisplay0 uhidev3 at uhub3 port 6 configuration 1 interface 1 "CHESEN PS2 to USB Converter" rev 1.10/0.10 addr 4 uhidev3: iclass 3/1, 3 report ids ums1 at uhidev3 reportid 1: 5 buttons, Z dir wsmouse0 at ums1 mux 0 uhid0 at uhidev3 reportid 2: input=1, output=0, feature=0 uhid1 at uhidev3 reportid 3: input=3, output=0, feature=0 softraid0 at root root on wd0a swap on wd0b dump on wd0b cpu1: unknown i686 model 0x1e, can't get bus clock (0x0) cpu2: unknown i686 model 0x1e, can't get bus clock (0x0) cpu3: unknown i686 model 0x1e, can't get bus clock (0x0) Thanks, Ross On 03/02/2010 03:07 PM, Tomas Bodzar wrote: > pcidump -v and complete dmesg will be more useful for developers > > On Tue, Mar 2, 2010 at 8:07 PM, Ross Davis wrote: >> Ah, I didn't know about that command, here it is: >> >> # pcidump >> Domain /dev/pci0: >> 0:0:0: Intel unknown >> 0:5:0: Intel unknown >> 0:8:0: Intel unknown >> 0:8:1: Intel unknown >> 0:8:2: Intel unknown >> 0:8:3: Intel unknown >> 0:16:0: Intel unknown >> 0:16:1: Intel unknown >> 0:25:0: Intel unknown >> 0:26:0: Intel unknown >> 0:28:0: Intel unknown >> 0:28:4: Intel unknown >> 0:28:6: Intel unknown >> 0:28:7: Intel unknown >> 0:29:0: Intel unknown >> 0:30:0: Intel 82801BA Hub-to-PCI >> 0:31:0: Intel unknown >> 0:31:2: Intel unknown >> 0:31:3: Intel unknown >> 0:31:5: Intel unknown >> 1:0:0: Intel PRO/1000 MT (82574L) >> 3:0:0: Inte
Re: network interface not recognized on Intel S3420GPLC board
Ah, I didn't know about that command, here it is: # pcidump Domain /dev/pci0: 0:0:0: Intel unknown 0:5:0: Intel unknown 0:8:0: Intel unknown 0:8:1: Intel unknown 0:8:2: Intel unknown 0:8:3: Intel unknown 0:16:0: Intel unknown 0:16:1: Intel unknown 0:25:0: Intel unknown 0:26:0: Intel unknown 0:28:0: Intel unknown 0:28:4: Intel unknown 0:28:6: Intel unknown 0:28:7: Intel unknown 0:29:0: Intel unknown 0:30:0: Intel 82801BA Hub-to-PCI 0:31:0: Intel unknown 0:31:2: Intel unknown 0:31:3: Intel unknown 0:31:5: Intel unknown 1:0:0: Intel PRO/1000 MT (82574L) 3:0:0: Intel PRO/1000 MT (82574L) 4:0:0: Matrox MGA G200e (ServerEngines) On 03/02/2010 02:01 PM, Gleydson Soares wrote: > can you show the out of the command pcidump ! > > On Tue, Mar 2, 2010 at 3:53 PM, Ross Davis wrote: >> I installed OpenBSD 4.6 on an Intel SR1630HGP server that has an Intel >> S3420GPLC board. There are three network interfaces on the server: one >> card, and two on the motherboard. >> >> The card is recognized: >> >> em0 at pci1 dev 0 function 0 "Intel PRO/1000 MT (82574L)" rev 0x00: apic >> 8 int 16 >> (irq 11), address 00:1b:21:49:8d:8c >> >> As is one of the interfaces on the board: >> >> em1 at pci3 dev 0 function 0 "Intel PRO/1000 MT (82574L)" rev 0x00: apic >> 8 int 16 >> (irq 10), address 00:15:17:ad:e4:20 >> >> Looking at dmesg, the devices flanking pci3 are: >> >> ppb1 at pci0 dev 28 function 0 vendor "Intel", unknown product 0x3b42 >> rev 0x05: a >> pic 8 int 16 (irq 10) >> pci2 at ppb1 bus 2 >> ppb2 at pci0 dev 28 function 4 vendor "Intel", unknown product 0x3b4a >> rev 0x05 >> pci3 at ppb2 bus 3 >> em1 at pci3 dev 0 function 0 "Intel PRO/1000 MT (82574L)" rev 0x00: apic >> 8 int 16 >> (irq 10), address 00:15:17:ad:e4:20 >> ppb3 at pci0 dev 28 function 6 vendor "Intel", unknown product 0x3b4e >> rev 0x05 >> pci4 at ppb3 bus 4 >> vga1 at pci4 dev 0 function 0 "Matrox MGA G200e (ServerEngines)" rev 0x02 >> >> I would expect there to be an "em2" for the second onboard interface, >> but there is none. `ifconfig -a` doesn't show any additional interfaces. >> >> Any magic hacks I can try to get that second onboard interface working? >> >> Thanks, >> Ross >> >> -- Ross P. Davis Software Engineer / IT Specialist The Foundation for Applied Molecular Evolution Phone: 352.271.7005 Fax: 352.271.7076 www.ffame.org
network interface not recognized on Intel S3420GPLC board
I installed OpenBSD 4.6 on an Intel SR1630HGP server that has an Intel S3420GPLC board. There are three network interfaces on the server: one card, and two on the motherboard. The card is recognized: em0 at pci1 dev 0 function 0 "Intel PRO/1000 MT (82574L)" rev 0x00: apic 8 int 16 (irq 11), address 00:1b:21:49:8d:8c As is one of the interfaces on the board: em1 at pci3 dev 0 function 0 "Intel PRO/1000 MT (82574L)" rev 0x00: apic 8 int 16 (irq 10), address 00:15:17:ad:e4:20 Looking at dmesg, the devices flanking pci3 are: ppb1 at pci0 dev 28 function 0 vendor "Intel", unknown product 0x3b42 rev 0x05: a pic 8 int 16 (irq 10) pci2 at ppb1 bus 2 ppb2 at pci0 dev 28 function 4 vendor "Intel", unknown product 0x3b4a rev 0x05 pci3 at ppb2 bus 3 em1 at pci3 dev 0 function 0 "Intel PRO/1000 MT (82574L)" rev 0x00: apic 8 int 16 (irq 10), address 00:15:17:ad:e4:20 ppb3 at pci0 dev 28 function 6 vendor "Intel", unknown product 0x3b4e rev 0x05 pci4 at ppb3 bus 4 vga1 at pci4 dev 0 function 0 "Matrox MGA G200e (ServerEngines)" rev 0x02 I would expect there to be an "em2" for the second onboard interface, but there is none. `ifconfig -a` doesn't show any additional interfaces. Any magic hacks I can try to get that second onboard interface working? Thanks, Ross
Re: cannot reach internal network from gateway (and vice-versa)
On 12/22/09 4:01 AM, Stijn wrote: > Ross Davis wrote: >> I am almost certainly doing something really stupid so hopefully someone >> can point out where the hole in my brain lies. >> >> I have a built a firewall/gateway from using OpenBSD 4.6. The external >> interface is 192.168.5.250 which is attached to a DSL router. The >> internal interface is 192.168.59.254 which is attached to a switch, >> branching out to the rest of my internal network. >> >> >From the gateway I can ping the outside world (e.g. google). However, I >> cannot ping machines on the internal network. I tried using a minimal >> set of PF rules - didn't work. I disabled PF entirely - still could not >> ping the internal network. >> >> Oddly, the dhcp server I am running on the gateway is reporting DHCP >> requests. So traffic is indeed arriving at the gateway from the internal >> network. Despite that the dhcp server says it is handing out addresses, >> machines on the internal network are not getting them. If I manually set >> an IP address on an internal machine, it can still not ping the gateway. >> Machines on the internal network /can/ ping each other though. >> >> When logging on PF, I can see my pings leaving the machine, but nothing >> coming back. >> >> I tried changing the interfaces around to see if the problem was a bad >> card, but I got the same problem. >> >> I tried rebooting the switches - no change. >> >> What am I missing? >> >> Thanks, >> Ross >> >> >> >> > Hi Ross, > > -First of, have both the firewall and switch port the same speed and > duplex settings (e.g. 100Mb/full duplex)? They should be auto-negotiated > correctly but check it anyway. Is this a managed switch, i.e. is it > using vlans? > -What's the output of "ifconfig"? > -What's the output of "cat /etc/dhcpd.conf"? > -What's the output of "arp -an"? > -What do you see if you sniff the interal interface? (e.g. run "tcpdump > -ni icmp" on the firewall and initiate a ping from an internal > host) > > I think there's a typo somewhere in your configs regarding your gateway > address, be it a wrong subnet mask, typo in the ip address, etc... It's > normal you see the dhcp requests since those are broadcasts. > > HTH, > Stijn Thanks to all that offered advice on this. After tracing wires around, I found that the problem was that the network interface and the switch "didn't like each other". I tried rebooting the switch and using a different port - no luck. But when I tried plugging the cable into a different switch, everything worked. Perhaps my older onboard network interfaces and my D-Link switch have some sort of incompatible settings... regardless, now I have everything up and running. Thanks! ross
cannot reach internal network from gateway (and vice-versa)
I am almost certainly doing something really stupid so hopefully someone can point out where the hole in my brain lies. I have a built a firewall/gateway from using OpenBSD 4.6. The external interface is 192.168.5.250 which is attached to a DSL router. The internal interface is 192.168.59.254 which is attached to a switch, branching out to the rest of my internal network. >From the gateway I can ping the outside world (e.g. google). However, I cannot ping machines on the internal network. I tried using a minimal set of PF rules - didn't work. I disabled PF entirely - still could not ping the internal network. Oddly, the dhcp server I am running on the gateway is reporting DHCP requests. So traffic is indeed arriving at the gateway from the internal network. Despite that the dhcp server says it is handing out addresses, machines on the internal network are not getting them. If I manually set an IP address on an internal machine, it can still not ping the gateway. Machines on the internal network /can/ ping each other though. When logging on PF, I can see my pings leaving the machine, but nothing coming back. I tried changing the interfaces around to see if the problem was a bad card, but I got the same problem. I tried rebooting the switches - no change. What am I missing? Thanks, Ross
Re: problem compiling bandwidthd on OpenBSD 4.3
On 11/23/09 1:10 AM, Philip Guenther wrote: > On Sun, Nov 22, 2009 at 9:41 PM, Ross Davis wrote: >> I am trying to compile bandwidthd 2.0.1 on OpenBSD 4.3. After installing >> a few needed ports, I was able to run the ./configure command >> successfully with: >> >> ./configure CFLAGS=-lz -x-libraries=/usr/X11R6/lib > > You should pass linker options like -lz via LDFLAGS instead of CFLAGS, > or even better, via LIBS if the Makefile supports that variable. > (That's the source of those "gcc: -lz: linker input file unused > because linking not done" warnings.) Replacing CFLAGS with LDFLAGS seemed to cause no problems, and eliminated the warning messages during make. >> However, `make` seems to error out with this message: "Graph cycles >> through conf.l.c" > > The makefile is either buggy or assumes a non-POSIX make. Try it > again with 'gmake'. If you still get errors, yell at the bandwidthd > authors. `gmake` worked, thank you! ross
problem compiling bandwidthd on OpenBSD 4.3
I am trying to compile bandwidthd 2.0.1 on OpenBSD 4.3. After installing a few needed ports, I was able to run the ./configure command successfully with: ./configure CFLAGS=-lz -x-libraries=/usr/X11R6/lib However, `make` seems to error out with this message: "Graph cycles through conf.l.c" Before I try digging into the source code, has anyone run into this before? For reference, here is the full make output: gcc -Wall -lz -I/usr/local/include -DHAVE_CONFIG_H -DINSTALL_DIR="\"/usr/local/bandwidthd\"" -c bandwidthd.c bandwidthd.c: In function `StoreIPDataInCDF': bandwidthd.c:897: warning: long unsigned int format, time_t arg (arg 4) bandwidthd.c: In function `RCDF_Test': bandwidthd.c:1093: warning: long unsigned int format, time_t arg (arg 4) bandwidthd.c: In function `RCDF_PositionStream': bandwidthd.c:1126: warning: long unsigned int format, time_t arg (arg 4) bandwidthd.c: In function `RCDF_Load': bandwidthd.c:1148: warning: long unsigned int format, time_t arg (arg 4) gcc: -lz: linker input file unused because linking not done gcc -Wall -lz -I/usr/local/include -DHAVE_CONFIG_H -DINSTALL_DIR="\"/usr/local/bandwidthd\"" -c graph.c gcc: -lz: linker input file unused because linking not done gcc -Wall -lz -I/usr/local/include -DHAVE_CONFIG_H -DINSTALL_DIR="\"/usr/local/bandwidthd\"" -c conf.tab.c gcc: -lz: linker input file unused because linking not done Graph cycles through conf.l.c `all' not remade because of errors. Thanks, Ross
Re: monitoring traffic/bandwidth on a bridge
Monitoring the total bandwidth through the bridge is easy with `bwm-ng` or `ifstat`. The problem is that I want to see the bandwidth on a per-IP address basis. I can do this with `ntop` on an interface that has an IP address, but when I try to use it on the bridge I get: # ntop -i bridge0 bridge0: no IPv4 address assigned Unless I am misunderstanding the concept of a bridge, I don't think a bridge can even have an IP address. Any ideas? Thanks, Ross
monitoring traffic/bandwidth on a bridge
I am running OpenBSD 4.0 and have a bridge set up between two interfaces: fxp0 and xl0. I would like a program that gives a fairly basic report on the traffic flowing through this bridge. I am primarily interested in knowing which IPs on the xl0 side of the bridge are pulling the most bandwidth. I am currently experimenting with bwm-ng and ntop, but was wondering if anyone had a super magic awesome tool that they could recommend. Thanks, Ross
