Serving a wrong address.

[psihozefir]

Simon Hobson wrote:

> I don't think anything is wrong with your config, the server seems to
> be acting normally.
>
>
> Go back and check the cabling - make sure you really do have the
> networks connected as you describe, and the client is connected to
> the right one.

eth2 is the only network interface connected to a switch. I use eth3
to connect computers with a crossover cable, only when I need to. The
other clients (exept another one) get the right configuration. And I
can tell you that I'm sure of this.

Here is the output of the command tac /var/log/messages | grep dhcp |
grep '192.168.3'
Jul 28 07:54:35 zefir dhcpd: DHCPACK on 192.168.3.5 to
00:d0:b7:09:67:b0 (rambo) via eth2
Jul 28 07:54:35 zefir dhcpd: DHCPREQUEST for 192.168.3.5 from
00:d0:b7:09:67:b0 (rambo) via eth2
Jul 28 07:54:27 zefir dhcpd: DHCPACK on 192.168.3.5 to
00:d0:b7:09:67:b0 (rambo) via eth2
Jul 28 07:54:27 zefir dhcpd: DHCPREQUEST for 192.168.3.5 from
00:d0:b7:09:67:b0 (rambo) via eth2
Jul 28 07:54:24 zefir dhcpd: DHCPACK on 192.168.3.5 to
00:d0:b7:09:67:b0 (rambo) via eth2
Jul 28 07:54:24 zefir dhcpd: DHCPREQUEST for 192.168.3.5 from
00:d0:b7:09:67:b0 (rambo) via eth2
Jul 28 07:53:43 zefir dhcpd: DHCPACK on 192.168.3.5 to
00:d0:b7:09:67:b0 (rambo) via eth2
Jul 28 07:53:43 zefir dhcpd: DHCPREQUEST for 192.168.3.5 from
00:d0:b7:09:67:b0 (rambo) via eth2
Jul 28 07:53:35 zefir dhcpd: DHCPACK on 192.168.3.5 to
00:d0:b7:09:67:b0 (rambo) via eth2
Jul 28 07:53:35 zefir dhcpd: DHCPREQUEST for 192.168.3.5 from
00:d0:b7:09:67:b0 (rambo) via eth2
Jul 28 07:44:48 zefir dhcpd: DHCPACK on 192.168.3.5 to
00:d0:b7:09:67:b0 (rambo) via eth3
Jul 28 07:44:48 zefir dhcpd: DHCPREQUEST for 192.168.3.5 from
00:d0:b7:09:67:b0 (rambo) via eth3
Jul 28 07:39:48 zefir dhcpd: DHCPACK on 192.168.3.5 to
00:d0:b7:09:67:b0 (rambo) via eth3
Jul 28 07:39:48 zefir dhcpd: DHCPREQUEST for 192.168.3.5 from
00:d0:b7:09:67:b0 (rambo) via eth3
Jul 28 07:37:23 zefir dhcpd: DHCPACK on 192.168.3.3 to
00:0b:db:de:42:55 (littlemammoth) via eth3
Jul 28 07:37:23 zefir dhcpd: DHCPREQUEST for 192.168.3.3 from
00:0b:db:de:42:55 (littlemammoth) via eth3
Jul 28 07:34:48 zefir dhcpd: DHCPACK on 192.168.3.5 to
00:d0:b7:09:67:b0 (rambo) via eth3
Jul 28 07:34:48 zefir dhcpd: DHCPREQUEST for 192.168.3.5 from
00:d0:b7:09:67:b0 (rambo) via eth3
Jul 28 07:32:23 zefir dhcpd: DHCPACK on 192.168.3.3 to
00:0b:db:de:42:55 (littlemammoth) via eth3
Jul 28 07:32:23 zefir dhcpd: DHCPREQUEST for 192.168.3.3 from
00:0b:db:de:42:55 (littlemammoth) via eth3
Jul 28 07:29:48 zefir dhcpd: DHCPACK on 192.168.3.5 to
00:d0:b7:09:67:b0 (rambo) via eth3
Jul 28 07:29:48 zefir dhcpd: DHCPREQUEST for 192.168.3.5 from
00:d0:b7:09:67:b0 (rambo) via eth3
Jul 28 07:27:24 zefir dhcpd: DHCPACK on 192.168.3.3 to
00:0b:db:de:42:55 (littlemammoth) via eth3
Jul 28 07:27:24 zefir dhcpd: DHCPREQUEST for 192.168.3.3 (192.168.3.1)
from 00:0b:db:de:42:55 (littlemammoth) via eth3
Jul 28 07:27:24 zefir dhcpd: DHCPOFFER on 192.168.3.3 to
00:0b:db:de:42:55 (littlemammoth) via eth3

I was running linux-2.6.17.1 until 7:54. Now I upgraded to
linux-2.6.17.4. The station was shuted down after 7:54. Now I wait to
see if it gets the right address. As you can see there are two
stations: 192.168.3.3 and 192.168.3.5, both connected via eth2. This
server is my personal computer and I know all about it. It's right
near me when I'm awake and when I sleep.