question about eth0 on debian

[kramerP]

i am probably not going to be very clear with this question so excuse my lack of clarity if it exists and feel free to ask questions if you dont know what im saying.

can anyone explain how debian (maybe more specifically gaim) handles an ethernet connection going down. like if i were on my mac os x system and i was signed into adium, fire, aim, etc and the internet connection failed for a few seconds adium would sign off but then would sign back on when the connection came back up. i'm not sure how debian handles a connection going down but i know even when i open up firefox right after i know the internet connection has gone down for a few seconds i have problems getting out to the internet. once i do

ifdown eth0

and then

ifup eth0

everything works okay. i am assuming there is some fundamental difference in the way this type of problem is handled on debian as opposed to os x or even win XP (i have a win XP box too where it comes back up with no user intervention).

anyone have any ideas about this?

thanks in advance.

k#

[oosterhouse]

I'm not sure exactly what you're asking but GAIM does have a plugin that's on it usually by default that reconnects you automatically.

[kramerP]

ignore my reference to gaim, i was using it to try to serve as an example (obviously not a good one ). anyways, my real issue arises from the fact that if my computer is configured to have a static ip i have explicity placed the gateway and mask the in /etc/network/interfaces so as long as my router is functioning i should be able to find the router and any packets sent to it would then be my routers responsibility to communicate with the modem and then out to the wwww. so if other computers on my home network can get out the internet i think i could make the assumption that my router is operating properly as well as the modem. so what i dont understand is why if the connection dropped for a short period of time, enough to cause gaim, adium, aim, or w/e to drop and disconnect from their respective servers, and the other computers on my network (1 running os x and 1 running win xp) are able to re-establish these connections and/or get out the internet via a web browser without me having to do anything why would debian require me to bring down and then bring back up my network interface in order to get out to the internet again?

maybe this is a rare occurrence or something, but this happening would lead me to the assumption that there is some difference in the way the OS is handling the network interfaces not finding an available network.

hopefully this clarifies what i am trying to say.

thanks again.

[oosterhouse]

Hmm..well I've never used debian and I've never had that problem so I doubt I can help you, I just thought you were talking about something else. Sorry.

[farslayer]

My box is plugged into a Broadband router. That keeps eth1 up all the time (if it goes down then the PC did to because the power in my house just went out.. ) The NAT router adds a later of security it also allows me to have multiple PC's connected to my Internet connection and I don't have to worry about momentary dropouts of the cable modem.

You can get Broadband routers for about $20.00 on sale these days. hardly makes sense not to have one.

[kramerP]

Thanks to those have replied but I'm not really looking for a solution to the problem.....having the system go offline really makes no difference to me, there are no critical functions housed on the box. What I was really looking for was almighty knowledge --> and an explanation of why the debian box might be doing what I had indicated.