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

    Pfsense and freenas

    General pfSense Questions
    5
    49
    16.0k
    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.
    • stephenw10S
      stephenw10 Netgate Administrator
      last edited by

      Hmm, raises the possibility that the IPMI interface could have been causing trouble all along.  :-\

      Steve

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

        I'd put my money on the IPMI and FreeNAS now having the same 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
        • johnpozJ
          johnpoz LAYER 8 Global Moderator
          last edited by

          "freenas  kernel: arp: 54:be:f7:66:6c:9a attempts to modify permanent entry for 10.0.1.2 on igb0"

          Well that looks like there is a static arp setting for that IP.  That mac is registered to PEGATRON CORPORATION  54:BE:F7:00:00:00 - 54:BE:F7:FF:FF:FF, Type IEEE MA-L

          What hardware is your freenas running on?  Do you have any hardware from that company pegatron?

          As to your other error, where did you point your freenas for dns?  Those clearly resolve on the public internet without any issues

          ;; QUESTION SECTION:
          ;0.freebsd.pool.ntp.org.                IN      A

          ;; ANSWER SECTION:
          0.freebsd.pool.ntp.org. 150    IN      A      65.182.224.60
          0.freebsd.pool.ntp.org. 150    IN      A      209.118.204.201
          0.freebsd.pool.ntp.org. 150    IN      A      74.120.8.2
          0.freebsd.pool.ntp.org. 150    IN      A      50.116.55.65

          So you got something wrong with your dns if those are not resolving - or connectivity to your dns.

          Lets make this simple.. What is the IP and mask of pfsense, what is the ip and mask of freenas, what is the ip and mask of your IPMI?

          Where are you pointing to for dns, gateway?

          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.7.2, 24.11

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

            FreeBSD places permanent arp entries in the table for its interfaces.  Something else (the device with MAC address 54:be:f7:66:6c:9a) is on IP 10.0.1.2.

            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 guys

              i hope this might give you guys more info to see whats wrong

              many thanks

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

                " ( answer is 10.0.1.*** and 255.255.255.0)"

                Sorry but *** is not a IP address.. Is you don't know what it is??  From Derelict is saying, you still have a duplicate IP of 10.0.1.2

                As stated already – all of your IPs must be unique!!  10.0.1.1, 2, 3, 4, 5, etc.. you can not have devices using the same IP address or you going to have all kinds of problems.

                so how does BLANK help us, or how would that be working.. Clearly that would explain why you can not resolve ntp server, etc..

                All of your global stuff is BLANK!!

                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.7.2, 24.11

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

                  hi johnpoz

                  i hope i given the right information this time

                  What is the IP and mask of pfsense (answer is 10.0.1.2 and 255.255.255.0) this is my i think should be gateway

                  what is the ip and mask of freenas ( answer is 10.0.1.125 and 255.255.255.0)

                  what is the ip and mask of your IPMI (answer is 10.0.1.13)

                  Where are you pointing to for dns, gateway ( i am pointing at 10.0.1.2 pfsense )

                  i dont know if i got this wrong or what for freenas global config.

                  Hostname:  freenas

                  Domain:  local

                  IPv4 Default Gateway:

                  IPv6 Default Gateway:

                  Nameserver 1:  8.8.8.8

                  Nameserver 2:  8.8.4.4

                  Nameserver 3:

                  Enable netwait feature:   
                  Netwait IP list:

                  Host name data base:

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

                    Well all of that looks fine..  Other than your freenas has not gateway?  From your global options doesn't look like any gateway, so how would it talk to 8.8.8.8 to ask for 0.freebsd.pool.ntp.org, etc..

                    And if freenas is still saying it detects duplicate you got something wrong still somewhere.  But why would it complain that that dupe on 10.0.1.2 if your sayings its IP address is 10.0.1.125?

                    Do you have more than 1 IP address set on freenas?

                    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.7.2, 24.11

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

                      hi johnpoz

                      i used to have 10.0.1.2 as a freenas gateway. i dont know if that should be or not? so i took that out and left it blank, as for the freenas ip address i have changed it to 10.0.1.125 because i thought that might be the problem with my internet going down.

                      many thanks

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

                        The FreeNAS IPv4 gateway should be set to the pfSense LAN address, 10.0.1.2.
                        Without that, as John said, FreeNAS cannot access anything outside it's own subnet including the Google DNS servers.

                        FreeNAS is not complianing about a duplicate IP directly but rather an IP that doesn't match it's static ARP entry. Perhaps that needs to be updated, by rebooting maybe?

                        Steve

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

                          hi steve

                          i just took your  advice re freenas (IPv4 Default Gateway and put 10.0.1.2 as soon i done that and rebooted the freenas server and pfsense i lost the internet connection same old problem like where i started from. one more thing in freenas static routes - my gateway is 10.0.1.2 is this right . i am lost with this whole thing.

                          many thanks

                          1 Reply Last reply Reply Quote 0
                          • KOMK
                            KOM
                            last edited by

                            I think the time has come for screenshots.  Interfaces - WAN and Interfaces - LAN, plus a shot of your FreeNAS network config page.

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

                              @stephenw10:

                              FreeNAS is not complianing about a duplicate IP directly but rather an IP that doesn't match it's static ARP entry. Perhaps that needs to be updated, by rebooting maybe?

                              Looks to me like freenas (freebsd) is complaining that it's seeing ARP for 10.0.1.2, which is a permanent ARP entry on freenas, which means it is still assigned to an interface on freenas (I think.)  Or was at that time.

                              freenas  kernel: arp: 54:be:f7:66:6c:9a attempts to modify permanent entry for 10.0.1.2 on igb0

                              What device has on 54:be:f7:66:6c:9a is anyone's guess.

                              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 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
                                            • First post
                                              Last post
                                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.