Re: Lockup problem with quad nic (dc driver)
Jason Dixon wrote:
On Sep 10, 2006, at 12:36 PM, Joe wrote:
Jason Dixon wrote:
On Sep 10, 2006, at 4:31 AM, Joe wrote:
Andreas Bihlmaier wrote:
I have the same problem with this board:
cpu0: VIA Esther processor 1500MHz ("CentaurHauls" 686-class) 1.50 GHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,CMOV,PAT,CFLUSH,ACPI,MMX,FXSR,SSE,SSE2,TM,SBF,SSE3,EST,TM2
The problem is not dc(4) specific, it seems the board can't handle pci
bridges, so far I tested dual nics: fxp, tl, sf, none of them seems to
work, they all lock up the box as soon as I up more than one of the
interfaces.
Thanks for the reply. This is disappointing. I really wanted to use
this board as my new firewall/vpn.
So, my advice for now is to stay away from the new VIA EN or CN
series boards with the C7 processor for use as multihomed firewalls.
I still don't understand why some folks avoid using VLANs in these
circumstances. You can get very creative with physical interfaces,
trunk(4), and vlan(4). It's pretty rare these days that you actually
*need* dual/quad cards.
I setup 3 vlans on fxp0 (replaced the quad nic with fxp0) and things
seem to be working great.
Thanks for the recommendation.
Re: Lockup problem with quad nic (dc driver)
On Sep 10, 2006, at 12:36 PM, Joe wrote:
Jason Dixon wrote:
On Sep 10, 2006, at 4:31 AM, Joe wrote:
Andreas Bihlmaier wrote:
I have the same problem with this board:
cpu0: VIA Esther processor 1500MHz ("CentaurHauls" 686-class)
1.50 GHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,CMOV,PAT,CFLUS
H,ACPI,MMX,FXSR,SSE,SSE2,TM,SBF,SSE3,EST,TM2
The problem is not dc(4) specific, it seems the board can't
handle pci
bridges, so far I tested dual nics: fxp, tl, sf, none of them
seems to
work, they all lock up the box as soon as I up more than one of the
interfaces.
Thanks for the reply. This is disappointing. I really wanted to
use this board as my new firewall/vpn.
So, my advice for now is to stay away from the new VIA EN or CN
series boards with the C7 processor for use as multihomed firewalls.
I still don't understand why some folks avoid using VLANs in these
circumstances. You can get very creative with physical
interfaces, trunk(4), and vlan(4). It's pretty rare these days
that you actually *need* dual/quad cards.
I was under the impression that VLANs were never meant to provide
any security and that VLAN "hopping" was possible. The thought did
cross my mind to use VLANs though.
VLAN hopping is possible if you don't know how to configure your
switch properly. Just like hacking my OpenBSD box is possible if I
leave the root password blank and give them the key to my server room.
--
Jason Dixon
DixonGroup Consulting
http://www.dixongroup.net
Re: Lockup problem with quad nic (dc driver)
Jason Dixon wrote:
On Sep 10, 2006, at 4:31 AM, Joe wrote:
Andreas Bihlmaier wrote:
I have the same problem with this board:
cpu0: VIA Esther processor 1500MHz ("CentaurHauls" 686-class) 1.50 GHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,CMOV,PAT,CFLUSH,ACPI,MMX,FXSR,SSE,SSE2,TM,SBF,SSE3,EST,TM2
The problem is not dc(4) specific, it seems the board can't handle pci
bridges, so far I tested dual nics: fxp, tl, sf, none of them seems to
work, they all lock up the box as soon as I up more than one of the
interfaces.
Thanks for the reply. This is disappointing. I really wanted to use
this board as my new firewall/vpn.
So, my advice for now is to stay away from the new VIA EN or CN series
boards with the C7 processor for use as multihomed firewalls.
I still don't understand why some folks avoid using VLANs in these
circumstances. You can get very creative with physical interfaces,
trunk(4), and vlan(4). It's pretty rare these days that you actually
*need* dual/quad cards.
--
Jason Dixon
DixonGroup Consulting
http://www.dixongroup.net
I was under the impression that VLANs were never meant to provide any
security and that VLAN "hopping" was possible. The thought did cross my
mind to use VLANs though.
Re: Lockup problem with quad nic (dc driver)
On Sep 10, 2006, at 4:31 AM, Joe wrote:
Andreas Bihlmaier wrote:
I have the same problem with this board:
cpu0: VIA Esther processor 1500MHz ("CentaurHauls" 686-class) 1.50
GHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,CMOV,PAT,CFLUSH,
ACPI,MMX,FXSR,SSE,SSE2,TM,SBF,SSE3,EST,TM2
The problem is not dc(4) specific, it seems the board can't handle
pci
bridges, so far I tested dual nics: fxp, tl, sf, none of them
seems to
work, they all lock up the box as soon as I up more than one of the
interfaces.
Thanks for the reply. This is disappointing. I really wanted to use
this board as my new firewall/vpn.
So, my advice for now is to stay away from the new VIA EN or CN
series boards with the C7 processor for use as multihomed firewalls.
I still don't understand why some folks avoid using VLANs in these
circumstances. You can get very creative with physical interfaces,
trunk(4), and vlan(4). It's pretty rare these days that you actually
*need* dual/quad cards.
--
Jason Dixon
DixonGroup Consulting
http://www.dixongroup.net
Re: Lockup problem with quad nic (dc driver)
Andreas Bihlmaier wrote:
On Sat, Sep 09, 2006 at 01:40:34PM -0700, Joe wrote:
Problem: After updating to OpenBSD 3.9 stable, my system locks up
whenever a dc interface is brought "up". This system has 5 network
interfaces, one on-board (vr0), and a Phobos P430 Quad NIC
(dc0,dc1,dc2,dc3). The vr0 interface works fine.
At first, I could not get the system to finish booting up. It would hang
at "starting network". I then removed the files:
/etc/hostname.dc0
/etc/hostname.dc1
/etc/hostname.dc2
/etc/hostname.dc3
and the system boots up. However, when I do either:
# ifconfig dc0 up
# ifconfig dc1 up
# ifconfig dc2 up
# ifconfig dc3 up
The system locks up.
Here is the dmesg:
OpenBSD 3.9-stable (GENERIC) #1: Sun Sep 3 11:32:26 PDT 2006
[EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: VIA Esther processor 1300MHz ("CentaurHauls" 686-class) 1.30 GHz
XSR,SSE,SSE2,TM,SBF,SSE3,EST,TM2
I have the same problem with this board:
cpu0: VIA Esther processor 1500MHz ("CentaurHauls" 686-class) 1.50 GHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,CMOV,PAT,CFLUSH,ACPI,MMX,FXSR,SSE,SSE2,TM,SBF,SSE3,EST,TM2
The problem is not dc(4) specific, it seems the board can't handle pci
bridges, so far I tested dual nics: fxp, tl, sf, none of them seems to
work, they all lock up the box as soon as I up more than one of the
interfaces.
Thanks for the reply. This is disappointing. I really wanted to use this
board as my new firewall/vpn.
So, my advice for now is to stay away from the new VIA EN or CN series
boards with the C7 processor for use as multihomed firewalls.
Re: Lockup problem with quad nic (dc driver)
On Sat, Sep 09, 2006 at 01:40:34PM -0700, Joe wrote:
> Problem: After updating to OpenBSD 3.9 stable, my system locks up
> whenever a dc interface is brought "up". This system has 5 network
> interfaces, one on-board (vr0), and a Phobos P430 Quad NIC
> (dc0,dc1,dc2,dc3). The vr0 interface works fine.
>
> At first, I could not get the system to finish booting up. It would hang
> at "starting network". I then removed the files:
>
> /etc/hostname.dc0
> /etc/hostname.dc1
> /etc/hostname.dc2
> /etc/hostname.dc3
>
> and the system boots up. However, when I do either:
>
> # ifconfig dc0 up
> # ifconfig dc1 up
> # ifconfig dc2 up
> # ifconfig dc3 up
>
> The system locks up.
>
>
>
> Here is the dmesg:
>
> OpenBSD 3.9-stable (GENERIC) #1: Sun Sep 3 11:32:26 PDT 2006
> [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC
> cpu0: VIA Esther processor 1300MHz ("CentaurHauls" 686-class) 1.30 GHz
> XSR,SSE,SSE2,TM,SBF,SSE3,EST,TM2
I have the same problem with this board:
cpu0: VIA Esther processor 1500MHz ("CentaurHauls" 686-class) 1.50 GHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,CMOV,PAT,CFLUSH,ACPI,MMX,FXSR,SSE,SSE2,TM,SBF,SSE3,EST,TM2
The problem is not dc(4) specific, it seems the board can't handle pci
bridges, so far I tested dual nics: fxp, tl, sf, none of them seems to
work, they all lock up the box as soon as I up more than one of the
interfaces.
I even installed window$ in order to flash the bios, it looked up as
well with the dual nics inserted.
Since I need 3 interfaces (inet, lan, wlan) I went back to using a singe
nic, the onboard vge and an USB2.0 axe nic.
Everything works great now and I'm able to push ~70Mb/s hmac-md5-aes
IPSEC traffic with latest snapshots (GREAT! Thanks developers!).
Hope this will save you some time buying and testing other dual/quad
nics.
Regards,
ahb
p.s. IF you can resolve the problem (I wasn't able to), please let me
know!
Lockup problem with quad nic (dc driver)
Problem: After updating to OpenBSD 3.9 stable, my system locks up
whenever a dc interface is brought "up". This system has 5 network
interfaces, one on-board (vr0), and a Phobos P430 Quad NIC
(dc0,dc1,dc2,dc3). The vr0 interface works fine.
At first, I could not get the system to finish booting up. It would hang
at "starting network". I then removed the files:
/etc/hostname.dc0
/etc/hostname.dc1
/etc/hostname.dc2
/etc/hostname.dc3
and the system boots up. However, when I do either:
# ifconfig dc0 up
# ifconfig dc1 up
# ifconfig dc2 up
# ifconfig dc3 up
The system locks up.
Here is the dmesg:
OpenBSD 3.9-stable (GENERIC) #1: Sun Sep 3 11:32:26 PDT 2006
[EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: VIA Esther processor 1300MHz ("CentaurHauls" 686-class) 1.30 GHz
XSR,SSE,SSE2,TM,SBF,SSE3,EST,TM2
cpu0: RNG AES AES-CTR SHA1 SHA256 RSA
real mem = 469344256 (458344K)
avail mem = 421076992 (411208K)
using 4278 buffers containing 23568384 bytes (23016K) of memory
mainbus0 (root)
bios0 at mainbus0: AT/286+(cd) BIOS, date 05/16/06, BIOS32 rev. 0 @ 0xfa950
apm0 at bios0: Power Management spec V1.2
apm0: AC on, battery charge unknown
apm0: flags 70102 dobusy 1 doidle 1
pcibios0 at bios0: rev 2.1 @ 0xf/0xdd04
pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfdc50/176 (9 entries)
pcibios0: bad IRQ table checksum
pcibios0: PCI BIOS has 9 Interrupt Routing table entries
pcibios0: PCI Exclusive IRQs: 5 10 11
pcibios0: PCI Interrupt Router at 000:17:0 ("VIA VT8237 ISA" rev 0x00)
pcibios0: PCI bus #2 is the last bus
bios0: ROM list: 0xc/0xf200 0xd/0x8000!
cpu0 at mainbus0
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 vendor "VIA", unknown product 0x0314 rev 0x00
pchb1 at pci0 dev 0 function 1 vendor "VIA", unknown product 0x1314 rev 0x00
pchb2 at pci0 dev 0 function 2 vendor "VIA", unknown product 0x2314 rev 0x00
pchb3 at pci0 dev 0 function 3 "VIA PT890 Host" rev 0x00
pchb4 at pci0 dev 0 function 4 vendor "VIA", unknown product 0x4314 rev 0x00
pchb5 at pci0 dev 0 function 7 vendor "VIA", unknown product 0x7314 rev 0x00
ppb0 at pci0 dev 1 function 0 "VIA VT8377 PCI-PCI" rev 0x00
pci1 at ppb0 bus 1
vga1 at pci1 dev 0 function 0 vendor "VIA", unknown product 0x3344 rev
0x01: aperture at 0xf400, size 0x1000
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
pciide0 at pci0 dev 15 function 0 "VIA VT6420 SATA" rev 0x80: DMA
pciide0: using irq 11 for native-PCI interrupt
pciide1 at pci0 dev 15 function 1 "VIA VT82C571 IDE" rev 0x06: DMA,
channel 0 configured to compatibility, channel 1 configured to compatibility
pciide1: channel 0 disabled (no drives)
wd0 at pciide1 channel 1 drive 0:
wd0: 16-sector PIO, LBA48, 38154MB, 78140160 sectors
wd0(pciide1:1:0): using PIO mode 4, DMA mode 2
uhci0 at pci0 dev 16 function 0 "VIA VT83C572 USB" rev 0x81: irq 10
usb0 at uhci0: USB revision 1.0
uhub0 at usb0
uhub0: VIA UHCI root hub, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
uhci1 at pci0 dev 16 function 1 "VIA VT83C572 USB" rev 0x81: irq 10
usb1 at uhci1: USB revision 1.0
uhub1 at usb1
uhub1: VIA UHCI root hub, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
uhci2 at pci0 dev 16 function 2 "VIA VT83C572 USB" rev 0x81: irq 11
usb2 at uhci2: USB revision 1.0
uhub2 at usb2
uhub2: VIA UHCI root hub, rev 1.00/1.00, addr 1
uhub2: 2 ports with 2 removable, self powered
uhci3 at pci0 dev 16 function 3 "VIA VT83C572 USB" rev 0x81: irq 11
usb3 at uhci3: USB revision 1.0
uhub3 at usb3
uhub3: VIA UHCI root hub, rev 1.00/1.00, addr 1
uhub3: 2 ports with 2 removable, self powered
ehci0 at pci0 dev 16 function 4 "VIA VT6202 USB" rev 0x86: irq 5
usb4 at ehci0: USB revision 2.0
uhub4 at usb4
uhub4: VIA EHCI root hub, rev 2.00/1.00, addr 1
uhub4: 8 ports with 8 removable, self powered
viapm0 at pci0 dev 17 function 0 "VIA VT8237 ISA" rev 0x00
iic0 at viapm0
"unknown" at iic0 addr 0x18 not configured
:e6:43:8e
ukphy0 at vr0 phy 1: Generic IEEE 802.3u media interface, rev. 10: OUI
0x004063, model 0x0032
ppb1 at pci0 dev 19 function 0 "Intel S21152BB PCI-PCI" rev 0x00
pci2 at ppb1 bus 2
dc0 at pci2 dev 4 function 0 "DEC 21142/3" rev 0x41: irq 11, address
00:60:f5:04:0a:10
lxtphy0 at dc0 phy 1: LXT970 10/100 PHY, rev. 3
dc1 at pci2 dev 5 function 0 "DEC 21142/3" rev 0x41: irq 11, address
00:60:f5:04:0a:11
lxtphy1 at dc1 phy 1: LXT970 10/100 PHY, rev. 3
dc2 at pci2 dev 6 function 0 "DEC 21142/3" rev 0x41: irq 11, address
00:60:f5:04:0a:12
lxtphy2 at dc2 phy 1: LXT970 10/100 PHY, rev. 3
dc3 at pci2 dev 7 function 0 "DEC 21142/3" rev 0x41: irq 11, address
00:60:f5:04:0a:13
lxtphy3 at dc3 phy 1: LXT970 10/100 PHY, rev. 3
isa0 at mainbus0
isadma0 at isa0
pckbc0 at isa0 port 0x60/5
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pmsi0 at pckbc0 (aux slot)
pckbc0: using irq 12 for aux slot
wsmou
