- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- LAN Routing
- >
- 3crwer200-75
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-27-2010 10:23 PM
03-27-2010 10:23 PM
3crwer200-75
I haven't been using this router recently due to some still unpatched security holes, but a former co-worker of mine still uses it and reported he was unable to connect back to Comcast, after doing some rewiring. He was able to hookup his pc to the same cable modem and it worked. Looking into the router logs I see a sigterm on the udhcpc process indicating the router is rejecting the dhcp assigned address from the cable modem. Putting a packet sniffer on shows that comcast is sending out dhcp messages via broadcast, and I found a bug that was solved in busy box after the last official patch for this router. The bug relates to not responding to a malformed rfc2131 packet sent broadcast if it is supposed to be unicast. The pc seems to be immune to this bug, or does not handle it according to the RFC, and thus works.
Any ideas or workaround? Putting in the dynamic information as static does not seem to work.