WiFi and pppos co-exist problems (IDFGH-2548)

[AxelLin]

• Module or chip used: ESP32-WROOM-32
• IDF version: v4.1-dev-1935-g647cb628a11a
• Build System: CMake
• Compiler version: xtensa-esp32-elf-gcc (crosstool-NG esp-2019r2) 8.2.0
• Operating System: Linux
• Power Supply: USB

1. If I start PPPoS first, then make wifi to join AP, I'm not able to get IP address.
   The device stuck at below messages:
   I (23480) net_utils: Joining AP: TEST_AP
   I (23574) phy: phy_version: 4180, cb3948e, Sep 12 2019, 16:39:13, 0, 0
   I (23576) wifi: mode : sta (24:0a:c4:15:2b:00)

   PS. It can get IP address if I don't start PPPoS.

2. If I start PPPoS first, then make ESP32 running as AP.
   I'm not able to join the ESP32 AP, it stuck with below messages:
   I (58802) wifi: new:<6,1>, old:<6,1>, ap:<6,1>, sta:<0,0>, prof:6
   I (58803) wifi: station: c8:ff:28:04:f8:09 join, AID=1, bgn, 40U
   I (104589) wifi: station: c8:ff:28:04:f8:09 leave, AID = 1, bss_flags is 134243, bss:0x3ffd3448
   I (104590) wifi: new:<6,0>, old:<6,1>, ap:<6,1>, sta:<0,0>, prof:6
   I (141975) wifi: new:<6,1>, old:<6,0>, ap:<6,1>, sta:<0,0>, prof:6
   I (141976) wifi: station: c8:ff:28:04:f8:09 join, AID=1, bgn, 40U
   I (187509) wifi: station: c8:ff:28:04:f8:09 leave, AID = 1, bss_flags is 134243, bss:0x3ffd3448
   I (187510) wifi: new:<6,0>, old:<6,1>, ap:<6,1>, sta:<0,0>, prof:6

3. If I start STA/AP first:

a)
When WiFi is in AP mde, I sometimes got below error message after PPPoS connected.
E (70041) wifi: age_bss: null bss

b) When WiFi is in AP or STA mode, the PPPoS shows wrong IP/Gateway address, see below:

I (22742) pppos_example: Modem PPP Started
I (22994) esp-netif_lwip-ppp: Connected
I (22995) esp-netif_lwip-ppp: Name Server1: 168.95.1.1
I (22995) esp-netif_lwip-ppp: Name Server2: 168.95.192.1
I (23000) net_utils: Unhandled IP event_id:5
I (23005) pppos_example: IP event! 5
I (23009) pppos_example: Modem Connect to PPP Server
I (23015) pppos_example: ~~~~~~~~~~~~~~
I (23019) pppos_example: IP : 0.0.0.0
I (23024) pppos_example: Netmask : 196.253.64.63
I (23030) pppos_example: Gateway : 0.0.0.0
I (23035) pppos_example: Name Server1: 168.95.1.1
I (23040) pppos_example: Name Server2: 168.95.192.1
I (23046) pppos_example: ~~~~~~~~~~~~~~
I (23050) pppos_example: GOT ip event!!!

I think you can easily reproduce the issue by combine pppos_client example with
wifi/getting_started/station/softAP or wifi/getting_started/station/station examples.

Above symptoms are 100% reproducable.

[AxelLin]

Hi @david-cermak
Can you commit a fix for this issue?

I just figure out why I got wrong IP/netmask/gateway on PPP interface.
In components/esp_netif/lwip/esp_netif_lwip_ppp.c
on_ppp_status_changed()

It uses "ip_event_ap_staipassigned_t evt"
for err = esp_event_post(IP_EVENT, netif->get_ip_event, &evt, sizeof(evt), 0);

However, in on_ip_event() it assumes:
ip_event_got_ip_t *event = (ip_event_got_ip_t *)event_data;

I think the fix is:
change "ip_event_ap_staipassigned_t evt = {}" to "ip_event_got_ip_t evt = {}" in on_ppp_status_changed.
And setup the corresponding fields in evt.
e.g.
evt.esp_netif = netif;
evt.ip_info = ipinfo;
I'm not sure if evt.ip_changed should be set or not.

[AxelLin]

BTW, there is a typo in
examples/protocols/pppos_client/main/pppos_client_main.c on_ip_event()

    ESP_LOGI(TAG, "Gateway     : " IPSTR, IP2STR(&event->ip_info.ip));

should change to
ESP_LOGI(TAG, "Gateway : " IPSTR, IP2STR(&event->ip_info.gw));

[david-cermak]

Hi @AxelLin

Thanks for the investigation and finding the bug!
I will look into it and provide fixes.

[AxelLin]

Hi @david-cermak

I'm wodering why I got below message:

E (48334) wifi: age_bss: null bss
E (56330) wifi: age_bss: null bss
E (56890) wifi: age_bss: null bss
E (71330) wifi: age_bss: null bss
E (71991) wifi: age_bss: null bss
E (89865) wifi: age_bss: null bss

It only happen when using AP+PPPoS and pretty easy to reproduce.
It looks like an error message, I'm not sure if I can just ignore it.

In AP+PPPoS case sometimes the AP will disappear and never back.
The only way to recover it is reboot device.
I'm not sure if it's related to above message.

[iosix]

I see the same behavior, if I wait until after PPP establishment AP works, and if I disconnect active sockets during establishment AP works, but if I have a socket open during establishment I lose the socket and AP connectivity (can't ping, etc). Robert Vogt IV CEO IOSiX, LLC 1300 Tefft Ct #1 Saline, MI 48176 Reception: (855) OBD-1939 Direct/Cell: +1-734-730-9690 robert@iosix.com

…

On Wed, Feb 12, 2020 at 1:40 AM Axel Lin ***@***.***> wrote: Hi @david-cermak <https://github.com/david-cermak> I'm wodering why I got below message: E (48334) wifi: age_bss: null bss E (56330) wifi: age_bss: null bss E (56890) wifi: age_bss: null bss E (71330) wifi: age_bss: null bss E (71991) wifi: age_bss: null bss E (89865) wifi: age_bss: null bss It only happen when using AP+PPPoS and pretty easy to reproduce. It looks like an error message, I'm not sure if I can just ignore it. In AP+PPPoS case sometimes the AP will disappear and never back. The only way to recover it is reboot device. I'm not sure if it's related to above message. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#4634?email_source=notifications&email_token=AAUXMB734O32RXAGUEJCFVTRCOKWLA5CNFSM4KHQQMSKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOELPTSQQ#issuecomment-585054530>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAUXMB4T6EUG5DSYGRLIVW3RCOKWLANCNFSM4KHQQMSA> .

[liuzfesp]

HI @AxelLin, the log "age_bss: null bss" is not a real bug, just ignore it, we will remove it in later IDF release.