Navigation

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

    Two PPPoE connections from the same ISP

    2.0-RC Snapshot Feedback and Problems - RETIRED
    3
    5
    2527
    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.
    • J
      jeebsion last edited by

      Hi … Until now I managed not to get the second PPPOE link up .. looking at the log file, it manages to get an IP from the ISP .. but up to a point registering it to the interface failed:

      Jan 16 04:31:28 ppp: [opt1] IPADDR 0.0.0.0
      Jan 16 04:31:28 ppp: [opt1] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
      Jan 16 04:31:28 ppp: [opt1] IPCP: rec'd Configure Reject #1 (Req-Sent)
      Jan 16 04:31:28 ppp: [opt1] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
      Jan 16 04:31:28 ppp: [opt1] IPCP: SendConfigReq #2
      Jan 16 04:31:28 ppp: [opt1] IPADDR 0.0.0.0
      Jan 16 04:31:28 ppp: [opt1] IPCP: rec'd Configure Nak #2 (Req-Sent)
      Jan 16 04:31:28 ppp: [opt1] IPADDR 175.145.99.226
      Jan 16 04:31:28 ppp: [opt1] 175.145.99.226 is OK
      Jan 16 04:31:28 ppp: [opt1] IPCP: SendConfigReq #3
      Jan 16 04:31:28 ppp: [opt1] IPADDR 175.145.99.226
      Jan 16 04:31:28 ppp: [opt1] IPCP: rec'd Configure Ack #3 (Req-Sent)
      Jan 16 04:31:28 ppp: [opt1] IPADDR 175.145.99.226
      Jan 16 04:31:28 ppp: [opt1] IPCP: state change Req-Sent –> Ack-Rcvd
      Jan 16 04:31:28 ppp: [opt1] IPCP: rec'd Configure Request #140 (Ack-Rcvd)
      Jan 16 04:31:28 ppp: [opt1] IPADDR 219.93.218.177
      Jan 16 04:31:28 ppp: [opt1] 219.93.218.177 is OK
      Jan 16 04:31:28 ppp: [opt1] IPCP: SendConfigAck #140
      Jan 16 04:31:28 ppp: [opt1] IPADDR 219.93.218.177
      Jan 16 04:31:28 ppp: [opt1] IPCP: state change Ack-Rcvd –> Opened
      Jan 16 04:31:28 ppp: [opt1] IPCP: LayerUp
      Jan 16 04:31:28 ppp: [opt1] 175.145.99.226 -> 219.93.218.177
      Jan 16 04:31:28 ppp: [opt1] IFACE: Adding IPv4 address to pppoe1 failed: File exists
      Jan 16 04:31:28 ppp: [opt1] IFACE: IfaceChangeAddr() error, closing IPCP
      Jan 16 04:31:28 ppp: [opt1] IPCP: parameter negotiation failed
      Jan 16 04:31:28 ppp: [opt1] IPCP: state change Opened –> Stopping
      Jan 16 04:31:28 ppp: [opt1] IPCP: SendTerminateReq #4
      Jan 16 04:31:28 ppp: [opt1] IPCP: LayerDown
      Jan 16 04:31:28 ppp: [opt1] IPCP: rec'd Terminate Ack #4 (Stopping)
      Jan 16 04:31:28 ppp: [opt1] IPCP: state change Stopping –> Stopped
      Jan 16 04:31:28 ppp: [opt1] IPCP: LayerFinish
      Jan 16 04:31:28 ppp: [opt1] Bundle: No NCPs left. Closing links…
      Jan 16 04:31:28 ppp: [opt1] Bundle: closing link "opt1_link0"…
      Jan 16 04:31:28 ppp: [opt1_link0] Link: CLOSE event
      Jan 16 04:31:28 ppp: [opt1_link0] LCP: Close event
      Jan 16 04:31:28 ppp: [opt1_link0] LCP: state change Opened –> Closing
      Jan 16 04:31:28 ppp: [opt1_link0] Link: Leave bundle "opt1"
      Jan 16 04:31:28 ppp: [opt1] Bundle: Status update: up 0 links, total bandwidth 9600 bps
      Jan 16 04:31:28 ppp: [opt1] IPCP: Close event
      Jan 16 04:31:28 ppp: [opt1] IPCP: state change Stopped –> Closed
      Jan 16 04:31:28 ppp: [opt1] IPCP: Down event
      Jan 16 04:31:28 ppp: [opt1] IPCP: state change Closed –> Initial
      Jan 16 04:31:28 ppp: [opt1_link0] LCP: SendTerminateReq #2
      Jan 16 04:31:28 ppp: [opt1_link0] LCP: LayerDown
      Jan 16 04:31:28 ppp: [opt1_link0] LCP: rec'd Terminate Ack #2 (Closing)
      Jan 16 04:31:28 ppp: [opt1_link0] LCP: state change Closing –> Closed
      Jan 16 04:31:28 ppp: [opt1_link0] LCP: LayerFinish
      Jan 16 04:31:28 ppp: [opt1_link0] Link: DOWN event
      Jan 16 04:31:28 ppp: [opt1_link0] LCP: Down event
      Jan 16 04:31:28 ppp: [opt1_link0] LCP: state change Closed –> Initial

      As a reference, I'm having 2 DSL pipes from the same ISP. Perhaps because it's registering the same gateway from pppoe0?

      1 Reply Last reply Reply Quote 0
      • jimp
        jimp Rebel Alliance Developer Netgate last edited by

        I split this topic off from the thread where you replied because that was for a specific issue that you are not having. Someone else might be able to better respond to this under a new thread with a more specific subject.

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

          jimp,

          ahh yes .. thank you ..

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

            "IFACE: Adding IPv4 address to pppoe1 failed: File exists" means you're getting assigned the same gateway on the second connection, which cannot function with the underlying software used. See if your ISP can assign you a different subnet for that connection or do the PPPoE on the modem or elsewhere instead.

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

              cmb,

              Thought so someone would reply as such :-) … but I was wondering if the coders could do something about interface/ip aliasing or if there was to be any gateway aliasing or even sort of trunking of pppoe interfaces in order to share the same gateway? I dunno .. I'm just exploring .. :D

              1 Reply Last reply Reply Quote 0
              • First post
                Last post

              Products

              • Platform Overview
              • TNSR
              • pfSense Plus
              • Appliances

              Services

              • Training
              • Professional Services

              Support

              • Subscription Plans
              • Contact Support
              • Product Lifecycle
              • Documentation

              News

              • Media Coverage
              • Press
              • Events

              Resources

              • Blog
              • FAQ
              • Find a Partner
              • Resource Library
              • Security Information

              Company

              • About Us
              • Careers
              • Partners
              • Contact Us
              • Legal
              Our Mission

              We provide leading-edge network security at a fair price - regardless of organizational size or network sophistication. We believe that an open-source security model offers disruptive pricing along with the agility required to quickly address emerging threats.

              Subscribe to our Newsletter

              Product information, software announcements, and special offers. See our newsletter archive to sign up for future newsletters and to read past announcements.

              © 2021 Rubicon Communications, LLC | Privacy Policy