All Projects → martin-ger → esp-lwip

martin-ger / esp-lwip

Licence: other
Fork of esp-lwIP with NAT feature

Programming Languages

c
50402 projects - #5 most used programming language
CMake
9771 projects
Makefile
30231 projects
C++
36643 projects - #6 most used programming language
perl
6916 projects
HTML
75241 projects

Projects that are alternatives of or similar to esp-lwip

Server Go
🎨OpenIoTHub Server[内网穿透和物联网设备管理服务器]
Stars: ✭ 127 (+746.67%)
Mutual labels:  esp32, nat
Esp Idf Nat Example
ESP-IDF example project with NAT setup.
Stars: ✭ 41 (+173.33%)
Mutual labels:  esp32, nat
Esp32 nat router
A simple NAT Router for the ESP32
Stars: ✭ 226 (+1406.67%)
Mutual labels:  esp32, nat
Gateway Go
🎁GateWay Client for OpenIoTHub[云易连访问内网端口和设备的网关]
Stars: ✭ 127 (+746.67%)
Mutual labels:  esp32, nat
esp-open-lwip
ESP8266 lwIP library with NAT, SLIP, ENC28j60 Ethernet, and routing support
Stars: ✭ 58 (+286.67%)
Mutual labels:  nat, napt
pycom-ruuvitag
Pycom MicroPython RuuviTag BLE Sensor Beacon scanner
Stars: ✭ 18 (+20%)
Mutual labels:  esp32
docker-esp-sdk
Executable docker image to easily compile and flash for the ESP32 and ESP8266
Stars: ✭ 30 (+100%)
Mutual labels:  esp32
codos
Un sistema de detección del CO2 para el aula
Stars: ✭ 41 (+173.33%)
Mutual labels:  esp32
DuinoDCX
WiFi remote controller for the Behringer Ultradrive.
Stars: ✭ 67 (+346.67%)
Mutual labels:  esp32
FastTunnel
expose a local server to the internet. 高性能跨平台的内网穿透解决方案 远程内网计算机 域名访问内网站点 反向代理内网服务 端口转发 http代理
Stars: ✭ 815 (+5333.33%)
Mutual labels:  nat
FT800-FT813
Multi-Platform C code Library for EVE graphics controllers from FTDI / Bridgetek (FT810, FT811, FT812, FT813, BT815, BT816, BT817, BT818)
Stars: ✭ 80 (+433.33%)
Mutual labels:  esp32
ESP32CommandStation
An ESP32 based DCC Command Station with integrated OpenLCB (LCC)
Stars: ✭ 69 (+360%)
Mutual labels:  esp32
ESPHome-Air-Quality-Monitor
ESPHome configuration for a DIY indoor air quality monitor for CO₂ concentration, PM2.5 and PM10 concentrations, and temperature, humidity and pressure
Stars: ✭ 42 (+180%)
Mutual labels:  esp32
PCF8575 library
Library to use i2c digital expander with arduino, esp8266 and esp32. Can read write digital value with only 2 wire (perfect for ESP-01).
Stars: ✭ 28 (+86.67%)
Mutual labels:  esp32
ormesh
[UNMAINTAINED: Try https://github.com/cmars/oniongrok instead] onion-routed mesh
Stars: ✭ 65 (+333.33%)
Mutual labels:  nat
ESP32-TFT-Library-ILI9486
A library for 3.5 inch RPi LCD (A) 320x480 display from Waveshare
Stars: ✭ 67 (+346.67%)
Mutual labels:  esp32
EasyBuzzer
The Beep Library For Arduino
Stars: ✭ 63 (+320%)
Mutual labels:  esp32
supla-arduino
SuplaDevice library for Arduino IDE that helps you build your own IoT device based on ESPx and Arduino Mega boards.
Stars: ✭ 25 (+66.67%)
Mutual labels:  esp32
n2d
An easy to use ESP8266 flash tool with built-in support for the Deauther Project.
Stars: ✭ 136 (+806.67%)
Mutual labels:  esp32
ESP32-R4sGate-for-Redmond
ESP32 Ready4Sky (R4S) Gateway for Redmond+ devices
Stars: ✭ 117 (+680%)
Mutual labels:  esp32
*Obsolete - NAPT ist now included in Espressif's esp-lwip*

To use NAPT with lwip on an ESP32, just replace the lwIP library from the 
lwIP component of the ESP-IDF with this one. This can be done by following 
these steps:

- Get this lib: git clone https://github.com/martin-ger/esp-lwip.git
- Rename or delete original lwIP library folder (/esp-idf/component/lwip/lwip)
- Copy the lwIP library with NAT repository folder from step 1 to 
  /esp-idf/component/lwip and rename it to lwip.

Now if you build a project with the ESP-IDF it will use the lwIP library 
with NAT.

In order for the NAT feature to work the option "Enable copy between Layer2 
and Layer3 packets" must be enabled in the ESP-IDF project configuration. 
An ESP-IDF project can be configured by calling make menuconfig 
(or idf.py menuconfig for CMake setups). In the configuration go to 
Component config -> LWIP.

In the code of your firmware enable NAPT for the softAP interface by calling 
the ip_napt_enable function from lwipt_napt.h header file.

See: https://github.com/jonask1337/esp-idf-nat-example for usage.

---

INTRODUCTION

lwIP is a small independent implementation of the TCP/IP protocol suite.

The focus of the lwIP TCP/IP implementation is to reduce the RAM usage
while still having a full scale TCP. This making lwIP suitable for use
in embedded systems with tens of kilobytes of free RAM and room for
around 40 kilobytes of code ROM.

lwIP was originally developed by Adam Dunkels at the Computer and Networks
Architectures (CNA) lab at the Swedish Institute of Computer Science (SICS)
and is now developed and maintained by a worldwide network of developers.

FEATURES

  * IP (Internet Protocol, IPv4 and IPv6) including packet forwarding over
    multiple network interfaces
  * ICMP (Internet Control Message Protocol) for network maintenance and debugging
  * IGMP (Internet Group Management Protocol) for multicast traffic management
  * MLD (Multicast listener discovery for IPv6). Aims to be compliant with 
    RFC 2710. No support for MLDv2
  * ND (Neighbor discovery and stateless address autoconfiguration for IPv6).
    Aims to be compliant with RFC 4861 (Neighbor discovery) and RFC 4862
    (Address autoconfiguration)
  * DHCP, AutoIP/APIPA (Zeroconf) and (stateless) DHCPv6
  * UDP (User Datagram Protocol) including experimental UDP-lite extensions
  * TCP (Transmission Control Protocol) with congestion control, RTT estimation
    fast recovery/fast retransmit and sending SACKs
  * raw/native API for enhanced performance
  * Optional Berkeley-like socket API
  * TLS: optional layered TCP ("altcp") for nearly transparent TLS for any
    TCP-based protocol (ported to mbedTLS) (see changelog for more info)
  * PPPoS and PPPoE (Point-to-point protocol over Serial/Ethernet)
  * DNS (Domain name resolver incl. mDNS)
  * 6LoWPAN (via IEEE 802.15.4, BLE or ZEP)


APPLICATIONS

  * HTTP server with SSI and CGI (HTTPS via altcp)
  * SNMPv2c agent with MIB compiler (Simple Network Management Protocol), v3 via altcp
  * SNTP (Simple network time protocol)
  * NetBIOS name service responder
  * MDNS (Multicast DNS) responder
  * iPerf server implementation
  * MQTT client (TLS support via altcp)


LICENSE

lwIP is freely available under a BSD license.


DEVELOPMENT

lwIP has grown into an excellent TCP/IP stack for embedded devices,
and developers using the stack often submit bug fixes, improvements,
and additions to the stack to further increase its usefulness.

Development of lwIP is hosted on Savannah, a central point for
software development, maintenance and distribution. Everyone can
help improve lwIP by use of Savannah's interface, Git and the
mailing list. A core team of developers will commit changes to the
Git source tree.

The lwIP TCP/IP stack is maintained in the 'lwip' Git module and
contributions (such as platform ports) are in the 'contrib' Git module.

See doc/savannah.txt for details on Git server access for users and
developers.

The current Git trees are web-browsable:
  http://git.savannah.gnu.org/cgit/lwip.git
  http://git.savannah.gnu.org/cgit/lwip/lwip-contrib.git

Submit patches and bugs via the lwIP project page:
  http://savannah.nongnu.org/projects/lwip/

Continuous integration builds (GCC, clang):
  https://travis-ci.org/yarrick/lwip-merged


DOCUMENTATION

Self documentation of the source code is regularly extracted from the current
Git sources and is available from this web page:
  http://www.nongnu.org/lwip/

There is now a constantly growing wiki about lwIP at
  http://lwip.wikia.com/wiki/LwIP_Wiki

Also, there are mailing lists you can subscribe at
  http://savannah.nongnu.org/mail/?group=lwip
plus searchable archives:
  http://lists.nongnu.org/archive/html/lwip-users/
  http://lists.nongnu.org/archive/html/lwip-devel/

lwIP was originally written by Adam Dunkels:
  http://dunkels.com/adam/

Reading Adam's papers, the files in docs/, browsing the source code
documentation and browsing the mailing list archives is a good way to
become familiar with the design of lwIP.

Adam Dunkels <[email protected]>
Leon Woestenberg <[email protected]>
Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].