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

    No internet with surten user account (

    Scheduled Pinned Locked Moved DHCP and DNS
    23 Posts 3 Posters 2.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.
    • johnpozJ Offline
      johnpoz LAYER 8 Global Moderator
      last edited by

      Dude your really started get on dok's nerves it seems ;)  Which I enjoy very much!!  He is fun as all hell when he gets perturbed by stupidity..

      Dude how hard is it to setup the same mask on both your pfsense interface and the rest of your network..  This is basic 101 stuff that really needs to be done before you start playing with proxies and shit..

      An intelligent man is sometimes forced to be drunk to spend time with his fools
      If you get confused: Listen to the Music Play
      Please don't Chat/PM me for help, unless mod related
      SG-4860 25.07.1 | Lab VMs 2.8.1, 25.07.1

      1 Reply Last reply Reply Quote 0
      • L Offline
        Linton89
        last edited by

        I know but like i've said: when i do that and reboot pfsense then there's no more internet (no pinging from lan side to both url and ip) and no pinging to url from pfsense console. Thats why i assumed there maybe is another problem in pfsense.

        Beginning from scratch could indeed ruled that out but i wanted to avoid resetting. As i get an error when loading i think that that should be solved and could be related but that will be something tot test later on.

        Thanks though and i will follow your advise after getting pfsense fully functional without errors (that are not related to configuration but packages etc, or so it seems)

        1 Reply Last reply Reply Quote 0
        • L Offline
          Linton89
          last edited by

          Beginning with an new configuration from scratch is what i didn't want to do.

          I partly followed the above advise by resetting the firewall but in stead of building everything from scratch I uploaded the configuration file i exported before updating pfsense. For me that made sense because the previous configuration worked for two years (i thought one but i saw it worked 2) and so the only thing that had to be changed was the LAN-subnetmask (like you can read in previous posts: i already knew that but after rebooting pfsense it didn't work at all).

          The problem with rebooting and pfsense not working anymore was solved after resetting en uploading my configuration file but the proxy error not. This was solved by installing squid3 (it first installed squid, the package that was used in the past).

          Thanks for the help.

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