No automatic connect to ISP

_igor_

Same thing happend to me too, but not everytime. So sometimes it was in a loop getting indefinitely a new IP. Pressing the "connect"-button established the connection.
But afterwards I had/have to call the DynDNS-page and save to actualize the DynDNS-IP. rc.newwanIP was never called upon manual connect.

Yesterday I did a complete new install because mpd died before and never "woke up" again. So I think, something broke up in my installation. mpd died instantly.
Will see if now things are better.

Update: After the fresh install I see that adding an external DNS-server results in the fact that my ISPs DNS-servers are not settled. No internet-activity possible. Even pfSense is not able to find updates. So only the external DNS is set. Deleting this DNS-entry results in an instantly added ISP-DNS and my Internet-connection works. pfSense finds its updates too.

Looking in the logs I see after restart of pfSense 3 attempts to connect to my ISP Then the log spits out this:
php: : The command 'fetch -o /dev/null -q https://localhost:443/preload.php' returned exit code '1', the output was 'fetch: https://localhost:443/preload.php: Unknown error: 0'.
That was it. I will try to add the "no noretry"-option.
When I manually connect I get the mentioned failings. Here mpd dies but restarts again (reverse order):

mpd: Multi-link PPP daemon for FreeBSD
Feb 19 11:07:37 mpd: process 6494 terminated
Feb 19 11:07:35 mpd: caught fatal signal term
Feb 19 11:07:27 php: : Could not find gateway for interface(wan).

I will keep you updated.

antiben

hi igor,

what do you mean by 'not everytime.' ?

for nocer and afrugone it seems to work, so i tried the "no noretry" bundle option on mpd 4.4.1 some days ago,
but like jimp and you wrote: it falls into a loop… fortunately i saw the loop 2 minutes later g

currently i'm writing with my new wan-pppoe ip - no need to manual reconnect for now. but here is the catch,
my pfsense 2.0 runs the old mpd 3.18 with the ng networking subsystem.
and here is a first quick freebsd question:
what / where are the diffs between ng0 (mpd3) and pppoe0 (mpd4)?

dyndns upate seems to work… but dnsmasq was invoked later, so that may be another order issue...
luckily i have the same dns(s) like yesterday, (as per mpd: they are really the same), so dyndns was successfully...

i may setup and try mpd 4.4.1 with my modifications...
why has the "no noretry" option been removed from the pppoe interface.inc section?

