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

    NAT Problem - outbound ports not working correctly

    Scheduled Pinned Locked Moved NAT
    3 Posts 2 Posters 1.7k 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.
    • R
      rob.janzen
      last edited by

      Good day,

      I am new to pfSense, and am having a bit of a strange problem.  I set up a basic config:  LAN addresses are 192.168.1.0/255, WAN net is 192.168.100.0/255 (with the gateway 192.168.100.254).  I have IP Blocklist, squid, and squid lightspeed packages loaded.  I tried using the Automatic Outbound NAT and configuring a manual rule with the same result:

      1. on an iPad (ios 5), when I view the app store, I can see updates to apps.  when I try to download the update, it eventually returns an error that it can not contact the store.
      2. on an iPad (ios 5) imap email to gmail.com is slow and unreliable.  I have not tried to replicate this problem elsewhere yet to see if it is a problem with imap or a problem with the iPad device.

      Currently I am using a manual rule:
      Interface: Wan
      Protocol: any
      Source: 192.168.1.0/24
      Destination type: any
          Source: blank
      Translation: interface address
          Port: blank
      No XMLRPC Sync: blank

      Any sugegestions would be appreciated.  Thanks.

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

        It is highly doubtful that your problem is NAT. Your problem is more likely with squid. Disable squid, and see if it works.

        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
        • R
          rob.janzen
          last edited by

          Thanks for the suggestion.  You were mostly right :). The problem was IP block list.  Evidently one of the lists doesn't like apple.

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