Pfsense needs to be restartet in case of pppoe 24h disconnect
-
Hi,
since I have upgraded my pf from 1.2 stable to 1.3 (1.3-ALPHA-ALPHA built on Tue Aug 12 19:22:04 EDT 2008 FreeBSD 7.0-RELEASE-p3) my pf needs to be restartet when my provider does an 24h disconnect.
Log shows that no gateway can be reached. If I try to disconnect the Interface manually nothing happens by clicking on disconnect…
When I restart my pf everything is normal again (for the next 24h to the next disconnect from provider)Same configuration worked fine with 1.2 stable.
Any known bugs?
Provider: Interroute Germany, PPPOE dialin with 16MBit ADSL+ T-Com
pf is virtualized under vmware-server with 2 nics. One nic is directly attached to the dsl-modem.Sry for bad english ;-)
regards
SiD
-
I have noticed the same behavior. If ISP revokes lease on pppoe address there is no more connectivity. Wan interface is pppoe with automatic reconnect checked and set not to disconnect an idle connection. ISP is embarq/sprint adsl the box is an alix with 1.3 full install on a microdrive. The behavior and logs are identical to what is reported above.
-
what happens if you do not reboot the box but hit the save button under interfaces -> wan ?
does pfsense reconnect then ? -
Hi, if I save the Interface/WAN Page there is an error shown on the page:
Fatal error: Cannot unset string offsets in /usr/local/www/interfaces_wan.php on line 366 -
No ideas? :-[
I´ve updated to today-build, don´t know where to look….
-
Had the same behaviour too. I have a Wimax-based ISP and they have frequent disconnections. When it happens, Pfsense does not automatically reconnect. Disconnect button does not work no matter how many times I click on it. If I go to Interfaces -> WAN and click "SAVE" then it's working again, no need to restart the computer.
However, I must always double check on the Interface -> WAN page because the Type always revert to "Static" instead of "PPPoE".
Running latest 1.3 ALPHA on a VA Linux 1221. Updated the firmware yesterday with the pfSense-20080823-2015.img but the status page still shows "built on Fri Aug 15 16:26:59 EDT 2008".
Hope this helps.
ArkAngel
-
You need to use the update files, not the img files as these are the embedded disk images.
-
You need to use the update files, not the img files as these are the embedded disk images.
Thanks, started to use the auto-update sunday, much better. But if I remember right, there are img files for the full install and images for the embedded. I never used the embedded. If I did not used the right image I think it would not have permitted the firmware upgrade.
ArkAngel
-
Hi,
the problem is still present and i think its a major bug for pppoe users, who cannot use it for wan connections. In germany nearly all DSL Providers give only pppoe access. If i just hit the "save" Button under my WAN Interface it took along time until the webinterface reacts to it (it seems to be frozen, also if i try to access it while he is restarting the mpd services). I added now a cronjob to restart every 24 hours the pfSense Box but it its not a solution.
-
When you enable this feature it is supposed to setup a cron entry. Do you see the entry in /etc/crontab?
-
I think it is the code underlying this that is broke not the cron job.
The PPPoE disconnect button has never worked for me on 2.0 (and 1.3) on embeded (never tried it on full).
When I click the disconnect button nothing happens and if I do get disconnected (I have no forced reset from my ISP) the button still says disconnect and when clicked has no effect. Just stays with disconnect as the text. The only way to get PPPoE to come up is to reboot.I think (but haven't looked too hard) that the disconnect code is looking at the interface (ie xl0) and not the PPPoE adaptor.
-
Yes there is a entry for the restart i think:
0 4 * * * root /etc/pppoerestarti tried to start it by hand. I got an error:
# /etc/pppoerestart Fatal error: Call to undefined function interfaces_wan_pppoe_restart() in /root/- on line 1so that might be why it will not disconnect to a given time. But i hope that he also reestablish the link to my dsl provider if he looses it at any time.
-
try latest snapshot and report.
-
Hi ermal,
same error occurs if try to restart it by hand with the latest snapshot.
Greetz,
mino -
Yeah i am going to trace this cause it happened to me at my home installation on pppoe too.
I will come back with something later tomorrow.Do you have anything in logs after mpd exits and it tries to restart it?!
-
I believe this should be fixed now. Please try next snapshot cycle.
If you want to test now, replace the pppoe_reconfigure function in /etc/pppoe_restart with interface_reconfigure();
-
PS: you need to click save on the wan interfaces configuration page to regenerate the /etc/pppoe_restart file..
-
As sullrich said retry with latest snapshot.
-
Okay, i installed the latest snapshot. I saved the WAN interface many times. But the /etc/pppoerestart file is still the same and so the error still occurs.
#!/bin/sh echo 'es_dyndns_reset(wan); ?>' | /usr/local/bin/php -q -
The new file should be on /var/etc/pppoefile actually.
It should have interface_reconfigure in it.