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

    [2.3.x] DPINGER WAN_PPPoE sendto error: 65 (no WAN access)

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    25 Posts 10 Posters 10.9k 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.
    • R Offline
      renegade
      last edited by

      Same here. After upgrading there was no connection to the internet although ppp had a public ip address.
      I have to disconnect and reconnect manually. This problem exists since 2.3.1 and is in most times reproducible after reboot.
      Already made a clean install and restored config.
      Using a vigor 130 for German adsl telekom.

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

        @Gertjan:

        This seems ok (in the right order) :
        May 23 22:11:26 ppp [wan] IPADDR 87.21.211.177
        May 23 22:11:26 ppp [wan] 87.21.211.177 is OK
        You have your IPv4.
        You're up.

        But then (in the right order)  :

        May 23 22:00:14 ppp [wan] IPADDR 192.168.100.1
        May 23 22:00:14 ppp [wan] 192.168.100.1 is OK
        May 23 22:00:14 ppp [wan] IPCP: state change Ack-Rcvd –> Opened
        May 23 22:00:14 ppp [wan] IPADDR 192.168.100.1
        May 23 22:00:14 ppp [wan] IPCP: SendConfigAck #11
        May 23 22:00:14 ppp [wan] IPCP: LayerUp
        May 23 22:00:14 ppp [wan] 79.18.210.145 -> 192.168.100.1
        May 23 22:00:14 ppp [wan] IFACE: Up event

        Where does this local IP "192.168.100.1" coming from ?

        Then the IPv6 starts to kick in.

        Btw : aliceadsl (France) supports IPv6 ?
        If so, deactivate IPv6, and try to get a good working IPv4 first.

        192.168.100.1 is the modem. I have a IPv6 tunnel with Hurricane Electric. I try only IPv4 with a fresh install, same problem with PPPoe. AliceADSL is by TIM Italy (VDSL 100Mb/s).

        Marlenio

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

          @renegade:

          Same here. After upgrading there was no connection to the internet although ppp had a public ip address.
          I have to disconnect and reconnect manually. This problem exists since 2.3.1 and is in most times reproducible after reboot.
          Already made a clean install and restored config.
          Using a vigor 130 for German adsl telekom.

          Yes, the same happens to my config. But i have problem since 2.3.0 and then 2.3.1. If i disconnect/reconnect 4/5 times, then WAN PPPoe goes up with internet connection.

          Marlenio

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

            Yesterday i tried another PC with 2 Reltek interface and pfSense 2.3.2 (0528). Same PPPoe on WAN (Telecom Fibra 100Mb/s), same PPPoE error: WAN get dynamic IP from ISP, gateway monitor show WAN gateway down, no internet connection.  :-[

            Instead, the other firewall with 2.3.1 crashed after running for 3 days. This time disconnect/connect WAN interface doesn't solve problem. Too much problems for now with 2.3.x with PPPoE, rollback on 2.2.6.

            There's is any news from pfSense team about this issue?

            Marlenio

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

              New test with 2.2.6, 2.3.1 and 2.3.2 (snapshot 05312016) and two different hardware (my ITX firewall and Alix 2D). I tried with two different italian ISP with PPPoE connection and modem in bridge mode.

              With 2.2.6 pfSense works without any kind of problem: WAN public IP is assigned fron ISP, on gateway widget PPPoE connection on WAN is green. Internet and outboud traffic works normally.

              With 2.3.1 and 2.3.2 both ITX and Alix get IP address from ISP, but gateway widget show PPPoE WAN down. No internet outbound traffic and outbound PING. Disconnect and reconnect WAN interface works only some times.

              I don't know what other kind of test i can do… I like very much new 2.3 pfSense, but i cannot install on my system.  :'(

              Marlenio

              1 Reply Last reply Reply Quote 0
              • G Offline
                generious
                last edited by

                Ran into the same problem yesterday when I did the 2.3.2 upgrade.
                It gets a ip on the wan connection but the gateway itself is down.

                Connected to it remotely using openvpn worked fine….
                Ended up reverting to a previous 2.2.6 snapshot and it worked straight away.

                Also tried doing a fresh install of 2.3.2 same problem appeared same as OP

                Ps on Uk BT ppoe

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

                  Yes, it seems the same error. I'd like to know if pfSense Team can open a bug about this issue.

                  Marlenio

                  1 Reply Last reply Reply Quote 0
                  • M Offline
                    myksto
                    last edited by

                    Same problem here.
                    Alix motherboard and bridged modem, all ok with 2.3.0 but after upgrading to 2.3.1 no more internet access.
                    If I go to Status->Interfaces and I do a disconnect and the a connect internet is ok.

                    It's surely a bug within version 2.3.1 and hope it will be solved soon.

                    1 Reply Last reply Reply Quote 0
                    • J Offline
                      JorgeOliveira
                      last edited by

                      I have been poking around this on the most weird ways using two pfSense installs running on VMware. One being the server and another the client. The only way I found to make it work was to do the following.

                      1. Edit WAN_PPPOE gateway using 'System > Routing > Gateways > Edit'
                        1.1) Check 'Use non-local gateway' on advanced options
                        1.2) Save & Apply

                      2. Edit WAN using 'Interfaces > WAN'
                        2.1) Add the WAN interface MAC address manually
                        2.2) Save & Apply

                      Then after a system reboot, everything magically worked.

                      My views have absolutely no warranty express or implied. Always do your own research.

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

                        Hi Jeorge, thank you for your post. I'll try tomorrow and let you know if it works. :)

                        EDIT: try your config. No luck, same error.  :(

                        Marlenio

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

                          New try, same PPPoE config, v 2.3.1 and 2.3.2 last snapshot. Same error on WAN PPPoE if, gateway down, no internet, no ping. Here is PPP log:

                          
Time	Process	PID	Message
Jun 9 18:33:43	ppp		[wan] IPV6CP: LayerFinish
Jun 9 18:33:43	ppp		[wan] IPV6CP: state change Stopping --> Stopped
Jun 9 18:33:40	ppp		[wan] IPV6CP: LayerDown
Jun 9 18:33:40	ppp		[wan] IPV6CP: SendTerminateAck #2
Jun 9 18:33:40	ppp		[wan] IPV6CP: state change Opened --> Stopping
Jun 9 18:33:40	ppp		[wan] IPV6CP: rec'd Terminate Request #42 (Opened)
Jun 9 18:33:40	ppp		[wan] 76d4:35ff:fe8a:b19c -> 02a0:a50f:fc86:8004
Jun 9 18:33:40	ppp		[wan] IPV6CP: LayerUp
Jun 9 18:33:40	ppp		[wan] IPV6CP: state change Ack-Rcvd --> Opened
Jun 9 18:33:40	ppp		[wan] IPV6CP: SendConfigAck #41
Jun 9 18:33:40	ppp		[wan] IPV6CP: rec'd Configure Request #41 (Ack-Rcvd)
Jun 9 18:33:40	ppp		[wan] IFACE: Rename interface ng0 to pppoe1
Jun 9 18:33:40	ppp		[wan] IFACE: Up event
Jun 9 18:33:40	ppp		[wan] 79.36.219.229 -> 192.168.100.1
Jun 9 18:33:40	ppp		[wan] IPCP: LayerUp
Jun 9 18:33:40	ppp		[wan] IPCP: state change Ack-Rcvd --> Opened
Jun 9 18:33:40	ppp		[wan] IPADDR 192.168.100.1
Jun 9 18:33:40	ppp		[wan] IPCP: SendConfigAck #112
Jun 9 18:33:40	ppp		[wan] 192.168.100.1 is OK
Jun 9 18:33:40	ppp		[wan] IPADDR 192.168.100.1
Jun 9 18:33:40	ppp		[wan] IPCP: rec'd Configure Request #112 (Ack-Rcvd)
Jun 9 18:33:40	ppp		[wan] IPCP: state change Req-Sent --> Ack-Rcvd
Jun 9 18:33:40	ppp		[wan] IPADDR 79.36.219.229
Jun 9 18:33:40	ppp		[wan] IPCP: rec'd Configure Ack #3 (Req-Sent)
Jun 9 18:33:40	ppp		[wan] IPADDR 79.36.219.229
Jun 9 18:33:40	ppp		[wan] IPCP: SendConfigReq #3
Jun 9 18:33:40	ppp		[wan] 79.36.219.229 is OK
Jun 9 18:33:40	ppp		[wan] IPADDR 79.36.219.229
Jun 9 18:33:40	ppp		[wan] IPCP: rec'd Configure Nak #2 (Req-Sent)
Jun 9 18:33:40	ppp		[wan] IPV6CP: state change Req-Sent --> Ack-Rcvd
Jun 9 18:33:40	ppp		[wan] IPV6CP: rec'd Configure Ack #1 (Req-Sent)
Jun 9 18:33:40	ppp		[wan] IPADDR 0.0.0.0
Jun 9 18:33:40	ppp		[wan] IPCP: SendConfigReq #2
Jun 9 18:33:40	ppp		[wan] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
Jun 9 18:33:40	ppp		[wan] IPCP: rec'd Configure Reject #1 (Req-Sent)
Jun 9 18:33:40	ppp		[wan] IPV6CP: SendConfigReq #1
Jun 9 18:33:40	ppp		[wan] IPV6CP: state change Starting --> Req-Sent
Jun 9 18:33:40	ppp		[wan] IPV6CP: Up event
Jun 9 18:33:40	ppp		[wan] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
Jun 9 18:33:40	ppp		[wan] IPADDR 0.0.0.0
Jun 9 18:33:40	ppp		[wan] IPCP: SendConfigReq #1
Jun 9 18:33:40	ppp		[wan] IPCP: state change Starting --> Req-Sent
Jun 9 18:33:40	ppp		[wan] IPCP: Up event
Jun 9 18:33:40	ppp		[wan] IPV6CP: LayerStart
Jun 9 18:33:40	ppp		[wan] IPV6CP: state change Initial --> Starting
Jun 9 18:33:40	ppp		[wan] IPV6CP: Open event
Jun 9 18:33:40	ppp		[wan] IPCP: LayerStart
Jun 9 18:33:40	ppp		[wan] IPCP: state change Initial --> Starting
Jun 9 18:33:40	ppp		[wan] IPCP: Open event
Jun 9 18:33:40	ppp		[wan] Bundle: Status update: up 1 link, total bandwidth 64000 bps
Jun 9 18:33:40	ppp		[wan_link0] Link: Join bundle "wan"
Jun 9 18:33:40	ppp		[wan_link0] Link: Matched action 'bundle "wan" ""'
Jun 9 18:33:40	ppp		[wan_link0] LCP: authorization successful
Jun 9 18:33:40	ppp		[wan_link0] MESG: REASON021 - TK MISSING: NOT IN DSL-LINE
Jun 9 18:33:40	ppp		[wan_link0] PAP: rec'd ACK #1 len: 44
Jun 9 18:33:40	ppp		[wan_link0] LCP: LayerUp
Jun 9 18:33:40	ppp		[wan_link0] PAP: sending REQUEST #1 len: 24
Jun 9 18:33:40	ppp		[wan_link0] PAP: using authname "aliceadsl"
Jun 9 18:33:40	ppp		[wan_link0] LCP: auth: peer wants PAP, I want nothing
Jun 9 18:33:40	ppp		[wan_link0] LCP: state change Ack-Sent --> Opened
Jun 9 18:33:40	ppp		[wan_link0] MAGICNUM 0x70f5e750
Jun 9 18:33:40	ppp		[wan_link0] MRU 1492
Jun 9 18:33:40	ppp		[wan_link0] PROTOCOMP
Jun 9 18:33:40	ppp		[wan_link0] LCP: rec'd Configure Ack #1 (Ack-Sent)
Jun 9 18:33:40	ppp		[wan_link0] LCP: state change Req-Sent --> Ack-Sent
Jun 9 18:33:40	ppp		[wan_link0] MAGICNUM 0x030439d9
Jun 9 18:33:40	ppp		[wan_link0] AUTHPROTO PAP
Jun 9 18:33:40	ppp		[wan_link0] MRU 1492
Jun 9 18:33:40	ppp		[wan_link0] LCP: SendConfigAck #213
Jun 9 18:33:40	ppp		[wan_link0] MAGICNUM 0x030439d9
Jun 9 18:33:40	ppp		[wan_link0] AUTHPROTO PAP
Jun 9 18:33:40	ppp		[wan_link0] MRU 1492
Jun 9 18:33:40	ppp		[wan_link0] LCP: rec'd Configure Request #213 (Req-Sent)
Jun 9 18:33:40	ppp		[wan_link0] MAGICNUM 0x70f5e750
Jun 9 18:33:40	ppp		[wan_link0] MRU 1492
Jun 9 18:33:40	ppp		[wan_link0] PROTOCOMP
Jun 9 18:33:40	ppp		[wan_link0] LCP: SendConfigReq #1
Jun 9 18:33:40	ppp		[wan_link0] LCP: state change Starting --> Req-Sent
Jun 9 18:33:40	ppp		[wan_link0] LCP: Up event
Jun 9 18:33:40	ppp		[wan_link0] Link: UP event
Jun 9 18:33:40	ppp		[wan_link0] PPPoE: connection successful
Jun 9 18:33:40	ppp		PPPoE: rec'd ACNAME "r-rm900"
Jun 9 18:33:40	ppp		[wan_link0] PPPoE: Connecting to 'TelecomFibra'
Jun 9 18:33:40	ppp		[wan_link0] LCP: LayerStart
Jun 9 18:33:40	ppp		[wan_link0] LCP: state change Initial --> Starting
Jun 9 18:33:40	ppp		[wan_link0] LCP: Open event
Jun 9 18:33:40	ppp		[wan_link0] Link: OPEN event
Jun 9 18:33:40	ppp		[wan] Bundle: Interface ng0 created
Jun 9 18:33:40	ppp		web: web is not running
Jun 9 18:33:40	ppp		process 5265 started, version 5.8 (root@pfSense_v2_3_1_amd64-pfSense_v2_3_1-job-13 19:20 16-May-2016)
Jun 9 18:33:40	ppp		Multi-link PPP daemon for FreeBSD

                          No problem with 2.2.6.

                          It would be good if pfSense Team let us knbow if they had replicate this issue. I'm trying and trying and trying 2.3.1 and 2.3.2 snapshot, doing test, restore many times my 2.2.6 config without any reply about this issue from team.  :(

                          Marlenio

                          1 Reply Last reply Reply Quote 0
                          • GertjanG Offline
                            Gertjan
                            last edited by

                            Again :

                            May 23 22:00:14  ppp      [wan] 79.18.210.145 -> 192.168.100.1

                            Where does this local IP "192.168.100.1" coming from ?

                            Then the IPv6 starts to kick in.

                            Btw : aliceadsl (France) supports IPv6 ?
                                If so, deactivate IPv6, and try to get a good working IPv4 first.

                            192.168.100.1 is the modem. I have a IPv6 tunnel with Hurricane Electric.

                            WHAT is your modem's IP doing in the 'ppp' log ?

                            I'm using a ADSL modem mode bridge (so pppoe) for years now.
                            True, I declared a 'fake' interface so I could connect to the web interface on this modem (on 10.0.0.138 for me)

                            But the modem is just 'tunneling' and the ppp connection shouldn't mention the modem IP at all (I never saw that in my connections logs).

                            I'm usinh HE.net also, and pfSense is my tunnels (the HE.net) end point. This has nothing to do with the modem, which just converts ADSL signals to "ethernet" RJ45 (to the pfSense box).

                            About pinger (Monitoring)  : it will default to a chosen IP address, often being your gateay upstream - some IP used by your ISP. NOT all of them do reply on ping. In case of doubt, just shut pinger down - its probably just just another issue.

                            With 2.3.2 snapshot and fresh install i get PPPoE working,

                            Good !
                            Keep that version ;)

                            edit :
                            My 'ppp' log.
                            You won't find ANY local non routable IP's here …

                            
