Messages

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.

Code Select Expand

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

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 Expand

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

So, the solution was to wipe pfSense from the drive completly on another computer for it to boot correctly.
But the USB-drive still refuses to boot for me! :(

Dunno what the problem could be, because UEFI is turned off.

Will try the 15.7 release also, but would be nice to see what could be the problem why I can´t boot 2 different images. :(

Hi all!

Having big big problems booting both the cdrom version from DVD (due to the size of the file) and the VGA release from USB.

Trying to install it on my proliant Microserver Gen7 and the BIOS is put to boot from all connected USB devices, but the cdrom images refuses to boot for me. And when I check the DVD on another computer it´s all there on it.

When trying to boot the VGA release, I end up with a blinking cursor on the screen and nothing more happens.

Search and found this: https://forum.opnsense.org/index.php?topic=1905.0, but that´s for the 15.7 release.

Best
Pontus

Hi all!

How do I get invite for this? I know I´m new, but has used PfSense in years now and on my move to migrate to OPNsense now...

Best
Pontus