I feel like I hit this once and had to use a rib-group. But it would probably be helpful to see the relevant configs in full.
On Wed, Dec 19, 2018 at 10:52 PM Anderson, Charles R <[email protected]> wrote: > On Wed, Dec 19, 2018 at 03:41:40PM -0800, Chris Cappuccio wrote: > > Nathan Ward [[email protected]] wrote: > > > Hi Chris, check out the forward-only-replies option, pretty sure there > was some stuff there I had to fiddle with. > > > > > > Can you post your config? > > > > > > > I'm using the bootp helper instead of the dhcp-relay feature. I don't > know > > if 'fud' handles both. When I tried using dhcp-relay, my remote PEs > stopped > > receiving DHCP replies. The router connected to the dhcp server would > eat the > > replies and they would never reach the remote PE router, despite the > > interface that the DHCP server connects to not having any relay enabled. > > Since it is a production network I stopped using dhcp-relay until I look > > further into the documentation.. > > bootp helper requires you to specify the routing-instance. Have you done > that? > > set forwarding-options helpers bootp interface irb.2287 server 10.0.1.10 > routing-instance FOO > set forwarding-options helpers bootp interface irb.2287 server 10.0.2.10 > routing-instance FOO > _______________________________________________ > juniper-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/juniper-nsp > _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
