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

    Layer7 Issues

    Scheduled Pinned Locked Moved 2.0-RC Snapshot Feedback and Problems - RETIRED
    17 Posts 7 Posters 8.8k 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.
    • S
      sscardefield
      last edited by

      And here's the log if it helps any.

      1 Reply Last reply Reply Quote 0
      • E
        eri--
        last edited by

        Try selecting quick on that floating rule but that will get you wide open firewall.
        Or just try putting direction out and see if that works.
        The best place would be your default LAN rule, if you have only that rule on LAN.

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

          The problem with applying it to the default LAN rule is that you have to change it to TCP/UDP, which means you'd have to create a second rule to allow the rest of the protocols. But either way, I changed the default LAN rule to TCP/UDP and applied the L7 container to it, still doesn't work. So then I changed the default LAN rule back and created a new rule above the default LAN rule and applied the L7 container to it, still didn't work. I tried setting the floating rule to In, Out, and Any, still didn't work. Any other suggestions? I have read other posts where people are saying that this works great. I wonder what I'm doing wrong.

          1 Reply Last reply Reply Quote 0
          • E
            eri--
            last edited by

            BTW it will not detect encrypted bittorrent.

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

              I'm fine with that. This layer7 filter along with the Captive Portal and OpenDNS is sufficient for what we're trying to accomplish. But if I can't get this working then I need to look elsewhere.

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

                Did you already try this with snort?

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

                  No, I have not tried it with snort. Is it easy to accomplish with snort? I just figure that this is exactly what this layer7 functionality is for. So nobody else has tried using this yet? Or if they have it's working perfectly for them?

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

                    Just updated to the latest build (built on Sat Nov 27 04:12:08 EST 2010) and still no go. I have tried setting it with one floating rule (in/out), two floating rules (one in, one out), a rule before the default LAN rule, and on the default LAN rule itself. I have tried all those rules with tcp, udp, and tcp/udp. The entries still show up in the firewall log, but nothing is actually being blocked. I'm getting down to crunch time now. I've been rocking pfSense for a quite some time now and love it, but this is probably a deal breaker for me going forward. I really don't want to start putting in ASA's (cost and ease of administration).

                    1 Reply Last reply Reply Quote 0
                    • _
                      _igor_
                      last edited by

                      I have had that same problem this days (somewhat different, not L7), but similar. I wanted to block certain traffic which worked fine before but now not. Tried the same things with rules everywhere with no success. Due to that i was thinking that me is/was not able to do this job, tried it with v1.2.3 and it worked instantly.

                      1 Reply Last reply Reply Quote 0
                      • D
                        dszp
                        last edited by

                        Last night I tried (with an up-to-date snapshot) to add a Layer 7 rule to block SSH (and added HTML later as well as a test) to an existing LAN Pass rule. It blocked neither, though the traffic was logged as being outbound based on that rule, so it was that rule being applied, but nothing was blocked based on Layer 7.

                        David Szpunar

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

                          So is this a bug then? If so, how do I go about submitting it? I saw some posts from earlier in the year where people had said this was working great for them. Maybe it worked in the earlier 2.0 builds?

                          1 Reply Last reply Reply Quote 0
                          • D
                            dszp
                            last edited by

                            Bugtracker is at http://redmine.pfsense.org/projects/pfsense/issues

                            Whether it's a bug or not isn't my call, but I'd certainly call the lack of functionality on my end a bug, unless I'm doing it totally wrong. But I read a couple of threads about it, I'm pretty sure I'm doing what I'm supposed to be doing for it to work. If you submit it, the devs will make the call :-)

                            David Szpunar

                            1 Reply Last reply Reply Quote 0
                            • nesenseN
                              nesense
                              last edited by

                              its an old issue (6 months) that never got fixed, check this: http://redmine.pfsense.org/issues/636

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

                                I see you added a comment to the bug, I did as well. Hopefully it gets addressed soon.

                                1 Reply Last reply Reply Quote 0
                                • V
                                  voona
                                  last edited by

                                  Agree, I havnt been able to get this working either.

                                  Oh while im here, does anyone know how to create different protocol containers to match a particular application? There is a fair few in the list but not everything i require.

                                  Regards,

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

                                    Voona maybe take a minute to add a comment to the bug? As for custom sigs, they mention it in the L7 portion of the traffic shaping guide. I'm guessing eventually they'll have their own write-up for it, but for now they mention taking a look at the sourceforge page.

                                    http://doc.pfsense.org/index.php/Traffic_Shaping_Guide#Layer_7

                                    http://l7-filter.sourceforge.net/Pattern-HOWTO

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