You are not logged in.
Last night, our local router siezed up and had to be rebooted. When we brought the router back up, the network card in our proxy server(SuSE Linux) failed to link back up. I was asked to look into the situation and see what kind of sollutions I could come up with. Does any one have any suggestions. I've seen ifplugd and it seems to be what we need, but does anyone have any experience working with this or any other suggested sollutions? This is our first experience with a linux server in a production environment. Also..just a note, the server runs SuSE linux because the admins that I work with like the sescurity of a support contract(understandably so).
Thanks
Offline
So ask suse or the admins. Learn yast and yast2.
Frumpus ♥ addict
[mu'.krum.pus], [frum.pus]
Offline
ifplugd works fine for me, but I don't know how it'd work with the cable remaining connected and the router going off then on - I use it on a laptop where I unplug the cable and plug it back in...
Offline
Wouldn't the system assume that the cable was uplugged? It will no longer be linking up to anything, so whats the difference between that and simply unplugging the cable?
Offline
Wouldn't the system assume that the cable was uplugged? It will no longer be linking up to anything, so whats the difference between that and simply unplugging the cable?
dunno... I was just covering all the bases... I'm not sure how much of a "link down" ifplugd needs to reconnect... hitting a "reset" button might cause it to not relink... I dunno
Best to just try it out on a desktop of your own (run ifplgud, shut the router off, restart... checking pings and whatnot the whole time)
Offline
I'll try to get ahold of a router or switch to test with. The server is a production server and rather than just a router, its our core switch. I'll do some more research on ifplugd and report back what I come up with.
Offline