lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20150212054035.7c7f6ff1@uryu.home.lan>
Date:	Thu, 12 Feb 2015 05:40:35 -0800
From:	Stephen Hemminger <stephen@...workplumber.org>
To:	安理 李剑 <dovelijian@....com>
Cc:	netdev@...r.kernel.org
Subject: Re: Some question about 802.1Q VLAN

On Tue, 10 Feb 2015 14:47:44 +0800 (CST)
安理 李剑 <dovelijian@....com> wrote:

> 
> 
> 
> 
> HI…I am a Linux VLAN user. Now, I encounter some question about 802.1Q VLAN in my wireless AP. My Linux kernel version is 2.6.31.
>  
> Plese see my setting:
>            vconfig add eth0 10
>            vconfig add ath0 10
>            ifconfig eth0.10 up
>            ifconfig ath0.10 up
>            brctl addbr br0
>           brctl addbr br1
>           brctl addif br0 ath0
>           brctl addif br0 eth0
>           brctl addif br1 ath0.10
>           brctl addif br1 eth0.10
>           ifconfig br0 up
>           ifconfig br1 up
>                           
> The eth0 and ath0 is real network card in my AP,and the ath0 is the wireless card.
>  
> Question:
>      Two station associate AP by wireless,the two station and AP use same VLAN setting like my describe.One station br0 Ip address is 192.168.1.10/24,br1 ip address is 192.168.2.10/24;other station br0 ip address is 192.169.1.11/24, br1 ip address is 192.168.2.12/24.The AP is used bridge the data from station.
>   But now use station1 ping station2: ping 192.168.1.11,it is successed; ping 192.168.2.12,it is failed!!!
>   I don’t know the reason about the fail situation ,I need some help.
>   Thank you!

Wireless internally is point to point and does support true promiscious
mode. Typically AP's implement Ethernet level (L2) NAT to deal with this.
 

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