I recently reinstalled R5F1 and am having an odd issue where the IP address with revert back to DHCP for no reason. I have set it through netcardconfig and still it reverts. When I go back through netcardconfig --force all the settings are right and the computer is set back to the proper settings.

Tonight I set the IP address through ifconfig and hopefully this will stick for much longer (read permanent).

Has anyone else experienced this problem and resolved it or could someone point me in the right direction to see what may be causing the IP address to revert to DHCP after setting it Statically.

_________________
Girkers

this happened to me yesterday. Took afew minutes figure out why the frontend couldnt find the backend.

I pinned the MAC address to the desire IP within the DHCP tables. Problem will never happen again.

_________________
R5F1 - Dell P4 2.4Ghz 500MB - PVR250 x 2 - GeForce FX 5200 - Onboard sound/NIC 80GB ATA/250GB ATA/400GB SATA

khrusher,

Thanks for the tip, but doesn't solve my problem.

My investigations have lead me to believe that I may be having a driver conflict and this could also be causing my problem with slow network access.

Looking through my log files I found a couple of logs that had changed since I have fixed my network issue yesterday and the first one I looked at, kern.log I found this message


Looking at this in itself does not explain the problem, but doing some research on this it does provide some insight. I found that my system is loading both the eepro100 and e100 driver which is the driver for my built in NIC.

My research on the eepro100 is that it can be a little buggy, so I then went it search of trying to remove this module or blacklist it and have the system then just load the e100 driver.

I found that eepro100 driver is already in /etc/modprobe.d/blacklist and I even added the line but alas the driver still loads.

Can someone please advise how I blacklist or even remove the eepro100 driver as I feel this is the root cause of my problems.

_________________
Girkers

Would unloading the module and physically renaming it stop it from loading?

Probably would the only problem is that rmmod eepro100 doesn't work and when I try to rename the directory /sys/bus/pci/drivers/eepro100 I get permission denied.

Next.

_________________
Girkers

You need to rename the .ko file in /lib/modules/2.6...

It should still let you rename it even if the module's loaded

mad_paddler,

I went in search of the driver (ko) file you mentioned but alas poor yorick it is not there. Here is the directory listing:

root@mythtv:/lib/modules/2.6.18-chw-13# ls -la
total 1436
drwxr-xr-x 10 root root 4096 Jul 20 19:14 .
drwxr-xr-x 3 root root 4096 Nov 30 2006 ..
drwxr-xr-x 2 root root 4096 Nov 30 2006 acx100
lrwxrwxrwx 1 root root 36 Jul 15 17:52 build -> /usr/src/linux-headers-2.6. 18-chw-13
drwxr-xr-x 2 root root 4096 Dec 14 2006 extra
drwxr-xr-x 11 root root 4096 Nov 30 2006 kernel
drwxr-xr-x 2 root root 4096 Nov 30 2006 linux-wlan-ng
drwxr-xr-x 2 root root 4096 Jul 15 17:57 misc
-rw-r--r-- 1 root root 296461 Jul 20 19:14 modules.alias
-rw-r--r-- 1 root root 69 Jul 20 19:14 modules.ccwmap
-rw-r--r-- 1 root root 329566 Jul 20 19:14 modules.dep
-rw-r--r-- 1 root root 813 Jul 20 19:14 modules.ieee1394map
-rw-r--r-- 1 root root 730 Jul 20 19:14 modules.inputmap
-rw-r--r-- 1 root root 32542 Jul 20 19:14 modules.isapnpmap
-rw-r--r-- 1 root root 74 Jul 20 19:14 modules.ofmap
-rw-r--r-- 1 root root 187741 Jul 20 19:14 modules.pcimap
-rw-r--r-- 1 root root 1051 Jul 20 19:14 modules.seriomap
-rw-r--r-- 1 root root 121612 Jul 20 19:14 modules.symbols
-rw-r--r-- 1 root root 411421 Jul 20 19:14 modules.usbmap
drwxr-xr-x 2 root root 4096 Jul 15 17:59 nvidia
drwxr-xr-x 2 root root 4096 Mar 6 17:15 pvrusb2
drwxr-xr-x 3 root root 4096 Dec 3 2006 updates

Any other thoughts?

_________________
Girkers

/lib/modules/2.6.18-chw-13/kernel/drivers/net/eepro.ko

Took less than a minute to find using locate.

This won't work. There is a file to change at /etc/network/interfaces. Edit this, and change dhcp to static. Read the man page for interfaces for details. This will be permanent: The system reads this file to determine what to do with the card.

The ip address shouldn't change anyway, if dhcp is set up correctly. Windows boxes are never set up to do this properly, if you're using one as a bridge. You can also usually configure your router, if this is what you use, to assign the mac address the same ip address each time.

Basically, if you're using a router, fix it up. If you're using Windows, edit the interfaces file for static ip address. If you do the latter, just be aware that a few devices may not allow you through if you aren't using dhcp (I've seen Windows do this), and all the settings (gateway, netmask, broadcast) should be written down before you go about moving to a static address, since they should be the same settings.

Good luck

Mike

_________________
*********************
LinHES 7.4
Australian Dragon
*********************

I just want to mention here that DHCP clients, by design, will request the last IP address (and other configuration parameters) that they had previously. This is dedfined in RFC-2131, which to my knowledge is still the definitive guide used by any TCP/IP implementation. From http://www.ietf.org/rfc/rfc2131.txt :
If your client requests parameters that are no longer available (another node has requested and been granted them) then your configuration will change.

I believe even the M$ OSes adhere to this RFC. If anyone has references to other specs for DHCP please post them, this is a strong interest of mine.

Gentlemen,

Thank you all for your wonderful suggestions.

tjc,

I didn't know the name of the file exactly so it made it a bit hard, obviously teaches me for overlooking the obvious. I have since renamed this file and have just now rebooted my KnoppMyth box...

and the results are in... (dmesg)


Looks like it is still loading.

I did check my /etc/network/interfaces file and it was correct and for some reason it still changed. It doesn't appear to have changed now for sometime, so a change I have made some time ago has obviously fixed the problem.

I would still like to know how to stop the eepro driver from loading. Any other tips.

_________________
Girkers

First, you don't need to change module names. Please change it back to it's proper name.

Second, the way to fix the issue is with modules.conf. You use modules.conf to remove/blacklist the one you don't want to use, then insert the proper module.

http://kbase.redhat.com/faq/FAQ_79_2521.shtm

Once you get that working, run depmod -ae once as root and reboot for good measure.