ps: after i saw the preload file, i understood the unknown error from fetch g
(joke, i know the preload.php exists longer… but that's not nice for the php interpreter)

_igor_

The loop only 2 or 3 times. Mostly not. Due to the spare times it looped I didn't think to mention it. Difficult to fix something like this.

Only to clarify, for me is not working perfectly, is better, but after some days (about a week) I get the same problem, and I have to manully reconnect

antiben

…loop only 2 or 3 times. / ...after some days (about a week) ...

don't dash my hopes, cause i'm now running the mpd 4.4.1 setup in my pfsense 2.0b setup.
nocer has also mentioned to use the last stable mpd5 … are you in favour?
(seems that the hole pppoe link type part has been rewritten.)

afrugone, igor, would you test my mods (some files - you only need little ssh / scp skills)?
what versions / setups are you running on your pfsense boxes?
multi-wan pppoe? multi dyndns? snapshot date? are you willing to update?

another mpd question: how important is the 'tcpmssfix' option for pppoe (since, if the mtu is empty, it's set to 1492)?
btw. (ot): there might be another dyndns issue, if you have multiple accounts for the same service/provider.

_igor_

Latest update is that PPPOE is nearly not usable. My connection is lost every 5 or 10 mins, reconnect only manually, with the "bundle no noretry" I get stuck in endless loops of mpd reconnecting endless. No Dyndns-Update ocurrs, connection is passing traffic only if I hit "save" in "General setup". Its more than strange. Looks like voodoo.
With the latest update it seems to be worse than ever: I'm getting endless delays and packet loss. Things that never happend before. The whole pfSense-box seems to stall after a while. Connection is getting slower and slower, logs are flooded wiith apinger warnings. When I reboot the box all is gettig ok for some minutes. Then all is getting slow again. Doesn't matter if there is traffic or not. Dashboard shows a cpu of 1-2%, net traffic is nearly nothing but a great slowdown occurs.
At the moment I see that lots of changes occur, but PPPOE seems to be a strange thing. With 1.2.3 no problem at all. Ok, I need some features of 2.0, but I'm more than willing to test every thing to get a better response here. Even if it gets worse, but I don't think so.

@antiben: Throw me your changes, I'll test it! I don't have programming skills but know something about how to use ssh and console.

antiben

ok, i'll prepare everything in a tgz file. base is the last build 20100221-0133
maybe it could all be done with pfsense's exec.php (diagnostics/command prompt).
precondition is, that my reconnect and dyndns-update works… (in about 4h) g

but despite everything, connection lost every 5 or 10 mins sounds differently from the 24h forced disconnect/reconnect…
can you quickly post your hardware setup? (or have you post it anywhere else before?)

//edit typo, changed build link from 20100220-0923 to 20100221-0133,
last changes doesn't affect interface/pppoe/mpd stuff

Antiben,

Just tell me what to do, I'll try your mods over version 20100221-0133.

_igor_

I have a Dell 1740. Send your mods! I'm ready

antiben

precondition complied,
so i sent you the file with a short instruction via pm. please reboot after that.
i soon post the changes, and some diffs for the devs.

i did the update, rebooted and a short time after the i reload the pfsense welcome screen my
wan pppoe was up and hopefully runs until the next hardware or power failure comes g

what features of 2.0 are you using? multi dyndns? multi-wan?
what type of internet-connection? (not only the pfsense hw)

_igor_

Oh sorry. At the moment its a simple and stupid config: Single-wan, single-lan. No opt, no packages. Only built-in features. My inet is a 100MBit-DSL.

At the moment it looks good. No disconnect since reboot. Only strange thing i have is a very weird connection. Endless delays and packet-loss. Due to that I have a really poor connection, but I'll try tomorrow with 1.2.3 to see if this changes.
But all relevant things work as expected for the moment: Dyndns-update occured and is shown right in the dyndns-page, on the dashboard wan-gateway tells me about the state of the gw, not only "gathering data" which was the only info before.
So at the moment your changes look very good! Thanks again!

antiben

ok, thx for the feedback.
if you look into your '/var/etc/mpd_wan.conf', you notice that i re-add the no noretry bundle option, disabled the tcpmssfix, removed the ppp-linkdown call and set the max-redial to 7 instead of unlimited, cause if i enter a wrong password, my t-dsl account may locked.

delays and packet-loss while browsing the web?
100MBit-DSL - that's not really poor?! g

try 1.2.3 and keep some system.log files…
you may want to test the 'old' mpd 3.18 in pfsense 2.0b (like i did... ^).

_igor_

Now the auto-reconnect works! After a while the line disconnected due to the packet-loss and it reconnected automagically. First time since long time! Very nice.

Normally my web is fast! But now all websites are as slow as ISDN. Not nice. Remote working is nearly impossible. :-(

Packet-loss is nearly by 50%.

nocer

Normally my web is fast! But now all websites are as slow as ISDN. Not nice. Remote working is nearly impossible. :-(

tcpmssfix may help, if it's disabled.

cheers,

_igor_

Used the last patch from antiben with tcpmssfix enabled. Looks as if this was the problem!

Packet-delays and losses are gone completely.
Web is as fast as again, I can send Mails again (was impossible with tcpmssfix disabled) and much more things work right now again!
I'm excited again. Thanks again for all your help! Great appliance, great community!

xbipin

im also having such issues, can u plz guide what file needs modification to solve this?

_igor_

I got this info from antiben:

just download this tgz file and upload it through the web interface (diagnostics/command prompt).
than simply run the following shell command (in top) and hit execute
Code:
tar xzf /tmp/antiben_mod.tgz -C / && rm /tmp/antiben_mod.tgz

it's not tested, but i'm testing this now, so don't blame me if something goes wrong.
always backup important settings and please report/post/link your setups, as i asked before…

Then patch for tcpmssfix:

since nocer has suggested to enable the tcpmssfix, so i re-added this option...
same procedure... just download this small tgz and run via diagnostics/command prompt
(you are still on the same build?)
Code:
tar xzf /tmp/tcpmssfix.tgz -C / && rm /tmp/tcpmssfix.tgz

Hope that helps you.
The patch is made for the snap from Feb 20/21. I have it working flawlessly with snap from Feb 22 04:29:20.

Good luck!

antiben asked me to remove the links. So please better wait for an official fix.

xbipin

im currently on the 23rd Feb nanobsd snapshot

antiben

as i wrote before (^), attached is a diff (for the most important things concerning auto-reconnect) against the 20100221-0133 snap…
(more infos soon)

antiben.diff.txt

Rich0x

Any updates to this ??