That's interesting.. I'm using exetel as well (at home), with pppoe to a pure-bridge adsl modem. According to my logs, the last time it reconnected was 10:12am on Nov 10th. (Saturday, so after the changes you mention to their backend) I didn't even notice, so it seems this didn't effect all clients. This is on Ubuntu 12.04 LTS, so maybe something changed in pppd? Nov 10 10:12:21 penfold pppd[1588]: Serial link appears to be disconnected. Nov 10 10:12:21 penfold pppd[1588]: Connect time 2786.4 minutes. Nov 10 10:12:21 penfold pppd[1588]: Sent 1706758826 bytes, received 2646704198 bytes. ... Nov 10 10:12:52 penfold pppd[1588]: CHAP authentication succeeded Nov 10 10:12:52 penfold pppd[1588]: peer from calling number 00:30:88:1A:D5:AC authorized Nov 10 10:12:52 penfold pppd[1588]: local IP address 58.96.97.xxx Nov 10 10:12:52 penfold pppd[1588]: remote IP address 58.96.2.210 My 'peers' file just contains: noipdefault usepeerdns defaultroute lcp-echo-interval 20 lcp-echo-failure 3 connect /bin/true noauth persist maxfail 0 mtu 1492 noaccomp default-asyncmap plugin rp-pppoe.so br0 user "xxxxxxxxx@vic.exetel.com.au" On 14/11/12 12:40, Trent W. Buck wrote:
Exetel made some changes to their backend on Fri which screwed me. I investigated this morning and now have a fix, detailed below. pppd is pretty cargo-culty, so let me know if I'm missing any best practice options.
* * *
I believe this issue is now resolved. By explicitly disabling PAP authentication, I get a public address (58.96.65.206).
Our modem runs Ubuntu 10.04, with pppd 2.4.5~git20081126t100229-0ubuntu3.