Pfsense and freenas
-
hi guys
i hope this might give you guys more info to see whats wrong
many thanks
-
" ( 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!!
-
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:
-
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?
-
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
-
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
-
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
-
I think the time has come for screenshots. Interfaces - WAN and Interfaces - LAN, plus a shot of your FreeNAS network config page.
-
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.
-
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 -
The logs are showing an error relatjng to the address 10.0.1.20. What is or was that address?
Steve
-
hi steve
that is my macbook pro ip address and my freenas does the backup my macbook pro to freenas server.
thanks
-
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
-
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
-
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
-
You don't need a static route. Delete that and set your gateway in freenas to the pfsense IP.
-
hi derelict
thanks for your reply is it possible to see and screenshot of this . and do you use freenas server too.
thanks
-
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.
-
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?
-
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