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

    [2.3.x] No default route on WAN PPPoE after link failure (with FIX, please test)

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    42 Posts 7 Posters 13.6k 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.
    • M
      Marlenio
      last edited by

      @sammcj:

      […]
      From memory this has been a problem for quite some time, I'll see if I can find the original bug report.

      Yes, there is redmine #1837 ticket about a similar issue, but the proposed solution by editing the file (/etc/inc/interfaces.inc) stop the creation of the default gateway if the PPPoE session is disconnected. For this reason i modified the code and now it look like that in version 2.2.6 (which worked perfectly).

      Today i made some other test with my pfSense box (Atom 1037U CPU), an Alix, an HP DL380 end a portable DELL. My ISP is a 100/20 FTTC (Telecom Fibra). Same config: clean install, then restore from 2.2.6 config backup. Everybody have the same problems on PPPoE.

      Marlenio

      1 Reply Last reply Reply Quote 0
      • S
        sammcj
        last edited by

        fyi - mine also has the default gateway set.

        1 Reply Last reply Reply Quote 0
        • M
          Marlenio
          last edited by

          @cmb: do you think it would be possible to modify code so as to keep both version (2.2.6 and 2.3.x) in file /etc/inc/interfaces.inc? Code was modifyied in 2.3 for a issue (#1837) about multiwan gateway switching, but it seems to have problems with a single wan gateway config. In "single gateway mode" code would run set iface route default command, in "multi gateway mode" no.

          Marlenio

          1 Reply Last reply Reply Quote 0
          • J
            jumpymonkey
            last edited by

            I came back to pfsense having used another router while having this problem. Having started it up, I found that the PPP interface wouldn't come up. Looking under advanced config on the PPPoE link, no underlying interface was selected. Having set that the interface came up and routed correctly. I'll continue to monitor and see want happens when the underlaying DSL link fail cycles.

            1 Reply Last reply Reply Quote 0
            • M
              Marlenio
              last edited by

              @jumpymonkey:

              I came back to pfsense having used another router while having this problem. Having started it up, I found that the PPP interface wouldn't come up. Looking under advanced config on the PPPoE link, no underlying interface was selected. Having set that the interface came up and routed correctly. I'll continue to monitor and see want happens when the underlaying DSL link fail cycles.

              Can you try the mod in /etc/inc/interfaces.inc i post?

              Marlenio

              1 Reply Last reply Reply Quote 0
              • J
                jumpymonkey
                last edited by

                It's working without the mod. I was about to try your mod, but now the interface is up and working as expected. I'll see what happens when I pull the modem link out later, and if that stops the routing working I'll apply the mod.

                1 Reply Last reply Reply Quote 0
                • M
                  Marlenio
                  last edited by

                  @jumpymonkey:

                  It's working without the mod. I was about to try your mod, but now the interface is up and working as expected. I'll see what happens when I pull the modem link out later, and if that stops the routing working I'll apply the mod.

                  What happened if you disconnect and riconnect WAN or PPPoE cable from modem?

                  Marlenio

                  1 Reply Last reply Reply Quote 0
                  • J
                    jumpymonkey
                    last edited by

                    I cycled the modem. When the link came back up, the I couldn't connect out to the Internet. Adding your fix and cycling the PPPoE link fixes the problem. Thanks!

                    1 Reply Last reply Reply Quote 0
                    • M
                      Marlenio
                      last edited by

                      @jumpymonkey:

                      I cycled the modem. When the link came back up, the I couldn't connect out to the Internet. Adding your fix and cycling the PPPoE link fixes the problem. Thanks!

                      Well, my fix is actually the same code present in 2.2.6, that works without problem. Thank you for test.  :)

                      Marlenio

                      1 Reply Last reply Reply Quote 0
                      • R
                        robi
                        last edited by

                        Is there a redmine on this?

                        1 Reply Last reply Reply Quote 0
                        • M
                          Marlenio
                          last edited by

                          @robi:

                          Is there a redmine on this?

                          Yes: https://forum.pfsense.org/index.php?topic=113750.msg632702#msg632702

                          Marlenio

                          1 Reply Last reply Reply Quote 0
                          • R
                            robi
                            last edited by

                            OK, for pfSense people to take this seriously you'll have to create it as a patch here:
                            https://github.com/pfsense/pfsense

                            Just register, choose your file, click the pencil icon to edit it, and it will create a fork for you. Then, submit a pull request for your fork. In the description, link to this topic and the redmine issue.

                            1 Reply Last reply Reply Quote 0
                            • M
                              Marlenio
                              last edited by

                              @robi:

                              OK, for pfSense people to take this seriously you'll have to create it as a patch here:
                              https://github.com/pfsense/pfsense

                              Just register, choose your file, click the pencil icon to edit it, and it will create a fork for you. Then, submit a pull request for your fork. In the description, link to this topic and the redmine issue.

                              Hi Roby, i'm not a PHP developer, so i don't think it's a good idea modify code on my own. Anyway, in redmine #6495 i suggested a possibile change about code:

                              if ONE GW then
                                  <the code="" i="" modify="">else (TWO or MORE GW)
                                  endif</the>                               `In this way it could work both configuration, one WAN gateway or two (or more).

                              P.S. What do you mean for "…for pfSense people to take this seriously"?`

                              Marlenio

                              1 Reply Last reply Reply Quote 0
                              • R
                                robi
                                last edited by

                                You said "my fix is actually the same code…" - I thougt you have a real fix for the problem...

                                As far as I noticed over the years, code snippets posted on the forum almost never reach to be in the actual product.

                                1 Reply Last reply Reply Quote 0
                                • M
                                  Marlenio
                                  last edited by

                                  @robi:

                                  You said "my fix is actually the same code…" - I thougt you have a real fix for the problem...

                                  As far as I noticed over the years, code snippets posted on the forum almost never reach to be in the actual product.

                                  As you can read in my reply to jumpymonkey, my fix is simply the recovery of the code of 2.2.6, that not rem the line set iface route default. But as said in Redmine #1837, 2.2.6 code works well with one WAN gateway, but create problems with multi WAN gateway configuration. So i thought multi choice <if…else...endif>would be a good solution.</if…else...endif>

                                  Marlenio

                                  1 Reply Last reply Reply Quote 0
                                  • R
                                    robi
                                    last edited by

                                    OK, the problem that this is all so confusing with your fix. Sorry.

                                    I don't mean to to offend you with this, just trying to help. Which file, which line number should be replaced with what.
                                    PHP is so easy…

                                    1 Reply Last reply Reply Quote 0
                                    • M
                                      Marlenio
                                      last edited by

                                      @robi:

                                      OK, the problem that this is all so confusing with your fix. Sorry.

                                      I don't mean to to hurt you with this, just trying to help. Which file, which line number should be replaced with what.
                                      PHP is so easy…

                                      Hi robi, really, there's absolutely no problem, why should be hurt?  :)  I'm not a PHP developer (i'm a network admin) and at office i managed 14 (16) pfSense box with WAN static IP. But i have pfSense at home too with PPPoE connection, and from 2.3 release i have several problem with auth. I have a little bit of knowledge of programming, so i try to investigate and finally i found redmine #1837 and so on.

                                      I start to learn PHP, but I think it is still early and I'm not at an advanced level as the official team, so I think it's better to just report the bug.  ;) ;)

                                      File is /etc/inc/interfaces.inc from line 1806 to line 1815.

                                      Thanks in advance.  :)

                                      Marlenio

                                      1 Reply Last reply Reply Quote 0
                                      • C
                                        cmb
                                        last edited by

                                        @robi:

                                        OK, for pfSense people to take this seriously you'll have to create it as a patch here:
                                        https://github.com/pfsense/pfsense

                                        Not true, there is a bug open and we'll get a proper fix. Going back to the change discussed in this thread will regress other things and isn't right. We need to track down the real source of the issue and fix that. I can't replicate it at all though, so going to need some help from those who can.

                                        mpd calls ppp-linkup after connecting, which triggers rc.newwanip. rc.newwanip sets the default gateway.

                                        When you're left with no default gateway after a reconnect, check the system log. What is there from rc.newwanip? Should see something like:

                                        rc.newwanip: ROUTING: setting default route to x.x.x.x

                                        is that there? What else is logged at the time?

                                        If you cause the WAN NIC to lose its link, in addition to rc.newwanip, rc.linkup will also set the default gateway and have a similar log. So you'll see it twice in that case, which is fine.

                                        Note I'm talking about using strictly stock source code, not the change in this thread. Revert that change first if you made it.

                                        1 Reply Last reply Reply Quote 0
                                        • M
                                          Marlenio
                                          last edited by

                                          @cmb:

                                          […]
                                          When you're left with no default gateway after a reconnect, check the system log. What is there from rc.newwanip? Should see something like:

                                          rc.newwanip: ROUTING: setting default route to x.x.x.x

                                          is that there? What else is logged at the time?

                                          If you cause the WAN NIC to lose its link, in addition to rc.newwanip, rc.linkup will also set the default gateway and have a similar log. So you'll see it twice in that case, which is fine.

                                          Note I'm talking about using strictly stock source code, not the change in this thread. Revert that change first if you made it.

                                          Hi Cmb,
                                          thanks for your post. I'll try and post the log.  :)

                                          Actually i can test with 3 PPPoE ISP provider and 1 PPPoA (converted by modem in PPPoE) ISP and four different hardware (Alix, APU, x64 a i386). I follow redmine #6495 status, as soon as a fix is posted, i'll try and let you know.

                                          Thanks in advance,

                                          –
                                          Marlenio

                                          Marlenio

                                          1 Reply Last reply Reply Quote 0
                                          • M
                                            Marlenio
                                            last edited by

                                            @cmb:

                                            […]
                                            When you're left with no default gateway after a reconnect, check the system log. What is there from rc.newwanip? Should see something like:

                                            rc.newwanip: ROUTING: setting default route to x.x.x.x

                                            is that there? What else is logged at the time?

                                            If you cause the WAN NIC to lose its link, in addition to rc.newwanip, rc.linkup will also set the default gateway and have a similar log. So you'll see it twice in that case, which is fine.

                                            Note I'm talking about using strictly stock source code, not the change in this thread. Revert that change first if you made it.

                                            Hi cmb, i revert the change, clear log and disconnect/reconnect PPPoE WAN interface. Here is the log. Look at line 71/72:

                                            
