› Forums › Network Management › Networking › Every 180 min provider kill my pppoe session with PADT
- This topic is empty.
-
AuthorPosts
-
September 25, 2014 at 7:37 am #44045
Boris
MemberHello, All.
I’m connect to new ISP (my client use this ISP) and have a problem 🙁 Thin client work on this connection closing every 180 min.
This unfriendly provider does not want to help me.Problem is:
Every 180 min this provider kill my ppp session with PADT frame. In support say: this gluck on my OS. And I need change OS to Windoze or using modem as router (In my condition router on router on router). They do not send this PADT on my device.
After googling i find:
Roaring Penguin PPPoE Version 3.6
drop down connection after receiving PADT for other device or session name. I see the patch for fix this. Tell me: – I need download and compile Roaring Penguin PPPoE with this patch. (Oh. My God, please, no! ) Or there is another solution.Below fragment of logs:
Sep 21 02:43:21 ns pppd[758]: pppd 2.4.3 started by root, uid 0
Sep 21 02:43:21 ns pppd[758]: Using interface ppp0
Sep 21 02:43:21 ns pppd[758]: Connect: ppp0 <--> /dev/pts/0
Sep 21 02:43:37 ns pppd[758]: PAP authentication succeeded
Sep 21 02:43:37 ns pppd[758]: local IP address 172.16.16.72
Sep 21 02:43:37 ns pppd[758]: remote IP address 85.90.204.62
Sep 21 05:43:37 ns pppd[758]: LCP terminated by peer
Sep 21 05:43:37 ns pppd[758]: Connect time 180.0 minutes.
Sep 21 05:43:37 ns pppd[758]: Sent 4312670 bytes, received 148679313 bytes.
Sep 21 05:43:37 ns pppd[758]: Modem hangup
Sep 21 05:43:37 ns pppd[758]: Connection terminated.
Sep 21 05:43:37 ns pppd[758]: Exit.Sep 21 02:43:22 ns pppoe[759]: PADS: Service-Name: ”
Sep 21 02:43:22 ns pppoe[759]: PPP session is 61046 (0xee76)
Sep 21 05:43:37 ns pppoe[759]: Session 61046 terminated — received PADT from peer
Sep 21 05:43:37 ns pppoe[759]: Sent PADTI do not know DSLAM, ADSL portocol, and other secrets of this field.
I think, in my case, ISP resets hung sessions and update dynamic IP for the entire pool. I want to get around the problem.With best regards.
BorisSeptember 30, 2014 at 6:15 am #53464Boris
MemberProblem solved.
As expected, source of the problem ISP.
Engineers operating the DSALM and ther prentice hands and a habit to lie.
Ancient billing.
Result: my lost time.
Shoot off engineers balls.
And rightly working line.Thank you, All.
-
AuthorPosts
- You must be logged in to reply to this topic.