Weird DHCPREQUEST to 192.168.0.1 even if it doesn't exist
Hello,
I have really weird problem with my dhcpclient.
I've found in my log this:
Nov 8 04:38:03 sheril dhclient: DHCPREQUEST on eth0 to 192.168.88.1 port 67
Nov 8 04:38:03 sheril dhclient: DHCPACK from 192.168.88.1
Nov 8 04:38:03 sheril dhclient: bound to 192.168.88.88 -- renewal in
10674 seconds.
Nov 8 04:38:21 sheril dhclient: DHCPREQUEST on eth0 to 192.168.0.1 port 67
And my ip address was 192.168.0.75 and it's not really my ip address. As
you can see I use 192.168.88.x.
This happens independently where I'm connected in.
In my dhcp server's log is this:
Nov 8 04:37:43 shilaka dhcpd: DHCPREQUEST for 192.168.88.88 from
00:1a:92:e4:f2:d7 via eth1
Nov 8 04:37:43 shilaka dhcpd: DHCPACK on 192.168.88.88 to
00:1a:92:e4:f2:d7 via eth1
Nov 8 04:37:56 shilaka nfsd[8392]: fd cache inconsistency!
Nov 8 04:37:56 shilaka last message repeated 2 times
Nov 8 04:38:01 shilaka dhcpd: DHCPREQUEST for 192.168.0.75 from
00:1a:92:e4:f2:d7 via eth1: unknown lease 192.168.0.75.
Nov 8 04:38:19 shilaka dhcpd: DHCPREQUEST for 192.168.0.75 from
00:1a:92:e4:f2:d7 via eth1: unknown lease 192.168.0.75.
Nov 8 04:38:53 shilaka last message repeated 2 times
Also my dns servers were set up to:
search mshome.net
nameserver 192.168.0.75
I tried to search 192.168.0 in /etc where it should be set, but not
successfully.
I really don't know what happend and why there is request to 192.168.0.1
if it doesn't exist even.
If anyone have a clue what it's going on here, please let me know. Thank
you very much.
Dal
P.S.:
I have avahi daemon installed because of my debian wants it :) I suspect
it a little, but I don't really know.
Reply to: