PPPoe with Idle status but internet connection still active!

Hello everyone,

I have noticed something strange on one of my Ipfire firewalls. My firewall is making the PPPoe connection to my ISP itself (the ISP router is configured in bridge mode).

Sometimes I notice that my PPPoe connection shows the status “Idle” on my firewall interface while the Internet connection is active. Only the OpenVPN (net-to-net) and Pakfire client connections cannot communicate over the Internet !
Have you ever noticed this ?
When this is the case I try to execute the command “/usr/local/bin/connscheduler reconnect” but this one once launched through the terminal never finishes ! (see below)

…I have to kill the command with “ctrl-c”!
To restore the PPPoe connection to the “connected” state and then be able to restore the n2n OpenVPN connections and allow pakfire to work, I have to run the following command “/etc/init.d/network restart red”

It is very strange this “Idle” state of the PPPoe connection and the fact that the Internet connection is partially working !

Is this a bug?

(My config: ASUSTeK COMPUTER INC. ‐ P9D-C Series | IPFire 2.27 - Core Update 172 | Intel(R) Core™ i3-4130T CPU @ 2.90GHz x2)

Do you have a dynamic IP? Can you check if this happens due to a DHCP renegotiation with the provider, associated with an IP address change?

Hi @cfusco,
Thanks for your reply.
No my IP is fix :wink:
Have a nice day

I suspect it depends on the implementation of PPOE of your provider. For example, it might be related to Dial-on-Demand routing?. Maybe you could open a ticket with Swisscom?

but… “/usr/local/bin/connscheduler reconnect ” should allow a reconnection…this “Idle” status is not displayed all the time…for 2 or 3 months I can have the “connected” status displayed correctly and sometimes…it’s the “idle” status that appears and when it’s like that I’m obliged to either restart the firewall, or do a simple network restart on the Red interface.

When the reconnect from the connection scheduler doesn’t work then that suggests that the interface has actually lost its connection for some reason so that a restart of the red interface is required.

What messages are in the red system logs for the time period when the interface changes from connected to idle and from when you try the reconnect and for when you do the complete red restart.

Below you can see the log on the RED interface. The problem occurred at 00:45 and I reconnected the interface correctly this morning at 11:45

00:45:21	pppd[2254]:	Modem hangup
00:45:21	pppd[2254]:	Connect time 1644.1 minutes.
00:45:21	pppd[2254]:	Sent 3927835687 bytes, received 522786134 bytes.
00:45:21	pppd[2254]:	Connection terminated.
00:45:22	pppd[2254]:	Exit.
00:45:23	pppd[22584]:	Plugin rp-pppoe.so loaded.
00:45:23	pppd[22584]:	PPPoE plugin from pppd 2.4.9
00:45:23	pppd[22584]:	pppd 2.4.9 started by root, uid 0
00:46:38	pppd[22584]:	Timeout waiting for PADO packets
00:46:38	pppd[22584]:	Unable to complete PPPoE Discovery
00:46:38	pppd[22584]:	Exit.
00:46:39	pppd[22961]:	Plugin rp-pppoe.so loaded.
00:46:39	pppd[22961]:	PPPoE plugin from pppd 2.4.9
00:46:39	pppd[22961]:	pppd 2.4.9 started by root, uid 0
00:46:44	pppd[22961]:	PPP session is 1
00:46:44	pppd[22961]:	Connected to 9e:52:c3:e1:13:cc via interface red0
00:46:44	pppd[22961]:	Using interface ppp0
00:46:44	pppd[22961]:	Connect: ppp0 <--> red0
00:46:47	pppd[22961]:	CHAP authentication failed
00:46:47	pppd[22961]:	CHAP authentication failed
00:46:47	pppd[22961]:	Modem hangup
00:46:47	pppd[22961]:	Connection terminated.
00:46:47	pppd[22961]:	Exit.
00:47:08	pppd[23221]:	Plugin rp-pppoe.so loaded.
00:47:08	pppd[23221]:	PPPoE plugin from pppd 2.4.9
00:47:08	pppd[23221]:	pppd 2.4.9 started by root, uid 0
00:47:13	pppd[23221]:	PPP session is 1
00:47:13	pppd[23221]:	Connected to 9e:52:c3:e1:13:cc via interface red0
00:47:13	pppd[23221]:	Using interface ppp0
00:47:13	pppd[23221]:	Connect: ppp0 <--> red0
00:47:16	pppd[23221]:	CHAP authentication succeeded
00:47:16	pppd[23221]:	CHAP authentication succeeded
00:47:16	pppd[23221]:	peer from calling number 9E:52:C3:E1:13:CC authorized
00:47:16	pppd[23221]:	local IP address 41.11.112.88
00:47:16	pppd[23221]:	remote IP address 211.2.201.31
00:47:16	pppd[23221]:	primary DNS address 195.186.4.162
00:47:16	pppd[23221]:	secondary DNS address 195.186.1.162
11:45:23	pppd[23221]:	Terminating on signal 15
11:45:23	pppd[23221]:	Connect time 658.1 minutes.
11:45:23	pppd[23221]:	Sent 1478556133 bytes, received 688863690 bytes.
11:45:23	pppd[23221]:	Connection terminated.
11:45:23	pppd[23221]:	Exit.
11:45:26	pppd[9311]:	Plugin rp-pppoe.so loaded.
11:45:26	pppd[9311]:	PPPoE plugin from pppd 2.4.9
11:45:26	pppd[9311]:	pppd 2.4.9 started by root, uid 0
11:45:31	pppd[9311]:	PPP session is 1
11:45:31	pppd[9311]:	Connected to 9e:52:c3:e1:13:cc via interface red0
11:45:31	pppd[9311]:	Using interface ppp0
11:45:31	pppd[9311]:	Connect: ppp0 <--> red0
11:45:34	pppd[9311]:	CHAP authentication succeeded
11:45:34	pppd[9311]:	CHAP authentication succeeded
11:45:34	pppd[9311]:	peer from calling number 9E:52:C3:E1:13:CC authorized
11:45:34	pppd[9311]:	local IP address 41.11.112.88
11:45:34	pppd[9311]:	remote IP address 211.2.201.31
11:45:34	pppd[9311]:	primary DNS address 195.186.4.162
11:45:34	pppd[9311]:	secondary DNS address 195.186.1.162

modem hangup and connection terminated are quite definitive statements, the interface at that point seems to me pretty much gone, therefore you need to request a new one. Why? no idea, but again to me it seems coming from the provider. Are you sure there is no setting in your provider modem to prevent the connection from going idle?

EDIT: you should edit your message to remove your IP address, for privacy precautions.
EDIT2: what about this? Did you try to set Idle timeout to 0, as recommended in the wiki linked before?

2 Likes

Thanks @cfusco …Don’t worry…IP is fake :wink:
About EDIT2, actually Idle timeout is set to 15…i can try to set to 0 because i’ve Fiber !
I hadn’t paid attention to this setting!..thanks…I’ll apply it and keep an eye on it…thanks a lot for your assistance :wink: