By "losing its interface", do you just mean that it gets the "wrong" IP address assigned? Or do you mean it sometimes does not get any IP address assigned? You seem to be saying the first, but I would not call that "losing its interface", so I want to be sure I understand you. Assuming I'm reading you correctly ...

Typically, if a pair of systems are (nearly) always on and can communicate with each other, and one gets a DHCP address assignment from the other, the address will remain the same for a long time (I'm tempted to say "forever", but I only know by observation that it is true for months). A host that needs to renew a lease will try to get the same address, and a DHCP server will normally (unless you deliberately configure it differently, as some ISPs now seem to do) try to oblige. But when you change to a new DHCP server (e.g., when you move from Eigerstein to Bering on your router), the new DHCP server lacks the lease history that keeps everything stable.

All this is a guess, of course; you don't even actually say that the LEAF router is doing DHCP assignment.

If you need to force a particular IP address for this host (as you probably do, since it is apparently a port-forwarded server), you can either assign its address statically at its end (probably in /etc/network/interfaces, but since I don't run Red Hat, that's only a guess) or modify the DHCP server's config file (/etc/dhcp.conf) to assign the address via MAC-address association. If you go with the DHCP option, you might also want to extend the lease life (I don't recall what Bering does here, but often DHCP servers out of the box are set up to renew leases every 10 minutes or so).

At 07:11 AM 11/22/02 -0800, Gary St wrote:

Hello everyone.
I'm running Bering version 1.0-stable with and RedHat
7.1 mail/web server behind it. I was running
Eigerstein for about a year without a problem, but
with Bering, the RedHat server is losing it's
interface (the IP address). Any ideas?
I could just write a script to test it and bring it
back up, but I'd rather get to the heart of the
problem.
With EigerStein the RH server had an IP address of
192.168.1.5 and with Bering it gets 192.168.1.1. I
might have hard coded 192.168.1.5 in somewhere, but I
haven't found it yet.



--
-------------------------------------------"Never tell me the odds!"--------
Ray Olszewski					-- Han Solo
Palo Alto, California, USA			  [EMAIL PROTECTED]
-------------------------------------------------------------------------------



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
------------------------------------------------------------------------
leaf-user mailing list: [EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user
SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html

Reply via email to