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

    PPPoE Clients cannot ping each other

    Scheduled Pinned Locked Moved Firewalling
    9 Posts 2 Posters 959 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.
    • F
      frapper
      last edited by

      Hello all,

      I am trrying to setup PFsense as a PPPoE Server Gateway for PPPoE Clients. I have succeesfully done it but I have a problem that I need help.

      PPPoE Clients cannot communicate each other. They can have internet connectivity but not with each other.
      Is there a limitation on PfSense for that or am I missing something?
      Thanks in advance
      Kostas

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

        What are your firewall rules for the PPPoE tab exactly?

        Remember: Upvote with the ๐Ÿ‘ button for any user/post you find to be helpful, informative, or deserving of recognition!

        Need help fast? Netgate Global Support!

        Do not Chat/PM for help!

        1 Reply Last reply Reply Quote 0
        • F
          frapper
          last edited by

          I have two pppoe clients (Mikrotik CHR) pppoe.png connected to the same lan port on PfSense.
          They get an ip address 172.17.1.11 and .12 respectively.
          I have added the rules on the firewall to permit traffic comming from the PPPoE Servers interface going to each other as per image. Screenshot at 2020-08-03 22-59-27.png but still no luck.
          If you could please help I would really appreciate it.
          Thanks
          Kostas

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

            You have the gateway set on all of those, so the traffic will be forced out the WAN.

            Add a new rule at the top to pass from/to the PPPoE client subnet but without a gateway set.

            Remember: Upvote with the ๐Ÿ‘ button for any user/post you find to be helpful, informative, or deserving of recognition!

            Need help fast? Netgate Global Support!

            Do not Chat/PM for help!

            1 Reply Last reply Reply Quote 0
            • F
              frapper
              last edited by

              But there is no such option not having a gateway in the advanced options of the rules...

              Screenshot at 2020-08-03 23-07-33.png

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

                Click in the gateway field and set it back to "Default".

                Remember: Upvote with the ๐Ÿ‘ button for any user/post you find to be helpful, informative, or deserving of recognition!

                Need help fast? Netgate Global Support!

                Do not Chat/PM for help!

                1 Reply Last reply Reply Quote 0
                • F
                  frapper
                  last edited by

                  Yes i have already done it but the "default" means the default gateway you have selected in the routing options...getting the same results Screenshot at 2020-08-03 23-24-45.png

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

                    "Default" means that it doesn't put a gateway on the rule, and it will instead follow the routing table. Bypassing policy routing for local traffic in that way is usually how you fix these kinds of issues.

                    PPPoE is kind of weird in that each client is actually on a separate interface in the same interface group. Assuming you made the right changes to your firewall rules on pfSense, your problem now is probably that the clients themselves are denying the inbound connections.

                    Remember: Upvote with the ๐Ÿ‘ button for any user/post you find to be helpful, informative, or deserving of recognition!

                    Need help fast? Netgate Global Support!

                    Do not Chat/PM for help!

                    1 Reply Last reply Reply Quote 0
                    • F
                      frapper
                      last edited by

                      Ok my mistake understanding the "default" option. So if it follows the routing table then PfSense has two legs on that are both reachable correct?
                      You are correct my friend..finally
                      thanks thanks thanks.

                      Screenshot at 2020-08-03 23-56-01.png

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