Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I'm trying to create the followig setup:

                                +----------+
                                |  Wi-Fi   |
                                +----------+
                                     ^
                                     |
                                     |
                                     |
     +------+           +------+     |
     |      |           |      |+----+
     | VoIP |+--------->| Thin |
     |Phone |           |Client|
     +------+ Ethernet  +------+

The Thin Client and the VoIP phone shall have different ip addresses on the same subnet(the wireless one). So far what i've reached is, to make the br0 interface get a valid ip through dhcp, with the following commands

echo 1 > /proc/sys/net/ipv4/ip_forward

ip link set dev wlan0 up
ip link set dev eth0 up

brctl addbr br0
brctl addif br0 wlan0
brctl addif br0 eth0
ip link set dev br0 up

wpa_supplicant -B -b br0 -i wlan0 -c /home/test/my.wpa.conf
dhclient br0

Routing works, and accessing the internet or Windows terminal server from the thin client work as expected. Am i missing something that needs to be configured to the phone get a valid dhcp lease too?

Listening with tcpdump on the eth0(tcpdump -i eth0 -nevvv) i get no traffic at all, and on wlan0 doing nothing than being connected, just stp topology updates.

Other thing: Masquerade/NAT is not an option, because we want to control the phones on the dhcp, with the mac vendor filter and making they act like different hosts to avoid configuring each phone, and managing them just on the VoIP central.

Cheers

share|improve this question
    
Is iptables running on the thin client and, if so, what is its rule set? –  phil-lavin Mar 25 '13 at 13:28
    
Have you done an ifconfig br0 up? –  NickW Mar 25 '13 at 13:29
    
@phil-lavin Iptables is running on an empty ruleset; –  nwildner Mar 25 '13 at 13:44
    
@NickW Yes, i forgot to comment that, sorry. The bridge is up and i can use the ThinClient normally to conect through PC-over-ip and rdp. –  nwildner Mar 25 '13 at 13:45
1  
BTW, your wireless card can do proxy arp/arp spoofing? The four requirements for proper bridging: 1 All devices share the same maximum packet size (MTU). The bridge doesn't fragment packets. 2 Devices must look like Ethernet. i.e have 6 byte source and destination address. 3 Support promiscuous operation. The bridge needs to be able to receive all network traffic, not just traffic destined for its own address. 4 Allow source address spoofing. The bridge must be able to send data over network as if it came from another host. –  NickW Mar 25 '13 at 15:18
show 8 more comments

3 Answers

up vote 0 down vote accepted

AFAIK it will not be working.
WiFi AP expect single MAC of single client node. So you can find bridge with wifi, but with modification of outgoing mac. (I can imagine that WiFi card can simulate more than one wireless client but I don't know any existing solution for this.)
I think you should reconsider NAT solution or - if it's possible in your environment - set L2 VPN, like OpenVPN, between eth of thin client and some remote wired VPN concentrator via WiFi.
(If you control all AP then maybe WDS or some mesh network is solution, but I don't think so.)

share|improve this answer
    
Hi dsnajder. I'll try this way if the WiFi bridge do not work. But first, i'll need to answer all the expectation of the bosses, and if this proves to be impossible to reach(bridge configs), i'll reconsider the NAT solution, for sure. :) –  nwildner Mar 26 '13 at 11:06
    
It turns out that i had to make a NAT to make this setup works. However, the quality of the sip connections jumped from very good to no quality at all depending on the utilization of the wireless, making this solution inviable. –  nwildner Nov 13 '13 at 16:04
add comment

Forget this setup and buy a purpose-built device which performs the same function. These Ethernet-wireless LAN client bridge devices (which can be hard to search for since there's no real standard name for the device's function) range from as little as $20 USD on the low end to $1500 or more for a ruggedized industrial grade device. In an office, you probably don't need IP68 protection, though...

share|improve this answer
    
but AFAIK bridge mode is point to point, and - if I correctly understand nwildner - here is needed point to multipoint. Or maybe am I wrong? –  dsznajder Mar 26 '13 at 13:28
    
Nope, these devices put the end device on the same subnet, which accomplishes the goal stated here. –  Michael Hampton Mar 26 '13 at 13:46
1  
We have similar devices to connect different geolocated offices and it's departaments. ubnt.com/download#doc:Rocket:M - They work flawlessly on WDS mode, so, from that hardware that we got the idea to do the same but with our office wireless(Motorola AP's) and the thin clients + VoIP phones ;) And yes, as @MichaelHampton said, they(Ubiquity radios) make both departaments be in the same subnet without the need of a "point-to-point like" connection –  nwildner Mar 26 '13 at 14:08
    
Yeah, we have lots of those Rocket M5 on other offices, where some places get about 1 mile of the nearest switch but, this bridge i'm trying to make, we'll use on the office, where other stations/notebooks are already using our wireless lan. –  nwildner Sep 12 '13 at 17:20
add comment

As it is, this won't work because the wireless access point on the other end will only allow traffic from the authenticated MAC. There's a potential solution here but that won't work for you, since the entire point is that you want different MACs. (note that your ipv4 forwarding is not necessary because you're not at that layer) As I see it your choices are

  1. Modify the configuration of the wifi AP to allow additional MACs (ideally from a whitelist) from authenticated connections. This is probably not going to work.
  2. Use WDS mode - Wireless Distribution mode, Documentation about it here, sample of someone runnning it here
  3. Use "four address" mode - This is the easiest and I believe should work. http://wireless.kernel.org/en/users/Documentation/iw#Using_4-address_for_AP_and_client_mode
  4. encapsulate the connection - create a tunnel tap0 device using openvpn or similar.
share|improve this answer
    
Hi Matthew. I'll try the WDS mode and i'll give a feedback here. The number of macs of this AP should not be a problem, since it's a Motorola Access Point and it have a lot of clients connected on it, with any kind of Mac Filtering. Of course that our DHCP have enough leases to distribute on this network :) –  nwildner Mar 26 '13 at 10:41
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.