Koozali.org: home of the SME Server

dhcp problem

CooLCaT1975

dhcp problem
« on: December 30, 2005, 12:37:53 PM »
i found following logfile entry when using dhcp with mac identification:

Dec 28 02:11:42 gateway dhcpcd[4195]: broadcasting DHCP_REQUEST for 213.47.6.207
Dec 28 02:11:42 gateway dhcpcd[4195]: dns option is missing in DHCP server response. Assuming 195.34.134.99
Dec 28 02:11:42 gateway dhcpcd[4195]: subnetMask option is missing in DHCP server response. Assuming 255.0.0.0
Dec 28 02:11:42 gateway dhcpcd[4195]: broadcastAddr option is missing in DHCP server response. Assuming 0.255.255.255
Dec 28 02:11:42 gateway dhcpcd[4195]: dhcpIPaddrLeaseTime option is missing in DHCP server response. Assuming 4294967295 sec
Dec 28 02:11:42 gateway dhcpcd[4195]: dhcpT1value option is missing in DHCP server response. Assuming 2147483647 sec
Dec 28 02:11:42 gateway dhcpcd[4195]: dhcpT2value option is missing in DHCP server response. Assuming 3758096383 sec
Dec 28 02:11:42 gateway dhcpcd[4195]: DHCP_NAK server response received
Dec 28 02:11:42 gateway dhcpcd[4195]: broadcasting DHCP_DISCOVER
Dec 28 02:11:42 gateway dhcpcd[4195]: dhcpT1value option is missing in DHCP server response. Assuming 2147483647 sec
Dec 28 02:11:42 gateway dhcpcd[4195]: dhcpT2value option is missing in DHCP server response. Assuming 3758096383 sec
Dec 28 02:11:42 gateway dhcpcd[4195]: broadcasting second DHCP_DISCOVER
Dec 28 02:11:42 gateway dhcpcd[4195]: DHCP_OFFER received from  (195.34.134.196)
Dec 28 02:11:42 gateway dhcpcd[4195]: broadcasting DHCP_REQUEST for 213.47.6.207
Dec 28 02:11:42 gateway dhcpcd[4195]: DHCP_ACK received from  (195.34.134.196)
Dec 28 02:11:42 gateway dhcpcd[4195]: dhcpConfig: ioctl SIOCADDRT: File exists
Dec 28 02:11:42 gateway dhcpcd[4195]: infinite IP address lease time. Exiting
Dec 28 02:11:42 gateway e-smith[4198]: Processing event: ip-change 213.47.6.207
Dec 28 02:11:42 gateway e-smith[4198]: Running event handler: /etc/e-smith/events/ip-change/S15set-external-ip
Dec 28 02:11:42 gateway e-smith[4198]: S15set-external-ip=action|Event|ip-change|Action|S15set-external-ip|Start|1135732302 64
8963|End|1135732302 853231|Elapsed|0.204268
Dec 28 02:11:42 gateway e-smith[4198]: Running event handler: /etc/e-smith/events/ip-change/S16adjust-masq..........

this message occurs about every 5 to 10 seconds

i changed over to static ip which isnt the correct configuration
now the log shows the following:

c 30 12:33:40 gatewayasb325 kernel: denylog:IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:01:5c:22:c6:d0:08:00 SRC=10.34.211.113 DST
=255.255.255.255 LEN=328 TOS=0x00 PREC=0x00 TTL=64 ID=11010 PROTO=UDP SPT=67 DPT=68 LEN=308
Dec 30 12:33:40 gatewayasb325 kernel: denylog:IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:01:5c:22:c6:d0:08:00 SRC=10.34.211.113 DST
=255.255.255.255 LEN=328 TOS=0x00 PREC=0x00 TTL=64 ID=11017 PROTO=UDP SPT=67 DPT=68 LEN=308
Dec 30 12:33:42 gatewayasb325 kernel: denylog:IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:01:5c:22:c6:d0:08:00 SRC=10.34.211.113 DST
=255.255.255.255 LEN=328 TOS=0x00 PREC=0x00 TTL=64 ID=11199 PROTO=UDP SPT=67 DPT=68 LEN=308
Dec 30 12:33:42 gatewayasb325 kernel: denylog:IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:01:5c:22:c6:d0:08:00 SRC=10.34.211.113 DST
=255.255.255.255 LEN=328 TOS=0x00 PREC=0x00 TTL=64 ID=11209 PROTO=UDP SPT=67 DPT=68 LEN=308
Dec 30 12:33:46 gatewayasb325 kernel: denylog:IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:01:5c:22:c6:d0:08:00 SRC=10.34.211.113 DST
=255.255.255.255 LEN=328 TOS=0x00 PREC=0x00 TTL=64 ID=12052 PROTO=UDP SPT=67 DPT=68 LEN=308
Dec 30 12:33:46 gatewayasb325 kernel: denylog:IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:01:5c:22:c6:d0:08:00 SRC=10.34.211.113 DST
=255.255.255.255 LEN=328 TOS=0x00 PREC=0x00 TTL=64 ID=12080 PROTO=UDP SPT=67 DPT=68 LEN=308

this occurs about every second.

i already calles my isp and he said, that my dhcp client must be misconfigured.

as far as i understand this whole thing:

i get on my external nic permant dhcp offers from my isp. so everytime my smebox thinks that the external ip has changed altough it hasnt

here is the dhcpcd-eth0.info

IPADDR=213.47.6.207
NETMASK=255.255.255.0
NETWORK=213.47.6.0
BROADCAST=255.255.255.255
GATEWAY=213.47.6.1
DOMAIN=chello.at
DNS=195.34.133.21,195.34.133.22
DHCPSID=195.34.134.196
DHCPGIADDR=10.34.211.113
DHCPSIADDR=0.0.0.0
DHCPCHADDR=00:E0:7D:C2:F4:99
DHCPSHADDR=00:01:5C:22:C6:D0
DHCPSNAME=
LEASETIME=4294967295
RENEWALTIME=2147483647
REBINDTIME=3758096383
INTERFACE=eth0
CLASSID="Linux 2.4.20-18.7 i686"
CLIENTID=00:E0:7D:C2:F4:99

i dont have any clues left for what to search or how to solve this problem

if use the correct configuration dhcp with mac identifier, the internet connection dies about every 5 to 10 minutes for 2 minutes.

i am using sme with a cablemodem

does anyone has an solution or a hint for what to search?

best regards

karl

Offline electroman00

  • ****
  • 491
  • +0/-0
dhcp problem
« Reply #1 on: December 30, 2005, 01:16:05 PM »
What version SME for starters?
What ISP?

Assume setup is server-gateway.

Power down modem for a long period of time and then power up SME
after modem has booted.

Might cables be swapped on SME wan/lan?

Check Mac Address's.....

Was this system ever working correctly or a new system?

CooLCaT1975

dhcp problem
« Reply #2 on: December 30, 2005, 01:52:28 PM »
SME 6.01 wit all yum updates applied
isp is chello.at aka upc

setup is server-gateway

cables are correct and interface settings are correct (just checked)
external eth0, internal eth1

it looks like that there are permanent dhcp offers via boradcast

Offline CharlieBrady

  • *
  • 6,918
  • +3/-0
Re: dhcp problem
« Reply #3 on: December 30, 2005, 08:23:13 PM »
Quote from: "CooLCaT1975"

Dec 28 02:11:42 gateway dhcpcd[4195]: infinite IP address lease time. Exiting


You might find an explanation of that here:

http://howto.htlw16.ac.at/at-highspeed-howto-3.html

I don't read German so I can't tell.

Quote

if use the correct configuration dhcp with mac identifier, the internet connection dies about every 5 to 10 minutes for 2 minutes.


When you mean "the correct configuration dhcp", do you mean the same configuration which generated the log messages above?  If so, then I'd guess the bad DHCP leases are causing your interface to intermittently lose its configuration.

Quote

it looks like that there are permanent dhcp offers via boradcast


It does indeed. I'd suggest you do a packet capture using tcpdump (restrict the capture to  eth0 and UDP ports 67 and 68) and then send to your ISP's support address. If they can't work out what is going on - change to a more competent ISP :-)

CooLCaT1975

dhcp problem
« Reply #4 on: December 31, 2005, 09:46:48 AM »
hi and good morning from snowy austria!

Quote
When you mean "the correct configuration dhcp", do you mean the same configuration which generated the log messages above? If so, then I'd guess the bad DHCP leases are causing your interface to intermittently lose its configuration.


the correct configuration for my internet connection should be dhcp with mac identifier. this configuration generates the log file entries which i posted first.

after talking once again to chello, i got at last an reasonable answer for the problem. these udp packets are the packets which are generated from the dhcp server to see if the cablemodem is still online. it's has been always this way, but chello changed over to "faster" dhcp servers and from that time on the problem perisist.

the german article seems to deal with this problem, cause there they advise to upgrade the dhcp.

i give this an try and will post the results.

thx charlie for the hint

charly

Offline electroman00

  • ****
  • 491
  • +0/-0
dhcp problem
« Reply #5 on: December 31, 2005, 02:08:42 PM »
Quote
after talking once again to chello, i got at last an reasonable answer for the problem. these udp packets are the packets which are generated from the dhcp server to see if the cablemodem is still online. it's has been always this way, but chello changed over to "faster" dhcp servers and from that time on the problem perisist.


Well there's your clue........
Quote

it's has been always this way,

In short Bullshit.....
Quote
but chello changed over to "faster" dhcp servers and from that time on the problem perisist.

Now that's the problem....

Their dns servers 195.34.134.99 is not pingable from my end.

If you can't ping the dns server then it's not likely you will be served the
correct dns info and your log is indicating that.
Quote
dns option is missing in DHCP server response.

Suggest you try another ISP's dns server by entering it in manually,
until they get their act together and fix the problemo.

So... as usual Charlie is right.....
Quote
change to a more competent ISP

Anyone who sets up a system without even doing a simple ping test
to make sure it's running before deployment is incompetent.

