Is PPPOE working for you guys?
-
there r no changes in config since pf v1.2.3, the only difference since then is pfsense itself and the mpd in both of the versions as i believe earlier versions of pf v2.0 used older mpd and that time it used to work flawless also.
there is no config change which makes it work or makes it dead, on boot almost any config change i make works and the same falls dead when unplugged or isp device goes down or reboots.
-
Still not what I asked. Look a the file right when it boots up. Then look again when it's reconnecting and failing.
I'm not saying you changed anything - I want to know if the file is different in some way at boot time and when it fails. If something internal to the box rewrites the mpd_wan.conf file and changes something behind the scenes.
If the file is identical both times, then the problem would be somewhere different than if the file is the same at both of those times.
-
sorry for the mis understanding, i guess i found out the issue.
actually i checked the config right after start and then again after i unplugged the wire and replugged it back in, there wasnt any difference in the config file at all but then i compared it to the config file i had posted earlier and found one line had changed and the below line was added new
set iface addrs 10.10.1.1 10.10.1.2
so while pf was attempting to reconnect and failing, what i did is i opened the config file and removed that line and saved it and then it reconnected in the next attempt but then now the config again started showing this line, so is there any way to remove this line permanently and then perform more tests so as to verify if thats the cause or no.
-
set iface addrs 10.10.1.1 10.10.1.2
is this related to the situation when in some countries i have noticed that as soon as u plug the wire in the isp device, u get a temporary local i based on dhcp enabled on the isp device and then usually u dial the connection related to the pppoe but in my country, if i take that cable and plug into my windows pc or any computer at all, the isp device doesn't assign any temporary ip so after some time windows starts showing limited connectivity but if u use the dialup connection to connect the pppoe then it would dial and connect to the internet perfectly fine.
so to make mpd work in dial on demand is it necessary for this temporary ip to be obtained before a pppoe connection can be established, if so then i would need a work around this problem
Also this command may be used to force specified addresses usage instead of negotiated ones. It may be useful in some specific cases, for example, to avoid routing loop with misconfigured PPTP server. In such case '!' mark specifies IPs to be forced.
-
It looks like that line should only be set of 'on demand' is checked, but judging by the other line in your config ("set iface disable on-demand") it would appear that you do not have that option set. Can you confirm whether or not you have "on demand" set?
-
it was disabled earlier coz it wouldnt anyways connect automatically but i have enabled it again and thats y that line appears.
startup: # configure the console set console close # configure the web server set web close default: pppoeclient: create bundle static wan set iface name pppoe0 set iface route default set iface enable on-demand set iface idle 0 set iface addrs 10.10.1.1 10.10.1.2 set iface enable tcpmssfix set iface up-script /usr/local/sbin/ppp-linkup set iface down-script /usr/local/sbin/ppp-linkdown set ipcp ranges 0.0.0.0/0 0.0.0.0/0 set ipcp no vjcomp #log -bund -ccp -chat -iface -ipcp -lcp -link create link static wan_link0 pppoe set link action bundle wan set link disable multilink set link keep-alive 10 60 set link max-redial 0 set link disable chap pap set link accept chap pap eap set link disable incoming set link mtu 1492 set auth authname "username" set auth password password set pppoe iface vr1 open -
So if you leave "on demand" unchecked, does it reconnect like it should?
-
it doesnt and like i mentioned the issue is this i guess
is this related to the situation when in some countries i have noticed that as soon as u plug the wire in the isp device, u get a temporary local ip based on dhcp enabled on the isp device and then usually u dial the connection related to the pppoe but in my country, if i take that cable and plug into my windows pc or any computer at all, the isp device doesn't assign any temporary ip so after some time windows starts showing limited connectivity but if u use the dialup connection to connect the pppoe then it would dial and connect to the internet perfectly fine.
-
Do you have the physical adapter you're using for PPPoE also assigned to access the modem?
That interface address in the mpd config can only be set if you have on demand checked, then you'll need to do another comparison at bootup/reconnect without that set to see if there are any differences.
-
there is no restriction on which physical adapter connects to the isp device network port.
at boot, almost all config connects fine, the problem only occurs if during a connection it drops and then pfsense just keeps trying to reconenct endlessly.
-
is there some way to enable some low level log for mpd, mayb that can reveal the difference when it connects to pppoe on boot and failure to reconnect once disconnected.
-
During the last week I have been playing around with 2.0-RC too, and a few times this problem occured for me too, pppoe fails to connect to matter what I try to do, only a reboot fixed it.
The funny thing is that replugging cable / restarting dslmodem usually works OK, pfsense detects link down, and reconnects normally once link is up again. But on a few occasions, the same error as is reported in this thread happens, it just keeps trying to reconnect with no success until it's rebooted.
The logs really tells me nothing, the config files looks OK in all circumstances and it just doesn't make much sense that this is happening..
I too can help trying to track this one down if given some instructions on how to do it.
-
I have been fighting PPPoE this weekend I don't want to deal with it right now. I have had multiple disconnects from a remote company to the main office. Maybe things will get worked out in the future and I will try it again, just never on this customer site.
This is what you do if you want to avoid PPPoE all together.
I put my DSL modem in default mode rather than bridge. I now get an internal natted IP from the modem. In the modem settings I made the IP that is handed to my pfsense a DMZ host, so all traffic from the static IP sitting on the modem is forwarded to my pfsense.I sure hope that this fixed my disconnect issues.
-
I put my DSL modem in default mode rather than bridge. I now get an internal natted IP from the modem. In the modem settings I made the IP that is handed to my pfsense a DMZ host, so all traffic from the static IP sitting on the modem is forwarded to my pfsense.
I ended up doing the same here on my 2.0-RC installation, PPPoE in 2.0-RC really seem to have issues. Not usable at all in it's current state here. 1.2.3 worked without a hickup for well over a year though.
-
If you don't get us useful information for debugging (mentioned earlier in this thread), then there is no hope of having it fixed. It works fine for the vast majority of people. It won't magically get fixed unless it can be determined just why it doesn't work for you.
-
to my experience its mpd only thats causing this, is there any way to switch to an older mpd used in 1.2.3 or mayb if u could tell me how to put mpd in debug mode then i can atleast get u more useful logs.
-
I just thought I'd post here to say that I'm running two WANs, both are PPPoE, and have had no problems at all. Now I realise that may not be much comfort for those of you who are having trouble but to say that it's "not usable at all in it's current state" is just wrong.
I am running a fresh install, not an upgrade from 1.2.3, using a snapshot from 13/05/11. I realise that's quite old now but it's still not as old as this thread!Steve
-
Site to Site Openvpn (remote branch having the issue)
If you are authenticating via PPPoE on your WAN to your modem I would be very concerned with your connection at this point. I am pretty sure that there are bugs with the PPPoE portion of pfsense. I have taken my modem out of bridged mode and the modem is now doing PPPoE authentication itself. The modem's DHCP has handed me its first internal natted address. I've been up since I made the change on Saturday the 11th.When I was in PPPoE mode my pfsense box would lose connection at least twice a day. Before I made the change to a full natted situation I replaced modems and had qwest come out and fix all of the telephone lines. Qwest said everything looks great and then the next day my connection went into a tail spin up and down up and down.
I don't know what it is because the main site I think was using the same build, I have it in PPPoE mode and knock on wood it has been staying up the whole time. Working a full-time job and having a side job customer yell at you for two weeks while I tried to fix the disconnection issue, I am happy to be NATed. I would try PPPoE again, just not with this customer.
Look at my previous post.
http://forum.pfsense.org/index.php/topic,37603.0.html
http://forum.pfsense.org/index.php/topic,35475.45.html -
[snip]
Look at my previous post.
http://forum.pfsense.org/index.php/topic,37603.0.html
http://forum.pfsense.org/index.php/topic,35475.45.htmlAnd you never did gather any log information that would have been helpful in tracking it down. Yelling "it's broken!" and then not helping to debug the problem is quite useless for everyone. Especially when most of us cannot reproduce the problem. Review my posts in this thread for things to try (system log entries for mpd, and comparing the mpd config before and after)
to my experience its mpd only thats causing this, is there any way to switch to an older mpd used in 1.2.3 or mayb if u could tell me how to put mpd in debug mode then i can atleast get u more useful logs.
It is highly unlikely that we will downgrade mpd since it's working fine for the vast majority of people. If you can check again the things I asked for (your responses were somewhat confusing and conflicted, you kept making too many changes at once), it would help.
Specifically we need to see:
- mpd logs from a working and a broken connection attempt (clog /var/log/system.log | egrep '(mpd|ppp)' ) be sure to just include the connection attemps, check the timestamps.
- /var/etc/mpd_<interfacename>.conf from a working and a broken connection attempt
- Try with/without "configure a null service name" turned on. (And provide the mpd_<interfacename>.conf from a broken/working attempt there.)
- Bonus points if you have a /var/etc/mpd*.conf from your old 1.2.3 install
- Make sure you remove/mask out your username and password from your mpd.conf files.
So in total that would ideally be as many as four (4) sets of logs and five (5) copies of various mpd.conf files. At a minimum it's two (2) copies of the log and two (2) mpd_something.conf files.</interfacename></interfacename>
-
ill work on the log and send it in as soon as i gather all of it as mentioned, the reason for not being able to provide info is because im not a BSD person so i hardly know any of its commands at all so thats y im clueless on what to gather from where
