esp-idf/tools/test_apps/protocols/pppos
David Cermak 6f1b8fe062 esp-modem: Remove esp-netif destroy from modem network glue code
To be in line with other interfaces, when deleting the driver and it's glue layer to esp-netif, we DO NOT delete the related esp-netif (since is was allocated and created outside of the glue code and it works the same way in esp-eth and esp-wifi driver/glue layers).

Closes https://github.com/espressif/esp-idf/issues/5486
2020-08-31 06:47:01 +00:00
..
main esp-modem: Remove esp-netif destroy from modem network glue code 2020-08-31 06:47:01 +00:00
app_test.py ppp-test: check if ppp interface is active and IP address correct before starting the test 2020-04-23 05:55:17 +00:00
CMakeLists.txt pppos_client: Add a test application for pppos_client 2020-04-14 21:46:07 +02:00
README.md pppos_client: Add a test application for pppos_client 2020-04-14 21:46:07 +02:00
sdkconfig.defaults pppos_client: Add a test application for pppos_client 2020-04-14 21:46:07 +02:00

PPP over Serial test

Testing connection of PPP client (ESP) to PPP server (raspberry pi)

Pin Assignment

ESP rpi
GPIO25 UART-RX
GPIO26 UART-TX
GND GND

Test workflow

  • Starts PPP server on a linux host
  • Starts PPPoS client on ESP board
  • Connects with both IPv4 and IPv6
  • Test IPv6 connection
    • Start server on ESP
    • Have linux host to connect and exchange some data
  • Test IPv4 connection
    • Start server on linux host
    • Connect with ESP to the server and exchange some data
  • Pass/fail

Manual test

Server side

sudo pppd /dev/ttyAMA0 115200 CONFIG_TEST_APP_PPP_SERVER_IP:TEST_APP_PPP_CLIENT_IP  modem local noauth debug nodetach dump nocrtscts

or with +ipv6 to support ipv6 assignment

IPv6 test

Connect to the ESP local link address and send data, e.g.

nc fe80::74d7:edc5:9907:5457 2222

IPv4 tst

Server side expects to run tcp server on port 2222

nc -l 2222

Test environment

configuration Example_PPP see wikis/test-docs/example-test-env#example_ppp