Re: [j-nsp] Filter based forwarding issue

It apears term 3 is far below term 1 and term 2. It appears ping and Telnet traffic from 192.168.4.128/26 would match terms ping and telnet; therefore, they will never hit term 3 and not use filter-based forwarding. Does this explain the behavior you are seeing? If so, I believe the

[j-nsp] Filter based forwarding issue

Hi, I have ran into an issue with the following on a J2350 (JUNOS Software Release [9.2R1.10] (Export edition) Enhanced Services) Presently the client has the following address range 192.168.4.0/24 which as can be seen below to be at the next-hop address of 212.111.105.238 which is directly

[j-nsp] Filter-Based Forwarding issue

Hello There, I've exprienced weird behaviour of FBF - it doesn't work at all :). Suppose there is a very simple filter: # show firewall family inet filter FILTER_INSTANCE_TO term C { from { source-prefix-list { PLIST_C; } } then { count ccount;

Re: [j-nsp] Filter-Based Forwarding issue

Could you provide the configuration snippets for the routing-options, routing-instances, and a 'show route summary' output. --- Gniewko [EMAIL PROTECTED] wrote: Hello There, I've exprienced weird behaviour of FBF - it doesn't work at all :). Suppose there is a very simple filter: # show