1
24.7 Production Series / Re: USB PPP 4G interface eventually goes down
« on: September 02, 2024, 09:53:28 am »Has no influence on disconnects probably. Different APNs may have different results, some being IPv4 only, some have public IPs while some stick you behind CGNAT. IPv6 may require a special APN and can influence IPv4 as well. You need to check with VF.
Definitely have the correct APN. Just happened to me again, understand I need to be watching /var/log/ppps/latest.log. When it stops responding:
Code: [Select]
<30>1 2024-09-02T05:55:32+00:00 hostname ppp 62108 - [meta sequenceId="1"] [opt1_link0] MODEM: can't ioctl(TIOCMGET) /dev/cuaU0.2: Device not confi
gured
<30>1 2024-09-02T05:55:32+00:00 hostname ppp 62108 - [meta sequenceId="1"] [opt1_link0] MODEM: can't ioctl(TIOCMGET) /dev/cuaU0.2: Device not confi
gured
<30>1 2024-09-02T05:55:32+00:00 hostname ppp 62108 - [meta sequenceId="2"] [opt1_link0] Link: DOWN event
<30>1 2024-09-02T05:55:32+00:00 hostname ppp 62108 - [meta sequenceId="3"] [opt1_link0] LCP: Down event
<30>1 2024-09-02T05:55:32+00:00 hostname ppp 62108 - [meta sequenceId="4"] [opt1_link0] LCP: state change Opened --> Starting
<30>1 2024-09-02T05:55:32+00:00 hostname ppp 62108 - [meta sequenceId="5"] [opt1_link0] Link: Leave bundle "opt1"
<30>1 2024-09-02T05:55:32+00:00 hostname ppp 62108 - [meta sequenceId="6"] [opt1] Bundle: Status update: up 0 links, total bandwidth 9600 bps
<30>1 2024-09-02T05:55:32+00:00 hostname ppp 62108 - [meta sequenceId="7"] [opt1] IPCP: Close event
<30>1 2024-09-02T05:55:32+00:00 hostname ppp 62108 - [meta sequenceId="8"] [opt1] IPCP: state change Opened --> Closing
<30>1 2024-09-02T05:55:32+00:00 hostname ppp 62108 - [meta sequenceId="9"] [opt1] IPCP: SendTerminateReq #4
<30>1 2024-09-02T05:55:32+00:00 hostname ppp 62108 - [meta sequenceId="10"] [opt1] IPCP: LayerDown
<13>1 2024-09-02T05:55:32+00:00 hostname ppp 31425 - [meta sequenceId="11"] ppp-linkdown: executing on ppp0 for inet
<30>1 2024-09-02T05:55:33+00:00 hostname ppp 62108 - [meta sequenceId="12"] [opt1] IFACE: Down event
<30>1 2024-09-02T05:55:33+00:00 hostname ppp 62108 - [meta sequenceId="13"] [opt1] IFACE: Rename interface ppp0 to ppp0
<30>1 2024-09-02T05:55:33+00:00 hostname ppp 62108 - [meta sequenceId="14"] [opt1] IPV6CP: Close event
<30>1 2024-09-02T05:55:33+00:00 hostname ppp 62108 - [meta sequenceId="15"] [opt1] IPV6CP: state change Stopped --> Closed
<30>1 2024-09-02T05:55:33+00:00 hostname ppp 62108 - [meta sequenceId="16"] [opt1] IPCP: Down event
<30>1 2024-09-02T05:55:33+00:00 hostname ppp 62108 - [meta sequenceId="17"] [opt1] IPCP: LayerFinish
<30>1 2024-09-02T05:55:33+00:00 hostname ppp 62108 - [meta sequenceId="18"] [opt1] Bundle: No NCPs left. Closing links...
<30>1 2024-09-02T05:55:33+00:00 hostname ppp 62108 - [meta sequenceId="19"] [opt1] IPCP: state change Closing --> Initial
<30>1 2024-09-02T05:55:33+00:00 hostname ppp 62108 - [meta sequenceId="20"] [opt1] IPV6CP: Down event
<30>1 2024-09-02T05:55:33+00:00 hostname ppp 62108 - [meta sequenceId="21"] [opt1] IPV6CP: state change Closed --> Initial
<30>1 2024-09-02T05:55:33+00:00 hostname ppp 62108 - [meta sequenceId="22"] [opt1_link0] LCP: LayerDown
<30>1 2024-09-02T05:55:33+00:00 hostname ppp 62108 - [meta sequenceId="23"] [opt1_link0] Link: reconnection attempt 1 in 2 seconds
Then connection failure attempts repeated indefinitely:
Code: [Select]
<30>1 2024-09-02T07:36:30+00:00 hostname ppp 88658 - [meta sequenceId="8560"] [opt1_link0] MODEM: chat script failed
<30>1 2024-09-02T07:36:30+00:00 hostname ppp 88658 - [meta sequenceId="8561"] [opt1_link0] Link: DOWN event
<30>1 2024-09-02T07:36:30+00:00 hostname ppp 88658 - [meta sequenceId="8562"] [opt1_link0] LCP: Down event
<30>1 2024-09-02T07:36:30+00:00 hostname ppp 88658 - [meta sequenceId="8563"] [opt1_link0] Link: reconnection attempt 2 in 4 seconds
<30>1 2024-09-02T07:36:34+00:00 hostname ppp 88658 - [meta sequenceId="8564"] [opt1_link0] Link: reconnection attempt 2
<30>1 2024-09-02T07:36:35+00:00 hostname ppp 88658 - [meta sequenceId="8565"] [opt1_link0] CHAT: The modem is not responding to "AT" at MomCmd: labeell.
Once again, after a reboot it comes up fine:
Code: [Select]
<30>1 2024-09-02T07:38:08+00:00 hostname ppp 6350 - [meta sequenceId="1"] Multi-link PPP daemon for FreeBSD
<30>1 2024-09-02T07:38:08+00:00 hostname ppp 6350 - [meta sequenceId="2"]
<30>1 2024-09-02T07:38:08+00:00 hostname ppp 6350 - [meta sequenceId="3"] process 6350 started, version 5.9
<30>1 2024-09-02T07:38:08+00:00 hostname ppp 6350 - [meta sequenceId="4"] web: web is not running
<30>1 2024-09-02T07:38:08+00:00 hostname ppp 6350 - [meta sequenceId="5"] [opt1] Bundle: Interface ng0 created
<30>1 2024-09-02T07:38:08+00:00 hostname ppp 6350 - [meta sequenceId="6"] [opt1_link0] Link: OPEN event
<30>1 2024-09-02T07:38:08+00:00 hostname ppp 6350 - [meta sequenceId="7"] [opt1_link0] LCP: Open event
<30>1 2024-09-02T07:38:08+00:00 hostname ppp 6350 - [meta sequenceId="8"] [opt1_link0] LCP: state change Initial --> Starting
<30>1 2024-09-02T07:38:08+00:00 hostname ppp 6350 - [meta sequenceId="9"] [opt1_link0] LCP: LayerStart
<30>1 2024-09-02T07:38:09+00:00 hostname ppp 6350 - [meta sequenceId="10"] [opt1_link0] CHAT: +CGDCONT=1,"IP","live.vodafone.com"
<30>1 2024-09-02T07:38:09+00:00 hostname ppp 6350 - [meta sequenceId="11"] [opt1_link0] CHAT: Detected Custom modem.
<30>1 2024-09-02T07:38:09+00:00 hostname ppp 6350 - [meta sequenceId="12"] [opt1_link0] CHAT: Dialing server at *99#...
<30>1 2024-09-02T07:38:09+00:00 hostname ppp 6350 - [meta sequenceId="13"] [opt1_link0] CHAT: ATDT*99#
<30>1 2024-09-02T07:38:09+00:00 hostname ppp 6350 - [meta sequenceId="14"] [opt1_link0] CHAT: Connected at 100000000.
<30>1 2024-09-02T07:38:09+00:00 hostname ppp 6350 - [meta sequenceId="15"] [opt1_link0] MODEM: chat script succeeded
<30>1 2024-09-02T07:38:09+00:00 hostname ppp 6350 - [meta sequenceId="16"] [opt1_link0] Link: UP event
<30>1 2024-09-02T07:38:09+00:00 hostname ppp 6350 - [meta sequenceId="17"] [opt1_link0] LCP: Up event
...
Wish I knew how to reinitialize the device like happens at boot so that it could be brought up again. I see plenty of similar issues being discussed with freebsd generally though so understand this is likely nothing directly related to opnsense.