I agree. Change the MTU on the bridges. I have a customer with 5 remote sites connected via 802.11b and trunking across all 5 and I have to increase the MTU.
What I would love to see is an update to the Aironet code that supports the actual trunking header so my bridge management interfaces could be on a non-native VLAN. I tend to make the native VLAN (Dot1Q) the most active VLAN and not the default VLAN 1. Unfortunately, in this scenario, the bridges won't communicate in VLAN 1 as these frames will be tagged and the bridges don't "understand" the tags. Maybe some day... Rik -----Original Message----- From: Priscilla Oppenheimer [mailto:[EMAIL PROTECTED]] Sent: Monday, April 29, 2002 9:19 PM To: [EMAIL PROTECTED] Subject: RE: Trunking over Aironet bridge? [7:42833] An ISL frame can be as big as 1518 + 30 = 1548 bytes. The original frame is encapsulated in a 26-byte header and a 4-byte CRC. An 802.1Q frame can be as big as 1522 bytes. 802.1Q inserts a 4-byte header immediately the destination and source MAC addresses (and source-routing information, if present) of the frame to be transmitted, which could have already been 1518 bytes. Priscilla At 05:24 PM 4/29/02, Marko Milivojevic wrote: > > yes, you must change the default frame size on the ethernet > > side of both > > bridges to 1522 (default 1518). As far as the radio is > > concern it will pass > > the frames out over the wireless. You will need a switch on > > the other end of > > the bridge to recieve the frames and break out the vlans. > > That would be required for ISL, but 802.1q should go with no >changes? > > >Marko. ________________________ Priscilla Oppenheimer http://www.priscilla.com Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=42872&t=42833 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
