Re: [j-nsp] [EXT] firewall filter misses connected interface addresses

2019-12-10 Thread Michael Hare via juniper-nsp
9, 2019 3:13 PM > To: juniper-nsp@puck.nether.net > Subject: Re: [j-nsp] [EXT] firewall filter misses connected interface > addresses > > I use something like this so the same firewall filter is applied on all lo0.* > interfaces of all VRFs and logical-systems: > >

Re: [j-nsp] [EXT] firewall filter misses connected interface addresses

2019-12-09 Thread Anderson, Charles R
I use something like this so the same firewall filter is applied on all lo0.* interfaces of all VRFs and logical-systems: set groups RE-FILTER logical-systems <*> interfaces lo0 unit <*> family inet filter input ROUTING-ENGINE set groups RE-FILTER logical-systems <*> interfaces lo0 unit <*>

Re: [j-nsp] [EXT] firewall filter misses connected interface addresses

2019-12-09 Thread Andreas
Hello Mike, if you're using that lo0.0 in a routing-instance or use more than one loopback you could also run into these restrictions: - If you configure Filter A on the default loopback interface and Filter B on the VRF loopback interface, the VRF routing instance uses Filter B. - If you

Re: [j-nsp] [EXT] firewall filter misses connected interface addresses

2019-12-09 Thread Anderson, Charles R
What hardware and software version? There were some bugs/limitations with certain combinations. On Mon, Dec 09, 2019 at 07:42:02AM -0800, Mike wrote: > Hello, > > I have a problem getting junos to filter out admin access to my router > from unauthorized addresses. > > I have some addresses