09-15-2010 02:54 PM
DUT: RV016-V3, v4.0.0.'7-tm
We discovered some clients dont receive IP addresses from DHCP from time to time - both block options disabled:
Block MAC address on the list with wrong IP address | |
Block MAC address not on the list |
In two cases now, we had to go the "Unknown MAC" addresses (both entries there!) and explicitly add these to the static list, and exnable - before the IP assignment happens.
Once more here I have to point out: The so called logging on this RV0xx is among the worst what I have seen in the industry for a long time. There is ZERO logging of any DHCP activities at all. Or simple connection accept messages from the firewall are sent to syslog from the Facility: kernel Severity: alert, and Application: kernel ... another sad strory. Hope the management is listening here!
Back to the product manager, and then to RD please. Oh - if your Taiwanese OEM should have no clue what we expect - check the following table of log entries filtered to DHCP events - alos form a major Taiwanese manufacturer:
1 | 2010-09-15 23:36:27 | info | DHCP | Sending ACK to 10.10.1.25 | DHCP ACK | ||
19 | 2010-09-15 23:35:37 | info | DHCP | DHCP server assigned 10.10.1.10 to (00:0E:A6:C4:7B:97) | DHCP ACK | ||
20 | 2010-09-15 23:35:37 | info | DHCP | Requested 10.10.1.10 from (00:0E:A6:C4:7B:97) | DHCP Request | ||
22 | 2010-09-15 23:34:13 | info | DHCP | Sending ACK to 10.10.1.25 | DHCP ACK | ||
25 | 2010-09-15 23:33:20 | info | DHCP | Sending ACK to 10.10.1.10 [count=2] | DHCP ACK | ||
28 | 2010-09-15 23:30:27 | info | DHCP | Sending ACK to 10.10.1.10 | DHCP ACK | ||
29 | 2010-09-15 23:28:02 | info | DHCP | Sending ACK to 10.10.1.25 | DHCP ACK | ||
34 | 2010-09-15 23:25:56 | info | DHCP | Sending ACK to 10.10.1.10 | DHCP ACK | ||
35 | 2010-09-15 23:25:03 | info | DHCP | DHCP server assigned 10.10.1.234 to NAS000075(00:08:9B:00:00:75) | DHCP ACK | ||
36 | 2010-09-15 23:25:02 | info | DHCP | Requested 10.10.1.234 from NAS000075(00:08:9B:00:00:75) | DHCP Request | ||
38 | 2010-09-15 23:24:48 | info | DHCP | Sending ACK to 10.10.1.25 [count=2] | DHCP ACK | ||
51 | 2010-09-15 23:19:44 | info | DHCP | Sending ACK to 10.10.1.25 | DHCP ACK | ||
71 | 2010-09-15 23:14:44 | info | DHCP | Sending ACK to 10.10.1.229 [count=2] | DHCP ACK | ||
73 | 2010-09-15 23:14:32 | info | DHCP | DHCP server assigned 10.10.1.229 to EeePC2(00:15:AF:DA:D7:C8) | DHCP ACK | ||
74 | 2010-09-15 23:14:31 | info | DHCP | Requested 10.10.1.229 from EeePC2(00:15:AF:DA:D7:C8) | DHCP Request | ||
80 | 2010-09-15 23:09:55 | info | DHCP | Sending ACK to 10.10.1.229 [count=2] | DHCP ACK | ||
81 | 2010-09-15 23:09:47 | info | DHCP | Sending ACK to 10.10.1.25 [count=2] | DHCP ACK |
Ok, ok: A major router manufacturer I have teached and consulted for many years. And I'm available for consulting...
-Kurt.
10-12-2010 03:16 PM
>We discovered some clients dont receive IP addresses from DHCP from time to time - both block options disabled:
Kurt, is this problem persistently occured. Router should assign (dynamic) IP address w/o having to provide an entry in *unknown mac* table. If you still have same setup currently, please try to capture packet trace from router to see the ARP and DCHP packets activities (also remove any entries from *unknown mac* while doing this so that we got less complexity and more accurate data).
I've tried w/ my router but can't seem to recreate this problem.
>Once more here I have to point out: The so called logging on this RV0xx is among the worst what I have seen in the industry for a long time. There is ZERO logging of any DHCP activities at all.
Agree! Logging needed to be improved in this area.
>Ok, ok: A major router manufacturer I have teached and consulted for many years. And I'm available for consulting...
You're the best, Kurt. Duly notice!
High Regards,
Don
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide