LinuxQuestions.org
Latest LQ Deal: Latest LQ Deals
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Security
User Name
Password
Linux - Security This forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.

Notices


Reply
  Search this Thread
Old 10-13-2010, 03:11 PM   #1
sarajevo
Member
 
Registered: Apr 2005
Distribution: Debian, OpenBSD,Fedora,RedHat
Posts: 228
Blog Entries: 1

Rep: Reputation: 31
strange dhclient requests from server


Hi all,

I have router connected to public ip address eg. ggg.sss.ccc.fff on eth0 interface.

On eth1 interface is address eg 192.168.1.20/24 and all hosts inside have some of address.

In logs I can see

dhclient: DHCPREQUEST on eth0 to 192.168.1.196 port 67

I do not have above address at all. eth0 is external interface with public ip address.

I can block with iptables, dhclient to send these requests but I am wondering what is initiate such messages.

OS is centos 5.5, minimal installation

Comments are welcome, thanks in advance,
 
Old 10-14-2010, 07:48 AM   #2
michaelk
Moderator
 
Registered: Aug 2002
Posts: 25,699

Rep: Reputation: 5895Reputation: 5895Reputation: 5895Reputation: 5895Reputation: 5895Reputation: 5895Reputation: 5895Reputation: 5895Reputation: 5895Reputation: 5895Reputation: 5895
Check your DHCPARGS. Is it configured for eth0?
 
Old 10-14-2010, 10:12 AM   #3
zhaozhou
LQ Newbie
 
Registered: Oct 2009
Location: Sweden
Distribution: Gentoo
Posts: 23

Rep: Reputation: 1
DHCPREQUEST is a broadcast.
 
Old 10-14-2010, 11:29 AM   #4
Noway2
Senior Member
 
Registered: Jul 2007
Distribution: Gentoo
Posts: 2,125

Rep: Reputation: 781Reputation: 781Reputation: 781Reputation: 781Reputation: 781Reputation: 781Reputation: 781
If eth0 is your public facing interface, do you have port 67 enabled (e.g. DHCP server bound to this interface without a firewall)?
It looks to me like it is either a mis-configuration that causes the DHCP to log as eth0 or some form of spoofed IP address to find a vulnerability in your (public facing?) DHCP server; possibly someone has this IP behind a router with NAT and tried connecting to your DHCP server and this is what showed up in the logs.

What is interesting is that the address (192.168.1.196) only works on a LAN and you are seeing this on a public NIC, which makes me think that it is a device behind a router, identifying itself as 192.168.1.196.
 
Old 10-14-2010, 01:25 PM   #5
sarajevo
Member
 
Registered: Apr 2005
Distribution: Debian, OpenBSD,Fedora,RedHat
Posts: 228

Original Poster
Blog Entries: 1

Rep: Reputation: 31
Quote:
Originally Posted by michaelk View Post
Check your DHCPARGS. Is it configured for eth0?
Thansk for reply, where to check this ? I cannot find above string in .conf files.
 
Old 10-14-2010, 01:49 PM   #6
sarajevo
Member
 
Registered: Apr 2005
Distribution: Debian, OpenBSD,Fedora,RedHat
Posts: 228

Original Poster
Blog Entries: 1

Rep: Reputation: 31
Quote:
Originally Posted by Noway2 View Post
If eth0 is your public facing interface, do you have port 67 enabled (e.g. DHCP server bound to this interface without a firewall)?
It looks to me like it is either a mis-configuration that causes the DHCP to log as eth0 or some form of spoofed IP address to find a vulnerability in your (public facing?) DHCP server; possibly someone has this IP behind a router with NAT and tried connecting to your DHCP server and this is what showed up in the logs.

What is interesting is that the address (192.168.1.196) only works on a LAN and you are seeing this on a public NIC, which makes me think that it is a device behind a router, identifying itself as 192.168.1.196.

Yes, I am getting static address from my ISP over dhcp protcol, so they sent me public ip I use over dhcp over eth0, but ISPs dhcp server I am getting address from is not in private set of ip addresses, it is also public address.

I had to change my eth0 MAC address to one ISP accept ( I have some router they gave me, but I do not use it, only its MAC address )

The address 192.168.1.196 is not used by any host in private network.

What here confuses me is, I am seeing in logs

dhclient: DHCPREQUEST on eth0 to 192.168.1.196 port 67

what is same as in case I run
dhclient eth0, except it send then request to 255.255.255.255 ( broadcast as some of you wrote ).

I am curious to find out what from this box initiate above dhclient request

Comments are welcome and thank you in advance,
 
Old 10-15-2010, 04:33 AM   #7
Noway2
Senior Member
 
Registered: Jul 2007
Distribution: Gentoo
Posts: 2,125

Rep: Reputation: 781Reputation: 781Reputation: 781Reputation: 781Reputation: 781Reputation: 781Reputation: 781
What does the entire transaction chain look like? For example, here is one from my DHCP server:
Code:
Oct 14 15:53:32 server dhcpd: DHCPDISCOVER from 30:7c:30:fc:98:75 (BLACKBERRY-5D92) via br0
Oct 14 15:53:33 server dhcpd: DHCPOFFER on 192.168.0.23 to 30:7c:30:fc:98:75 (BLACKBERRY-5D92) via br0
Oct 14 15:53:33 server dhcpd: DHCPREQUEST for 192.168.0.23 (192.168.0.49) from 30:7c:30:fc:98:75 (BLACKBERRY-5D92) via br0
Oct 14 15:53:33 server dhcpd: DHCPACK on 192.168.0.23 to 30:7c:30:fc:98:75 (BLACKBERRY-5D92) via br0
In this case, it is correctly identifying the interface (br0), it provides the involved IP addresses, the MAC addresses and shows the chain of the events. Does this 192.168.1.196, in your case, get an IP or does it get a reject / error code of any sort?
 
Old 10-15-2010, 03:02 PM   #8
sarajevo
Member
 
Registered: Apr 2005
Distribution: Debian, OpenBSD,Fedora,RedHat
Posts: 228

Original Poster
Blog Entries: 1

Rep: Reputation: 31
I think I found out that wierd address

less /var/lib/dhclient/dhcliet.leases

lease {
interface "eth0";
fixed-address PUBLIC_IP;
option subnet-mask 255.255.255.0;
option dhcp-lease-time 86400;
option routers PUBLIC_IP;
option dhcp-message-type 5;
option dhcp-server-identifier 192.168.1.196;---it is here
option domain-name-servers PUBLIC-IP1,PUBLCI_IP2;
option ntp-servers PUBLIC_IP;
option domain-name "domain.com";
renew 5 2010/10/15 15:42:19;
rebind 6 2010/10/16 02:13:24;
expire 6 2010/10/16 05:13:24;
}

so based on this, it looks like my ISP use 192.168.1.196 as option when provide address back to me.

Last edited by sarajevo; 10-15-2010 at 03:30 PM.
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Strange ARP behavior : A linux server responds to all ARP requests Hdvd21 Linux - Networking 4 10-24-2013 05:02 AM
Would like to forward requests received on Server in one subnet to server on another scheidel21 Linux - Networking 3 08-16-2009 09:20 AM
dhcp server - can't figure out dhclient.conf for eth1 JoeBleaux Debian 1 04-06-2009 05:13 PM
Squid Server forwarding requests matrix_aash Linux - Newbie 4 03-20-2009 01:15 PM
Allow page requests from a given server txtoolman Linux - Software 5 06-21-2006 08:55 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Security

All times are GMT -5. The time now is 10:57 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration