[7.385] PPPOE DSL Connection does not recover from a reboot

Just installed 7.385... now anytime I reboot the Astaro, the PPPOE connection will not automatically reconnect... I have to disable, then re-enable the interface before PPPOE will reconnect (just clicking the reconnect button does not work). This is new behavior in 7.385; the previous betas did not have this issue.

I thought it might be the new kernel-mode driver, so I switched the PPPOE driver back to "regular" mode... the same problem exists... so it's not the Kernel-mode driver.

The link light is lit on that interface while all this is going on... so it's not a hardware driver issue (at least I don't think so)...

Here are some of the log entries from the PPPOE log while the issue is occurring.

2009:01:16-00:05:03 myastaro pppoe[4540]: send (sendPacket): Network is down
2009:01:16-00:05:08 myastaro pppoe[4540]: send (sendPacket): Network is down
2009:01:16-00:05:13 myastaro pppoe[4540]: Timeout waiting for PADO packets
2009:01:16-00:05:13 myastaro pppoe-sh: Can not connect DSL AC - retry in 60 seconds
2009:01:16-00:06:14 myastaro pppoe[4943]: send (sendPacket): Network is down
2009:01:16-00:06:14 myastaro pppoe[4943]: recv (receivePacket): Network is down
2009:01:16-00:06:19 myastaro pppoe[4943]: send (sendPacket): Network is down
2009:01:16-00:06:24 myastaro pppoe[4943]: send (sendPacket): Network is down
2009:01:16-00:06:29 myastaro pppoe[4943]: Timeout waiting for PADO packets
2009:01:16-00:06:29 myastaro pppoe-sh: Can not connect DSL AC - retry in 60 seconds
2009:01:16-00:07:29 myastaro pppoe[4954]: send (sendPacket): Network is down
2009:01:16-00:07:29 myastaro pppoe[4954]: recv (receivePacket): Network is down
2009:01:16-00:07:34 myastaro pppoe[4954]: send (sendPacket): Network is down
2009:01:16-00:07:39 myastaro pppoe[4954]: send (sendPacket): Network is down
2009:01:16-00:07:44 myastaro pppoe[4954]: Timeout waiting for PADO packets
2009:01:16-00:07:44 myastaro pppoe-sh: Can not connect DSL AC - retry in 60 seconds
2009:01:16-00:08:44 myastaro pppoe[4971]: send (sendPacket): Network is down
2009:01:16-00:08:44 myastaro pppoe[4971]: recv (receivePacket): Network is down
2009:01:16-00:08:49 myastaro pppoe[4971]: send (sendPacket): Network is down
2009:01:16-00:08:54 myastaro pppoe[4971]: send (sendPacket): Network is down
2009:01:16-00:08:59 myastaro pppoe[4971]: Timeout waiting for PADO packets
2009:01:16-00:08:59 myastaro pppoe-sh: Can not connect DSL AC - retry in 60 seconds
2009:01:16-00:09:59 myastaro pppoe[4988]: send (sendPacket): Network is down
2009:01:16-00:09:59 myastaro pppoe[4988]: recv (receivePacket): Network is down
2009:01:16-00:10:04 myastaro pppoe[4988]: send (sendPacket): Network is down
2009:01:16-00:10:09 myastaro pppoe[4988]: send (sendPacket): Network is down
2009:01:16-00:10:14 myastaro pppoe[4988]: Timeout waiting for PADO packets
2009:01:16-00:10:14 myastaro pppoe-sh: Can not connect DSL AC - retry in 60 seconds
2009:01:16-00:11:14 myastaro pppoe[5031]: send (sendPacket): Network is down
2009:01:16-00:11:14 myastaro pppoe[5031]: recv (receivePacket): Network is down
2009:01:16-00:11:19 myastaro pppoe[5031]: send (sendPacket): Network is down
2009:01:16-00:11:24 myastaro pppoe[5031]: send (sendPacket): Network is down
2009:01:16-00:11:29 myastaro pppoe[5031]: Timeout waiting for PADO packets

Parents

0 RFCat_vk_01 over 16 years ago

Hi,
my experience was worse than that, disabled the interface a couple of times after stop/start of the ASG, no internet.
Powered the modem off then on then disabled and re-enabled the the interface, then it came up.

I hope there is an immediate fix released and secondly I don't have to many link dropouts.

