PPP support(over serial) for esp-idf v2.0

[rajkumar patel]

hello,

i'm curious about a statement which is provided in updated menuconfig options' list in the latest idf.
inside menuconfig -

component config ---> LWIP ----> Enable PPP support (new/experimental)

when i query a ''help'' for this option i am seeing a message showing me following lines on my console :
[img]

menuconfig window for ppp settings

menuconfig.JPG (29.96 KiB) Viewed 11128 times

[/img]

following lines are pretty obscure :

Enable PPP stack. Now only PPP over serial is possible.
PPP over serial support is experimental and unsupported.

so, my questions are :
1. ppp over serial functionality is supported or not?]

2. i'm using idf v2.0 and i wanna used pppos functionality.
For my idf version no such ppp enabling option is provided in menuconfig.
will pppos work for my version too?

3. if support is not availble(for v2.0), then is there any patch or somethis so that i could enable this support?

4. & if availble, could we users get the example code(if available) for PPPos?

I know, inside components\lwip\include\lwip\lwip\opt.h i can enable PPP_SUPPORT macro and hence PPPOS_SUPPORT will also come alive;
like this can i start using pppos?

ESP_team and any one who are having answeres to the listed questions,
kindly, give your important comments.

thanks.

[loboris]

I've posted two examples earlier:
ESP32 with GSM modem - PPP over Serial (PPPoS) client example
and
Full example of using libcurl with ESP32 which also has PPPoS support.

There was a patch for earlier versions of esp-idf but it was removed when PPPoS support was include in esp-idf. You can still get it if you checkout commit 8eedcc29d8dc58040f0b9302a489f3c5505fa13b from ESP32-PPPOS-EXAMPLE.
What is the reason you don't want to use esp-idf v2.1 ?

[rajkumar patel]

hi loboris,

many gratitudes for your quick response.
however, there's no any strong reason for not movig for v2.1. but for my application, i've carried out all the tests and feasibility on v2.0 only. so i'm trying to get this support for this version only(if possible).
i check out the codes provided by you for more clarity on ppp.

using v2.0 could keep me away form having full fledged support of pppos?

[ESP_Angus]

PPP over serial support is marked as unsupported in V2.1 and in the current master branch V3.0-dev versions.

The reason for marking it as unsupported is as follows: It was community developed and contributed (thanks loboris). We thought it was so useful (and it requires modifications to the IDF core), therefore we merged the support to our main repository.

However, although we ran some of our own tests with PPP/Serial we (Espressif) don't produce any reference designs or lists of supported serial devices which work with IDF PPP over Serial. We also don't run the same suite of automated & manual tests for PPP that we do for WiFi and Ethernet.

The PPP over Serial support is also not fully integrated into the "tcpip_adapter" which sends events for connection/disconnection/etc of other kinds of network interfaces (ie WiFi, Ethernet).

If you need PPP support then I suggest enabling this functionality and using it. If you experience issues with a particular PPP/Serial configuration then we'll do our best to help you solve them. However if you experience problems you will need to be prepared to "get your hands dirty" and debug some of the LWIP PPP code yourself. All of the relevant source code is available as part of ESP-IDF.

On a general note, I'd recommend updating to IDF V2.1 if you can. The release notes have a list of possible compatibility issues, but this list is not long (V2.1 was a minor release.)

Regarding examples, there is one in the IDF source code (thanks again, loboris!):
https://github.com/espressif/esp-idf/tr ... pos_client

[loboris]

...thanks loboris...

I think you should also credit amuzyka-grinn who was the first one to implement the PPPoS support.

[ESP_Angus]

...thanks loboris...

I think you should also credit amuzyka-grinn who was the first one to implement the PPPoS support.

Oops, I should indeed. Mis-remembered!