Switched my router and can’t access some jails now

[Amsoil_Jim]

my old router was tacking a crap and was on a 192.168.0.0 subnet.
I now have a pfsense firewall/router with a 192.168.1.0 subnet and after changing the IP of the freenas server and the gateway I can access the GUI.
I went in the the jails configuration and changed the ip’s to reflect the new ranges.
The jails are
Plex, sickrage, couch potato, transmission, and Tautulli
They all had static addresses but were now accessible for some reason. So on Plex I went in and changed it to DHCP and then I was able to access Plex. Tautulli I was able to acces without enabling a DHCP address change.
I am not able to access sickrage, couch potato, or transmission.
Also I see a string of messages about arp attempting to change something on 192.168.1.1
I’m just trying to get everything back running until I have more time to migrate to 11.2 and iocage.
I don’t really understand how changing the gateway breaks everything.

 

[Chris Moore]

I don’t really understand how changing the gateway breaks everything.

It is a feature of TCP/IP communication. If your subnet mask is 255.255.255.0 and you have a system on the address 192.168.1.100 and another system on the address 192.168.0.100, as far as the communication protocol is concerned, those two systems are on different networks and you can't get from one address to the other without going through a router. The communication protocol does not know that the two systems are virtual and sitting inside the same host.
You have to get all the addresses in the same range and then you might need to reboot everything to ensure it picked up the new address.

 

[danb35]

Why didn't/don't you set your pfSense router to use 192.168.0.0/24 for the LAN?

 

[Amsoil_Jim]

I did change all the ip’s and the gateway on the freenas setting and jail settings and the jails so everything is now on the 192.168.1.0 subnet. And rebooted the system. I can even see the ip’s with the jail names in pfsense. But when I try to connect to them from my computer I get a connection refused error

 

[Amsoil_Jim]

Why didn't/don't you set your pfSense router to use 192.168.0.0/24 for the LAN?

I have no good answer for that... I guess I was trying to do to many things at once and just used what it was pre configured to

 

[Jailer]

Change /etc/resolv.conf in each jail to your new default gateway and restart each jail after the change.

 

[Amsoil_Jim]

Change /etc/resolv.conf in each jail to your new default gateway and restart each jail after the change.

I’ll try this later
Thanks
I was thinking there was probably something I needed to edit in each jail but didn’t know where

 

[Amsoil_Jim]

what needs to be fixed for this error message to stop?

Code:

Jul 26 16:47:16 FreeNAS kernel: arp: d0:50:99:c0:6c:4d attempts to modify permanent entry for 192.168.1.1 on epair2b
Jul 26 16:47:16 FreeNAS kernel: arp: d0:50:99:c0:6c:4d attempts to modify permanent entry for 192.168.1.1 on epair2b
Jul 26 16:47:25 FreeNAS kernel: arp: d0:50:99:c0:6c:4d attempts to modify permanent entry for 192.168.1.1 on epair2b
Jul 26 16:47:25 FreeNAS kernel: arp: d0:50:99:c0:6c:4d attempts to modify permanent entry for 192.168.1.1 on epair2b
Jul 26 16:47:28 FreeNAS kernel: arp: d0:50:99:c0:6c:4d attempts to modify permanent entry for 192.168.1.1 on epair2b
Jul 26 16:47:28 FreeNAS kernel: arp: d0:50:99:c0:6c:4d attempts to modify permanent entry for 192.168.1.1 on epair2b
Jul 26 16:48:39 FreeNAS kernel: arp: d0:50:99:c0:6c:4d attempts to modify permanent entry for 192.168.1.1 on epair2b
Jul 26 16:48:39 FreeNAS kernel: arp: d0:50:99:c0:6c:4d attempts to modify permanent entry for 192.168.1.1 on epair2b
Jul 26 16:49:25 FreeNAS kernel: arp: d0:50:99:c0:6c:4d attempts to modify permanent entry for 192.168.1.1 on epair2b
Jul 26 16:49:25 FreeNAS kernel: arp: d0:50:99:c0:6c:4d attempts to modify permanent entry for 192.168.1.1 on epair2b

Also I can access my plex server and in the settings it says its connectable but my roku said it could not connect to it on my network but it can connect to it remotely.

 

[kjbjhbik]

You can reset your router and check what is going one, you can get your router IP from http://whatsmyrouterip.com/

 

[Elliot Dierksen]

what needs to be fixed for this error message to stop?

One of your jails (or FreeNAS) is using 192.168.1.1, and your router is attempting to use that as well. You have to change the IP on one of them to something that does not conflict.

 

[pschatz100]

If networking works with DHCP, but not with a static IP, then there are two likely culprits: 1) IP address conflict or 2) need to specify the correct Default Gateway. When you use DHCP, the system sets the gateway for you. When setting a static IP, you have to specify this yourself.

 

[Amsoil_Jim]

Sorry, many things have changed since posting this and is no longer an issue