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

The Path is too deep when Filtering is on and extremely slow (SOLVED)

Scheduled Pinned Locked Moved Firewalling
3 Posts 1 Posters 1.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
    SuperFly_za
    last edited by Jan 7, 2010, 9:01 AM Jan 6, 2010, 2:23 PM

    Hello

    I'm busy trying to set up pfsense in my network but am running into a little issue when coping files from the LAN to my file server when filtering is turned on. I'm getting an error "The Path is too deep" when I try to copy files to the file server. Also, just simply browsing the folder structure on the server is extreme slow but again only when filtering is enabled.

    LAN IP: 192.168.1.1
    WAN IP: 192.168.2.1 (Connects to DSL load balancer appliance)
    OPT1 IP (Locally hosted Servers): 10.0.0.1

    I have a mail server, Web server and File Server hosted on the OPT1 interface.

    If I turn filtering off everything runs smoothly. I've even tried creating allow all rules on all interfaces and so on but still experiencing the same issues.

    Is there something that I've missed? Also, is there not a way to disable filtering on the OPT1 interface only?

    Thanks for the assistance.

    1 Reply Last reply Reply Quote 0
    • S
      SuperFly_za
      last edited by Jan 6, 2010, 4:34 PM

      I came across this site: http://teknotes.wordpress.com/2007/08/01/cannot-copy-file_name-the-path-is-too-deep/

      It's says that I might need to increase my max window size

      To make the command survive a reboot:

      1. On Linux or SecurePlatform, edit the $FWDIR/boot/modules/fwkern.conf file using vi.
        2. Set a parameter name to a value, e.g.,
            fwtcpstr_max_window=65536
        3. Run the fw ctl get int fwtcpstr_max_window command to verify whether the new value is applied on the OS properly.

      Any ideas on how to try this on pfsense?

      1 Reply Last reply Reply Quote 0
      • S
        SuperFly_za
        last edited by Jan 7, 2010, 9:00 AM

        Solved this by disabling Automatic outbound NAT and created my own outbound NAT rules. Solved my speed issues as well as the "The Path is too deep" error.

        1 Reply Last reply Reply Quote 0
        2 out of 3
        • First post
          2/3
          Last post
        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
          This community forum collects and processes your personal information.
          consent.not_received