5 May
2017
5 May
'17
10:33 a.m.
Hi Marius,
Thanks for the reply, here's what I have in prefix lists:
[ve7alb@ca-vic-cu-router02] > /routing prefix-lists print
0 chain=ampr prefix=44.0.0.1/32 prefix-length=0-32 invert-match=no
action=discard
1 chain=ampr prefix=44.0.0.0/8 prefix-length=8-32 invert-match=no
action=accept
2 chain=ampr prefix=0.0.0.0/0 prefix-length=0-32 invert-match=no
action=discard
And here's what I have for assigned IP addresses:
[ve7alb@ca-vic-cu-router02] > /ip address print
Flags: X - disabled, I - invalid, D - dynamic
# ADDRESS NETWORK INTERFACE
0 ;;; cipherkey WAN
208.110.114.235/29 208.110.114.232 ether2
1 44.135.193.129/8 44.0.0.0 ucsd-gw
2 ;;; 44.135.193 lan
44.135.192.33/29 44.135.192.32 ucsd-gw
3 44.135.193.18/32 44.135.193.18 ucsd-gw
4 44.135.193.130/32 44.135.193.130 ucsd-gw
It's very strange, when I ping Mark's IP I can see the IPIP packets
going out, but nothing coming back and after examining the packet
capture from Mark's end I can that he is sending IPIP packets to the
correct router, but I never receive them.
I'll check firewall rules on my upstream router and see if there's
something strange going on there.
On 5/4/2017 10:51 PM, Marius Petrescu wrote:
> (Please trim inclusions from previous messages)
> _______________________________________________
> 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(a)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(a)hamradio.ucsd.edu
>>>>
https://u4477715.ct.sendgrid.net/wf/click?upn=vS4GjSiF-2F5vYmfX5tr6ez81-2Fe…
>>>>
>>>>
>>>