Jump to content
Sign in to follow this  
Zonediver

[SOLVED] Changed Mainboard - now inet-connection not working

15 posts in this topic Last Reply

Recommended Posts

Hi folks,

again a network problem i didnt understand.

I am not able to reach the inet over the new onboard Broadcom-NIC.

All PCs are in the same Network and reachable except the router (192.168.2.253) and i cant ping unraid from the router-console.

Before i changed the Board, i deleted the network.cfg and network-rules.cfg

When i do a ping to www.google.at over the console it resolves the ip but i have 100% paket-loss...

I did all changes over the web-interface under settings, Network-Settings.

What the heck is going on here???

Is there a "special trick" to reconfigure the LAN or are the Network-Settings broken at v6.8.2?

 

This is the network.cfg:

# Generated settings:
IFNAME[0]="eth0"
DESCRIPTION[0]="Broadcom-1000Mbit"
PROTOCOL[0]="ipv4"
USE_DHCP[0]="no"
IPADDR[0]="192.168.2.250"
NETMASK[0]="255.255.255.0"
GATEWAY[0]="192.168.2.253"
DNS_SERVER1="1.1.1.1"
DNS_SERVER2="8.8.8.8"
DHCP_KEEPRESOLV="yes"
USE_DHCP6[0]="no"
IFNAME[1]="eth1"
DESCRIPTION[1]="ASUS-10Gbit"
PROTOCOL[1]="ipv4"
USE_DHCP[1]="no"
IPADDR[1]="10.10.10.250"
NETMASK[1]="255.255.255.0"
SYSNICS="2"

Maybe someone can help - Thanks a lot

 

unraid-diagnostics-20200212-2241.zip

Edited by Zonediver

Share this post


Link to post

Ok - next weird thing: I reconfigured the network again and now the process doesn't finish... 😡

Can someone explain what's going on here?

Is there a procedure to configure the LAN over the console?

Edited by Zonediver

Share this post


Link to post

Your original network configuration is okay and interfaces started up correctly.

 

About 10 minutes later something seems to reconfigure eth0.

 

Start your system in safe mode and test if any plugin was interfering.

Share this post


Link to post
4 minutes ago, bonienl said:

Your original network configuration is okay and interfaces started up correctly.

 

About 10 minutes later something seems to reconfigure eth0.

 

Start your system in safe mode and test if any plugin was interfering.

Thanks bonienl - thanks for your help - strange... ok, will test it.

Edited by Zonediver

Share this post


Link to post
6 minutes ago, bonienl said:

Your original network configuration is okay and interfaces started up correctly.

 

About 10 minutes later something seems to reconfigure eth0.

 

Start your system in safe mode and test if any plugin was interfering.

So - did a reboot in safe mode but still cant ping the router under 192.168.2.253 - all other devices are reachable - all are connected at the same LAN-segment 192.168.2.x... what can i do next?

Share this post


Link to post
5 minutes ago, bonienl said:

Can you post diagnostics are the reboot in safe mode

I am not sure, if i understand. I boot in safe mode and then take the diagnostics again?

I remember, i had a simmilar problem with the old board and the onboard realtek NIC - i was never able to get a inet connection...

 

Edited by Zonediver

Share this post


Link to post

Ok. I’ll have a look later.

Going to bed, it’s 1:30am and need sleep

Share this post


Link to post
13 minutes ago, bonienl said:

Ok. I’ll have a look later.

Going to bed, it’s 1:30am and need sleep

Yep - its late - thanks for your help and a good night 👍

Share this post


Link to post
1 hour ago, bonienl said:

Ok. I’ll have a look later.

Going to bed, it’s 1:30am and need sleep

FYI: I did a test and changed the ip from 192.168.2.250 to 192.168.2.150 and guess what - it works!!!

So is there a restriction if the NIC is changed to not use the "old" ip?

This seems strange because why? Should not be... or is there somewhere a misconfig under the hood?

Edited by Zonediver

Share this post


Link to post
5 hours ago, Zonediver said:

or is there somewhere a misconfig under the hood?

Difficult to say, the log shows a correct assignment

Share this post


Link to post
5 hours ago, bonienl said:

Difficult to say, the log shows a correct assignment

Did a new test and gave my PC the ip 192.168.2.250 - no connection to the router...

So its not an unraid-problem, its an IPFire-problem...

 

EDIT: Found the problem...

The ARP-Cache from the linux-router needs to be flushed, then it works and the ip 250 is usable again 👍

Edited by Zonediver

Share this post


Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this