OPNsense Forum

Archive => 16.1 Legacy Series => Topic started by: gh0st on March 25, 2016, 08:21:26 am

Title: OPNsense changed from 192.168.1.1 -> .100 during the night!
Post by: gh0st on March 25, 2016, 08:21:26 am
Hi all!

Today when I was starting to contiune with the setup of OPNsense I found out that I couldn´t connect to the box at all. No Internet and nothing worked from my other computers.

Fired up the TV that the server is connected to, only to found out that OPNsense during the night has switched the LAN from 192.168.1.1 to 192.168.1.100 with the result of a broken network and forced to reboot the firewall.

Code: [Select]
Mar 25 06:46:38 opnsense: /usr/local/etc/rc.newwanip: rc.newwanip: on (IP address: 192.168.1.100) (interface: LAN[lan]) (real interface: em1).
Mar 25 04:46:35 opnsense: /usr/local/etc/rc.newwanip: rc.newwanip: on (IP address: 192.168.1.100) (interface: LAN[lan]) (real interface: em1).
Mar 25 02:46:30 opnsense: /usr/local/etc/rc.newwanip: rc.newwanip: on (IP address: 192.168.1.100) (interface: LAN[lan]) (real interface: em1).
Mar 25 00:46:28 opnsense: /usr/local/etc/rc.newwanip: rc.newwanip: on (IP address: 192.168.1.100) (interface: LAN[lan]) (real interface: em1).
Mar 24 22:46:24 opnsense: /usr/local/etc/rc.newwanip: rc.newwanip: on (IP address: 192.168.1.100) (interface: LAN[lan]) (real interface: em1).
Mar 24 20:46:28 opnsense: /usr/local/etc/rc.linkup: The command '/usr/local/sbin/dhcpd -user dhcpd -group dhcpd -chroot /var/dhcpd -cf /etc/dhcpd.conf -pf /var/run/dhcpd.pid em0' returned exit code '1', the output was 'Internet Systems Consortium DHCP Server 4.2.8 Copyright 2004-2015 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ bad range, address 192.168.1.100 not in subnet 85.24.129.0 netmask 255.255.255.128 If you did not get this software from ftp.isc.org, please get the latest from ftp.isc.org and install that before requesting help. If you did get this software from ftp.isc.org and have not yet read the README, please read it before requesting help. If you intend to request help from the dhcp-bugs at isc.org mailing list, please read the section on the README about submitting bug reports and requests for help. Please do not under any circumstances send requests for help directly to the authors of this software - please send them to the
Mar 24 20:46:20 opnsense: /usr/local/etc/rc.newwanip: rc.newwanip: on (IP address: 192.168.1.100) (interface: LAN[lan]) (real interface: em1).

Best
Pontus
Title: Re: OPNsense changed from 192.168.1.1 -> .100 during the night!
Post by: AdSchellevis on March 25, 2016, 08:56:32 am
Hi Pontus,

Can you share some more information about your setup? A changing ip on a static interface sounds really odd.
Is the address 192.168.1.100 used anywhere in your setup?

Just to be sure can you grep your config directory for this address?
Code: [Select]
grep -r '192.168.1.100' /conf/


Regards,

Ad
Title: Re: OPNsense changed from 192.168.1.1 -> .100 during the night!
Post by: gh0st on March 25, 2016, 09:22:13 am
Code: [Select]
root@OPNsense:~ # grep -r '192.168.1.100' /conf/
/conf/backup/config-1458848571.9003.xml:        <from>192.168.1.100</from>
/conf/backup/config-1458848637.8221.xml:        <from>192.168.1.100</from>
/conf/backup/config-1458848724.9111.xml:        <from>192.168.1.100</from>
/conf/backup/config-1458848784.8232.xml:        <from>192.168.1.100</from>
/conf/backup/config-1458848977.1463.xml:        <from>192.168.1.100</from>
/conf/backup/config-1458849056.0971.xml:        <from>192.168.1.100</from>
/conf/backup/config-1458890255.534.xml:        <from>192.168.1.100</from>
/conf/backup/config-1458890255.645.xml:        <from>192.168.1.100</from>
/conf/backup/config-1458893443.0615.xml:        <from>192.168.1.100</from>
/conf/backup/config-1458893540.9328.xml:        <from>192.168.1.100</from>
/conf/backup/config-1458893611.102.xml:        <from>192.168.1.100</from>
/conf/backup/config-1458893619.5872.xml:        <from>192.168.1.100</from>
/conf/backup/config-1458893695.1191.xml:        <from>192.168.1.100</from>
/conf/backup/config-1458893890.7084.xml:        <from>192.168.1.100</from>
/conf/backup/config-1458893923.3725.xml:        <from>192.168.1.100</from>
/conf/backup/config-1458893962.1139.xml:        <from>192.168.1.100</from>
/conf/config.xml:        <from>192.168.1.100</from>

Best
Pontus
Title: Re: OPNsense changed from 192.168.1.1 -> .100 during the night!
Post by: AdSchellevis on March 25, 2016, 09:26:01 am
ok, that looks like the starting address of your dhcp server. any chance that your lan was reconfigured to use dhcp somewhere (maybe without applying)?

If you like, I can check your configuration to see if there's anything odd in there, if you can arrange access to the machine or email me a configuration. (I'm online at our irc channel)
Title: Re: OPNsense changed from 192.168.1.1 -> .100 during the night!
Post by: gh0st on March 25, 2016, 09:33:02 am
The only place I found the .100 is on Services -> DHCP -> Server where the range is put to 192.168.1.100 as starting point. But I didn´t put that in there, and I haven´t clicked saved also.

So, it seems that this can interfere with the rest.

Anyhow, I will change it all now, but just wounder how it can change without human input.
Title: Re: OPNsense changed from 192.168.1.1 -> .100 during the night!
Post by: AdSchellevis on March 25, 2016, 09:35:51 am
Well, the only thing I can think of is that for some strange reason a dhcp client was active on your lan network. The address is the default, which shouldn't be any issue.
Title: Re: OPNsense changed from 192.168.1.1 -&gt; .100 during the night!
Post by: jstrebel on March 25, 2016, 10:29:41 am
My 2ct. I never use the 192.168.0 and 192.168.1 because many devices fall back to this adress ranges after a factory reset. Some devices have per default dhcp server on. This can cause problems


Gesendet von iPhone mit Tapatalk
Title: Re: OPNsense changed from 192.168.1.1 -> .100 during the night!
Post by: franco on March 25, 2016, 11:42:09 am
I've seen this one or two times over the last year: the WAN interface picks up an IP address from the LAN DHCP server. This is a problem in the default config when trying to switch LAN <-> WAN interfaces from the console and/or connecting the system as an endpoint host instead into a network that has the same IP as Jakob said.

If this was indeed an endpoint scenario setup, please attach WAN to your network and disable LAN.