Jun 22 20:13:08	php-fpm	40496	/rc.dyndns.update: Curl error occurred: Could not resolve host: ipv4.tunnelbroker.net
Jun 22 20:13:07	php-fpm	31985	/rc.newwanip: Curl error occurred: Could not resolve host: freedns.afraid.org
Jun 22 20:13:07	php-fpm	31985	/rc.newwanip: Dynamic DNS freedns (casalener.mooo.com): _checkStatus() starting.
Jun 22 20:13:00	xinetd	14152	Reconfigured: new=0 old=1 dropped=0 (services)
Jun 22 20:13:00	xinetd	14152	readjusting service 6969-udp
Jun 22 20:13:00	xinetd	14152	Swapping defaults
Jun 22 20:13:00	xinetd	14152	Starting reconfiguration
Jun 22 20:12:59	php-fpm	31985	/rc.newwanip: Dynamic DNS freedns (casalener.mooo.com): _update() starting.
Jun 22 20:12:59	php-fpm	31985	/rc.newwanip: DynDns (casalener.mooo.com): Dynamic Dns: cacheIP != wan_ip. Updating. Cached IP: 82.51.169.204 WAN IP: 79.17.44.55
Jun 22 20:12:59	php-fpm	31985	/rc.newwanip: Dynamic Dns (casalener.mooo.com): Current WAN IP: 79.17.44.55 Cached IP: 82.51.169.204
Jun 22 20:12:59	php-fpm	31985	/rc.newwanip: Dynamic DNS freedns (casalener.mooo.com): 79.17.44.55 extracted from local system.
Jun 22 20:12:59	php-fpm	31985	/rc.newwanip: Dynamic DNS (casalener.mooo.com): running get_failover_interface for wan. found pppoe1
Jun 22 20:12:59	php-fpm	31985	/rc.newwanip: Dynamic DNS freedns (casalener.mooo.com): 79.17.44.55 extracted from local system.
Jun 22 20:12:59	php-fpm	40496	/rc.dyndns.update: Curl error occurred: Could not resolve host: freedns.afraid.org
Jun 22 20:12:59	php-fpm	40496	/rc.dyndns.update: Dynamic DNS freedns (casalener.mooo.com): _checkStatus() starting.
Jun 22 20:12:59	php-fpm	31985	/rc.newwanip: Dynamic DNS: updatedns() starting
Jun 22 20:12:58	xinetd	14152	Reconfigured: new=0 old=1 dropped=0 (services)
Jun 22 20:12:58	xinetd	14152	readjusting service 6969-udp
Jun 22 20:12:58	xinetd	14152	Swapping defaults
Jun 22 20:12:58	xinetd	14152	Starting reconfiguration
Jun 22 20:12:58	check_reload_status		Reloading filter
Jun 22 20:12:58	php-fpm	24848	/rc.newipsecdns: IPSEC: One or more IPsec tunnel endpoints has changed its IP. Refreshing.
Jun 22 20:12:58	php-fpm	31985	/rc.newwanip: Curl error occurred: Could not resolve host: dynupdate.no-ip.com
Jun 22 20:12:57	xinetd	14152	Reconfigured: new=0 old=1 dropped=0 (services)
Jun 22 20:12:57	xinetd	14152	readjusting service 6969-udp
Jun 22 20:12:57	xinetd	14152	Swapping defaults
Jun 22 20:12:57	xinetd	14152	Starting reconfiguration
Jun 22 20:12:56	xinetd	14152	Reconfigured: new=0 old=1 dropped=0 (services)
Jun 22 20:12:56	xinetd	14152	readjusting service 6969-udp
Jun 22 20:12:56	xinetd	14152	Swapping defaults
Jun 22 20:12:56	xinetd	14152	Starting reconfiguration
Jun 22 20:12:56	check_reload_status		Reloading filter
Jun 22 20:12:56	php-fpm	46306	/rc.newipsecdns: IPSEC: One or more IPsec tunnel endpoints has changed its IP. Refreshing.
Jun 22 20:12:50	php-fpm	40496	/rc.dyndns.update: Dynamic DNS freedns (casalener.mooo.com): _update() starting.
Jun 22 20:12:50	php-fpm	40496	/rc.dyndns.update: DynDns (casalener.mooo.com): Dynamic Dns: cacheIP != wan_ip. Updating. Cached IP: 82.51.169.204 WAN IP: 79.17.44.55
Jun 22 20:12:50	php-fpm	40496	/rc.dyndns.update: Dynamic Dns (casalener.mooo.com): Current WAN IP: 79.17.44.55 Cached IP: 82.51.169.204
Jun 22 20:12:50	php-fpm	40496	/rc.dyndns.update: Dynamic DNS freedns (casalener.mooo.com): 79.17.44.55 extracted from local system.
Jun 22 20:12:50	php-fpm	40496	/rc.dyndns.update: Dynamic DNS (casalener.mooo.com): running get_failover_interface for wan. found pppoe1
Jun 22 20:12:50	php-fpm	40496	/rc.dyndns.update: Dynamic DNS freedns (casalener.mooo.com): 79.17.44.55 extracted from local system.
Jun 22 20:12:50	php-fpm	40496	/rc.dyndns.update: Dynamic DNS: updatedns() starting
Jun 22 20:12:49	php-fpm	40496	/rc.dyndns.update: Curl error occurred: Could not resolve host: dynupdate.no-ip.com
Jun 22 20:12:43	kernel		gif0: link state changed to UP
Jun 22 20:12:43	kernel		gif0: link state changed to DOWN
Jun 22 20:12:43	php-fpm	24848	/status_interfaces.php: ROUTING: setting IPv6 default route to 2001:470:1f12:62c::1
Jun 22 20:12:39	check_reload_status		Reloading filter
Jun 22 20:12:39	check_reload_status		Restarting OpenVPN tunnels/interfaces
Jun 22 20:12:39	check_reload_status		Reloading filter
Jun 22 20:12:39	check_reload_status		Restarting ipsec tunnels
Jun 22 20:12:39	check_reload_status		Restarting OpenVPN tunnels/interfaces
Jun 22 20:12:39	check_reload_status		updating dyndns WAN_PPPOE
Jun 22 20:12:39	check_reload_status		Restarting ipsec tunnels
Jun 22 20:12:39	check_reload_status		updating dyndns HE_IPV6_TUNNELV6
Jun 22 20:12:37	ppp		[wan] IPV6CP: LayerFinish
Jun 22 20:12:37	ppp		[wan] IPV6CP: state change Stopping --> Stopped
Jun 22 20:12:36	php-fpm	31985	/rc.newwanip: Removing static route for monitor 2001:4860:4860::8888 and adding a new route through 2001:470:1f12:62c::1
Jun 22 20:12:36	php-fpm	40496	/rc.resolv_conf_generate: The command '/sbin/route delete -host 208.67.220.220 ' returned exit code '1', the output was 'route: writing to routing socket: No such process delete host 208.67.220.220 fib 0: not in table'
Jun 22 20:12:36	php-fpm	40496	/rc.resolv_conf_generate: The command '/sbin/route delete -host 208.67.222.222 ' returned exit code '1', the output was 'route: writing to routing socket: No such process delete host 208.67.222.222 fib 0: not in table'
Jun 22 20:12:36	php-fpm	40496	/rc.newwanipv6: rc.newwanipv6: No IPv6 address found for interface WAN [wan].
Jun 22 20:12:36	php-fpm	40496	/rc.newwanipv6: rc.newwanipv6: Info: starting on pppoe1.
Jun 22 20:12:35	xinetd	14152	Reconfigured: new=0 old=1 dropped=0 (services)
Jun 22 20:12:35	xinetd	14152	readjusting service 6969-udp
Jun 22 20:12:35	xinetd	14152	Swapping defaults
Jun 22 20:12:35	xinetd	14152	Starting reconfiguration
Jun 22 20:12:35	php-fpm	31985	/rc.newwanip: IP has changed, killing states on former IP 87.1.223.208.
Jun 22 20:12:35	kernel		gif0: link state changed to UP
Jun 22 20:12:35	kernel		gif0: link state changed to DOWN
Jun 22 20:12:35	php-fpm	31985	/rc.newwanip: ROUTING: setting IPv6 default route to 2001:470:1f12:62c::1
Jun 22 20:12:35	kernel		gif0: link state changed to UP
Jun 22 20:12:35	kernel		gif0: link state changed to DOWN
Jun 22 20:12:35	php-fpm	31985	/rc.newwanip: ROUTING: setting IPv6 default route to 2001:470:1f12:62c::1
Jun 22 20:12:35	php-fpm	31985	/rc.newwanip: The command '/sbin/route delete -host 208.67.220.220 ' returned exit code '1', the output was 'route: writing to routing socket: No such process delete host 208.67.220.220 fib 0: not in table'
Jun 22 20:12:35	php-fpm	31985	/rc.newwanip: The command '/sbin/route delete -host 208.67.222.222 ' returned exit code '1', the output was 'route: writing to routing socket: No such process delete host 208.67.222.222 fib 0: not in table'
Jun 22 20:12:35	php-fpm	31985	/rc.newwanip: rc.newwanip: on (IP address: 79.17.44.55) (interface: WAN[wan]) (real interface: pppoe1).
Jun 22 20:12:35	php-fpm	31985	/rc.newwanip: rc.newwanip: Info: starting on pppoe1.
Jun 22 20:12:34	check_reload_status		Rewriting resolv.conf
Jun 22 20:12:34	ppp		[wan] IPV6CP: LayerDown
Jun 22 20:12:34	ppp		[wan] IPV6CP: SendTerminateAck #2
Jun 22 20:12:34	ppp		[wan] IPV6CP: state change Opened --> Stopping
Jun 22 20:12:34	ppp		[wan] IPV6CP: rec'd Terminate Request #91 (Opened)
Jun 22 20:12:34	check_reload_status		rc.newwanipv6 starting pppoe1
Jun 22 20:12:34	ppp		[wan] 76d4:35ff:fe8a:b19c -> 02a0:a50f:fc86:8004
Jun 22 20:12:34	ppp		[wan] IPV6CP: LayerUp
Jun 22 20:12:34	ppp		[wan] IPV6CP: state change Ack-Rcvd --> Opened
Jun 22 20:12:34	ppp		[wan] IPV6CP: SendConfigAck #90
Jun 22 20:12:34	ppp		[wan] IPV6CP: rec'd Configure Request #90 (Ack-Rcvd)
Jun 22 20:12:34	ppp		[wan] IFACE: Rename interface ng0 to pppoe1
Jun 22 20:12:34	ppp		[wan] IFACE: Up event
Jun 22 20:12:34	check_reload_status		rc.newwanip starting pppoe1
Jun 22 20:12:34	ppp		[wan] 79.17.44.55 -> 192.168.100.1
Jun 22 20:12:34	ppp		[wan] IPCP: LayerUp
Jun 22 20:12:34	ppp		[wan] IPCP: state change Ack-Rcvd --> Opened
Jun 22 20:12:34	ppp		[wan] IPADDR 192.168.100.1
Jun 22 20:12:34	ppp		[wan] IPCP: SendConfigAck #26
Jun 22 20:12:34	ppp		[wan] 192.168.100.1 is OK
Jun 22 20:12:34	ppp		[wan] IPADDR 192.168.100.1
Jun 22 20:12:34	ppp		[wan] IPCP: rec'd Configure Request #26 (Ack-Rcvd)
Jun 22 20:12:34	ppp		[wan] IPCP: state change Req-Sent --> Ack-Rcvd
Jun 22 20:12:34	ppp		[wan] IPADDR 79.17.44.55
Jun 22 20:12:34	ppp		[wan] IPCP: rec'd Configure Ack #3 (Req-Sent)
Jun 22 20:12:34	ppp		[wan] IPADDR 79.17.44.55
Jun 22 20:12:34	ppp		[wan] IPCP: SendConfigReq #3
Jun 22 20:12:34	ppp		[wan] 79.17.44.55 is OK
Jun 22 20:12:34	ppp		[wan] IPADDR 79.17.44.55
Jun 22 20:12:34	ppp		[wan] IPCP: rec'd Configure Nak #2 (Req-Sent)
Jun 22 20:12:34	ppp		[wan] IPV6CP: state change Req-Sent --> Ack-Rcvd
Jun 22 20:12:34	ppp		[wan] IPV6CP: rec'd Configure Ack #1 (Req-Sent)
Jun 22 20:12:34	ppp		[wan] IPADDR 0.0.0.0
Jun 22 20:12:34	ppp		[wan] IPCP: SendConfigReq #2
Jun 22 20:12:34	ppp		[wan] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
Jun 22 20:12:34	ppp		[wan] IPCP: rec'd Configure Reject #1 (Req-Sent)
Jun 22 20:12:34	ppp		[wan] IPV6CP: SendConfigReq #1
Jun 22 20:12:34	ppp		[wan] IPV6CP: state change Starting --> Req-Sent
Jun 22 20:12:34	ppp		[wan] IPV6CP: Up event
Jun 22 20:12:34	ppp		[wan] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
Jun 22 20:12:34	ppp		[wan] IPADDR 0.0.0.0
Jun 22 20:12:34	ppp		[wan] IPCP: SendConfigReq #1
Jun 22 20:12:34	ppp		[wan] IPCP: state change Starting --> Req-Sent
Jun 22 20:12:34	ppp		[wan] IPCP: Up event
Jun 22 20:12:34	ppp		[wan] IPV6CP: LayerStart
Jun 22 20:12:34	ppp		[wan] IPV6CP: state change Initial --> Starting
Jun 22 20:12:34	ppp		[wan] IPV6CP: Open event
Jun 22 20:12:34	ppp		[wan] IPCP: LayerStart
Jun 22 20:12:34	ppp		[wan] IPCP: state change Initial --> Starting
Jun 22 20:12:34	ppp		[wan] IPCP: Open event
Jun 22 20:12:34	ppp		[wan] Bundle: Status update: up 1 link, total bandwidth 64000 bps
Jun 22 20:12:34	ppp		[wan_link0] Link: Join bundle "wan"
Jun 22 20:12:34	ppp		[wan_link0] Link: Matched action 'bundle "wan" ""'
Jun 22 20:12:34	ppp		[wan_link0] LCP: authorization successful
Jun 22 20:12:34	ppp		[wan_link0] PAP: rec'd ACK #1 len: 5
Jun 22 20:12:34	ppp		[wan_link0] LCP: LayerUp
Jun 22 20:12:34	ppp		[wan_link0] PAP: sending REQUEST #1 len: 24
Jun 22 20:12:34	ppp		[wan_link0] PAP: using authname "aliceadsl"
Jun 22 20:12:34	ppp		[wan_link0] LCP: auth: peer wants PAP, I want nothing
Jun 22 20:12:34	ppp		[wan_link0] LCP: state change Ack-Sent --> Opened
Jun 22 20:12:34	ppp		[wan_link0] MAGICNUM 0x30806941
Jun 22 20:12:34	ppp		[wan_link0] MRU 1492
Jun 22 20:12:34	ppp		[wan_link0] PROTOCOMP
Jun 22 20:12:34	ppp		[wan_link0] LCP: rec'd Configure Ack #1 (Ack-Sent)
Jun 22 20:12:34	ppp		[wan_link0] LCP: state change Req-Sent --> Ack-Sent
Jun 22 20:12:34	ppp		[wan_link0] MAGICNUM 0x0107258b
Jun 22 20:12:34	ppp		[wan_link0] AUTHPROTO PAP
Jun 22 20:12:34	ppp		[wan_link0] MRU 1492
Jun 22 20:12:34	ppp		[wan_link0] LCP: SendConfigAck #48
Jun 22 20:12:34	ppp		[wan_link0] MAGICNUM 0x0107258b
Jun 22 20:12:34	ppp		[wan_link0] AUTHPROTO PAP
Jun 22 20:12:34	ppp		[wan_link0] MRU 1492
Jun 22 20:12:34	ppp		[wan_link0] LCP: rec'd Configure Request #48 (Req-Sent)
Jun 22 20:12:34	ppp		[wan_link0] MAGICNUM 0x30806941
Jun 22 20:12:34	ppp		[wan_link0] MRU 1492
Jun 22 20:12:34	ppp		[wan_link0] PROTOCOMP
Jun 22 20:12:34	ppp		[wan_link0] LCP: SendConfigReq #1
Jun 22 20:12:34	ppp		[wan_link0] LCP: state change Starting --> Req-Sent
Jun 22 20:12:34	ppp		[wan_link0] LCP: Up event
Jun 22 20:12:34	ppp		[wan_link0] Link: UP event
Jun 22 20:12:34	ppp		[wan_link0] PPPoE: connection successful
Jun 22 20:12:33	ppp		PPPoE: rec'd ACNAME "r-rm900"
Jun 22 20:12:33	ppp		[wan_link0] PPPoE: Connecting to 'TelecomFibra'
Jun 22 20:12:33	ppp		[wan_link0] LCP: LayerStart
Jun 22 20:12:33	ppp		[wan_link0] LCP: state change Initial --> Starting
Jun 22 20:12:33	ppp		[wan_link0] LCP: Open event
Jun 22 20:12:33	kernel		ng0: changing name to 'pppoe1'
Jun 22 20:12:33	ppp		[wan_link0] Link: OPEN event
Jun 22 20:12:33	ppp		[wan] Bundle: Interface ng0 created
Jun 22 20:12:33	ppp		web: web is not running
Jun 22 20:12:33	ppp		process 31483 started, version 5.8 (root@pfSense_v2_3_1_amd64-pfSense_v2_3_1-job-13 19:20 16-May-2016)
Jun 22 20:12:33	ppp		Multi-link PPP daemon for FreeBSD
Jun 22 20:12:29	ppp		process 5179 terminated
Jun 22 20:12:29	ppp		[wan_link0] Link: Shutdown
Jun 22 20:12:29	ppp		[wan] Bundle: Shutdown
[b]Jun 22 20:12:28	php-fpm	24848	/rc.resolv_conf_generate: The command '/sbin/route delete -host 208.67.220.220 ' returned exit code '1', the output was 'route: writing to routing socket: No such process delete host 208.67.220.220 fib 0: not in table'
Jun 22 20:12:28	php-fpm	24848	/rc.resolv_conf_generate: The command '/sbin/route delete -host 208.67.222.222 ' returned exit code '1', the output was 'route: writing to routing socket: No such process delete host 208.67.222.222 fib 0: not in table'[/b]
Jun 22 20:12:27	ppp		[wan_link0] LCP: state change Stopping --> Closing
Jun 22 20:12:27	ppp		[wan_link0] LCP: Close event
Jun 22 20:12:27	ppp		[wan_link0] Link: CLOSE event
Jun 22 20:12:27	ppp		[wan_link0] LCP: LayerDown
Jun 22 20:12:27	ppp		[wan_link0] LCP: SendTerminateAck #2
Jun 22 20:12:27	ppp		[wan] IPV6CP: state change Closed --> Initial
Jun 22 20:12:27	ppp		[wan] IPV6CP: Down event
Jun 22 20:12:27	ppp		[wan] IPCP: state change Closed --> Initial
Jun 22 20:12:27	ppp		[wan] IPCP: Down event
Jun 22 20:12:27	ppp		[wan] IPV6CP: Close event
Jun 22 20:12:27	ppp		[wan] IPCP: Close event
Jun 22 20:12:27	ppp		[wan] Bundle: Status update: up 0 links, total bandwidth 9600 bps
Jun 22 20:12:27	ppp		[wan_link0] Link: Leave bundle "wan"
Jun 22 20:12:27	ppp		[wan_link0] LCP: state change Opened --> Stopping
Jun 22 20:12:27	ppp		[wan_link0] LCP: rec'd Terminate Request #109 (Opened)
Jun 22 20:12:27	ppp		[wan] Bundle: closing link "wan_link0"...
Jun 22 20:12:27	ppp		[wan] Bundle: No NCPs left. Closing links...
Jun 22 20:12:27	ppp		[wan] IPCP: LayerFinish
Jun 22 20:12:27	ppp		[wan] IPCP: state change Closing --> Closed
Jun 22 20:12:27	ppp		[wan] IPCP: rec'd Terminate Ack #4 (Closing)
Jun 22 20:12:27	ppp		[wan] IPV6CP: state change Stopped --> Closed
Jun 22 20:12:27	ppp		[wan] IPV6CP: Close event
Jun 22 20:12:27	ppp		[wan] IFACE: Rename interface pppoe1 to pppoe1
Jun 22 20:12:27	ppp		[wan] IFACE: Down event
Jun 22 20:12:27	check_reload_status		Rewriting resolv.conf
Jun 22 20:12:27	ppp		[wan] IPCP: LayerDown
Jun 22 20:12:27	ppp		[wan] IPCP: SendTerminateReq #4
Jun 22 20:12:27	ppp		[wan] IPCP: state change Opened --> Closing
Jun 22 20:12:27	ppp		[wan] IPCP: Close event
Jun 22 20:12:27	ppp		[wan] IFACE: Close event
Jun 22 20:12:27	ppp		caught fatal signal TERM
Jun 22 20:12:20	syslogd		kernel boot file is /boot/kernel/kernel

                                            208.67.222.222 and 208.67.220.200 are my OpenDNS name server. IPv6 Tunnel is from HE.

                                            Thanks in advance,

                                            Marlenio

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