Is promiscuous mode needed for proxy arp?
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
I use a Raspberry Pi 3B+ with Rasbian Stretch and set it up with proxy arp following the tutorial from Debian: Bridging Network Connections with Proxy ARP to "bridge" eth0 to wlan0. According to this it is easy to set up proxy arp with:
rpi3 ~# echo 1 > /proc/sys/net/ipv4/conf/all/proxy_arp
rpi3 ~# echo 1 > /proc/sys/net/ipv4/ip_forward
rpi3 ~# ip route add 192.168.10.60/32 dev eth0
192.168.10.60 is the client on eth0 that should be "bridged" to wlan0.
But it doesn't work. I have to enable promiscuous mode on wlan0 to get it to work but could not find any hints to do this.
rpi3 ~# ip link set wlan0 promisc on
Is promiscuous mode needed for Stretch? If not, how can I avoid it?
updates:
Checked that rp_filter is set to 0.hostapd is not installed. wlan0 is in client mode and managed by wpa_supplicant.
raspberry-pi raspbian proxy-arp
asked May 29 at 21:17
Ingo
1387
add a comment |Â
up vote
0
down vote
favorite
I use a Raspberry Pi 3B+ with Rasbian Stretch and set it up with proxy arp following the tutorial from Debian: Bridging Network Connections with Proxy ARP to "bridge" eth0 to wlan0. According to this it is easy to set up proxy arp with:
rpi3 ~# echo 1 > /proc/sys/net/ipv4/conf/all/proxy_arp
rpi3 ~# echo 1 > /proc/sys/net/ipv4/ip_forward
rpi3 ~# ip route add 192.168.10.60/32 dev eth0
192.168.10.60 is the client on eth0 that should be "bridged" to wlan0.
But it doesn't work. I have to enable promiscuous mode on wlan0 to get it to work but could not find any hints to do this.
rpi3 ~# ip link set wlan0 promisc on
Is promiscuous mode needed for Stretch? If not, how can I avoid it?
updates:
Checked that rp_filter is set to 0.hostapd is not installed. wlan0 is in client mode and managed by wpa_supplicant.
raspberry-pi raspbian proxy-arp
asked May 29 at 21:17
Ingo
1387
have you set rp_filter to 0?
– Rui F Ribeiro
May 29 at 21:29
@RuiFRibeiro I haven't touched that settings but checking them, all possible pseudo files in/proc/ /sys/net/ipv4/conf/*/rp_filtercontain 0.
– Ingo
May 29 at 23:39
is wlan0 in hostapd/AP mode or just a client?
– Rui F Ribeiro
May 30 at 2:52
@RuiFRibeiro Have updated the question. wlan0 is in client mode.
– Ingo
May 30 at 11:51
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I use a Raspberry Pi 3B+ with Rasbian Stretch and set it up with proxy arp following the tutorial from Debian: Bridging Network Connections with Proxy ARP to "bridge" eth0 to wlan0. According to this it is easy to set up proxy arp with:
rpi3 ~# echo 1 > /proc/sys/net/ipv4/conf/all/proxy_arp
rpi3 ~# echo 1 > /proc/sys/net/ipv4/ip_forward
rpi3 ~# ip route add 192.168.10.60/32 dev eth0
192.168.10.60 is the client on eth0 that should be "bridged" to wlan0.
But it doesn't work. I have to enable promiscuous mode on wlan0 to get it to work but could not find any hints to do this.
rpi3 ~# ip link set wlan0 promisc on
Is promiscuous mode needed for Stretch? If not, how can I avoid it?
updates:
Checked that rp_filter is set to 0.hostapd is not installed. wlan0 is in client mode and managed by wpa_supplicant.
raspberry-pi raspbian proxy-arp
asked May 29 at 21:17
Ingo
1387
I use a Raspberry Pi 3B+ with Rasbian Stretch and set it up with proxy arp following the tutorial from Debian: Bridging Network Connections with Proxy ARP to "bridge" eth0 to wlan0. According to this it is easy to set up proxy arp with:
rpi3 ~# echo 1 > /proc/sys/net/ipv4/conf/all/proxy_arp
rpi3 ~# echo 1 > /proc/sys/net/ipv4/ip_forward
rpi3 ~# ip route add 192.168.10.60/32 dev eth0
192.168.10.60 is the client on eth0 that should be "bridged" to wlan0.
But it doesn't work. I have to enable promiscuous mode on wlan0 to get it to work but could not find any hints to do this.
rpi3 ~# ip link set wlan0 promisc on
Is promiscuous mode needed for Stretch? If not, how can I avoid it?
updates:
Checked that rp_filter is set to 0.hostapd is not installed. wlan0 is in client mode and managed by wpa_supplicant.
raspberry-pi raspbian proxy-arp
asked May 29 at 21:17
Ingo
1387
edited May 30 at 11:50
asked May 29 at 21:17
Ingo
1387
asked May 29 at 21:17
Ingo
1387
asked May 29 at 21:17
Ingo
1387
1387
have you set rp_filter to 0?
– Rui F Ribeiro
May 29 at 21:29
@RuiFRibeiro I haven't touched that settings but checking them, all possible pseudo files in/proc/ /sys/net/ipv4/conf/*/rp_filtercontain 0.
– Ingo
May 29 at 23:39
is wlan0 in hostapd/AP mode or just a client?
– Rui F Ribeiro
May 30 at 2:52
@RuiFRibeiro Have updated the question. wlan0 is in client mode.
– Ingo
May 30 at 11:51
add a comment |Â
have you set rp_filter to 0?
– Rui F Ribeiro
May 29 at 21:29
@RuiFRibeiro I haven't touched that settings but checking them, all possible pseudo files in/proc/ /sys/net/ipv4/conf/*/rp_filtercontain 0.
– Ingo
May 29 at 23:39
is wlan0 in hostapd/AP mode or just a client?
– Rui F Ribeiro
May 30 at 2:52
@RuiFRibeiro Have updated the question. wlan0 is in client mode.
– Ingo
May 30 at 11:51
have you set rp_filter to 0?
– Rui F Ribeiro
May 29 at 21:29
have you set rp_filter to 0?
– Rui F Ribeiro
May 29 at 21:29
@RuiFRibeiro I haven't touched that settings but checking them, all possible pseudo files in
/proc/ /sys/net/ipv4/conf/*/rp_filter contain 0.– Ingo
May 29 at 23:39
@RuiFRibeiro I haven't touched that settings but checking them, all possible pseudo files in
/proc/ /sys/net/ipv4/conf/*/rp_filter contain 0.– Ingo
May 29 at 23:39
is wlan0 in hostapd/AP mode or just a client?
– Rui F Ribeiro
May 30 at 2:52
is wlan0 in hostapd/AP mode or just a client?
– Rui F Ribeiro
May 30 at 2:52
@RuiFRibeiro Have updated the question. wlan0 is in client mode.
– Ingo
May 30 at 11:51
@RuiFRibeiro Have updated the question. wlan0 is in client mode.
– Ingo
May 30 at 11:51
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
0
down vote
Aparently, it is not possible to bridge ethernet frames between wireless in client mode and ethernet. e.g. It wont work.
Also, beware of injecting frames from others sources into an AP infrastructure as a client.
most Access Points (APs) will reject frames that have a source
address that didn’t authenticate with the AP.
answered May 30 at 12:39
Rui F Ribeiro
34.4k1268113
I know that bridging wireless to ethernet interface isn't possible on OSI layer 2 because lack of 4addr support. That is the reason why I want to work around this with proxy arp on layer 3. My internet router as access point does not reject frames. It responses. Otherwise I won't get responses in promiscuous mode on the raspi.
– Ingo
Jun 11 at 9:58
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
Aparently, it is not possible to bridge ethernet frames between wireless in client mode and ethernet. e.g. It wont work.
Also, beware of injecting frames from others sources into an AP infrastructure as a client.
most Access Points (APs) will reject frames that have a source
address that didn’t authenticate with the AP.
answered May 30 at 12:39
Rui F Ribeiro
34.4k1268113
I know that bridging wireless to ethernet interface isn't possible on OSI layer 2 because lack of 4addr support. That is the reason why I want to work around this with proxy arp on layer 3. My internet router as access point does not reject frames. It responses. Otherwise I won't get responses in promiscuous mode on the raspi.
– Ingo
Jun 11 at 9:58
add a comment |Â
up vote
0
down vote
Aparently, it is not possible to bridge ethernet frames between wireless in client mode and ethernet. e.g. It wont work.
Also, beware of injecting frames from others sources into an AP infrastructure as a client.
most Access Points (APs) will reject frames that have a source
address that didn’t authenticate with the AP.
answered May 30 at 12:39
Rui F Ribeiro
34.4k1268113
I know that bridging wireless to ethernet interface isn't possible on OSI layer 2 because lack of 4addr support. That is the reason why I want to work around this with proxy arp on layer 3. My internet router as access point does not reject frames. It responses. Otherwise I won't get responses in promiscuous mode on the raspi.
– Ingo
Jun 11 at 9:58
add a comment |Â
up vote
0
down vote
up vote
0
down vote
Aparently, it is not possible to bridge ethernet frames between wireless in client mode and ethernet. e.g. It wont work.
Also, beware of injecting frames from others sources into an AP infrastructure as a client.
most Access Points (APs) will reject frames that have a source
address that didn’t authenticate with the AP.
answered May 30 at 12:39
Rui F Ribeiro
34.4k1268113
Aparently, it is not possible to bridge ethernet frames between wireless in client mode and ethernet. e.g. It wont work.
Also, beware of injecting frames from others sources into an AP infrastructure as a client.
most Access Points (APs) will reject frames that have a source
address that didn’t authenticate with the AP.
answered May 30 at 12:39
Rui F Ribeiro
34.4k1268113
answered May 30 at 12:39
Rui F Ribeiro
34.4k1268113
answered May 30 at 12:39
Rui F Ribeiro
34.4k1268113
answered May 30 at 12:39
Rui F Ribeiro
34.4k1268113
34.4k1268113
I know that bridging wireless to ethernet interface isn't possible on OSI layer 2 because lack of 4addr support. That is the reason why I want to work around this with proxy arp on layer 3. My internet router as access point does not reject frames. It responses. Otherwise I won't get responses in promiscuous mode on the raspi.
– Ingo
Jun 11 at 9:58
add a comment |Â
I know that bridging wireless to ethernet interface isn't possible on OSI layer 2 because lack of 4addr support. That is the reason why I want to work around this with proxy arp on layer 3. My internet router as access point does not reject frames. It responses. Otherwise I won't get responses in promiscuous mode on the raspi.
– Ingo
Jun 11 at 9:58
I know that bridging wireless to ethernet interface isn't possible on OSI layer 2 because lack of 4addr support. That is the reason why I want to work around this with proxy arp on layer 3. My internet router as access point does not reject frames. It responses. Otherwise I won't get responses in promiscuous mode on the raspi.
– Ingo
Jun 11 at 9:58
I know that bridging wireless to ethernet interface isn't possible on OSI layer 2 because lack of 4addr support. That is the reason why I want to work around this with proxy arp on layer 3. My internet router as access point does not reject frames. It responses. Otherwise I won't get responses in promiscuous mode on the raspi.
– Ingo
Jun 11 at 9:58
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f446795%2fis-promiscuous-mode-needed-for-proxy-arp%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
have you set rp_filter to 0?
– Rui F Ribeiro
May 29 at 21:29
@RuiFRibeiro I haven't touched that settings but checking them, all possible pseudo files in
/proc/ /sys/net/ipv4/conf/*/rp_filtercontain 0.– Ingo
May 29 at 23:39
is wlan0 in hostapd/AP mode or just a client?
– Rui F Ribeiro
May 30 at 2:52
@RuiFRibeiro Have updated the question. wlan0 is in client mode.
– Ingo
May 30 at 11:51