Resetting network configuration is the only way

[tfran1990]

Currently on freenas 11.2U8
This issue has never happen before the update from 11.1U7

After reboot i get "the web interface could not be accessed"
for some reason the only way i can get to the GUI of freenas is by connecting a monitor and using the console to reconfigure network interface(option1)


i noticed this because i got an email saying

Code:

FreeNAS @ freenas.local

New alerts:
* The web interface could not bind to 192.168.1.222; using 0.0.0.0

So far I have tried going to system>general> and changing the GUIipv4 to 0.0.0.0 then network< interface and reassigning the ip. it made no difference.

i can get to my SMB shares but there very slow to connect.

i looked at my router DHCP and i dont have the ip reserved.(in the last 4 years it has been fine)
If i have to reboot the server or the switch and router i can no longer get to the freenas, i have to go reassign the the ip again in the console.

Not sure if it is related but it takes an EXTREAMLY long time for freenas to reboot. im not running any jails or vm's

could their be something wrong with the onboard NIC. maybe?

 

[Basil Hendroff]

If you boot into U7, does the problem go away?

 

[tfran1990]

I have choosen to save my 11.1U7 Environment, but i have promoted the datasets.
i though you couldnt go back or you get stuck in read only mode on datasets.

i back up my config all the time BTW.

 

[tfran1990]

 

[Basil Hendroff]

That's fine. All we want to establish is that U7 behaves as you expect. For future noting: Wait a while before upgrading ZFS flags in case you need to rollback and stay on a previous FreeNAS version until you've resolved any issues.

 

[SweetAndLow]

What is your hardware? How many nic's? What switch? what router? How is your network layout? There isn't enough information in your original post to actually help you.

Can you ping your freenas server? is there any packet loss?

 

[tfran1990]

What is your hardware? How many nic's? What switch? what router? How is your network layout?

im using an HP prolient ml10 with the single onboard NIC, the switch im using is an ProSAFE JGS516PE and it's connected by the shitty ATT gateway on a basic class c network.

When i am trying to get to the gui and its not responding, i can still ping it.

im trying to activate the 11.1U7 env. to see if i get the same issues.

 

[tfran1990]

After i activate 11.1U7 it boots to this point.
i still get a ping from it tho....

 

[Apollo]

Freenas is in panic mode (it crashed) from what I can tell.
This is the reason why your system is unresponsive.
You won't go any further in that state.

 

[tfran1990]

i was able to get it to boot to 11.1U7 but i still have to go set the ip to get to the gui.

when i look at my devices using advance ip scanner, once i set the ip from the console it shown the right MAC but after it becomes unresponsive it shows a MAC address close to the att gateway.

 

[Apollo]

Cleanest way would be to reset network settings through console. Iocage jail or VM could mess with the network interface.

 

[tfran1990]

Cleanest way would be to reset network settings through console. iocage jail or VM could mess with the network interface.

Thats what i do everytime.

 

[tfran1990]

DHCP should be handled by the gateway.
Here is an option on my switch.

 

[Apollo]

You said you are not using any Iocage jail or VM, do you have any plugins installed?
One thing I think to remember, is that in order to use binding, you need to set the proper interface under "Network" => "Interfaces" in GUI.
Have you tried clearing the cache of your browser?
I suspect the issue could be related to your switch.
Can you assign an IP address from the switch which will set the IP on Freenas when DHCP negotiation takes place.

 

[tfran1990]

You said you are not using any iocage jail or VM, do you have any plugins installed?
One thing I think to remember, is that in order to use binding, you need to set the proper interface under "Network" => "Interfaces" in GUI.
Have you tried clearing the cache of your browser?
I suspect the issue could be related to your switch.
Can you assign an IP address from the switch which will set the IP on Freenas when DHCP negotiation takes place.

no jails,vm or plugins.
I made sure the correct ip was set in the interface, as well as the gui ipv4.
As for the browser, no i have not, but no devices can talk to the server when i lose connectivity.
i have never messed with any of the settings. it does not let me set any ips.


The ATT gateway is kinda limited on what you can do, it has a DHCP range in which it will start and end address. i might try to use one if them and see if it sticks.

Another thing i didnt think about is i have a freenas test server running 11.3U2 and i have no issues ever.

 

[Apollo]

Have you tried to run the command under CLI?

service netif restart

 

[tfran1990]

Have you tried to run the command under CLI?

service netif restart

no i have not

