Great.. I understand that.... but my question is what and how do I fix this?
Main Topics
Browse All TopicsI have a Arris CMTS 1000; with a new Centos 5.2 DHCPD (3.04) server. I am trying despirately to hand out IP's to cable modems and there are three different MAC subsets that refuse to bind. There was on the old server (which crashed) some type of "wildcard" and I can not figure this out...
The MAC's starting with 00:10:95, 00:90:64 and 00:11:e3; get the DHCP lease from the server but will not bind; however the 00:50:da, and some others have no problem.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
It is physical interface - Layer 1 problem involving electrical circuitry between cable modem and customers netcard.
Most straightforward fix is cable modem firmware update, if release notes mention something about ethernet auto-negotiation, MDI-X and things like that.
There is nothing your customer is able to do to fix given they do not have internet connection.
You can try different network card, maybe current driver is bad.
Or CentOS5
or up2date
it is definetly lowlevel frame loss, hard to trace etc.
maybe ethtool can disable udp/tcp checksumming - I am out of ideas
let tcpdump run for an hour n interface not doung checksumming, then load report into wireshark and have a look
tcpdump -s 1600 -w outfile.log -i eth0
or like that
Maybe some of the cable modems are too stupid to understand dhcp and need the old bootp. Which are really similiar...
add the" allow bootp" directive to the configuration block for the subnet containing the client and restart dhcpd.
Failing that install boopd on the box.
Good luck and remember to take a shower tonight.
The problem was two fold...
1. The cable plant operator had NO equipment to analyze the incoming signal.
2. The ISC DHCP option were default on most options. I specifically designated the TOD and Logging servers and they came up; but only after thecable plant operator cleaned up the signal at the ingress port.
Thanks!
Business Accounts
Answer for Membership
by: gheistPosted on 2009-04-27 at 05:09:28ID: 24240846
It boils down to particular type of network adapters not connecting to cable modem's ethernet port. regauth/ou i/oui.txt
http://standards.ieee.org/