An HTML attachment was scrubbed... URL: http://ns2.lanforge.com/pipermail/vlan/attachments/20060718/53008f53/attachment.html -------------- next part -------------- Hi, I have a Appliance with 4 Intel Cards on board. My Linux is Debian Sarge with 2.4.17 Kernel. Vlan works fine with eth0 but not with eth1,2 or 3. Example: Appliance eth3.6 --- Trunk: Swicht :static vlan 6 --- Linux Server A I do a ping from the appliance to the Linux Server A. On the Linux Server I see with snort the arp request and the answer with the mac address. On the appliance arp -n shows incomplete mac for Linux Server A and so the ping don't work. Again, the same config with eth0.6 works fine. Have anyone a solution for this problem? Here the networkdrivers from dmesg Intel(R) PRO/100 Network Driver - version 2.3.43-k1 Copyright (c) 2004 Intel Corporation PCI: Found IRQ 5 for device 01:00.0 PCI: Sharing IRQ 5 with 00:02.0 PCI: Sharing IRQ 5 with 00:1d.0 divert: allocating divert_blk for eth0 e100: selftest OK. e100: eth0: Intel(R) PRO/100 Network Connection Hardware receive checksums enabled cpu cycle saver enabled PCI: Found IRQ 12 for device 01:01.0 PCI: Sharing IRQ 12 with 00:1f.3 divert: allocating divert_blk for eth1 e100: selftest OK. e100: eth1: Intel(R) PRO/100 Network Connection Hardware receive checksums enabled cpu cycle saver enabled PCI: Found IRQ 10 for device 01:02.0 PCI: Sharing IRQ 10 with 00:1d.2 PCI: Sharing IRQ 10 with 00:1f.1 divert: allocating divert_blk for eth2 e100: selftest OK. e100: eth2: Intel(R) PRO/100 Network Connection Hardware receive checksums enabled cpu cycle saver enabled PCI: Found IRQ 11 for device 01:03.0 PCI: Sharing IRQ 11 with 00:1d.1 divert: allocating divert_blk for eth3 e100: selftest OK. e100: eth3: Intel(R) PRO/100 Network Connection Hardware receive checksums enabled cpu cycle saver enabled THX Jens