BTW... it is their server......

195.34.134.99 (viedhcp00.chello.at)

 and as you can see that's all the response I get from their dns server.

Their server is so much faster it doesn't work.....!!!
Don't you just love wasting your time due to someone elses incompetents.

Offline CharlieBrady

  • *
  • 6,918
  • +3/-0
dhcp problem
« Reply #6 on: December 31, 2005, 05:03:35 PM »
I'm sorry, electoman00, but you are wrong in a few facts.

Quote from: "electroman00"

Their dhcp servers 195.34.134.99 is not pingable from my end.


And that means nothing more than that 195.34.134.99  is not pingable from your end. That says nothing about what services it may offer, and in particular, nothing about what services it may offer to karl's system.

Quote

If you can't ping the server then it's not likely you will be served the
correct dhcp lease ...


That's a very large, and unjustified, leap in logic.

Quote

Suggest you try another ISP's dhcp's server by entering it in manually,


It's not possible to choose one's DHCP server. A DHCP server is discovered via broadcast. It's also usually not possible to communicate outside the local network until a DHCP lease is secured.

Offline CharlieBrady

  • *
  • 6,918
  • +3/-0
dhcp problem
« Reply #7 on: December 31, 2005, 05:06:48 PM »
Quote from: "CooLCaT1975"

the german article seems to deal with this problem, cause there they advise to upgrade the dhcp.


To upgrade the dhcp client, or they advise the ISP to upgrade their server? If the former is true, it's possible there's a bug in the dhcp client. Please open a bug report, with all the facts you've presented here, and a translation of the advice from the article. Thanks.

Offline electroman00

  • ****
  • 491
  • +0/-0
dhcp problem
« Reply #8 on: December 31, 2005, 05:23:47 PM »
Well my mistake, I meant DNS server.

Their DNS server 195.34.134.99 is not pingable, so it's not responding with
dns info and his log verifies that.

All the dns servers I've tested ping responed and I don't use my ISP's
dns it's to sloooow.

I'll edit my post, thanks Charlie.

Offline CharlieBrady

  • *
  • 6,918
  • +3/-0
dhcp problem
« Reply #9 on: December 31, 2005, 06:07:59 PM »
Quote from: "electroman00"

Their DNS server 195.34.134.99 is not pingable, so it's not responding with
dns info and his log verifies that.


Your logic is still flawed, I'm afraid. His log refers only to the content of DHCP leases, not to the effectiveness of any DNS servers offered. In any case, SME server does not use the DNS server address information provided in DHCP leases.

Quote

I'll edit my post, thanks Charlie.


Please don't do that, you'll confuse anyone reading the thread.

Offline electroman00

  • ****
  • 491
  • +0/-0
dhcp problem
« Reply #10 on: December 31, 2005, 10:24:42 PM »
So if it's not getting the DNS server ip from dhcp then where's it
getting from?

Offline CharlieBrady

  • *
  • 6,918
  • +3/-0
dhcp problem
« Reply #11 on: December 31, 2005, 10:45:34 PM »
Quote from: "electroman00"
So if it's not getting the DNS server ip from dhcp then where's it getting from?


The SME server doesn't need to use any external DNS resolver, as it has its own built in (much like an ISP uses). It obtains DNS information direct from where it's published. It starts at the DNS root servers, and follows delegations from there.

Here's a few quick references to how DNS works:

http://cr.yp.to/djbdns/intro-dns.html
http://www.unix.org.ua/orelly/networking/dnsbind/ch02_01.htm

Offline electroman00

  • ****
  • 491
  • +0/-0
dhcp problem
« Reply #12 on: January 01, 2006, 12:55:45 AM »
Charlie

Thanks, I know how dns works just didn't know sme could take care
on it's own.

Also I just noticed I pinged the wrong dns ip.

DNS=195.34.133.21,195.34.133.22 are both working.

Well I'm sorry, and will remember not to post at 6am before
I have my coffee. I'll make it a two cup rule from now on.

So he needs to upgrade DHCP, are we all going to be looking at this
senareo sooner or later?

CooLCaT1975

dhcp problem
« Reply #13 on: January 01, 2006, 01:39:16 PM »
Quote from: "CharlieBrady"
Quote from: "CooLCaT1975"

the german article seems to deal with this problem, cause there they advise to upgrade the dhcp.


To upgrade the dhcp client, or they advise the ISP to upgrade their server? If the former is true, it's possible there's a bug in the dhcp client. Please open a bug report, with all the facts you've presented here, and a translation of the advice from the article. Thanks.


they advise to upgrade the client. i took a look at it and saw that the version which comes with sme is newer than the version advised in the article. i wil try to update to the newest dhcp client and see what will happen.

btw i am wondering how windows machines deal with these packets.

happy new year :)

CooLCaT1975

dhcp problem
« Reply #14 on: January 01, 2006, 01:52:29 PM »
the version i have installed is dhcpcd-1.3.22pl1-7.i386.rpm.

is there any newer version out there??

couldnt find any at http://www.phystech.com/download/