Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Some PPPoE Bugs

    Scheduled Pinned Locked Moved 2.0-RC Snapshot Feedback and Problems - RETIRED
    11 Posts 6 Posters 4.0k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • T
      the6thday
      last edited by

      Hi,

      some PPPoE Bugs still present in 2.0-BETA4  (i386) built on Mon Sep 13 08:05:00 EDT 2010:

      1: I have to enter dns servers manually(system->general setup) since they don't get applied when the pppoe connection is established, looks like "Allow DNS server list to be overridden by DHCP/PPP on WAN" is not working…(see logs below...)

      2: Dyndns accounts are not updated with the new ip adress after a pppoe reconnect (periodic reset).

      3: When entering PPPoE account data in the "setup wizard" it is not saved correctly so what you get after the wizard is finished is a wan pppoe connection without username/password....

      
Sep 15 16:40:57 	ppp: PPPoE: rec'd ACNAME "MAIR71-se800-B2224180702378"
Sep 15 16:40:58 	ppp: [wan_link0] PPPoE: connection successful
Sep 15 16:40:58 	ppp: [wan_link0] Link: UP event
Sep 15 16:40:58 	ppp: [wan_link0] LCP: Up event
Sep 15 16:40:58 	ppp: [wan_link0] LCP: state change Starting --> Req-Sent
Sep 15 16:40:58 	ppp: [wan_link0] LCP: SendConfigReq #1
Sep 15 16:40:58 	ppp: [wan_link0] PROTOCOMP
Sep 15 16:40:58 	ppp: [wan_link0] MRU 1492
Sep 15 16:40:58 	ppp: [wan_link0] MAGICNUM e0890c48
Sep 15 16:40:58 	ppp: [wan_link0] LCP: rec'd Configure Request #202 (Req-Sent)
Sep 15 16:40:58 	ppp: [wan_link0] MRU 1492
Sep 15 16:40:58 	ppp: [wan_link0] AUTHPROTO PAP
Sep 15 16:40:58 	ppp: [wan_link0] MAGICNUM 77e7ba53
Sep 15 16:40:58 	ppp: [wan_link0] LCP: SendConfigAck #202
Sep 15 16:40:58 	ppp: [wan_link0] MRU 1492
Sep 15 16:40:58 	ppp: [wan_link0] AUTHPROTO PAP
Sep 15 16:40:58 	ppp: [wan_link0] MAGICNUM 77e7ba53
Sep 15 16:40:58 	ppp: [wan_link0] LCP: state change Req-Sent --> Ack-Sent
Sep 15 16:40:58 	ppp: [wan_link0] LCP: rec'd Configure Reject #1 (Ack-Sent)
Sep 15 16:40:58 	ppp: [wan_link0] PROTOCOMP
Sep 15 16:40:58 	ppp: [wan_link0] LCP: SendConfigReq #2
Sep 15 16:40:58 	ppp: [wan_link0] MRU 1492
Sep 15 16:40:58 	ppp: [wan_link0] MAGICNUM e0890c48
Sep 15 16:40:58 	ppp: [wan_link0] LCP: rec'd Configure Ack #2 (Ack-Sent)
Sep 15 16:40:58 	ppp: [wan_link0] MRU 1492
Sep 15 16:40:58 	ppp: [wan_link0] MAGICNUM e0890c48
Sep 15 16:40:58 	ppp: [wan_link0] LCP: state change Ack-Sent --> Opened
Sep 15 16:40:58 	ppp: [wan_link0] LCP: auth: peer wants PAP, I want nothing
Sep 15 16:40:58 	ppp: [wan_link0] PAP: using authname "xxxxxxxxxxxxxxx"
Sep 15 16:40:58 	ppp: [wan_link0] PAP: sending REQUEST #1 len: 54
Sep 15 16:40:58 	ppp: [wan_link0] LCP: LayerUp
Sep 15 16:40:58 	ppp: [wan_link0] PAP: rec'd ACK #1 len: 5
Sep 15 16:40:58 	ppp: [wan_link0] LCP: authorization successful
Sep 15 16:40:58 	ppp: [wan_link0] Link: Matched action 'bundle "wan" ""'
Sep 15 16:40:58 	ppp: [wan_link0] Link: Join bundle "wan"
Sep 15 16:40:58 	ppp: [wan] Bundle: Status update: up 1 link, total bandwidth 64000 bps
Sep 15 16:40:58 	ppp: [wan] IPCP: Open event
Sep 15 16:40:58 	ppp: [wan] IPCP: state change Initial --> Starting
Sep 15 16:40:58 	ppp: [wan] IPCP: LayerStart
Sep 15 16:40:58 	ppp: [wan] IPCP: Up event
Sep 15 16:40:58 	ppp: [wan] IPCP: state change Starting --> Req-Sent
Sep 15 16:40:58 	ppp: [wan] IPCP: SendConfigReq #1
Sep 15 16:40:58 	ppp: [wan] IPADDR 0.0.0.0
Sep 15 16:40:58 	ppp: [wan] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
Sep 15 16:40:58 	ppp: [wan] PRIDNS 0.0.0.0
Sep 15 16:40:58 	ppp: [wan] SECDNS 0.0.0.0
Sep 15 16:40:58 	ppp: [wan] IPCP: rec'd Configure Request #169 (Req-Sent)
Sep 15 16:40:58 	ppp: [wan] IPADDR 217.0.119.33
Sep 15 16:40:58 	ppp: [wan] 217.0.119.33 is OK
Sep 15 16:40:58 	ppp: [wan] IPCP: SendConfigAck #169
Sep 15 16:40:58 	ppp: [wan] IPADDR 217.0.119.33
Sep 15 16:40:58 	ppp: [wan] IPCP: state change Req-Sent --> Ack-Sent
Sep 15 16:40:58 	ppp: [wan] IPCP: rec'd Configure Reject #1 (Ack-Sent)
Sep 15 16:40:58 	ppp: [wan] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
Sep 15 16:40:58 	ppp: [wan] IPCP: SendConfigReq #2
Sep 15 16:40:58 	ppp: [wan] IPADDR 0.0.0.0
Sep 15 16:40:58 	ppp: [wan] PRIDNS 0.0.0.0
Sep 15 16:40:58 	ppp: [wan] SECDNS 0.0.0.0
Sep 15 16:40:58 	ppp: [wan] IPCP: rec'd Configure Nak #2 (Ack-Sent)
Sep 15 16:40:58 	ppp: [wan] IPADDR 79.225.54.49
Sep 15 16:40:58 	ppp: [wan] 79.225.54.49 is OK
Sep 15 16:40:58 	ppp: [wan] PRIDNS 217.237.148.22
Sep 15 16:40:58 	ppp: [wan] SECDNS 217.237.150.51
Sep 15 16:40:58 	ppp: [wan] IPCP: SendConfigReq #3
Sep 15 16:40:58 	ppp: [wan] IPADDR 79.225.54.49
Sep 15 16:40:58 	ppp: [wan] PRIDNS 217.237.148.22
Sep 15 16:40:58 	ppp: [wan] SECDNS 217.237.150.51
Sep 15 16:40:58 	ppp: [wan] IPCP: rec'd Configure Ack #3 (Ack-Sent)
Sep 15 16:40:58 	ppp: [wan] IPADDR 79.225.54.49
Sep 15 16:40:58 	ppp: [wan] PRIDNS 217.237.148.22
Sep 15 16:40:58 	ppp: [wan] SECDNS 217.237.150.51
Sep 15 16:40:58 	ppp: [wan] IPCP: state change Ack-Sent --> Opened
Sep 15 16:40:58 	ppp: [wan] IPCP: LayerUp
Sep 15 16:40:58 	ppp: [wan] 79.225.54.49 -> 217.0.119.33
Sep 15 16:40:58 	ppp: [wan] IFACE: Up event


      
Sep 15 16:40:57 	kernel: em1: link state changed to UP
Sep 15 16:40:57 	kernel: em1_vlan7: link state changed to UP
Sep 15 16:40:57 	php: : Could not find gateway for interface(wan).
Sep 15 16:40:57 	last message repeated 4 times
Sep 15 16:40:58 	apinger: Starting Alarm Pinger, apinger(18487)
Sep 15 16:40:58 	apinger: No usable targets found, exiting
Sep 15 16:40:59 	php: : ROUTING: change default route to 217.0.119.33
Sep 15 16:40:59 	check_reload_status: Linkup starting em0
Sep 15 16:40:59 	kernel: em0: link state changed to UP
Sep 15 16:40:59 	dhcpd: Internet Systems Consortium DHCP Server V3.0.7
Sep 15 16:40:59 	dhcpd: Copyright 2004-2008 Internet Systems Consortium.
Sep 15 16:40:59 	dhcpd: All rights reserved.
Sep 15 16:40:59 	dhcpd: For info, please visit http://www.isc.org/sw/dhcp/
Sep 15 16:40:59 	dnsmasq[34372]: started, version 2.55 cachesize 10000
Sep 15 16:40:59 	dnsmasq[34372]: compile time options: no-IPv6 GNU-getopt no-DBus I18N DHCP TFTP
Sep 15 16:40:59 	dnsmasq[34372]: no servers found in /etc/resolv.conf, will retry
Sep 15 16:40:59 	dnsmasq[34372]: no servers found in /etc/resolv.conf, will retry
Sep 15 16:40:59 	dnsmasq[34372]: read /etc/hosts - 2 addresses
Sep 15 16:40:59 	check_reload_status: updating all dyndns
Sep 15 16:41:02 	php: : Creating rrd update script
Sep 15 16:41:02 	php: : Resyncing configuration for all packages.
      1 Reply Last reply Reply Quote 0
      • G
        gnhb
        last edited by

        Use a snapshot from Sept 16th or later. That will fix issue #1.

        Not sure about the others.

        1 Reply Last reply Reply Quote 0
        • E
          eri--
          last edited by

          ghnb should fix #3.
          The others should be fixed on new snapshots.

          1 Reply Last reply Reply Quote 0
          • E
            eweri
            last edited by

            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

            1 Reply Last reply Reply Quote 0
            • E
              eweri
              last edited by

              more info:

              after a pppoe-reset the WAN connection stops working - it works again after a reboot of the router

              Bye,
              eweri

              1 Reply Last reply Reply Quote 0
              • T
                the6thday
                last edited by

                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.
                1 Reply Last reply Reply Quote 0
                • C
                  cemx
                  last edited by

                  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.

                  Kelimesiz geldiğin fikirler yol almaz..

                  1 Reply Last reply Reply Quote 0
                  • T
                    the6thday
                    last edited by

                    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

                    1 Reply Last reply Reply Quote 0
                    • E
                      eweri
                      last edited by

                      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 now

                      Should work right?

                      Bye,
                      eweri

                      1 Reply Last reply Reply Quote 0
                      • T
                        the6thday
                        last edited by

                        All of the PPPoE Bugs are fixed now.

                        1 Reply Last reply Reply Quote 0
                        • B
                          black
                          last edited by

                          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

                          1 Reply Last reply Reply Quote 0
                          • First post
                            Last post
                          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.