NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
DHCP not traversing switch Part 2
Hi,
Unfortunatly I have a follow up issue to my last issue here. This time however only the Netgear is involved.
I have performed various tests already and it boild down to that the S3300 does not seem to pass on DHCP traffic at all at the moment.
Test setup:
I have a box A on Port 12 and a box B on Port 13. On B there is a dhcp server active and tcpdump on 67/68 udp.
I start a dhcp request on box a connected via Netgear switch - I don't see any requests. On Box A I can see the requests being sent out with wireshark, but o/c no replies.
A static IP on Box A results ins perfectly fine communication, no issues.
Now I used another switch (cheap 8 port) and attached box A and B to it and with that switch DHCP is working fine, tcpdump listing everything.
Both boxes are on VLAN 1, no security features active, no helper, relay or anything.
S3300 (stack of 2) is on latest FW (6.6.4.7) but I think the issue was present before. I noticed weird behaviour for about 2 weeks but can't really tell what I could have changed to cause this :(
Lost again :(
Hey,
I missed a line in the config. You have DHCP snooping turned on it seems. Can we turn that off?
System > Services > Global Configuration > Turn it off
Cheers
17 Replies
So nobody here has any idea how to further pin down the issue or re potential cause? :(
As far as I have checked, there is no issue about DHCP traffic not able to pass on the S3300 switch models either set as stack or standalone as per described in your post. Let us isolate the problem. Kindly answer the questions below:
a. If you are going to unstack the S3300 switches, is the DHCP traffic working fine on both S3300 switches when set as standalone switches?
b. Are you using virtual machines as the DHCP server and DHCP client? If yes, kindly try to test using an actual PC or router as the DHCP server and a PC as the DHCP client on the S3300 switches set either as a stack and as standalone switches.
c. Since you have upgraded the firmware of both S3300 switches to the latest v6.6.4.7, were you able to perform a factory reset on both S3300 switches then reconfigure it from scratch? It is best to perform a factory reset after upgrading the firmware then reconfigure the settings from scratch to start clean using the firmware. Then, check if DHCP traffic is able to pass to the S3300 switches either it is configured as a stack or as standalone switches.
Regards,
DaneA
NETGEAR Community TeamHi DaneA,
thanks for replying.
Those switches are currently as 'productive' as they can be in a SOHO environment, so I have significant problems following the debugging steps you suggested :/, i.e. both unstacking and reverting to factory results will require significant effort to implement so if we can prevent that at all I'd much appreciate it.
I have since posting tried another reboot of the stack but that did not help.
Re b:
I have tried with both virtual and physical server and both as client to rule out issues on ESX side.
Also as I said I think this issue started while still on the old firmware (which has been in place for a while) and I am sure it has been working fine previously.
Thanks,
regards,
Thomas
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
