unraid not receiving IPv4 address, can't login to GUI.

[noweakness]

So unraid has really testing my patience out, and I know its my fault but dang. I plan on getting a separate hardware device to install pfsense, but in the meantime I thought I'd get a temporary setup to get a head start setting everything up. Well somehow I can't login to my unraid GUI. I'm guessing because pfsense doesn't load until unraid is fully loaded and has an IP, but it can't reach pfsense because its not loaded yet.

 

When I turn on my unraid machine, i get "IPv4 address: not set". I've deleted my config file from usb with no luck.

Here is a summary of my NICs.

 

Onboard NIC eth0 - Plugged into my ATT home router, also a wan port and connection to my old 192.168.1.XX network ( kept this connected for a backup, clearly this did not good)

Intel NIC port 4 - WAN port within pfsense

Intel NIC Port 1 & 2 - Unraid LAN bonding port with my new network 192.168.11.XX

 

Below is my network config file settings, I tried to add [GATEWAY[0]="192.168.1.254"] to the config file hoping my AT&T router could at least give it an IP. Needless to say I'm stressed and running out of options to log into unraid. I tried looking up commands for console to reset or refresh my network settings but couldn't find anything except "ifconfig eth0 up/down" which did nothing. I appreciate any suggestions. pfsense loads up after a reboot and I can access it, just can't log into my unraid server because it can't get an IP. 

 

# Generated settings:
IFNAME[0]="eth0"
DESCRIPTION[0]="Onboard NIC"
PROTOCOL[0]="ipv4"
USE_DHCP[0]="yes"
DHCP_KEEPRESOLV="no"
USE_DHCP6[0]="yes"
DHCP6_KEEPRESOLV="no"
IFNAME[1]="br1"
BONDNAME[1]="bond1"
BONDNICS[1]="eth1 eth2"
BONDING_MODE[1]="4"
BONDING_MIIMON[1]="100"
BRNAME[1]="br1"
BRNICS[1]="bond1"
BRSTP[1]="no"
BRFD[1]="0"
DESCRIPTION[1]="LAG LAN"
PROTOCOL[1]="ipv4"
USE_DHCP[1]="no"
IPADDR[1]="192.168.11.100"
NETMASK[1]="255.255.255.0"
GATEWAY[1]="192.168.11.98"
IFNAME[2]="eth3"
PROTOCOL[2]="ipv4"
SYSNICS="3"
 

[Trollski]

Have you set the array to autostart on boot?

 

I cant remeber which config it is in but I know that one has the setting to disable the autostart of the array if that helps?

[noweakness]

1 hour ago, Trollski said:

Have you set the array to autostart on boot?

 

I cant remeber which config it is in but I know that one has the setting to disable the autostart of the array if that helps?

I should be able to access unraid even if the array isn't started, right? But yes, it should be set to automatically run. 

[bonienl]

To make this work, you need to configure bonding for eth0 as well, and have eth0 as the only member.

 

[Trollski]

Yes the array just holds the VMS docker etc and the usb stick controls the system

[noweakness]

4 minutes ago, bonienl said:

To make this work, you need to configure bonding for eth0 as well, and have eth0 as the only member.

 

Oh interesting. Since Eth0 is my onboard NIC, I don't really need it. Can I just disable it within unraid or change it from Eth0 to something else from the config file or console? 

 

Also, any ideas how I can access my GUI?

 

I knew bonding would mess things up....smh. 

[bonienl]

eth0 is used to access the GUI.

If you don’t need the onboard NIC and have disabled it, you need tonupdate the network interface rules to make one of the other interfaces eth0. Actually you need to define the new eth0 and eth1 interfaces.

 

Delete the file network.cfg to start with a default config and make changes afterwards.

 

[noweakness]

6 hours ago, bonienl said:

eth0 is used to access the GUI.

If you don’t need the onboard NIC and have disabled it, you need tonupdate the network interface rules to make one of the other interfaces eth0. Actually you need to define the new eth0 and eth1 interfaces.

 

Delete the file network.cfg to start with a default config and make changes afterwards.

 

 I guess it was as simple as unplugging the other connections and just plugging into Eth0 (after deleting the config file) to get an IP address. I'll start working on that setup, appreciate the information for bonding. 

[noweakness]

Two more questions if I can.

 

1. If I'm running pfsense virtual on unraid, is there a particular setup I need for IP allocation? Will I need to create a static IP on unraid AND pfsense for the unraid server, or does it matter? I have a feeling if I reboot unraid with pfsense not loaded yet, it won't retrieve its IP and not let me log in again.

 

2. Can I run 2 separate networks to unraid without problems?

   Network 1 - Pfsense 192.168.11.XXX subnet (Main)/2 ports bonded (Eth0 + Eth1)

   Network 2 - ATT box 192.168.1.XXX subnet (Backup or guest wifi network)

 

I'm looking to purchase pfsense hardware, but for different setups, I'd like to know what options I have. Thanks in advance. 

[transparent]

On 1/26/2022 at 1:42 AM, noweakness said:

Two more questions if I can.

 

1. If I'm running pfsense virtual on unraid, is there a particular setup I need for IP allocation? Will I need to create a static IP on unraid AND pfsense for the unraid server, or does it matter? I have a feeling if I reboot unraid with pfsense not loaded yet, it won't retrieve its IP and not let me log in again.

 

2. Can I run 2 separate networks to unraid without problems?

   Network 1 - Pfsense 192.168.11.XXX subnet (Main)/2 ports bonded (Eth0 + Eth1)

   Network 2 - ATT box 192.168.1.XXX subnet (Backup or guest wifi network)

 

I'm looking to purchase pfsense hardware, but for different setups, I'd like to know what options I have. Thanks in advance. 

 

May I recommend this guide from SpaceInvader One. It has a few years on its back, but still holds up in many cases. 

 

 

Edited August 29, 2022 by transparent
Forgot part of the the name for SpaceInvader One