Chris,
The test systems are still there and working. Also, your route is in the RIP and working (I can ping 44.135.193.1).
Please check in your router if you don't drop those 44 routes in Routing->Prefix Lists.
Also please take care to DROP 44.0.0.1 in your prefix list, since this will render the RIP receiving non-functional.
Also make sure you do not have another interface with 44.x.x.x/8 (netmask /8) assigned to any other interface.
Marius, YO2LOJ
On 2017-05-05 03:27, Christopher S. Munz-Michielin wrote:
(Please trim inclusions from previous messages) _______________________________________________ Thanks for the reply Mike.
I've just tested and have been unsuccessful. I've done a packet capture and can see the IPIP packets leaving my router with source IP 208.110.114.235 and destination IP 44.131.14.255. Inside the tunnel I have source IP 44.135.193.130 and destination IP 44.131.14.254.
Can you confirm if you have routes for 44.135.193.0/24 destined to 208.110.114.235?
Cheers, Chris
On 5/4/2017 4:16 PM, M6XCV (Mike) wrote:
(Please trim inclusions from previous messages) _______________________________________________ I currently have 44.131.14.0/24 routed to 44.131.14.255, you should be able to ping 44.131.14.254 encapsulated.
Mike, M6XCV
On 4 May 2017 at 22:11, Christopher S. Munz-Michielin <christopher@ve7alb.ca
wrote: (Please trim inclusions from previous messages) _______________________________________________ Hello All,
I've just implemented the newest version of Marius' Mikrotik script which enables accessing 44net IPs using a gateway in 44 address space, and was wondering if there is an IP which uses this configuration I can test my setup against. The network which Marius was originally tested with ( 44.130.120.0/24) seems to no longer be present in my routing table.
Cheers! Chris VE7ALB
44Net mailing list 44Net@hamradio.ucsd.edu https://u4477715.ct.sendgrid.net/wf/click?upn=vS4GjSiF-2F5vYmfX5tr6ez81-2Fej...