Ian M
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 BrucekConvergent over 16 years ago in reply to RFCat_vk_01

Yep, something was changed... and not for the better... this has to be fixed before release--there are a lot of branch offices out there that use DSL.

CTO, Convergent Information Security Solutions, LLC

https://www.convergesecurity.com

Advice given as posted on this forum does not construe a support relationship or other relationship with Convergent Information Security Solutions, LLC or its subsidiaries. Use the advice given at your own risk.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 BrucekConvergent over 16 years ago in reply to BrucekConvergent

Thought I'd mention: This was a clean install of the first beta, with up2dates added as the new beta updates were released... don't know if this makes a difference, but it might help you reproduce the issue so you can make sure the release version doesn't do this to working 7.305 units.

CTO, Convergent Information Security Solutions, LLC

https://www.convergesecurity.com

Advice given as posted on this forum does not construe a support relationship or other relationship with Convergent Information Security Solutions, LLC or its subsidiaries. Use the advice given at your own risk.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 BrucekConvergent over 16 years ago in reply to BrucekConvergent

And... to reiterate, the unit was fine on 7.380 ...

CTO, Convergent Information Security Solutions, LLC

https://www.convergesecurity.com

Advice given as posted on this forum does not construe a support relationship or other relationship with Convergent Information Security Solutions, LLC or its subsidiaries. Use the advice given at your own risk.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 da_merlin over 16 years ago in reply to BrucekConvergent

Ok something mixed up the order of your init scripts.
Try this little goodie via command line, this should fix the issue:

rm -f /etc/init.d/rc3.d/S*; for i in $(rpmquery -a -l|grep ^/etc/init.d/rc3.d/S); do ln -s ../${i:21} $i;done
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 BrucekConvergent over 16 years ago in reply to da_merlin

That's great; how did that happen... the up2date obviously did this... can we make sure this won't happen in production... I'm just thinking of all the units we'd have to send a body out to to login and fix this in the field... it would be a costly nightmare.

CTO, Convergent Information Security Solutions, LLC

https://www.convergesecurity.com

Advice given as posted on this forum does not construe a support relationship or other relationship with Convergent Information Security Solutions, LLC or its subsidiaries. Use the advice given at your own risk.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 RFCat_vk_01 over 16 years ago in reply to BrucekConvergent

Hi,
I have been trying to convince putty to communicate with my ASG. During these attempts the ADSL link dropped out and restored itself asfter about 4 re-tries.

I haven't applied the fix suugested to Bruce.

Should I apply that script?

Ian M
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 BarryG over 16 years ago in reply to RFCat_vk_01

I may be another victim... my internal bridge failed:
https://community.sophos.com/products/unified-threat-management/astaroorg/f/95/t/67257

edit: running the command from above fixed my probem.

Barry
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 BrucekConvergent over 16 years ago in reply to RFCat_vk_01

Hi,
I have been trying to convince putty to communicate with my ASG. During these attempts the ADSL link dropped out and restored itself asfter about 4 re-tries.

I haven't applied the fix suugested to Bruce.

Should I apply that script?

Ian M

If your rc3.d script list looks like mine, I'd say yes.

CTO, Convergent Information Security Solutions, LLC

https://www.convergesecurity.com

Advice given as posted on this forum does not construe a support relationship or other relationship with Convergent Information Security Solutions, LLC or its subsidiaries. Use the advice given at your own risk.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Johannes Hiby over 16 years ago in reply to BrucekConvergent

Hi,

i had the same Problem with my internal interface eth0.
The rc3.d script list looks like yours.
The running the script fixed it.

--Johannes
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 BrucekConvergent over 16 years ago in reply to Johannes Hiby

I just hope that the 7.400 release up2date doesn't do this... that would be a mess.

CTO, Convergent Information Security Solutions, LLC

https://www.convergesecurity.com

Advice given as posted on this forum does not construe a support relationship or other relationship with Convergent Information Security Solutions, LLC or its subsidiaries. Use the advice given at your own risk.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 trollvottel over 16 years ago in reply to BrucekConvergent

This has already been fixed. Next version, whichever will be available, will also repair affected configurations.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 trollvottel over 16 years ago in reply to BrucekConvergent

This has already been fixed. Next version, whichever will be available, will also repair affected configurations.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data