Junos Asymmetric Routing
curupas at gmail.com
Thu May 27 19:07:09 CDT 2010
Not sure if I correctly undestand you but default route its the route
that the packet must follow if it do not have a specific route for the
destination, so, if the next-hop for the source IP (126.96.36.199) is not in
the route table then the packet will follow the default route (ISP1).
So, this behavior will be correct if next-hop for 188.8.131.52/24 is not
installed. Just for troubleshooting purpose install a static route
set routing-options static route 184.108.40.206/24 next-hop
If this works fine then verify the route table, are you using BGP to
receive such routing info? If you are not filtering the update maybe
the sender is. Verify the received routes using the "show route
protocol bgp receive-protocol bgp x.x.x.x" (x.x.x.x is the bgp
On Thu, May 27, 2010 at 8:27 PM, Ken Gilmour <ken.gilmour at gmail.com> wrote:
> Hi all,
> I have a very peculiar situation here that i seem to have difficulty
> explaining in such a way for people to understand. I just got off the phone
> to the Juniper Devs after about 4 hours with no result. They understand the
> problem but can't seem to think of a working solution (last solution led to
> the primary firewall hard crashing and then failing over after a commit
> (which also makes me wonder what made the primary crash and not the
> secondary)). I am wondering if there is anyone "creative" on the list who
> has encountered and worked around this problem before...
> Here goes *sigh*
> ISP1 - 220.127.116.11/24
> ISP2 - 18.104.22.168/24
> ISP1 is the default gateway, ISP2 is a backup provider but which is always
> active. Client comes in on ISP1's link, traffic goes back out on ISP1s link.
> Client comes in on ISP2's link (non default gateway) but for some reason,
> the packets seem to be going back out through the link for ISP1.
> So look at it this way:
> SYN comes from client at 22.214.171.124 aimed at 126.96.36.199, packet is received by the
> firewall. Firewall sends a SYN/ACK but the firewall at 188.8.131.52 sees it in
> TCPDump, the firewall at 184.108.40.206 never sees it.
> Here's a log snippet (I can send you more if you need:
> May 27 21:38:49 21:38:48.1509569:CID-1:RT: route lookup: dest-ip 220.127.116.11 *orig
> ifp reth3.0* *output_ifp reth2.0* orig-zone 19 out-zone 19 vsd 3
> You will see that the orig and out zones are the same zone, however this was
> a last ditch effort (putting both interfaces into one zone, effectively
> creating a swamp).
> Our current (non-preferred) solution is to put match-all rules on our
> Catalyst 6513s and put both providers into a swamp and the switch will then
> intercept the packets if they are destined for the wrong interface and send
> them out the right one based on a bunch of boolean.
> We've tried setting up a virtual instance on the offending interface and a
> firewall filter, but this had little to no effect (at one point it stopped
> passing the packets to the end machine altogether). We're using small SRX
> 650ies. Why do we want to do it this way you ask? In the event of a BGP
> session failure we need to be able to use our statically routed IPs and rely
> on someone else.
More information about the NANOG