Log in to ask questions, share your expertise, or stay connected to content you value. Don’t have a login? Learn how to become a member.
If you have a question or a use case, likely there are others who are experiencing or worked through the same thing. Don't hesitate to jump in and ask or share your knowledge!
Need additional guidance? Check out these Juniper Resources.
Ask AI Juniper Threat Labs SRX Upgrade Guide Security Advisories
Ok, I really think my theory from earlier was right ... Something with the DHCP relay done by the WLC. On the SRX, the DHCP server interacts with the ARP table. That's why the static IP eventually started working as well. If you want to keep the PA ...
Sure thing! I marked 21 as the best answer. Thanks again. Have a great weekend!
I'm glad everything is sorted out now. That was an interesting problem! Could you please mark post #13 or #21 as answer to help out people who might come across this thread so they don't have through lots of posts? ------------------------------ Nikolay ...
Yep.... diabling DHCP proxy fixed it... tested again with 1681 and everything worked. Wow. One check box resulted in months of grief. Genuinely I cannot thank you enough. This was giving me gray hairs.
Yes, DHCP proxy, DHCP relay, same thing. Very useful when you have a centralized DHCP server, out of broadcast reach, but really not necessary when the server is listening in the same broadcast domain as the clients. And, now we learned, sometimes terrible ...
I was looking but can't seem to find an option, unless DHCP proxy == DHCP relay. I'll ask around on the Cisco community and let you know.
See if there's an option on the WLC for it to NOT relay DHCP requests. Basically turn off everything DHCP-related for 1681 on the WLC. I think my original theory was right. On the SRX, the DHCP server interacts with the ARP table. ------------------------------ ...
Complete this three-question survey to help us identify where you are in your upgrade journey.
Log in to see this information