Swapping a NIC in FreeNAS

[philious77]

So here's the situation. I installed freeness with an intel nic and did some tests. Everything went well and I decided that I wanted to swap out the existing nic with a dual-port intel nic to test out LACP.

Shut down --> replace nic with dual port --> power on.

There were some issues (for example, em0 still had my old ip address (192.168.0.200)) but I could not ping it from the network.

I reconfigured the interface, set it to DHCP, rebooted, set it back to static, rebooted again, etc etc...

Eventually I was able to ping the IP from the network and was also able to browse the shares. However, as hard as I tried, I could not browse to the web interface. No matter what I did, I could not browse to http://192.168.0.200 to get the management interface.

Accessing shares via \\192.168.0.200 and pinging was fine though.

I had to reinstall freenas and re-import the volumes for the sake of saving time.

Any ideas?

 

[iSCSIinitiator]

Philious77, sorry to hear about the trouble. In another thread, you were mentioning blocking out some of the web UI code; was this problem on the same box? Is it possible that the web interface couldn't properly start after reboot because of altered code?

Either way, were nginx and django running when the box came back up? If the web services weren't started, you could have tried manually starting them and seen if that helped.

Also, if the issue was because of modified code, I would both caution against rough block-outs of the web UI code and suggest, if you absolutely had to do that, that you could back up the original web UI code on FreeNAS before making edits, then edit the code (again, this is a dangerous move), copy the altered code as well, then swap out the altered code and the original code at every restart to get it back up and running the way you want. If you don't want someone that's not savvy to see the web UI at all, changing the port for the web UI would prevent users that browse to the box's IP from seeing the web UI on port 80 and would be safer than modifying code (though this might not be sufficient for you).

Best.

 

[philious77]

I appreciate the help but of course there is no modified code here. The modifications I was talking about in other threads are being done on a test vm.

Also, I verified that nginx was listening on :80