Activating eth0 causes problems/delays in login... Why? And how to remediate?
 

Hi there,

I am a newbie and posted this question on the corresponding forum a few days ago. Unfortunately, the couple of replies i got did not help solving my problem. I hope i'll be luckier this time. :)

I successfully installed an ethernet card, hooked my workstation to a LAN, and accessed the internet through its firewall. The problem is the following. Activating eth0 results in incredebly long delays in password checks when performed from the current X session (about 60s), or a failure of the login procedure when performed from CTL-ALT-Fx consoles. Conversely, the behaviour of login procedures goes back to normal as soon as eth0 is deactivated.

Does anyone have any idea why? and how to remediate?

Could that relate at all to authentication control / kerberos / ldap / pam.d / ipchains? My intuition is that the fact that the network/eth0 is enabled results in a change in the way password check is performed.

Here are some details about my machine:
CPU: PIII i686 1GHz
NIC: Netgear FA311 (it works perfectly fine, i can http, ssh, etc.)
Distro/Linux: Redhat 7.1 / 2.4.9-12
Static IP: 192.168.0.181

Thx

Eric

It seems that you are submiting a request to get provided with an ip, are you provided an ip via a dhcp server or is it a static ip?

Sometime it can take quite a while to resolve, so it might not be your machine the problem but the time it takes your dhcp server to give away an address.
To test if it is the case, i would ping an ip that your are suspecting to be not used and than, if you don't have a reply, change your dynamic adressing to that particular static address.
Reboot and observe the time it takes to pass this step and obviously it will be quite fast.
If it is the case than it as nothing to do with your station.

[c0c0deuz] BTW I have a local, static IP
 

> It seems that you are submiting a request to get provided with an ip, are you provided an ip via a dhcp server or is it a static ip?

I use a static IP and access the internet through a LAN's firewall which itself also have a static IP (ADSL). The access to the internet is instantaneous and does not cause any problem. Same with ssh., ftp, etc. There is no problem at all accessing the net. My problem has nothing to do dhcp.

The problem is rather login to the host itself!! I can simply not login any more when eth0 is up (that's from the CTL-ALT-Fxs consoles); or a simple 'su -' from an xterm local to the X-sesion will take about 60s to go through once the password has been typed and <CR> pressed. :)

Eric :)

using static adress on a private network as nothing to do with logging in to your provider of service. This one uses a dhcp resolution to provide you with the service and i suspect that the service is crowded...
If your static address start with 10 172 192 they are private addresses your provider provides you with an public one.