No automatic connect to ISP
-
8 posts up antiben supplied a diff.
Updated to snap from Fri Feb 26 23:14:37, mpd4 is still used. I've seen that mpd5 is installed too, but not used. Will this be automatically activated or do I have to change something to activate mpd5? -
igor - it's there if someone wants to experiment, but it is not activated yet. There may be some config changes and other things that need to happen before it would be switched out. Most important is to find out if it actually fixed the reconnection issues…
Hopefully I can get some time in the next day or two to spend on it.
-
Ah, ok. Thanks for the info. I was just curious.
-
After the earthquake, here in Santiago we've all services back again, but I've to manually reconnect the ppoe adsl.
Regards
Alfredo -
This auto connect/reconnect issue was also present in m0n0wall, but was repaired, perhaps we could do the same thing?
http://m0n0.ch/wall/changelog.php
1.3b10 (03/01/2008)
-fix MPD WAN PPPoE/PPTP auto-reconnect issue -
For anybody please try this patch on latest snapshots and report how their pppoe behaves on mpd5.
-
@ermal:
For anybody please try this patch on latest snapshots and report how their pppoe behaves on mpd5.
Working great for me so far ermal. I kicked my session about 5 times and each time it reconnected within 5-10 seconds, as it used to.
Looks like mpd4 is just a dud when it comes to PPPoE reconnecting.
-
Hello,
Thanks for your cleaner patch, I just wiped my DIY patchy and apply this, and I second that as jimp said so now willing this one to be committed anytime soon. And, mpd5 ROCKS!
cheers,
-
can it be commited so i can also benefit from it using latest snapshots?
-
or could some1 tell me what command to run in order to apply the patch directly in a nanobsd box?
-
You can do it on NanoBSD like so:
# /etc/rc.conf_mount_rw <fetch or="" scp="" the="" mpd5.txt="" file="" to="" box="" somehow=""># cd / # patch -p1 < /root/mpd5.txt # /etc/rc.conf_mount_ro</fetch>Just make sure you are running a snap that includes the md5 binary before you do that.
-
im on the 4th feb nanobsd , no idea how to check if mpd5 is there or no
-
im on the 4th feb nanobsd , no idea how to check if mpd5 is there or no
Go to a shell and type:
# which mpd5 /usr/local/sbin/mpd5If you get back that second line, you have it. Though that snapshot is probably too early, you'll need to update/reflash to a newer one.
-
it says the exact line u mentioned but when i ran the below
/etc/rc.conf_mount_rw
through web interface, the web interface seemed to have died, tried restarting also but no effect, need to reboot the box. -
Yeah, that should have been done from a shell, not the webgui. The Diagnostics > Command interface in the GUI automatically switches to rw/ro during execution.
-
hmmmmmmmmmm….it's not that difficult, first click & save ermal's patch somewhere on your local pc, then go grab shell from the console not from the webGUI, then follow jimp's instruction, it's only 3 minutes cook. have fun!
cheers,
ooops, you quick ;D
-
Typo? What typo? ;-)
-
You can do it on NanoBSD like so:
# /etc/rc.conf_mount_rw <fetch or="" scp="" the="" mpd5.txt="" file="" to="" box="" somehow=""># cd / # patch -p1 < /root/mpd5.txt # /etc/rc.conf_mount_ro</fetch>Just make sure you are running a snap that includes the md5 binary before you do that.
this is what i get
[root@pfsense.pfsense]/(4): patch -p1 < /root/mpd5.txt
Hmm… Looks like a unified diff to me...
The text leading up to this was:|diff --git a/etc/inc/interfaces.inc b/etc/inc/interfaces.inc
|index 54808a6..f4bd81e 100644
|--- a/etc/inc/interfaces.inc+++ b/etc/inc/interfaces.inc Patching file etc/inc/interfaces.inc using Plan A... Hunk #1 failed at 2011. Hunk #2 failed at 2044. Hunk #3 failed at 2070. Hunk #4 failed at 2081. Hunk #5 failed at 2092. Hunk #6 failed at 2108. 6 out of 6 hunks failed--saving rejects to etc/inc/interfaces.inc.rej done -
Hi guys,
Just to clear up, which file on this mirror http://mirror.optus.net/pub/pfSense/downloads/ Should i install to resolve this issue?
Cheers
-
You can do it on NanoBSD like so:
# /etc/rc.conf_mount_rw <fetch or="" scp="" the="" mpd5.txt="" file="" to="" box="" somehow=""># cd / # patch -p1 < /root/mpd5.txt # /etc/rc.conf_mount_ro</fetch>Just make sure you are running a snap that includes the md5 binary before you do that.
this is what i get
[root@pfsense.pfsense]/(4): patch -p1 < /root/mpd5.txt
Hmm… Looks like a unified diff to me...
The text leading up to this was:|diff --git a/etc/inc/interfaces.inc b/etc/inc/interfaces.inc
|index 54808a6..f4bd81e 100644
|--- a/etc/inc/interfaces.inc+++ b/etc/inc/interfaces.inc Patching file etc/inc/interfaces.inc using Plan A... Hunk #1 failed at 2011. Hunk #2 failed at 2044. Hunk #3 failed at 2070. Hunk #4 failed at 2081. Hunk #5 failed at 2092. Hunk #6 failed at 2108. 6 out of 6 hunks failed--saving rejects to etc/inc/interfaces.inc.rej done Yeah i get the same thing too.
