Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have 2 wireless interfaces, one real (eth1) and one virtual (vt0), running on top of the same physical wireless adapter. Both have separate IP address spaces.

eth1 is connected to a laptop, and vt0 is connected to another system over p2p.

I cannot ping any system on the p2p system from the laptop as there is no bridging over eth1 and vt0. How do I achieve this? Tried with brctl, adding the vt0 and the eth1 interfaces to a bridge and then activating the bridge. DOesn't seem to work.

share|improve this question
up vote 1 down vote accepted

You cannot bridge to a WiFi client connection. That's why when you set up wireless bridging (WDS), you have to enable it on both ends. If you want to connect networks over a wireless link you must either configure WDS on both ends, use some form of NAT (sometimes called a "client bridge" but it actually NATs the MAC address), or use routing rather than bridging.

To preserve WiFi bandwidth (and for a few other historical reasons), the access point will only send non-broadcast traffic over the WiFi link if it's directed at one of its clients. Any machines connected to the virtual wireless interface are not clients of the access point connected to the real wireless interface. So the access point is not permitted to send packets bound for them over the real wireless link.

Sadly, WiFi is just enough like Ethernet to make people expect it to work the same way. But it is not wireless Ethernet. It's its own protocol with its own rules. WiFi-to-Wifi bridging is only supported with WDS on both ends.

share|improve this answer

Your Answer


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.