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

    Pfsense and freenas

    Scheduled Pinned Locked Moved General pfSense Questions
    49 Posts 5 Posters 17.6k 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
      rakeshbaden2hotmail.com
      last edited by

      hi guys

      thanks once again for everybody help so far. i have done something which i would like to share to see if that help with my problem. i have changed my pfsense ipv4 addresss from 10.0.1.2 to 10.0.1.120. i am still getting this on my freenas please advice thanks

      Nov 22 12:18:43 freenas ntpd_initres[9681]: host name not found: 0.freebsd.pool.ntp.org
      Nov 22 12:18:43 freenas ntpd_initres[9681]: host name not found: 1.freebsd.pool.ntp.org
      Nov 22 12:18:43 freenas ntpd_initres[9681]: host name not found: 2.freebsd.pool.ntp.org
      Nov 22 12:18:44 freenas smbd[21897]:  STATUS=daemon 'smbd' finished starting up and ready to serve connectionsmatchname: host name/name mismatch: 10.0.1.20 != (NULL)
      Nov 22 12:18:44 freenas smbd[21897]: [2014/11/22 12:18:44.897773,  0] ../source3/lib/util_sock.c:1199(get_remote_hostname)
      Nov 22 12:18:44 freenas smbd[21897]:  matchname failed on 10.0.1.20
      Nov 22 12:20:54 freenas smbd[21954]:  STATUS=daemon 'smbd' finished starting up and ready to serve connectionsmatchname: host name/name mismatch: 10.0.1.20 != (NULL)
      Nov 22 12:20:54 freenas smbd[21954]: [2014/11/22 12:20:54.128137,  0] ../source3/lib/util_sock.c:1199(get_remote_hostname)
      Nov 22 12:20:54 freenas smbd[21954]:  matchname failed on 10.0.1.20
      Nov 22 12:20:54 freenas smbd[21955]:  STATUS=daemon 'smbd' finished starting up and ready to serve connectionsmatchname: host name/name mismatch: 10.0.1.20 != (NULL)
      Nov 22 12:20:54 freenas smbd[21955]: [2014/11/22 12:20:54.130880,  0] ../source3/lib/util_sock.c:1199(get_remote_hostname)
      Nov 22 12:20:54 freenas smbd[21955]:  matchname failed on 10.0.1.20
      Nov 22 12:23:34 freenas smbd[21996]:  STATUS=daemon 'smbd' finished starting up and ready to serve connectionsmatchname: host name/name mismatch: 10.0.1.20 != (NULL)
      Nov 22 12:23:34 freenas smbd[21996]: [2014/11/22 12:23:34.061577,  0] ../source3/lib/util_sock.c:1199(get_remote_hostname)
      Nov 22 12:23:34 freenas smbd[21996]:  matchname failed on 10.0.1.20
      Nov 22 12:23:34 freenas smbd[21997]:  STATUS=daemon 'smbd' finished starting up and ready to serve connectionsmatchname: host name/name mismatch: 10.0.1.20 != (NULL)
      Nov 22 12:23:34 freenas smbd[21997]: [2014/11/22 12:23:34.065449,  0] ../source3/lib/util_sock.c:1199(get_remote_hostname)
      Nov 22 12:23:34 freenas smbd[21997]:  matchname failed on 10.0.1.20
      Nov 22 12:27:54 freenas smbd[22087]:  STATUS=daemon 'smbd' finished starting up and ready to serve connectionsmatchname: host name/name mismatch: 10.0.1.20 != (NULL)
      Nov 22 12:27:54 freenas smbd[22087]: [2014/11/22 12:27:54.505510,  0] ../source3/lib/util_sock.c:1199(get_remote_hostname)
      Nov 22 12:27:54 freenas smbd[22087]:  matchname failed on 10.0.1.20
      Nov 22 12:27:54 freenas smbd[22088]:  STATUS=daemon 'smbd' finished starting up and ready to serve connectionsmatchname: host name/name mismatch: 10.0.1.20 != (NULL)
      Nov 22 12:27:54 freenas smbd[22088]: [2014/11/22 12:27:54.508444,  0] ../source3/lib/util_sock.c:1199(get_remote_hostname)
      Nov 22 12:27:54 freenas smbd[22088]:  matchname failed on 10.0.1.20
      Nov 22 12:29:05 freenas smbd[22104]:  STATUS=daemon 'smbd' finished starting up and ready to serve connectionsmatchname: host name/name mismatch: 10.0.1.20 != (NULL)
      Nov 22 12:29:05 freenas smbd[22104]: [2014/11/22 12:29:05.211041,  0] ../source3/lib/util_sock.c:1199(get_remote_hostname)
      Nov 22 12:29:05 freenas smbd[22104]:  matchname failed on 10.0.1.20
      Nov 22 12:29:05 freenas smbd[22105]:  STATUS=daemon 'smbd' finished starting up and ready to serve connectionsmatchname: host name/name mismatch: 10.0.1.20 != (NULL)
      Nov 22 12:29:05 freenas smbd[22105]: [2014/11/22 12:29:05.215825,  0] ../source3/lib/util_sock.c:1199(get_remote_hostname)
      Nov 22 12:29:05 freenas smbd[22105]:  matchname failed on 10.0.1.20
      Nov 22 12:33:38 freenas smbd[22362]:  STATUS=daemon 'smbd' finished starting up and ready to serve connectionsmatchname: host name/name mismatch: 10.0.1.20 != (NULL)
      Nov 22 12:33:38 freenas smbd[22362]: [2014/11/22 12:33:38.917707,  0] ../source3/lib/util_sock.c:1199(get_remote_hostname)
      Nov 22 12:33:38 freenas smbd[22362]:  matchname failed on 10.0.1.20
      Nov 22 12:33:38 freenas smbd[22363]:  STATUS=daemon 'smbd' finished starting up and ready to serve connectionsmatchname: host name/name mismatch: 10.0.1.20 != (NULL)
      Nov 22 12:33:38 freenas smbd[22363]: [2014/11/22 12:33:38.923588,  0] ../source3/lib/util_sock.c:1199(get_remote_hostname)
      Nov 22 12:33:38 freenas smbd[22363]:  matchname failed on 10.0.1.20
      Nov 22 12:35:12 freenas ntpd_initres[9681]: host name not found: 0.freebsd.pool.ntp.org
      Nov 22 12:35:12 freenas ntpd_initres[9681]: host name not found: 1.freebsd.pool.ntp.org
      Nov 22 12:35:12 freenas ntpd_initres[9681]: host name not found: 2.freebsd.pool.ntp.org
      Nov 22 12:38:54 freenas smbd[22525]:  STATUS=daemon 'smbd' finished starting up and ready to serve connectionsmatchname: host name/name mismatch: 10.0.1.20 != (NULL)
      Nov 22 12:38:54 freenas smbd[22525]: [2014/11/22 12:38:54.082255,  0] ../source3/lib/util_sock.c:1199(get_remote_hostname)
      Nov 22 12:38:54 freenas smbd[22526]:  STATUS=daemon 'smbd' finished starting up and ready to serve connectionsmatchname: host name/name mismatch: 10.0.1.20 != (NULL)
      Nov 22 12:38:54 freenas smbd[22525]:  matchname failed on 10.0.1.20
      Nov 22 12:38:54 freenas smbd[22526]: [2014/11/22 12:38:54.082946,  0] ../source3/lib/util_sock.c:1199(get_remote_hostname)
      Nov 22 12:38:54 freenas smbd[22526]:  matchname failed on 10.0.1.20
      Nov 22 12:45:38 freenas smbd[22729]:  STATUS=daemon 'smbd' finished starting up and ready to serve connectionsmatchname: host name/name mismatch: 10.0.1.20 != (NULL)
      Nov 22 12:45:38 freenas smbd[22729]: [2014/11/22 12:45:38.958032,  0] ../source3/lib/util_sock.c:1199(get_remote_hostname)
      Nov 22 12:45:38 freenas smbd[22729]:  matchname failed on 10.0.1.20
      Nov 22 12:45:38 freenas smbd[22730]:  STATUS=daemon 'smbd' finished starting up and ready to serve connectionsmatchname: host name/name mismatch: 10.0.1.20 != (NULL)
      Nov 22 12:45:38 freenas smbd[22730]: [2014/11/22 12:45:38.960917,  0] ../source3/lib/util_sock.c:1199(get_remote_hostname)
      Nov 22 12:45:38 freenas smbd[22730]:  matchname failed on 10.0.1.20

      1 Reply Last reply Reply Quote 0
      • stephenw10S
        stephenw10 Netgate Administrator
        last edited by

        The logs are showing an error relatjng to the address 10.0.1.20. What is or was that address?

        Steve

        1 Reply Last reply Reply Quote 0
        • R
          rakeshbaden2hotmail.com
          last edited by

          hi steve

          that is my macbook pro ip address and my freenas does the backup my macbook pro to freenas server.

          thanks

          1 Reply Last reply Reply Quote 0
          • stephenw10S
            stephenw10 Netgate Administrator
            last edited by

            Hmm. Ok. Did you change the IP details in FreeNAS to use the new pfSense address as it's gateway?

            Screenshots would really be great here.  ;)

            Steve

            1 Reply Last reply Reply Quote 0
            • stephenw10S
              stephenw10 Netgate Administrator
              last edited by

              Looks fine.
              A screenshot of the FreeNAS network config page would probably be helpful.

              Can you resolve those NTP servers from any other machine on the LAN? Or from the pfSense box?

              Steve

              1 Reply Last reply Reply Quote 0
              • stephenw10S
                stephenw10 Netgate Administrator
                last edited by

                The default gateway must be set to the pfSense LAN address, 10.0.1.120. Without that set the FreeNAS box will not have a route to anywhere outside it's own subnet, it can't reach the Google DNS servers at 8.8.8.8 and 8.8.4.4.

                Steve

                1 Reply Last reply Reply Quote 0
                • DerelictD
                  Derelict LAYER 8 Netgate
                  last edited by

                  You don't need a static route.  Delete that and set your gateway in freenas to the pfsense IP.

                  Chattanooga, Tennessee, USA
                  A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                  DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                  Do Not Chat For Help! NO_WAN_EGRESS(TM)

                  1 Reply Last reply Reply Quote 0
                  • R
                    rakeshbaden2hotmail.com
                    last edited by

                    hi derelict

                    thanks for your reply is it possible to see and screenshot of this . and do you use freenas server too.

                    thanks

                    1 Reply Last reply Reply Quote 0
                    • DerelictD
                      Derelict LAYER 8 Netgate
                      last edited by

                      Yes, I use FreeNAS and pfSense.

                      Screenshot of what?

                      You keep talking about some static route.  You don't need any static routes so if you have configured one, delete it.

                      Change the gateway in FreeNAS to the LAN IP of pfSense, which I suppose is 10.0.1.120.

                      Chattanooga, Tennessee, USA
                      A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                      DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                      Do Not Chat For Help! NO_WAN_EGRESS(TM)

                      1 Reply Last reply Reply Quote 0
                      • johnpozJ
                        johnpoz LAYER 8 Global Moderator
                        last edited by

                        Dude it seems like there is a language barrier here, and just basic concepts maybe - you don't seem to grasp the concept of what a gateway is or what IPs even do..

                        You change your pfsense to 10.0.1.120, then why do you have freenas default gateway set to 10.0.1.1 ???  Do you not understand what a gateway is?

                        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 24.11 | Lab VMs 2.8, 24.11

                        1 Reply Last reply Reply Quote 0
                        • stephenw10S
                          stephenw10 Netgate Administrator
                          last edited by

                          Those are both FreeNAS issues. The first looks like some problem with jails perhaps? It's trying to rename the virtual Ethernet pair and can't for whatever reason. The second issue maybe DNS related. Read this: https://bugs.freenas.org/issues/4027 Have you recently updated FreeNAS?

                          You will probably have more luck on the FreeNAS forum solving those, though many here run FreeNAS.

                          Steve

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