Hardware: ESP-12F
Core Version: 2.3.0
How to ArduinoIDE on Windows with IP-FORWARD?
IP-forwarding is usually for routers or cores with at least 2 IP interfaces.
You could enable IP forwarding within lwip, so a client of the AP network could talk with other hosts on the STA side.
Is this really what you want ?
I have already tried this with the nodemcu firmware (lua), per
areresearch's instructions. It requires a routing rule in the router, so
that it knows to forward packets destined to clients connected the SOFTAP
to the STA address. A few other minor things also need to be setup, like a
dns forwarder, but it works.
I was able to stream 30mins of netflix through the ESP without a hitch
(router <-> ESP <-> laptop).
This tells me that the ESP is fully capable of acting like a transparent
access point for a wifi extender, or as a real mesh node (e.g. with
B.A.T.M.A.N. or something).
I just wish somebody with the knowhow in lwip and network meshes could take
an interest and implement this.
In addition, I also know that somebody implemented a soft NAT for the ESP.
On May 22, 2017 4:16 PM, "david gauchard" notifications@github.com wrote:
IP-forwarding is usually for routers or cores with at least 2 IP
interfaces.
You could enable IP forwarding within lwip, so a client of the AP network
could talk with other hosts on the STA side.
Is this really what you want ?—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/esp8266/Arduino/issues/3243#issuecomment-303208202,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQC6BvhPHGJhTp_1SyZeCo_aAe-0W0fdks5r8e0TgaJpZM4NaZ2j
.
You could try IP_FORWARD = 1
find tools/sdk/lwip/include/lwipopts.h, change IP_FORWARD to 1
then recompile from tools/sdk/lwip/src/ with make release
(before that you should backup tools/sdk/liblwip*.a)
about soft nat, a lwip proper patch is needed (or tell your internet modem to do so :) )
Considering #1924, are we still willing to directly route between AP clients and STA peers ?
As said above, this needs a routing rule in the host network router (unless we do NAT too).
Do we have enough RAM for useful NAT?
This project does NAT
@NeoCat has a branch with Napt implemented in lwip (I think). It has an api for setting things up.
I had a quick look. It is indeed implemented in lwip, and it seems to be clean.
@NeoCat have you considered to propose your work to lwip guys ?
hi there I tried setting IP_FORWARD=1 both in lwip and lwip2 . I rebuilt the libs but with no succes any suggestions?
I have already tried this with the nodemcu firmware (lua), per areresearch's instructions. It requires a routing rule in the router, so that it knows to forward packets destined to clients connected the SOFTAP to the STA address. A few other minor things also need to be setup, like a dns forwarder, but it works. I was able to stream 30mins of netflix through the ESP without a hitch (router <-> ESP <-> laptop). This tells me that the ESP is fully capable of acting like a transparent access point for a wifi extender, or as a real mesh node (e.g. with B.A.T.M.A.N. or something). I just wish somebody with the knowhow in lwip and network meshes could take an interest and implement this. In addition, I also know that somebody implemented a soft NAT for the ESP.
…
On May 22, 2017 4:16 PM, "david gauchard" @.*> wrote: IP-forwarding is usually for routers or cores with at least 2 IP interfaces. You could enable IP forwarding within lwip, so a client of the AP network could talk with other hosts on the STA side. Is this really what you want ? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#3243 (comment)>, or mute the thread https://github.com/notifications/unsubscribe-auth/AQC6BvhPHGJhTp_1SyZeCo_aAe-0W0fdks5r8e0TgaJpZM4NaZ2j .
Hello,
You did wifi mesh node, for that what you used?
arduino ide or SDK or other?
As a general rule, doing custom builds of internal libs like lwip isn't meant for normal users. However, it is ok to support it for advanced users in some manner.
lwip2 currently supports being manually built with different config param than the default, including IP_FORWARD enabled. It is not automatic, and must be done from command line with a git install of the core, but it can be done, and it is documented in a README in the lwip build directory and in @d-a-v 's link layer repo.
Closing this as resolved.
Most helpful comment
@NeoCat has a branch with Napt implemented in lwip (I think). It has an api for setting things up.