after I sent that, I realized that it made no sense. I'm testing something out right now though, so I'll send an update after this. On Sun, 20 Mar 2005 21:36:20 -0800, Derek Fedel <synikal@xxxxxxxxx> wrote: > Some other information. to me, it looks as though the vlan encap is > set to 1q.. I'll check into the eepro card though. Any other ideas > maybe? > > VLAN Name Status IfIndex Mod/Ports, Vlans > ---- -------------------------------- --------- ------- ------------------------ > 1 default active 5 > 2 VLAN0002 active 826 > 3 VLAN0003 active 828 3/3-24 > 4/1-24 > 5/1-24 > 6/1-24 > 7/1-24 > 8/1-24 > 9/1-24 > 10/1-24 > 11/1-24 > 12/1-24 > 1002 fddi-default active 6 > 1003 token-ring-default active 9 > 1004 fddinet-default active 7 > 1005 trnet-default active 8 > > VLAN Type SAID MTU Parent RingNo BrdgNo Stp BrdgMode Trans1 Trans2 > ---- ----- ---------- ----- ------ ------ ------ ---- -------- ------ ------ > 1 enet 100001 1500 - - - - - 0 0 > 2 enet 100002 1500 - - - - - 0 0 > 3 enet 100003 1500 - - - - - 0 0 > 1002 fddi 101002 1500 - - - - - 0 0 > 1003 trcrf 101003 1500 - - - - - 0 0 > 1004 fdnet 101004 1500 - - - - - 0 0 > 1005 trbrf 101005 1500 - - - ibm - 0 0 > > VLAN DynCreated RSPAN > ---- ---------- -------- > 1 static disabled > 2 static disabled > 3 static disabled > 1002 static disabled > 1003 static disabled > 1004 static disabled > 1005 static disabled > > VLAN AREHops STEHops Backup CRF 1q VLAN > ---- ------- ------- ---------- ------- > 1003 7 7 off > > adm.2 VID: 2 REORDER_HDR: 1 dev->priv_flags: 1 > total frames received 3058 > total bytes received 262343 > Broadcast/Multicast Rcvd 104 > > total frames transmitted 1060 > total bytes transmitted 107868 > total headroom inc 0 > total encap on xmit 1060 > Device: adm > INGRESS priority mappings: 0:0 1:0 2:0 3:0 4:0 5:0 6:0 7:0 > EGRESSS priority Mappings: > istanbul:~# cat /proc/net/vlan/int.3 > int.3 VID: 3 REORDER_HDR: 1 dev->priv_flags: 1 > total frames received 0 > total bytes received 0 > Broadcast/Multicast Rcvd 0 > > total frames transmitted 3805 > total bytes transmitted 175030 > total headroom inc 0 > total encap on xmit 3669 > Device: int > INGRESS priority mappings: 0:0 1:0 2:0 3:0 4:0 5:0 6:0 7:0 > EGRESSS priority Mappings: > > * - indicates vtp domain mismatch > Port Mode Encapsulation Status Native vlan > -------- ----------- ------------- ------------ ----------- > 3/1 on dot1q trunking 3 > 3/2 on dot1q trunking 2 > > Port Vlans allowed on trunk > -------- --------------------------------------------------------------------- > 3/1 1,3 > 3/2 2 > > Port Vlans allowed and active in management domain > -------- --------------------------------------------------------------------- > 3/1 1,3 > 3/2 2 > > Port Vlans in spanning tree forwarding state and not pruned > -------- --------------------------------------------------------------------- > 3/1 1,3 > 3/2 2 > > > On Mon, 21 Mar 2005 05:57:13 +0100, Peter Stuge <stuge-vlan@xxxxxxx> wrote: > > On Sun, Mar 20, 2005 at 08:46:47PM -0800, Derek Fedel wrote: > > > The NIC connected to the switch is a Realtek 8100 series that I > > > believe should support the extra MTU size (8139too driver) > > > > It will, but I would suggest getting an Intel card instead, they > > don't cost a lot and are higher quality cards. Use the e100 or e1000 > > driver in the kernel though, not the old eepro100 driver. > > > > > > > Its odd, I set up the vlans I want on the switch, set up the > > > trunking on the port that the firewall is connected to, and vconfig > > > the vlans to the interface on the firewall, but once I bring the > > > vlan'd interface up, it will transmit packets, but not actually > > > receive anything except for what tcpdump identifies as "Unknown IPX > > > packets". hooray. Anyone have any ideas? I'll be glad to supply > > > more information if need be. I suspect an MTU issue, but I'm not > > > too sure. > > > > Is trunking specifically set to use dot1q? If not, I believe Cisco > > prefers their own trunking protocol ISL, which is incompatible with > > 802.1Q. > > > > //Peter > > _______________________________________________ > > Vlan mailing list > > Vlan@xxxxxxxxxxxx > > http://www.lanforge.com/mailman/listinfo/vlan > > >