do i also use service routing restart

 

[tfran1990]

Ok so i used the command service netif restart and service routing restart earler today because i was no longer able to get to the GUI.
This is the output of the command

Code:

root@freenas:~ # service netif restart
Stopping Network: lo0 em0.
lo0: flags=8048<LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
        options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
        groups: lo
em0: flags=8c02<BROADCAST,OACTIVE,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=209b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC                                     >
        ether e0:07:1b:ff:fa:ff
        hwaddr e0:07:1b:ff:fa:ff
        nd6 options=9<PERFORMNUD,IFDISABLED>
        media: Ethernet autoselect (1000baseT <full-duplex>)
        status: active
Starting Network: lo0 em0.
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
        options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
        inet6 ::1 prefixlen 128
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2
        inet 127.0.0.1 netmask 0xff000000
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
        groups: lo
em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=209b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC                                     >
        ether e0:07:1b:ff:fa:ff
        hwaddr e0:07:1b:ff:fa:ff
        inet 192.168.1.222 netmask 0xffffff00 broadcast 192.168.1.255
        nd6 options=9<PERFORMNUD,IFDISABLED>
        media: Ethernet autoselect
        status: no carrier
root@freenas:~ # service routing restart
delete host 127.0.0.1: gateway lo0
route: route has not been found
delete net 192.168.1.222: gateway 192.168.1.254 fib 0: not in table
route: route has not been found
delete net default: gateway 192.168.1.254 fib 0: not in table
delete host ::1: gateway lo0
delete net fe80::: gateway ::1
delete net ff02::: gateway ::1
delete net ::ffff:0.0.0.0: gateway ::1
delete net ::0.0.0.0: gateway ::1
add host 127.0.0.1: gateway lo0
add net 192.168.1.222: gateway 192.168.1.254
add net default: gateway 192.168.1.254
add host ::1: gateway lo0
add net fe80::: gateway ::1
add net ff02::: gateway ::1
add net ::ffff:0.0.0.0: gateway ::1
add net ::0.0.0.0: gateway ::1
root@freenas:~ #

 

[Apollo]

Ok so i used the command service netif restart and service routing restart earler today because i was no longer able to get to the GUI.
This is the output of the command

Code:

root@freenas:~ # service netif restart
Stopping Network: lo0 em0.
lo0: flags=8048<LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
        options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
        groups: lo
em0: flags=8c02<BROADCAST,OACTIVE,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=209b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC                                     >
        ether e0:07:1b:ff:fa:ff
        hwaddr e0:07:1b:ff:fa:ff
        nd6 options=9<PERFORMNUD,IFDISABLED>
        media: Ethernet autoselect (1000baseT <full-duplex>)
        status: active
Starting Network: lo0 em0.
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
        options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
        inet6 ::1 prefixlen 128
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2
        inet 127.0.0.1 netmask 0xff000000
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
        groups: lo
em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=209b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC                                     >
        ether e0:07:1b:ff:fa:ff
        hwaddr e0:07:1b:ff:fa:ff
        inet 192.168.1.222 netmask 0xffffff00 broadcast 192.168.1.255
        nd6 options=9<PERFORMNUD,IFDISABLED>
        media: Ethernet autoselect
        status: no carrier
root@freenas:~ # service routing restart
delete host 127.0.0.1: gateway lo0
route: route has not been found
delete net 192.168.1.222: gateway 192.168.1.254 fib 0: not in table
route: route has not been found
delete net default: gateway 192.168.1.254 fib 0: not in table
delete host ::1: gateway lo0
delete net fe80::: gateway ::1
delete net ff02::: gateway ::1
delete net ::ffff:0.0.0.0: gateway ::1
delete net ::0.0.0.0: gateway ::1
add host 127.0.0.1: gateway lo0
add net 192.168.1.222: gateway 192.168.1.254
add net default: gateway 192.168.1.254
add host ::1: gateway lo0
add net fe80::: gateway ::1
add net ff02::: gateway ::1
add net ::ffff:0.0.0.0: gateway ::1
add net ::0.0.0.0: gateway ::1
root@freenas:~ #

Seems fine, I think.
I didn't know about the service routing restart .
But once you have run those commands, were you able to access the GUI?

 

[tfran1990]

Seems fine, I think.
I didn't know about the service routing restart .
But once you have run those commands, were you able to access the GUI?

ya it came back up, and its snappy.
maybe i should make a task for it to do it every couple hours.