2
1
I've looked around quite a bit and can't really find anything putting all the pieces together.
I'm using Debian and looking to connect to a wireless network and repeat the signal without using nat or any other unpleasantness.
ap -> wlan0 {debian} wlan1 -> repeated_ap_signal
I have two identical wireless nics, ath9k driver modules, and a router that supports 4 address mode.
From what I gather I need to have wlan0 connect to the ap as a client, and I need to turn on 4addr mode on wlan1, and bridge the two of them. Actual implementation is a little more confusing.
Do I still need to setup hostapd for wlan1 and set it to have an identical ssid/pw with the channel being 3 or more away from the one the ap is hosting?
Are there any special things that need to be set on the bridge for this to work?
Does 4addr mode need to be turned on for both wlan interfaces or only the "repeater" one?
Thanks!
Would DCHP leasing, where the ap handles it, work across something like this? – Peck – 2015-06-04T14:10:28.887
@Peck: I cannot see why not. After all, the initial DHCP request is just a message to the broadcast address, and the reply is a unicast without ARP. Even if it didn't, you could setup a local dhcp server dishing out IP addresses from a range not overlapping that of the main router, and a proxy_arp configuration which allows you to maintain ARP connections across wireless, the only (possible) stumbling block. – MariusMatutiae – 2015-06-04T14:27:17.673
Thanks. The part about enabling ipv4 forwarding is a little odd to me, since I want this all to be working at L2 how would that be effected? – Peck – 2015-06-04T16:27:03.070
@ Peck I understand, but you still need to enable IPv4 forwarding. Have you ever setup a bridged OpenVPN? It works at the L2 level, but you still have to allow IPv4 forwarding in sysctl.conf. – MariusMatutiae – 2015-06-04T16:59:31.483