8 May
2017
8 May
'17
7:52 a.m.
Are you able to see the packets originating from your end?
I seem to be sending to that IP correctly, but get no reply.
https://u4477715.ct.sendgrid.net/wf/click?upn=MJaTQVDJZogYIZySndf7y-2BCWLgZ…
When I tested from 44.131.14.140, which is behind a non-44 gateway, I
did get a reply. I did not get a reply from an Internet IP.
Thanks,
Mike, M6XCV
On 8 May 2017 at 12:11, Leon Zetekoff <wa4zlw(a)backwoodswireless.net> wrote:
(Please trim inclusions from previous messages)
_______________________________________________
Hi Mike...doesnt work from here....
source should be 44.56.53.3 (NAT from internal network)
here is snippet of my routing table
242 ADr 44.131.11.0/29 44.0.0.1 120
243 ADr 44.131.14.128/26 44.0.0.1 120
244 ADr 44.131.14.252/31 44.131.14.253 120
245 ADr 44.131.35.128/29 44.0.0.1 120
246 ADr 44.131.56.0/29 44.0.0.1 120
C:\>tracert 44.131.14.253
Tracing route to 44.131.14.253 over a maximum of 30 hops
1 <1 ms * <1 ms xtm520.wa4zlw.homedns.org [10.161.51.3]
2 1 ms 1 ms <1 ms core100.wa4zlw.ampr.org [44.56.53.1]
3 br0.core100.wa4zlw.homedns.org [10.4.0.2] reports: Destination host
unreachable.
Trace complete.
C:\>tracert 44.131.14.252
Tracing route to 44.131.14.252 over a maximum of 30 hops
1 <1 ms <1 ms * xtm520.wa4zlw.homedns.org [10.161.51.3]
2 2 ms <1 ms <1 ms core100.wa4zlw.ampr.org [44.56.53.1]
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 ^C
C:\>
Leon