That would explain the slowness in obtaining a lease, but after it's obtained it would only be a problem at expiration time, correct? I haven't observed the issue corresponding to expiration. The lease is obtained (show system services dhcp client) and the route installed in both the routing table and forwarding table, so I assume that means that (eventually) the DHCP transaction is complete. Just no pings or anything after that.
Aaron On May 28, 2012, at 4:49 PM, Tim Eberhard wrote: > What you're most likely running into is the DHCP ttl limitation. > > While it's not often a problem, the SRX sends out a DHCP request with > a TTL of 1. > > http://forums.juniper.net/t5/SRX-Services-Gateway/SRX-DHCP-client-sends-discover-request-with-TTL-1/td-p/99180 > > I've seen this in the past, and while rare it does happen every now > and again depending on the ISP. As far as I know there hasn't been an > feature to tweak the TTL for dhcp discover requests. > > I hope this helps, > -Tim Eberhard > > On Mon, May 28, 2012 at 5:29 PM, Aaron Dewell <aaron.dew...@gmail.com> wrote: >> >> Hi all, >> >> I've been having a problem with an SRX210 connected to a Wildblue satellite >> modem (Surfbeam 2 if it matters). This is DHCP which appears to be proxied >> by the modem. There are a couple of different states, but neither work: >> >> Case 1: No ARP entry for the DHCP default route (forwarding table entry says >> "hold") >> Case 2: ARP entry but cannot ping the router or anything else >> >> Upon reboot, it works right after obtaining the lease for about 10 seconds, >> then stops (in one of those two states). >> >> Their "troubleshooting" method involves plugging it into a PC, which works, >> at which point they wash their hands of it, saying it's clearly a router >> problem. I have swapped in an SRX100, as well as another 210, and both >> exhibit identical symptoms. Also, the router works connected to a CX111/VZW >> Aircard. And it has been working for a few months and only quit last week >> (no change in SRX config). >> >> The current best theory is an invalid ARP packet which windows accepts but >> JunOS does not. That explains case #1 but not #2. >> >> I have the Wildblue people going out to swap out the modem tomorrow morning >> (too bad they can't just send one to switch) on the theory that it's the >> most likely thing to be the problem. >> >> Has anyone had any issues with an SRX connected to a satellite modem >> before? Any suggestions would be greatly appreciated! >> >> Thanks! >> >> Aaron >> >> >> _______________________________________________ >> juniper-nsp mailing list juniper-nsp@puck.nether.net >> https://puck.nether.net/mailman/listinfo/juniper-nsp _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
