No automatic connect to ISP
-
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.
-
Tried the patch with snap from Sun Mar 7 00:22:39 EST, but got errors:
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 succeeded at 2011 with fuzz 2. Hunk #2 succeeded at 2044. Hunk #3 failed at 2070. Hunk #4 failed at 2081. Hunk #5 succeeded at 2092. Hunk #6 succeeded at 2108. 2 out of 6 hunks failed--saving rejects to etc/inc/interfaces.inc.rej done Think I'm too late...
cat /etc/inc/interfaces.inc.rej
*** 2052,2057 ****
 set link no acfcomp protocomp
 set link disable pap chap
 set link accept chapEOD;
 if (empty($wancfg['mtu']))
–- 2070,2077 ----
 set link no acfcomp protocomp
 set link disable pap chap
 set link accept chap- set pppoe iface {$wancfg['if']}
- set pppoe service "{$wancfg['provider']}"
EOD;
 if (empty($wancfg['mtu']))
*** 2061,2085 ****
$mpdconf .= <<<eod<br>set link mtu {$mpdmtu}
- set ipcp yes vjcomp
- set ipcp ranges 0.0.0.0/0 0.0.0.0/0
EOD;
- if (isset($config['system']['dnsallowoverride'])) {
- $mpdconf .= <<<eod<br>- set ipcp enable req-pri-dns
- EOD;
- }
- if (!isset($wancfg['dnsnosec']) && isset($config['system']['dnsallowoverride'])) {
- $mpdconf .= <<<eod<br>- set ipcp enable req-sec-dns
- EOD;
- }
$mpdconf .= <<<eod<br>open
–- 2081,2089 ----
$mpdconf .= <<<eod<br>set link mtu {$mpdmtu}
EOD;
$mpdconf .= <<<eod<br>open
#</eod<br></eod<br></eod<br></eod<br></eod<br></eod<br>
-
a simple solution would be if some1 could simply upload the interfaces.inc file after the patch applied so everyone else could simply replace the existing file with it to test the new patch.
-
I've just re-installed to pfSense-1.2.3-RELEASE-LiveCD-Installer.iso.gz and this does not contain MPD5 as far as i can tell. Running the command 'which mdp5' results in 'mpd5: Command not found'.
'which mpd' works though, /usr/local/sbin/mpd
Now that I am running on a different version, I'll see how it goes with the auto-reconnect and general connection stability.
My DSL condition is below:
–- DSL Information ---
DSL Driver Version:Â AnnexA version - A2pB022g.d20e
DSL VPI/VCI:Â Â Â Â 8/35
DSL Status:Â Â Â Â Â ShowtimeRetrain Reason: 0
DSL Mode:Â Â Â Â Â Â ADSL2+
DSL Channel:Â Â Â Â FAST
DSL Upstream Rate:Â 1023 Kbps
DSL Downstream Rate: 12470 KbpsDown    up Â
DSL Noise Margin:Â Â 11.1 dBÂ Â Â 13.9 dB
DSL Attenuation:Â Â 31.0 dBÂ Â Â 19.1 dB
DSL Transmit Power: 18.7 dBm  12.6 dBm -
I've just re-installed to pfSense-1.2.3-RELEASE-LiveCD-Installer.iso.gz and this does not contain MPD5 as far as i can tell. Running the command 'which mdp5' results in 'mpd5: Command not found'.
This thread is for pfSense 2.0 beta (it's in the 2.0 board, even) - it will not work on 1.2.3.
-
I've just re-installed to pfSense-1.2.3-RELEASE-LiveCD-Installer.iso.gz and this does not contain MPD5 as far as i can tell. Running the command 'which mdp5' results in 'mpd5: Command not found'.
This thread is for pfSense 2.0 beta (it's in the 2.0 board, even) - it will not work on 1.2.3.
I understand - Sorry about that, however if the auto-connect feature works correctly on the version I have installed, I will be happy to stick to that.
-
hi Jimp,
could u paste the contents of the interface.inc file after the patch so i can simply edit the file?
Regards
-
I suppose I could put it somewhere but the patch still applies cleanly on today's snapshot – I'm not sure why people are having any problems with it.
[2.0-BETA1] [root@tester.local]/root(1): cd / [2.0-BETA1] [root@tester.local]/(2): patch -p1 < root/mpd5.diff 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 succeeded at 2030 (offset 19 lines). Hunk #2 succeeded at 2063 (offset 19 lines). Hunk #3 succeeded at 2089 (offset 19 lines). Hunk #4 succeeded at 2100 (offset 19 lines). Hunk #5 succeeded at 2111 (offset 19 lines). Hunk #6 succeeded at 2127 (offset 19 lines). Hmm...  Ignoring the trailing garbage. done [2.0-BETA1] [root@tester.local]/(3): uname -a FreeBSD tester.local 8.0-STABLE FreeBSD 8.0-STABLE #1: Mon Mar  8 02:04:41 EST 2010   sullrich@FreeBSD_8.0_pfSense_2.0-snaps.pfsense.org:/usr/obj.pfSense/usr/pfSensesrc/src/sys/pfSense_SMP.8  i386Here is my copy:
mv /etc/inc/interfaces.inc /etc/inc/interfaces.inc.old fetch -o /etc/inc/interfaces.inc http://pingle.org/files/interfaces.inc.txt -
It will be on latest snapshots.
-
Hi,
I suppose I could put it somewhere but the patch still applies cleanly on today's snapshot – I'm not sure why people are having any problems with it.
same here…even with Mar 1st build clearly patched so I neither have issues. Hopefully ermal will soon or later commit, be patient 'til then or edit by hand using .rej file.
cheers,
ooops, message just crossed. glad to hear emarl made it into next snap. danke!
-
thanks Jimp, i tried the file on the 4th March nanobsd but didnt seem to work so will try the latest snapshots once the traffic shaper issue is solved on them
