loss of network connectivity after reboot-Ron

[jamie17]

Ron,

My VBA is only a few days old and after shutting it down I lost network connectivity over an ethernet line. I checked the line, etc and then powered down everything and that didnt help. The VBA is not showing as a connected device in the router.

I found in the forum your reply to FRJimT3 and it appears I have a nearly identical problem. I jumped ahead and logged in using a monitor and usb keyboard. Per your instructions*I typed in

ifconfig eth0

Response:

link encap: ethernet HWaddr 6c:62:6D7:57:3A

UP BROADCAST MULTICAST MTU:1500 Metric:1

RX packets: 0 errors:0 dropped:0 overruns: 0 frame:0

TX packets: 0 errors:0 dropped:0 overruns: 0 carrier:0

** collisions:0 txqueuelen:1000

RX bytes:0 (0.0 b) TX bytes:0 (0.0b)

Interrupt: 42 Base Address:0x2000

Then I typed in

cat /etc/sysconfig/network-scripts/ifcfg-eth0

Response:

#Created by Vortexbox web admin on 07/29/2011 10:53:00 am

DEVICE=eth0

HWADDR="6C:62:6D7:57:3A"

BOOTPROTO=dhcp

ONBOOT=yes

NM_CONTROLLED=yes

Please advise what is happening and what to do to reconnect. I dont understand any of the above.

Jamie?

[Ron Olsen]

Your ifcfg-eth0 file is correct, but your VB is not connected to your network.

What happens if you enter

ifup eth0

This command should start your network interface. Please post the output from this command.

Check if the network has come up by

ifconfig eth0

and see if there is a line starting with "inet addr:" that contains the VB IP address.

I keep my VBA running 24x7 to avoid unnecessary reboots and problems like this.

[jamie17]

Thanks Ron

In response to ifup etho

Response: Determining IP information for etho..failed; no link present. Check Cable

*

I not only checked the cable, I temporarily put a new cable in. That didnt help.

In response to ifconfig eth0 I got the same response as above.

Now what?*

[jamie17]

In response to your suggestion about running the VBA 24/7, I can do that but shouldnt it be able to power down and up without problems?

[Ron Olsen]

jamie17 said:


In response to your suggestion about running the VBA 24/7, I can do that but shouldnt it be able to power down and up without problems?


Depends how you power down. *Do it from software for the best results, or press and release the power button on the VBA; do not hold the power button down.

Even though power down/power up should be foolproof, many posts on this forum show that it causes problems for some users. *I always shutdown/reboot my VBA from software, and never use the power button. *I also have set up my VBA with a static IP address. *This has worked very well for me.

[Ron Olsen]

jamie17 said:


Thanks Ron

In response to ifup etho

Response: Determining IP information for etho..failed; no link present. Check Cable


Sounds as if your network interface hardware is not in a sane state.

Try shutting down your VBA, then remove the power plug for 30 seconds.

Completely removing power sometimes fixes hardware glitches. Then plug the power cord back in and reboot. *See if that helps.


I not only checked the cable, I temporarily put a new cable in. That didnt help.

In response to ifconfig eth0 I got the same response as above.

Now what?*


See above. *If your still having problems, see*How To Fix Weird Networking Problems*for other things to try.

[jamie17]

I held the power button down. Maybe that was the problem. I did that because that* is the normal way to do it on my computer. I made sure the VBA wasnt doing anything. I had not ripped a CD in over 20 minutes and the disk drive (orange) light was not on.* Whenever I tried the momentary push it seemed like nothing happened. I guess software is the safetest method. Its a little scary powering down when headless.

[jamie17]

Ron,

I had already powered it down and unplugged following the procedure on the Wiki but that didnt help.

Will try again now but how to power down using software when I cannot connect? Is there a lynux command to power down from the keyboard?

[Ron Olsen]

jamie17 said:


I held the power button down. Maybe that was the problem. I did that because that* is the normal way to do it on my computer. I made sure the VBA wasnt doing anything. I had not ripped a CD in over 20 minutes and the disk drive (orange) light was not on.* Whenever I tried the momentary push it seemed like nothing happened. I guess software is the safetest method. Its a little scary powering down when headless.


The momentary push initiates a soft shutdown, which can take a minute or more to complete. *You can also shutdown/reboot using the buttons on the VB GUI System Configuration page, or from the command line via the shutdown or reboot commands.

[jamie17]

Ron,

I shut it down. Unplugged. Waited 1 minute. Powered up. Ran same command and got same response.

Do you think this could be defective hardware?

Jamie