4

I've read a lot of contradictory posts about this topic, but essentially what I need is for my Raspberry Pi to act as a Wi-Fi dongle for an Ethernet-enabled device. The Ethernet device connected to the Pi must be passed through to the same subnet of the wireless AP, as if it was connecting directly (the Pi cannot do any NAT!).

Apart from this, the Pi itself does not need any internet connectivity. Its sole function is to act as a wireless adapter for an Ethernet-only device.

With the help of things such as MAC spoofing, is this even remotely possible? I see plenty of products such as a TP link travel router that offer a "client" mode, which I presume the Pi can somehow emulate?

Note: I have a special usage scenario where I'm putting a publicly routed subnet over Wi-Fi for "server"-like devices that are supposed to be portable. Each device requires a public IP address but does not have Wi-Fi capabilities, hence no NAT can be used.

Greenonline
  • 2,969
  • 5
  • 27
  • 38

1 Answers1

2

From debian.org i have tested ProxyArp and DHCP relay with parprouted, dhcp-helper and avahi-daemon packages and it's work for me on Raspbian. My other computer (ethernet connected device) get his dhcp IP addr successfully trought the RPi with full IP connectivity.

Detail: I use bcm wlan0 RPi interface for internet wireless gateway (W.A.P on fire) wpa_supplicant connection and auth and not another wireless card. and RPi eth0 interface for the client .

sudo apt-get install parprouted dhcp-helper avahi-daemon

see the debian link for configuration.

parprouted is designed to monitor the ARP table and both proxy ARP requests and install matching /32 host routes. Running parprouted with the inside and outside interfaces handles the ARP and routing completely automatically. Note that the kernel's proxy ARP mechanism (/proc/sys/net/ipv4/conf/all/proxy_arp) is not required

parprouted does not handle packet forwarding nor DHCP or mDNS, so these features need to be enabled separately

Ephemeral
  • 2,167
  • 1
  • 8
  • 19