change of initial IP 172.16.16.16

Question

If i want to replace my old UTM i cannot simply put the XG into the same network because of this fixed IP. 
 Why is the initial ip not set via DHCP? 
 I&acute;ve build this network in my enviroment only to move it then to the real address. 
 
 Christian

rfcat_vk · Accepted Answer

Hi Christian, 
you need to setup the external interface, allow login for the external interface then change the default IP to you preferred IP range. 
I did this during the beta, haven't done it yet for the production version. One warning check your DNS setup after you change things. The DNS takes a bit of getting used to, to change. You need to change the SF-OS DNS settings then change your DHCP DNS settings otherwise the DNS reverts, anyway that is my experience which means most things don't work correctly and the answer is not obvious. 
 
Ian M

Billybob · Answer

Hi Christian, this was not a problem during the first two betas as I installed from scratch both times. The external Interface got the IP from DHCP and I could change the Internal Interface LAN IP to fit my internal network on the console. I did not beta test v3 but I ran into the same problem as you when I tried to test this final GA.

Logging into the console using admin as password gives you a copyright notice and then "You need to agree to EULA. Login to Admin console to accept" and then I am logged out. I could have agreed to EULA just as well over the console by typing "yes" but now I have to login via web interface.

This is a step backward for initial configuration and I don't know how it ended up in the final GA. This is almost like a home router that you have to connect to directly @192.168.1.1 before you can do anything with it. For this very reason, I haven't tried using this GA version yet.

My guess is someone at licensing added the agree to EULA requirement without giving it much thought :/

rfcat_vk · Answer

I did the change in the GA version. Logged in remotely, deleted the dhcp server, changed the IP address of the internal network and then created the dhcp server for the new address range. Had to change the DNS settings in the DNS and DHCP tabs. 
 
ian m