ex4500 policy based routing not working

I have not assigned 185.9.156.19 ip to anywhere ,  it also hits the filter counter but udp still working

            term 1 {
                from {
                    prefix-list {
                        LIST-op;
                    }
                    protocol udp;
                }
                then {
                    count UDPTest;
                    routing-instance UDP-Routes;
                }
            }
routing-instances {
    UDP-Routes {
        routing-options {
            static {
                route 185.9.157.18/32 next-hop 185.9.156.19;
            }
        }
    }
}

Open in new window



Filter: Bloker
Counters:
Name                                                Bytes              Packets
AckTest                                         123415334              1618124
Trafik                                        26910367452            180864640
UDPTest                                        1367970105             13008817
Policers:
Name                                                Bytes              Packets
ack-dos-policer                                                              0

Open in new window

FireBallITAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

giltjrCommented:
According to:

https://www.juniper.net/documentation/en_US/junos14.1/topics/reference/general/firewall-filter-ex-series-match-conditions-support.html

The EX4500 does not support an action of assigning a routing-instance.  Just goto the above page and search for "routing-instance" and you'll see not supported.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
FireBallITAuthor Commented:
i think you check wrong column it does not support on egress port please check the header of the table
0
giltjrCommented:
Sorry about that.  You may want to try and create a host with the address 185.9.156.19.  Not sure about the Juniper box, but I know that some devices if they can't communicate with an adjacent host  in a routing table will remove that host from the routing table and stop trying to use it.

If you display that routing instance does it still show with that host in the routing table?
0
FireBallITAuthor Commented:
creating a rib group for imports the solution but it is not working as expected it is dropping packets in somewhere i need to check a little more
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Routers

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.