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

    Reroot exposes SSH, Telnet, Web UI to WAN

    Scheduled Pinned Locked Moved General pfSense Questions
    29 Posts 7 Posters 3.5k 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.
    • U
      User1337
      last edited by User1337

      My mistake, for some reason I thought there was telnet. I do use SSH, however. I determined it by checking my logs and seeing brute force attacks, verified it with my phone's non-wifi connection as well.

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

        @user1337

        So, when you reroot, you can use a device like a phone, and via the 3G/4G/4G you 'hammer' (nmap if possible ) your IP WAN, and you can connect to SSH and the pfSense GUI ?

        What are your WAN firewall rules ?

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

        U 1 Reply Last reply Reply Quote 0
        • U
          User1337 @Gertjan
          last edited by

          @gertjan Yes, the first thing that pops up when connecting to my public facing IP is the web UI. I even disabled the traffic shaper rule for the sake of troubleshooting and was only left with the default block bogon/private networks rules.on WAN. Again, with full reboot the firewall works as intended and any external attempts time out. nmap after reroot:

          Interesting ports on x.x.x.x:
          Not shown: 996 filtered ports
          PORT    STATE SERVICE
          22/tcp  open  ssh
          53/tcp  open  domain
          80/tcp  open  http
          443/tcp open  https
          
          Nmap done: 1 IP address (1 host up) scanned in 16.93 seconds
          
          1 Reply Last reply Reply Quote 0
          • N
            NOCling
            last edited by

            No problem here, can you show your ruleset?

            If you setup Rules like this:
            706095b5-556f-4df3-9c93-c574acddbf1a-image.png

            You expose your WAN IP to the Guest Users, you need this first:
            ec754c2c-16ab-4f9b-b2c9-d8f3ecdb36fc-image.png

            Netgate 6100 & Netgate 2100

            U 1 Reply Last reply Reply Quote 0
            • U
              User1337 @NOCling
              last edited by User1337

              @nocling My rules:
              Untitled-3.png

              GertjanG 1 Reply Last reply Reply Quote 0
              • N
                NOCling
                last edited by

                Your last Rule allows your LAN to 443,80,22 on the pfSense WAN Adresse.

                Do not try a Scan on the WAN Adresse from a LAN Client!

                Netgate 6100 & Netgate 2100

                U 1 Reply Last reply Reply Quote 0
                • GertjanG
                  Gertjan @User1337
                  last edited by

                  @user1337

                  LAN : ok
                  WAN : why ? the default 'hidden' block rule will take care of these. "The good WAN is an empty WAN".
                  Floating : Looks fine to me.

                  @nocling said in Reroot exposes SSH, Telnet, Web UI to WAN:

                  Do not try a Scan on the WAN Adresse from a LAN Client!

                  Because he's scanning the outside from the inside ?
                  Well, yeah, the test is wrong then.

                  I was serious :

                  @gertjan said in Reroot exposes SSH, Telnet, Web UI to WAN:

                  you can use a device like a phone, and via the 3G/4G/4G you 'hammer' (nmap if possible ) your IP WAN

                  In short : from the outside.

                  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
                  • N
                    NOCling
                    last edited by

                    Limiter Rules works best with match and no quick.
                    Have a look on the documentation:
                    https://docs.netgate.com/pfsense/en/latest/firewall/floating-rules.html?highlight=match

                    Netgate 6100 & Netgate 2100

                    1 Reply Last reply Reply Quote 0
                    • NollipfSenseN
                      NollipfSense @Gertjan
                      last edited by

                      @gertjan Learned something new today, thank you!

                      pfSense+ 23.09 Lenovo Thinkcentre M93P SFF Quadcore i7 dual Raid-ZFS 128GB-SSD 32GB-RAM PCI-Intel i350-t4 NIC, -Intel QAT 8950.
                      pfSense+ 23.09 VM-Proxmox, Dell Precision Xeon-W2155 Nvme 500GB-ZFS 128GB-RAM PCIe-Intel i350-t4, Intel QAT-8950, P-cloud.

                      1 Reply Last reply Reply Quote 0
                      • U
                        User1337 @NOCling
                        last edited by

                        @nocling said in Reroot exposes SSH, Telnet, Web UI to WAN:

                        Your last Rule allows your LAN to 443,80,22 on the pfSense WAN Adresse.

                        Do not try a Scan on the WAN Adresse from a LAN Client!

                        Unless I am missing something, It's a default rule created by the setup wizard. Disabling this would lock me out even from LAN. I changed the limiter rule to "Match," but regardless even with the rule disabled my network becomes exposed to WAN after reroot.

                        @gertjan said in Reroot exposes SSH, Telnet, Web UI to WAN:

                        In short : from the outside.

                        The test was done from my phone with LTE. Why do you think I did it from LAN given the premise of the thread?

                        1 Reply Last reply Reply Quote 0
                        • U
                          User1337
                          last edited by User1337

                          Ok, the cause of the issue is from using the TOE function of my NIC (Chelsio T5). With TOE disabled, nmap fails even after reroot. With TOE enabled, nmap can scan ports and port 80 appears open but my web UI is configured to use HTTPS, so fails to connect from WAN. After reroot, everything becomes exposed and accessible from WAN. I thought the ASIC was a self-contained firewall that further passed packets to the regular (system) firewall, but it appears to (partially) bypass it. I guess that's how it achieves line-rate filtering. For now I guess I will leave TOE disabled unless someone can suggest how to use it without bypassing PfSense's firewall.

                          1 Reply Last reply Reply Quote 0
                          • U
                            User1337
                            last edited by

                            Sorry, can't edit old posts, but I found the answer: https://calomel.org/freebsd_chelsio_toe_firewall.html:

                            The Chelsio Offload Policy (COP) manages when the TCP Offload Engine (TOE) takes affect allowing the card to only offload TCP connections which you want to offload and leave the other connection to the default FreeBSD TCP stack.
                            ...
                            SECURITY NOTE: The Chelsio TCP Offload Engine (TOE) will completely bypass the FreeBSD TCP stack as well as any Chelsio filter rules. This means that traffic using TOE will NOT be filtered using our Chelsio Rules of Engagement filter rules or the Pf packet filter, nor will Pf log TOE connections. Netstat will show the connections using "netstat -np tcp" though.

                            S U 2 Replies Last reply Reply Quote 0
                            • S
                              SteveITS Galactic Empire @User1337
                              last edited by

                              @user1337 That’s a feature? I wonder if that’s something Netgate can disable in the driver/config. You might open a Redmine.pfsense.org about it.

                              Side note:there’s a long thread here somewhere about (some?) Chelsio cards downloading at half speed in 23.01.

                              Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
                              When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
                              Upvote 👍 helpful posts!

                              1 Reply Last reply Reply Quote 0
                              • stephenw10S
                                stephenw10 Netgate Administrator
                                last edited by

                                Hmm, so this was eliminated by disabling TOE or rather simply not enabling it?

                                What pfSense version did you see this in?

                                You only saw it after rerooting?

                                This was permanent after the reroot? Not just while the reroot was happening?

                                Steve

                                1 Reply Last reply Reply Quote 0
                                • U
                                  User1337 @User1337
                                  last edited by User1337

                                  @steveits TOE is disabled by default and can't be enabled by accident so nothing Netgate needs to worry about. My WAN speed matches my expectations when using typical web-based speed tests, but I only have a ~350/10Mbps plan so it's not enough to expose a large bottleneck.

                                  @stephenw10 Yes, I disabled TOE by commenting out these lines in a custom script in /usr/local/etc/rc.d:

                                  #ifconfig cxl0 toe
                                  #ifconfig cxl1 toe
                                  

                                  I enabled TOE on LAN manually via SSH ifconfig cxl1 toe and indeed it works, 1.15 vs .23 TIME+ shown in htop for each respective iperf2 server process. No difference with iperf3. Interestingly enough pfblockerng also works, which means the system firewall is taking effect. This all may be due to this detail from the same calomel link:

                                  TCP TIMING: We noticed that short lived connections of less then 0.6 seconds will NOT use the Chelsio TCP Offload Engine (TOE) even if TOE is allowed universally or through Chelsio Offload Policy (COP). Not sure of the reason.

                                  Next I tried enabling TOE on WAN ifconfig cxl0 toe and noticed SSH and web UI don't become exposed to WAN until after reroot. Version CE 2.6.0 (22.01). Yes it's permanently exposed after reroot. At this point it's not a real issue but may be of help to anyone else that goes down this path.

                                  1 Reply Last reply Reply Quote 0
                                  • stephenw10S
                                    stephenw10 Netgate Administrator
                                    last edited by

                                    Yes, that's a nice catch. It should definitely be documented.

                                    Did you try both 2.6 and 22.01 or just noted they are closely equivalent?

                                    U 1 Reply Last reply Reply Quote 0
                                    • U
                                      User1337 @stephenw10
                                      last edited by

                                      @stephenw10 Just 2.6.0.

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

                                        Given the description of how TOE works I would have expected it to always bypass pf and not just at reroot. I'll try to work a working against using that into the docs but I'm not sure where it might fit that users would see it. The most likely place would seem to be https://docs.netgate.com/pfsense/en/latest/hardware/tune.html#chelsio-cxgbe-4-cards

                                        In the future, if you believe you have discovered a security vulnerability, please report it privately as described on https://www.netgate.com/security and not on a public forum post. That way we can investigate it and work on a fix before it is widely known to the public.

                                        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
                                        • jimpJ
                                          jimp Rebel Alliance Developer Netgate
                                          last edited by

                                          Also I wonder how this works then:

                                          https://redmine.pfsense.org/issues/9091

                                          Maybe it's different on the T4 vs T5 cards? Or maybe you need that module loaded so TOE works as expected.

                                          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
                                          • U
                                            User1337
                                            last edited by User1337

                                            @jimp Yes, I also load t4_tom as part of the script mentioned above. As for why those services become exposed after reroot, I'm not sure, perhaps something to do with the startup sequence and that 600ms exception. The real issue is there's no mention of TOE bypassing pf in Chelsio's FreeBSD manual. However obvious it is to most, it's quite the gotcha for someone like me and unfortunately resulted in creating this thread. A lot of things are poorly or not documented at all.

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