Pfsense and freenas

KOM · Nov 19, 2014, 2:51 PM

Glad to see that this issue is almost fixed. This would have gone much faster if we had the correct information from the start with regard to the IP addresses of pfSense and FreeNAS, and if you had a little more knowledge of TCP/IP and networking in general.

stephenw10 · Nov 19, 2014, 6:38 PM

Everyone was there at some point. ;)

rakeshbaden2hotmail.com · Nov 19, 2014, 7:07 PM

hi everybody

first of all i like to say a very big thanks to all for your support. i have got the internet still working with everybody help in here. i got still one small problem with my freenas server i lost my ipmi connection with it. my original problem was losing internet connection once the freenas server comes on. i changed my (IPv4 Default Gateway) and ( Nameserver 1) in freenas under global configuration which was same as my pfsense ip address. but since then i can't use my ipmi connection. any advice please

many thanks

johnpoz · Nov 19, 2014, 7:13 PM

what?? You would want your gateway and name server to be pfsense IP.. What other gateway do you have? What other name server? In a typical setup, all lan devices would use pfsense as their gateway off the lan, and as the nameserver - ie to lookup www.google.com

You need to change the IP of your freenas, not to be the same as pfsense lan IP, ie the big warning pfsense was telling you

"kernel: arp: 02:62:91:00:11:0b is using my IP address 10.0.1.2 on em1"

So what did you change the freenas IP to be?? What IP did you or do you have setup on the IPMI?

Derelict · Nov 19, 2014, 8:37 PM

All IP addresses need to be unique on your network segment. This also applies to your IPMI. You probably need to reboot, get into your IPMI config, and be sure it has been given unique and proper network settings.

stephenw10 · Nov 19, 2014, 8:36 PM

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

Steve

Derelict · Nov 19, 2014, 8:38 PM

I'd put my money on the IPMI and FreeNAS now having the same IP.

johnpoz · Nov 20, 2014, 6:48 PM

"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?

Derelict · Nov 20, 2014, 7:11 PM

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.

rakeshbaden2hotmail.com · Nov 20, 2014, 8:48 PM

hi guys

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

many thanks

johnpoz · Nov 20, 2014, 9:18 PM

" ( 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!!

rakeshbaden2hotmail.com · Nov 20, 2014, 9:37 PM

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:

johnpoz · Nov 20, 2014, 10:01 PM

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?

rakeshbaden2hotmail.com · Nov 20, 2014, 10:14 PM

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

stephenw10 · Nov 20, 2014, 10:32 PM

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

rakeshbaden2hotmail.com · Nov 20, 2014, 11:19 PM

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

KOM · Nov 21, 2014, 12:36 AM

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

Derelict · Nov 21, 2014, 12:40 AM

@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.

rakeshbaden2hotmail.com · Nov 22, 2014, 12:46 PM

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

stephenw10 · Nov 22, 2014, 1:10 PM

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

Steve