6 Jun
2017
6 Jun
'17
1:50 p.m.
It is simple. When the move started, I published a workaround for using
both gateways by creating an additional gw interface and apply some
connection/packet marks on it, so that outgoing 44 to internet traffic
would go via tunnel.
Now this new route appeared and created a tunnel with the same endpoint
parameters which took precedence over the old one, being newer.
So incoming traffic via the old gateway never got its connection/packet
marks and responses never got out via tunnel (old or new, it doesn't
matter).
Can someone explain exactly how the 44.0.0.2/32 route
is causing an
issue on the tiks?
Because that route could have been removed Monday anyway, as it would no
longer be needed if the migration was completed.
Did all services and routing move to New_AMPRGW yesterday?
73,
- Lynwood
KB3VWG