21 Jan
2013
21 Jan
'13
11:26 a.m.
Marius,
I understand, but not to belabour the point; are you saying that you
have custom configured routes on your device using the public Internet
to contact 44.0.0.1?
We are testing connections over AMPR.
We both agree '44.0.0.1 via 169.228.66.251' is not a gateway, it is only
a connection to AMPRGW.
I noted that 'default via 169.228.66.251' is both a GW and connection to
44.0.0.1 (confirmed as my firewall only permits 44.0.0.1 on the RIP
network port).
You noted:
"To reach 44.0.0.1 properly you need a smaller metric route to
circumvent
the tunnel and use public addresses."
In that case, you would agree that you are NOT reaching 44.0.0.1 over AMPR?
Under your scenario, Source NAT must be used, as you are using the
public Internet for 44 hosts in your network to reach 44.0.0.1.
~Lynwood