Some PPPoE Bugs
-
Use a snapshot from Sept 16th or later. That will fix issue #1.
Not sure about the others.
-
ghnb should fix #3.
The others should be fixed on new snapshots. -
I have another pppoe-problem:
Looks like every time the pppoe-connections gets dropped by the provider and pfsense reconnects the connection is not made properly. Looks like the WAN gets a new ip address and everything seams to be fine, but it is not possible to send data over the WAN.
I setup pppoe resets to everyday, but still a death WAN connection in the morning, after reboot the WAN works as expected.
Running build from 9.Sept. on ALIX-board.
Bye,
eweri -
more info:
after a pppoe-reset the WAN connection stops working - it works again after a reboot of the router
Bye,
eweri -
Hi,
just updated to 2.0-BETA4 (i386) built on Thu Sep 16 13:40:26 EDT 2010 FreeBSD 8.1-RELEASE
The Dyndns accounts are still not updated after a reboot.
And i had the same problem as "eweri" this morning with the september 15. Build.
(dyndns on bootup)
Sep 17 10:33:53 apinger: No usable targets found, exiting Sep 17 10:33:54 check_reload_status: Rewriting resolv.conf Sep 17 10:33:55 kernel: em0: link state changed to UP Sep 17 10:33:55 dhcpd: Internet Systems Consortium DHCP Server V3.0.7 Sep 17 10:33:55 dhcpd: Copyright 2004-2008 Internet Systems Consortium. Sep 17 10:33:55 dhcpd: All rights reserved. Sep 17 10:33:55 dhcpd: For info, please visit http://www.isc.org/sw/dhcp/ Sep 17 10:33:55 php: : Removing static route for monitor 87.190.161.170 and adding a new route through 217.0.119.33 Sep 17 10:33:55 dnsmasq[32393]: started, version 2.55 cachesize 10000 Sep 17 10:33:55 dnsmasq[32393]: compile time options: no-IPv6 GNU-getopt no-DBus I18N DHCP TFTP Sep 17 10:33:55 dnsmasq[32393]: reading /etc/resolv.conf Sep 17 10:33:55 dnsmasq[32393]: using nameserver 217.237.150.51#53 Sep 17 10:33:55 dnsmasq[32393]: using nameserver 217.237.148.22#53 Sep 17 10:33:55 dnsmasq[32393]: read /etc/hosts - 2 addresses Sep 17 10:33:55 apinger: Starting Alarm Pinger, apinger(32848) Sep 17 10:34:55 php: : send_event: sent service reload dyndnsall got Sep 17 10:34:55 php: : send_event: sent service reload dyndns wan got Sep 17 10:34:57 php: : Creating rrd update script Sep 17 10:34:58 php: : Resyncing configuration for all packages. -
Dear Eweri, and everyone.
I've had the same problem.
I discovered the cause very difficult.
The wan interface settings "Advanced and MLPPP", I click on the line.
Name service line "Configure a NULL Service name" When I click I saw improvement.
I think some service providers do not provide this information automatically Pfsense wan interface can not run again.
Not experienced this problem as well Pfsense beta1. After beta 3 has changed.Best Regards.
-
hi,
adding dns servers is working now.
but the problem that eweri reported still exists and it's a pain in the a***
After the connection has been reset by the periodic reset, it is re-established correctly, but until I do a manual "filter reload" there is no traffic going through it….
and the Dyndns accounts are still not updated after a pppoe reset or after a complete reboot.
2.0-BETA4 (i386) built on Thu Sep 16 13:40:26 EDT 2010 FreeBSD 8.1-RELEASE
-
Hm, i setup a service name so this could not be the problem.
I setup the router to reboot at 3:15 in the morning but yesterday in the evening the connections to the internet was lost and after a power cyle today in the morning the connection was up and running again. I think it was a power cycle - i am not on site.
So why does a power cycle work but not a reboot? Maybe I setup cron wrong - just looking - right crontab was empty :-( stupid me - think I forgot to make fs writable before setting up a crontab for root.
This is what I setup now for user root:
15 3 * * * /sbin/shutdown -r nowShould work right?
Bye,
eweri -
All of the PPPoE Bugs are fixed now.
-
Hi,
Can I setup WAN1, WAN2, WAN3 with all PPPoE and work well??
Now I only connected one WAN (PPPoE) is OK but enable both not OK that just one connected at the same time
build i386
Thanks