From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Tue, 23 Sep 2008 19:01:41 +0530 (IST) From: rahul bhardwaj In-Reply-To: <20080922083322.22fcc415@extreme> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-638661803-1222176701=:58969" Message-ID: <694310.58969.qm@web8804.mail.in.yahoo.com> Subject: Re: [Bridge] bridge is not forwarding the packet List-Id: Linux Ethernet Bridging List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: bridge@lists.linux-foundation.org Cc: Stephen Hemminger --0-638661803-1222176701=:58969 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi Stephen, Thanks for your very prompt response! Actually my problem is not related to MAC address restrictions from wireless interface/driver. The problem lies mainly in multiple bridges for different= vlans. Since bridging happens first, the packet ends up on wrong bridge and gets discarded form that bridge. =C2=A0If Vlan handling is done prior to bridge handling, my setup will work fine.=20 =C2=A0 There is also another thing which I did not understand. When we add an interface to vlan, the newly created interface=E2=80=99s hard_header is set to vlan_dev_= hard_header function. This vlan_dev_hard_header adds the vlan tag for outing packet. Interestingly this happens after bridging code hand over the packet to interface. Convers= ely when the packet is received, interface should remove the vlan tag and hand over = the packet to bridge. But we are seeing that bridge code is executing prior to = vlan handling. =C2=A0 Regards, =C2=A0 Rahul Bhardwaj =C2=A0 =C2=A0 --- On Mon, 22/9/08, Stephen Hemminger wrote: From: Stephen Hemminger Subject: Re: [Bridge] bridge is not forwarding the packet To: "rahul bhardwaj" Cc: bridge@lists.linux-foundation.org Date: Monday, 22 September, 2008, 8:33 AM On Mon, 22 Sep 2008 16:24:00 +0530 (IST) rahul bhardwaj wrote: > Hello to all, >=20 > I am stating my problem below in detail so that you all can understand it properly. >=20 > I am having setup of Linux box. In that box I am having one Ethernet interface eth0 and one wireless interface ath0. I have also configured one = vlan port as eth0.100 with the help of vconfig (vconfig add eth 100).=C2=A0 Now = I have created two bridges br1 and br100. I have added eth0 into br1 so br1 is hav= ing only one interface. I have added ath0 and eth0.100 into br100. Physically e= th0 is connected to a switch which is configured to handle vlan 100. DHCP serve= r is also running into that switch to provide IP address to wireless stations. T= his is all about my setup. >=20 > After this I am associating one wireless station with the ath0. After successful association station issues a dhclient to get ip address, which reaches to ath0 interface of my Linux box. ath0 bridges that request to eth0.100. Now eth0.100 adds it's vlan tags and forward that request to the switch. Because switch is configured to support vlan 100, so it process the= dhcp request and send back the dhcp response with vlan tag 100.=20 >=20 > Now I don't know but this response is not reaching to ath0. I have putted wireshark and figured out that those dhcp responses are reaching on = eth0 and as eth0 is part of br1 so this packet is reaching to br1 which is just discarding them all. So the wireless station is not getting the ip address. According to me eth0 should give these packets to eth0.100 port instead of = br1. Or what I mean to say first vlan handling should be done priror then=C2=A0 = bridge handling. Do I need to change something into Linux kernel for that or there= is some other problem with my setup? >=20 > Can anybody help me in this? If anybody want more detail I will provide. = I am using Linux 2.6.15 kernel. Any kind of help will be much appreciated.=20 >=20 >=20 > With Regards=20 >=20 > Rahul Bhardwaj=20 Full bridging to wireless requires WDS which Linux wireless does not suppor= t (yet). http://www.linuxfoundation.org/en/Net:Bridge#It_doesn.27t_work_with_my_Wire= less_card.21 _______________________________________________ Bridge mailing list Bridge@lists.linux-foundation.org https://lists.linux-foundation.org/mailman/listinfo/bridge=0A=0A=0A Co= nnect with friends all over the world. Get Yahoo! India Messenger at http:/= /in.messenger.yahoo.com/?wm=3Dn/ --0-638661803-1222176701=:58969 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Hi Stephen,

