Is PPPOE working for you guys?
-
Jimp,
You have to see that I was in a pressing situation and I had to make a change or the customer would have outed me. I didn't have any time to do a lot of troubleshooting because this was going on for two weeks, I did not know there was more detailed logs in the /var/logs being new to pfsense. I though when you said system logs, you just mean the GUI system logs and I never saw any mpd or ppp errors. If this happens to me again heaven forbid I know which logs to send you. Go easy on me Dr. when it is sick I don't always know where to look for problems that is why I turned to you guys, I'm a rookie.
Believe me if I knew where to access all of these configs and logs I would have sent them. I really like pfSense and wanted to help others if they were in the same situation as me.
Thanks,
-
Members -
Is there definitive work-around solution to this? I just try to deploy this with version 2.0 RC3 and it does not seem to work.
Please advise.
-
I did have problems with PPPoE initially but 'Null service name' solved the problem for me. I do remember during initial configuration that the 'null service name' setting got lost (unchecked) but since re-checking it and rebooting, it hasn't happened since.
If it helps anyone, this is my working pfsense 2rc3 PPPoE config with Eti$alat
$cat /var/etc/mpd_wan.conf 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 disable on-demand set iface idle 0 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 #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 service "" set pppoe iface em4 open
-
Thanks Thermo. So, your ppoe was default setting with ppoe login/password and did not work. And when you checked 'null service name' in advance setting, it started working?
Will give that try tonight.
-
probie: yes, that's correct, it worked when 'null service name' was checked but as I kept configuring/fiddling/reconnecting other interfaces, it stopped working and when I eventually re-looked at the PPPoE configuration, the 'null service name' was unchecked by itself.
This was a couple of months ago (April/May?) though, and I can't remember whether it was with the default 2 install or the daily update available on the firmware update page.
Do try rebooting after changing the PPPoE options. -
Thanks Thermo. So, your ppoe was default setting with ppoe login/password and did not work. And when you checked 'null service name' in advance setting, it started working?
Will give that try tonight.
I used that "trick" since long time ago ( Since "Beta 5" till "RC3" ), and my PPPoE connection works fine.
http://forum.pfsense.org/index.php/topic,34377.msg178168.html#msg178168
-
null service name still doesnt do the trick for most others like me and its definately something to do with mpd
-
Thanks ptt / thermo. Checking the "null service name" worked with an isp in Germany.
-
Attached are four files. Here's how I got them:
1. Boot system fresh. PPPoE connected.
2.```clog /var/log/system.log | egrep '(mpd|ppp)' > ppp_working.txt
cp /var/etc/mpd_wan.conf mpd_wan_working.conf.txt3\. Pull plug on WAN NIC. Wait 2 minutes. Re-plug. (WAN not connecting) 4.``` clog /var/log/system.log | egrep '(mpd|ppp)' > ppp_not_working.txt cp /var/etc/mpd_wan.conf mpd_wan_not_working.conf.txt
5. Reboot to working WAN.
Null Service Name is checked.
same here, mpd is the problem and i guess few others and myself have mentioned the same. some1 definitely needs to break apart mpd and have a look at its code
-
I split out the only recent report with info and am locking this thread as it's all over the place and the originally reported issues were long ago fixed and it's been hijacked a ton of times since.