Re: Marvell 88E80856 switching from static to dhcp configuration all on its own
The Friday 18 July 2008 00:24:04 Andrew Sackville-West, you wrote :
> On Thu, Jul 17, 2008 at 02:30:42PM -0700, Freddy Freeloader wrote:
> > Andrew Sackville-West wrote:
> >> On Thu, Jul 17, 2008 at 01:36:43PM -0700, Freddy Freeloader wrote:
> >>> Andrew Sackville-West wrote:
> >>>> On Thu, Jul 17, 2008 at 11:14:25AM -0700, Freddy Freeloader wrote:
>
> [...]
>
> >>>>> I have two NICs. The onboard Marvell and a 3Com 3c905b. The
> >>>>> 3Com handles dhcp and dns requests. Both are configured for
> >>>>> statically configured IP addresses in /etc/network/interfaces.
> >>>>> However, the Marvell will, after some unknown amount of
> >>>>> time--less than 12 hours--drop its static IP address and
> >>>>> request a dhcp address from the 3Com adapter.
>
> [...]
>
> >>>> probably a killall dhclient will sort it out.
>
> [...]
>
> >>> [I] will give that a try and see if the behavior changes.
>
> [...]
>
> >> perhaps some other package is starting dhclient? Basically, if you
> >> have both interfaces using static ip, dhclient shouldn't even be
> >> started. care to post /etc/network/interfaces?
>
> [...]
>
> > For some reason dhclient WAS running, but I don't know why.
>
> if it reappears, try a `ps aux`, maybe there will be a clue there as
> to where it's coming from. And after a reboot, run
>
> watch grep dhclient /var/log/syslog
>
> or some equivalent and watch for it to show up.
>
> > You wouldn't happen to have any guesses on the second problem I listed
> > would you? :)
>
> nope, sorry.
>
> A
You could also look with a pstree or recompile dhclient with a getppid at the
beginning in order to see which process launch dhclient.
--
Thomas Preud'homme
Why debian : http://www.debian.org/intro/why_debian
Reply to: