Alright, I'll give that a shot here after I finish lunch and respond back with my findings.

 

@Hoopster @Squid @trurl Thank you all so much for your help, I really appreciate it!

 

Alright, got back, installed the card, and it fired right up! So it seems like not having the drivers for the Bigfoot Killer network chip was the issue.

 

Thank you all again for you help, I'm really excited to start using this.

I would also post a feature req for LT to add in the appropriate drivers to unRaid

Sure. Is that done through Unraid, or how would I do that?

https://forums.unraid.net/forum/53-feature-requests/

1 hour ago, Arcaeus said:

Alright, got back, installed the card, and it fired right up! So it seems like not having the drivers for the Bigfoot Killer network chip was the issue.

Glad to hear it is working now.  It is a rarity to find a NIC not supported by unRAID.  Good thing @Squid suspected this might be the case and pointed you in the right direction.

I seem to having the same exact problem too. ipv4 / ipv6 adress not set. I will follow your advices

 

 

Edited October 3, 20196 yr by Stream Arcanine

hi folks, I am having the same issue, ipv4 not set, when I loook into the config folder, what file am I to look for, is it the network.cfg as below

 

 

# Generated settings:
IFNAME[0]=""
DHCP_KEEPRESOLV="no"
DHCP6_KEEPRESOLV="no"
BONDNICS[0]="eth0 eth1 eth2 eth3"
BONDING_MODE[0]="1"
BONDING_MIIMON[0]="100"
BRNICS[0]="bond0"
BRSTP[0]="0"
BRFD[0]="0"
USE_DHCP[0]="yes"
IFNAME[1]="eth3"
PROTOCOL[1]="ipv4"
USE_DHCP[1]="no"
IPADDR[1]="19*.***.***.***"
NETMASK[1]="255.255.255.0"
GATEWAY[1]="192.168.123.123"
MTU[1]="9000"
SYSNICS="2"

 

 

7 hours ago, Dudedawg said:

hi folks, I am having the same issue, ipv4 not set, when I loook into the config folder, what file am I to look for, is it the network.cfg as below

 

 

# Generated settings:
IFNAME[0]=""
DHCP_KEEPRESOLV="no"
DHCP6_KEEPRESOLV="no"
BONDNICS[0]="eth0 eth1 eth2 eth3"
BONDING_MODE[0]="1"
BONDING_MIIMON[0]="100"
BRNICS[0]="bond0"
BRSTP[0]="0"
BRFD[0]="0"
USE_DHCP[0]="yes"
IFNAME[1]="eth3"
PROTOCOL[1]="ipv4"
USE_DHCP[1]="no"
IPADDR[1]="19*.***.***.***"
NETMASK[1]="255.255.255.0"
GATEWAY[1]="192.168.123.123"
MTU[1]="9000"
SYSNICS="2"

 

 

That is pretty far away from the default network.cfg. Try renaming it and reboot so the default can be regenerated, then go from there.

On 11/19/2019 at 9:05 AM, trurl said:

That is pretty far away from the default network.cfg. Try renaming it and reboot so the default can be regenerated, then go from there.

thank you so much, it worked like a charm

 

 

Just upgraded from 6.8.0 nvidia to 6.8.2 nvidia.

 

It seems this update changed my network settings and re-enabled bonding (which i am not using)

turning off bonding in the network settings for eth0 fixed my issue.

Hope this helps. Anyone know why this might have happened?

3 hours ago, IMI4tth3w said:

Anyone know why this might have happened?

If it can't read config/network.cfg on Flash it will give you default settings. 

I'm having the same issue.... Could someone provide assistance?  I've tried the steps in the earlier posts (deleting config file, turning off bonding, etc).

pandora-diagnostics-20200719-0507.zip

3 hours ago, kenny_pacheco said:

I'm having the same issue.

No link on the NIC:

 

Link detected: no

 

I got same issue, br0 not getting IP after boot, but not always. maybe some timeout is stopping us from getting IP?