2016-06-08 12:53:11	Daemon.Info	192.168.1.1	Jun  8 12:53:14 ppp: [wan_link0] Link: reconnection attempt 9 in 4 seconds
2016-06-08 12:53:15	User.Notice	192.168.1.1	Jun  8 12:53:18 check_reload_status: Restarting ipsec tunnels
2016-06-08 12:53:15	Daemon.Info	192.168.1.1	Jun  8 12:53:18 ppp: [wan_link0] Link: reconnection attempt 9
2016-06-08 12:53:15	Daemon.Info	192.168.1.1	Jun  8 12:53:18 ppp: [wan_link0] PPPoE: Connecting to ''
2016-06-08 12:53:17	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: PPPoE: rec'd ACNAME "BSBOR653-H104L0413L00VZ"
2016-06-08 12:53:17	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan_link0] PPPoE: connection successful
2016-06-08 12:53:17	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan_link0] Link: UP event
2016-06-08 12:53:17	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan_link0] LCP: Up event
2016-06-08 12:53:17	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan_link0] LCP: state change Starting --> Req-Sent
2016-06-08 12:53:17	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan_link0] LCP: SendConfigReq #5
2016-06-08 12:53:17	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan_link0]   PROTOCOMP
2016-06-08 12:53:17	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan_link0]   MRU 1492
2016-06-08 12:53:17	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan_link0]   MAGICNUM 0x3128d37e
2016-06-08 12:53:17	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan_link0] LCP: rec'd Configure Request #2 (Req-Sent)
2016-06-08 12:53:17	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan_link0]   MRU 1492
2016-06-08 12:53:17	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan_link0]   AUTHPROTO CHAP MD5
2016-06-08 12:53:17	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan_link0]   MAGICNUM 0x266e15b2
2016-06-08 12:53:17	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan_link0] LCP: SendConfigAck #2
2016-06-08 12:53:17	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan_link0]   MRU 1492
2016-06-08 12:53:17	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan_link0]   AUTHPROTO CHAP MD5
2016-06-08 12:53:17	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan_link0]   MAGICNUM 0x266e15b2
2016-06-08 12:53:17	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan_link0] LCP: state change Req-Sent --> Ack-Sent
2016-06-08 12:53:17	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan_link0] LCP: rec'd Configure Reject #5 (Ack-Sent)
2016-06-08 12:53:17	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan_link0]   PROTOCOMP
2016-06-08 12:53:17	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan_link0] LCP: SendConfigReq #6
2016-06-08 12:53:17	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan_link0]   MRU 1492
2016-06-08 12:53:17	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan_link0]   MAGICNUM 0x3128d37e
2016-06-08 12:53:18	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan_link0] LCP: rec'd Configure Ack #6 (Ack-Sent)
2016-06-08 12:53:18	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan_link0]   MRU 1492
2016-06-08 12:53:18	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan_link0]   MAGICNUM 0x3128d37e
2016-06-08 12:53:18	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan_link0] LCP: state change Ack-Sent --> Opened
2016-06-08 12:53:18	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan_link0] LCP: auth: peer wants CHAP, I want nothing
2016-06-08 12:53:18	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan_link0] CHAP: rec'd CHALLENGE #1 len: 29
2016-06-08 12:53:18	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan_link0]   Name: "BSTOL653"
2016-06-08 12:53:18	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan_link0] CHAP: Using authname "fti/kp4jhgj"
2016-06-08 12:53:18	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan_link0] CHAP: sending RESPONSE #1 len: 32
2016-06-08 12:53:18	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan_link0] CHAP: rec'd SUCCESS #1 len: 43
2016-06-08 12:53:18	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan_link0]   MESG: CHAP authentication success, unit 20212
2016-06-08 12:53:18	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan_link0] LCP: authorization successful
2016-06-08 12:53:18	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan_link0] Link: Matched action 'bundle "wan" ""'
2016-06-08 12:53:18	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan_link0] Link: Join bundle "wan"
2016-06-08 12:53:18	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan] Bundle: Status update: up 1 link, total bandwidth 64000 bps
2016-06-08 12:53:18	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan] IPCP: Open event
2016-06-08 12:53:18	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan] IPCP: state change Initial --> Starting
2016-06-08 12:53:18	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan] IPCP: LayerStart
2016-06-08 12:53:18	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan] IPV6CP: Open event
2016-06-08 12:53:18	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan] IPV6CP: state change Initial --> Starting
2016-06-08 12:53:18	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan] IPV6CP: LayerStart
2016-06-08 12:53:18	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan] IPCP: Up event
2016-06-08 12:53:18	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan] IPCP: state change Starting --> Req-Sent
2016-06-08 12:53:18	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan] IPCP: SendConfigReq #5
2016-06-08 12:53:18	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan]   IPADDR 0.0.0.0
2016-06-08 12:53:18	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan]   COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
2016-06-08 12:53:18	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan]   PRIDNS 0.0.0.0
2016-06-08 12:53:18	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan]   SECDNS 0.0.0.0
2016-06-08 12:53:18	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan] IPV6CP: Up event
2016-06-08 12:53:18	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan] IPV6CP: state change Starting --> Req-Sent
2016-06-08 12:53:18	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan] IPV6CP: SendConfigReq #2
2016-06-08 12:53:18	Daemon.Info	192.168.1.1	Jun  8 12:53:20 avahi-daemon[89303]: Withdrawing workstation service for pppoe0.
2016-06-08 12:53:18	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan] IPCP: rec'd Configure Request #226 (Req-Sent)
2016-06-08 12:53:18	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan]   IPADDR 193.253.160.3
2016-06-08 12:53:18	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan]     193.253.160.3 is OK
2016-06-08 12:53:18	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan] IPCP: SendConfigAck #226
2016-06-08 12:53:18	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan]   IPADDR 193.253.160.3
2016-06-08 12:53:18	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan] IPCP: state change Req-Sent --> Ack-Sent
2016-06-08 12:53:18	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan] IPCP: rec'd Configure Reject #5 (Ack-Sent)
2016-06-08 12:53:18	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan]   COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
2016-06-08 12:53:18	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan] IPCP: SendConfigReq #6
2016-06-08 12:53:18	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan]   IPADDR 0.0.0.0
2016-06-08 12:53:18	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan]   PRIDNS 0.0.0.0
2016-06-08 12:53:18	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan]   SECDNS 0.0.0.0
2016-06-08 12:53:18	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan_link0] LCP: protocol IPV6CP was rejected
2016-06-08 12:53:18	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan] IPV6CP: protocol was rejected by peer
2016-06-08 12:53:18	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan] IPV6CP: state change Req-Sent --> Stopped
2016-06-08 12:53:18	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan] IPV6CP: LayerFinish
2016-06-08 12:53:18	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan] IPCP: rec'd Configure Nak #6 (Ack-Sent)
2016-06-08 12:53:18	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan]   IPADDR 109.214.60.150
2016-06-08 12:53:18	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan]     109.214.60.150 is OK
2016-06-08 12:53:18	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan]   PRIDNS 80.10.246.132
2016-06-08 12:53:18	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan]   SECDNS 81.253.149.2
2016-06-08 12:53:18	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan] IPCP: SendConfigReq #7
2016-06-08 12:53:18	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan]   IPADDR 109.214.60.150
2016-06-08 12:53:18	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan]   PRIDNS 80.10.246.132
2016-06-08 12:53:18	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan]   SECDNS 81.253.149.2
2016-06-08 12:53:18	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan] IPCP: rec'd Configure Ack #7 (Ack-Sent)
2016-06-08 12:53:18	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan]   IPADDR 109.214.60.150
2016-06-08 12:53:18	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan]   PRIDNS 80.10.246.132
2016-06-08 12:53:18	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan]   SECDNS 81.253.149.2
2016-06-08 12:53:18	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan] IPCP: state change Ack-Sent --> Opened
2016-06-08 12:53:18	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan] IPCP: LayerUp
2016-06-08 12:53:18	Daemon.Info	192.168.1.1	Jun  8 12:53:20 ppp: [wan]   109.214.60.150 -> 193.253.160.3
2016-06-08 12:53:18	User.Notice	192.168.1.1	Jun  8 12:53:20 check_reload_status: Rewriting resolv.conf
2016-06-08 12:53:19	User.Notice	192.168.1.1	Jun  8 12:53:21 check_reload_status: rc.newwanip starting pppoe0
2016-06-08 12:53:19	Daemon.Info	192.168.1.1	Jun  8 12:53:21 ppp: [wan] IFACE: Up event
2016-06-08 12:53:19	Daemon.Info	192.168.1.1	Jun  8 12:53:21 ppp: [wan] IFACE: Rename interface ng0 to pppoe0

                            afterwards, the GIF interface gets upped, HE.net (ipv6) kicks in, etc.

                            No "help me" PM's please. Use the forum, the community will thank you.
                            Edit : and where are the logs ??

                            1 Reply Last reply Reply Quote 0
                            • S Offline
                              simi8
                              last edited by

                              @renegade:

                              Same here. After upgrading there was no connection to the internet although ppp had a public ip address.
                              I have to disconnect and reconnect manually. This problem exists since 2.3.1 and is in most times reproducible after reboot.
                              Already made a clean install and restored config.
                              Using a vigor 130 for German adsl telekom.

                              I confirm the same problem with 2.3.1 and Telecom Italia as provider. My warkround was to disable the 'fake interface' that i created to access the modem. Since than the connection is stable as never before!

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