Thanks for your very promp= t response!

=

Actually my problem is not related to MAC address restrictions from wireless interface/driver. The problem lies mainly in multiple bridges for different= vlans. Since bridging happens first, the packet ends up on wrong bridge and gets discarded form that bridge.  If Vlan handling is done prior to bridge handling, my setup will work fine.

 

There is also another thing which I did not understand. When we add an interface to vlan, the newly created interface=E2=80=99s hard_header is set to vlan_dev_= hard_header function. This vlan_dev_hard_header adds the vlan tag for outing packet.

Interestingly this happens after bridging code hand over the packet to interface. Convers= ely when the packet is received, interface should remove the vlan tag and hand over = the packet to bridge. But we are seeing that bridge code is executing prior to = vlan handling.

 

Regards,

 

Rahul Bhardwaj

 

 


--- On Mon, 22/9/08, Stephen Hemminger= <shemminger@vyatta.com> wrote:
Cc: brid= ge@lists.linux-foundation.org
Date: Monday, 22 September, 2008, 8:33 AM<= br>
On Mon, 22 Sep 2008 16:24:00 +0530 (IST)
rahul bhardwaj <=
rahul_bhardwaj36in@yahoo.co.in> wrote:

> Hello to all,
>=
 
> I am stating my problem below in detail so that you all can under=
stand it
properly.
> 
> I am having setup of Linux box. In t=
hat box I am having one Ethernet
interface eth0 and one wireless interfa=
ce ath0. I have also configured one vlan
port as eth0.100 with the
 help of vconfig (vconfig add eth 100).  Now I have
created two bri=
dges br1 and br100. I have added eth0 into br1 so br1 is having
only one=
 interface. I have added ath0 and eth0.100 into br100. Physically eth0
i=
s connected to a switch which is configured to handle vlan 100. DHCP server=
 is
also running into that switch to provide IP address to wireless stat=
ions. This
is all about my setup.
> 
> After this I am assoc=
iating one wireless station with the ath0. After
successful association =
station issues a dhclient to get ip address, which
reaches to ath0 inter=
face of my Linux box. ath0 bridges that request to
eth0.100. Now eth0.10=
0 adds it's vlan tags and forward that request to the
switch. Because sw=
itch is configured to support vlan 100, so it process the dhcp
request a=
nd send back the dhcp response with vlan tag 100. 
> 
> Now I d=
on't know but this response is not reaching to ath0. I
 have
putted wireshark and figured out that those dhcp responses are rea=
ching on eth0
and as eth0 is part of br1 so this packet is reaching to b=
r1 which is just
discarding them all. So the wireless station is not get=
ting the ip address.
According to me eth0 should give these packets to e=
th0.100 port instead of br1.
Or what I mean to say first vlan handling s=
hould be done priror then  bridge
handling. Do I need to change som=
ething into Linux kernel for that or there is
some other problem with my=
 setup?
> 
> Can anybody help me in this? If anybody want more =
detail I will provide. I
am using Linux 2.6.15 kernel. Any kind of help =
will be much appreciated. 
> 
> 
> With Regards 
> =

> Rahul Bhardwaj 

Full bridging to wireless requires WDS whic=
h Linux wireless does not
 support
(yet).

http://www.linuxfoundation.org/en/Net:Bridge#It_d=
oesn.27t_work_with_my_Wireless_card.21
_________________________________=
______________
Bridge mailing list
Bridge@lists.linux-foundation.org<=
br>https://lists.linux-foundation.org/mailman/listinfo/bridge

=0A=0A=0A
Share = files, take polls, and make new friends - all under one roof. = Click here. --0-638661803-1222176701=:58969--