SRX routing problem

top.png
We are using policy based routing  for to send udp traffic from different route
We have started a TCPdump on cent os server and realize that traffic succesfully arriving to the cent os from expected route
And it is answering it

19:27:15.218635 IP (tos 0x0, ttl 118, id 11236, offset 0, flags [none], proto: UDP (17), length: 62) 88.236.126.6.59836 > 185.9.157.18.9987: UDP, length 34
19:27:15.218831 IP (tos 0x0, ttl  64, id 0, offset 0, flags [DF], proto: UDP (17), length: 60) 185.9.157.18.9987 > 88.236.126.6.59836: UDP, length 32
19:27:15.221301 IP (tos 0x0, ttl 118, id 11237, offset 0, flags [none], proto: UDP (17), length: 207) 88.236.126.6.59836 > 185.9.157.18.9987: UDP, length 179
19:27:15.791476 IP (tos 0x0, ttl 118, id 11241, offset 0, flags [none], proto: UDP (17), length: 62) 88.236.126.6.59836 > 185.9.157.18.9987: UDP, length 34
19:27:15.791568 IP (tos 0x0, ttl  64, id 0, offset 0, flags [DF], proto: UDP (17), length: 60) 185.9.157.18.9987 > 88.236.126.6.59836: UDP, length 32
19:27:15.794575 IP (tos 0x0, ttl 118, id 11242, offset 0, flags [none], proto: UDP (17), length: 207) 88.236.126.6.59836 > 185.9.157.18.9987: UDP, length 179
19:27:16.491439 IP (tos 0x0, ttl 118, id 11247, offset 0, flags [none], proto: UDP (17), length: 62) 88.236.126.6.59836 > 185.9.157.18.9987: UDP, length 34
19:27:16.491498 IP (tos 0x0, ttl  64, id 0, offset 0, flags [DF], proto: UDP (17), length: 60) 185.9.157.18.9987 > 88.236.126.6.59836: UDP, length 32
19:27:16.494480 IP (tos 0x0, ttl 118, id 11248, offset 0, flags [none], proto: UDP (17), length: 207) 88.236.126.6.59836 > 185.9.157.18.9987: UDP, length 179
19:27:17.491905 IP (tos 0x0, ttl 118, id 11251, offset 0, flags [none], proto: UDP (17), length: 62) 88.236.126.6.59836 > 185.9.157.18.9987: UDP, length 34
19:27:17.492084 IP (tos 0x0, ttl  64, id 0, offset 0, flags [DF], proto: UDP (17), length: 60) 185.9.157.18.9987 > 88.236.126.6.59836: UDP, length 32
19:27:17.494781 IP (tos 0x0, ttl 118, id 11252, offset 0, flags [none], proto: UDP (17), length: 207) 88.236.126.6.59836 > 185.9.157.18.9987: UDP, length 179
19:27:18.791610 IP (tos 0x0, ttl 118, id 11266, offset 0, flags [none], proto: UDP (17), length: 62) 88.236.126.6.59836 > 185.9.157.18.9987: UDP, length 34
19:27:18.791708 IP (tos 0x0, ttl  64, id 0, offset 0, flags [DF], proto: UDP (17), length: 60) 185.9.157.18.9987 > 88.236.126.6.59836: UDP, length 32
19:27:18.893045 IP (tos 0x0, ttl 118, id 11269, offset 0, flags [none], proto: UDP (17), length: 207) 88.236.126.6.59836 > 185.9.157.18.9987: UDP, length 179

Open in new window



We put counters to trace udp traffic for 185.9.157.18 and udp answers arrive to the srx from xe-1/0/1 as expected but not go outside from any where on the device


Filter: Bloker2
Counters:
Name                                                Bytes              Packets
UDPFROMxe102                                1200                   20
Filter: Bloker3
Counters:
Name                                                Bytes              Packets
UDPTOXE101                                             5385                   40

Open in new window



and there is no output
no IDS log on screens
when i change tcp and udp traffic routings to the opposite it is working perfectly
Whenever i put to udp traffic to different uplink then main gateway'a L3 port it is stopping


what should be the problem ?
FireBallITAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
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.

RafaelCommented:
What does your route table look like ? Are you able to post it ? Please do.

HTH
-Rafael
FireBallITAuthor Commented:
We found theproblem sorry for that problem was about the trust to trust rights

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
RafaelCommented:
OK. Glad it worked out.

Don't forget to close your request for help.

HTH
-Rafael
FireBallITAuthor Commented:
Delete
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
Hardware Firewalls

From novice to tech pro — start learning today.