Navigation

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

    Pfsense lan ip

    Firewalling
    7
    9
    3849
    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.
    • E
      eagle last edited by

      hi;
      i use command "tracert www.google.com" and i dont want to see "pfsense.local [192.168.1.1]" .it is my lan ip.if you help me im glad. ;)

      1 Reply Last reply Reply Quote 0
      • P
        Perry last edited by

        Hmm it's always the first hop else you'll have to traceroute from pfsense.

        1 Reply Last reply Reply Quote 0
        • E
          eagle last edited by

          @Perry:

          Hmm it's always the first hop else you'll have to traceroute from pfsense.

          from pfsense its ok. but windows cmd screen i use tracert command i dont want to see pfsense.local ip adress. i want to hide lan ip adress and how can i do at pfsense   ;)

          1 Reply Last reply Reply Quote 0
          • Cry Havok
            Cry Havok last edited by

            The only way to do it is with a transparent firewall.  This has issues - do search the forum.

            1 Reply Last reply Reply Quote 0
            • A
              AtomicPlayboy last edited by

              @eagle:

              from pfsense its ok. but windows cmd screen i use tracert command i dont want to see pfsense.local ip adress. i want to hide lan ip adress and how can i do at pfsense   ;)

              Any host that has gotten an address via dhcp (or is otherwise properly configured to get to the Internet) will have a default route and thus know the lan ip address of your pfSense box.

              What problem exactly are you trying to solve here?

              1 Reply Last reply Reply Quote 0
              • E
                eagle last edited by

                @AtomicPlayboy:

                @eagle:

                from pfsense its ok. but windows cmd screen i use tracert command i dont want to see pfsense.local ip adress. i want to hide lan ip adress and how can i do at pfsense   ;)

                Any host that has gotten an address via dhcp (or is otherwise properly configured to get to the Internet) will have a default route and thus know the lan ip address of your pfSense box.

                What problem exactly are you trying to solve here?

                in my system user use tracert command at windows cmd example "tracert www.google.com"  they see "pfsense.local[192.168.1.1].but i want to hide this ip adress.in other words user will not know firewall(pfsense) at system.i hope i can explain it

                1 Reply Last reply Reply Quote 0
                • ?
                  Guest last edited by

                  wut?

                  1 Reply Last reply Reply Quote 0
                  • GruensFroeschli
                    GruensFroeschli last edited by

                    eagle: As Cry Havok said, this is only possible with a "transparent firewall" setup.
                    Searc the forum and the docs for info on how to set that up: http://doc.pfsense.org/index.php/Tutorials

                    As long as pfSense itself actually routes traffic it's not possible what you're trying to achieve.

                    But what i'm thinking: why are you trying to hide the pfSense IP?
                    I mean as it is right now your users can type "ipconfig" on the cmd and they will see the default gateway which is the pfSense IP, so no point in what you're proposing.

                    1 Reply Last reply Reply Quote 0
                    • C
                      cmb last edited by

                      Oh, I think what the original poster is saying is he doesn't want the name of the firewall to show up in the traceroute?

                      That comes from the reverse DNS, on the System -> General page you have it set to pfsense.local so when you traceroute and it does a reverse DNS lookup that's what you get. You can change the name thee to have it show up as something else but there really isn't any point in that at all, you should be able to broadcast to the world what firewall you're using without any security risk. Especially when that's just on your internal network.

                      1 Reply Last reply Reply Quote 0
                      • First post
                        Last post

                      Products

                      • Platform Overview
                      • TNSR
                      • pfSense Plus
                      • Appliances

                      Services

                      • Training
                      • Professional Services

                      Support

                      • Subscription Plans
                      • Contact Support
                      • Product Lifecycle
                      • Documentation

                      News

                      • Media Coverage
                      • Press
                      • Events

                      Resources

                      • Blog
                      • FAQ
                      • Find a Partner
                      • Resource Library
                      • Security Information

                      Company

                      • About Us
                      • Careers
                      • Partners
                      • Contact Us
                      • Legal
                      Our Mission

                      We provide leading-edge network security at a fair price - regardless of organizational size or network sophistication. We believe that an open-source security model offers disruptive pricing along with the agility required to quickly address emerging threats.

                      Subscribe to our Newsletter

                      Product information, software announcements, and special offers. See our newsletter archive to sign up for future newsletters and to read past announcements.

                      © 2021 Rubicon Communications, LLC | Privacy Policy