Replies: 2 comments
-
Please create a proper issue of this, no need to waste time in discussions. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Ok, will do. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi everyone,
I have a curious observation, and I am not quite sure, if I am using the driver wrong, or I encountered a bug. The LCP-Statemachine gets stuck after calling net_if_down on the PPP interface. Do I need to reset the driver somehow?
Obeserved behaviour
I am running a custom AT-Command modem driver that hands over to the Zephyr-PPP driver after successfully establishing a mobile link.
When the modem unilaterally terminates the PPP link (see log below) the PPP-driver switches to phase "DEAD".
The AT-Command driver then takes over, calls
net_if_down
, reestablishes the mobile connection and callsnet_if_up
on the ppp-interface.The LCP-Statemachine then gets stuck in state "PPP_STOPPED".
Solution
The problem goes away if I reset
lcp.fsm.state
to "PPP_INITIAL" inppp_link_terminated
(https://github.com/zephyrproject-rtos/zephyr/blob/main/subsys/net/l2/ppp/link.c#L115):To Reproduce
Unfortuantely I have no easy way to reproduce this without a modem that terminates the connection. If someone points me to a testsuite where I could add this as a test, I would be happy to do so.
Expected behavior
The statemachine should start from the same initial state each time ppp_start is called.
Impact
This bug makes the PPP driver unusable in a commercial product.
Logs and console output
Environment (please complete the following information):
Beta Was this translation helpful? Give feedback.
All reactions