[BlueOnyx:11562] Re: Network interface problem

[Jeff Folk]

Still having these issues with swatch emails, what's worse, my server lost communication with my ISP gateway and these problems are keeping swatch from reporting the issue. I had to restart the box to regain connectivity to the outside world as restarting network services had no positive effect.

In addition, the TCP system settings in the GUI report the wrong MAC address for the secondary interface. Reported in GUI as 00:13:72:D1:78:A1 (the dead 5150), when ifconfig reports 00:19:B9:0A:D8:8C (the present GX620).

Please, PLEASE. . . How can I sort this out?

Regards;
Jeff

On Oct 4, 2012, at 3:34 PM, Jeff Folk wrote:

> Had a hardware failure last night… My trusty, dusty Dimension 5150 finally croaked. So, to get my hobby server up again, I swapped the drives into a spare Optiplex GX 620. Booted with no problems, or so I thought…
> 
> I get an admin mail stating that eth1 is down (eth1 is my on-board nic, set to local IP). When I look at my active interfaces, I have loop,  eth0 (3com pci card, public IP) and a p2p1 which is down. Defined interfaces are eth0, eth1, and loop.
> 
> Also getting swatch emails stating:
> 
> /usr/sausalito/swatch/bin/am_network.sh: line 64: [: too many arguments
> 
> Google states that there has been a change in hardware naming, and I guess I'm getting caught in changing hardware after OS install. They suggest adding a line to grub.conf (biosdevname=0).
> 
> Will this set me straight? What are the suggestions of the group? At the moment this only kills my nightly ftp backup to my other server over LAN, which I would really like to get back…