Networking
cancel
Showing results for 
Search instead for 
Did you mean: 

1000BASE-ST ETHERNET will not connect after a re-boot

SOLVED
Go to solution

1000BASE-ST ETHERNET will not connect after a re-boot

Hi network people,

I have a new rp4440 with a 1000NASE-ST (copper)
for lan interface. good OS running good but every time i re-boot the system, the boot completes but the lan0 will not connect. The only way to get the network to talk is to unplug the copper from the card and plug it back in at which time the network responds.
until that happens i cannot ping the local gate way.
nslookup is good. netsonf is good as is all other configs i can think of.
any help on this ?

jim
Few men know where they are going
5 REPLIES
Michael Steele_2
Honored Contributor
Solution

Re: 1000BASE-ST ETHERNET will not connect after a re-boot

What's in your /etc/rc.config.d/netconf file?

INTERFACE_NAME[0]="lan2"
IP_ADDRESS[0]="192.72.16.20"
SUBNET_MASK[0]="255.255.0.0"
BROADCAST_ADDRESS[0]=""
INTERFACE_STATE[0]=""
DHCP_ENABLE[0]=0

????
Support Fatherhood - Stop Family Law

Re: 1000BASE-ST ETHERNET will not connect after a re-boot

attached is the netconf

thanks
Few men know where they are going
Viktor Balogh
Honored Contributor

Re: 1000BASE-ST ETHERNET will not connect after a re-boot

your netconf is corrupt. lan0 and lan1 are defined with the same IP address?

...
INTERFACE_NAME[0]=lan0
IP_ADDRESS[0]=172.16.3.70
SUBNET_MASK[0]=255.255.255.0
BROADCAST_ADDRESS[0]=172.16.3.255
INTERFACE_STATE[0]=up
DHCP_ENABLE[0]=0
INTERFACE_MODULES[0]=""
...
...
...
INTERFACE_NAME[1]=lan1
IP_ADDRESS[1]=172.16.3.70
SUBNET_MASK[1]=255.255.255.0
BROADCAST_ADDRESS[1]=172.16.3.255
INTERFACE_STATE[1]=down
DHCP_ENABLE[1]=0
****
Unix operates with beer.
Michael Steele_2
Honored Contributor

Re: 1000BASE-ST ETHERNET will not connect after a re-boot

don't forget to assign points
Support Fatherhood - Stop Family Law

Re: 1000BASE-ST ETHERNET will not connect after a re-boot

thanks to all. The netconf file had both lan0
and lan1 assigned an the same ip. However the lan1 was not enabled. I saw this but i was counting on the fact that if an interface is not enabled it is also not configured. In any case, i commented out lan1 and that did the fix

thanks
jim
Few men know where they are going