5 May
2017
5 May
'17
7:59 a.m.
Hi,
Sorry for the delay, I just had a look and I am able to ping 44.135.193.1
but not .130. I am going out as .254 inside source .255 outsource source.
However, .1 replies back to .254 without encapsulation. I get no response
from .130.
https://u4477715.ct.sendgrid.net/wf/click?upn=MJaTQVDJZogYIZySndf7y-2BCWLgZ…
root@newjersey:~# ip route get 44.135.193.130
44.135.193.130 via 208.110.114.235 dev tunl0 src 44.131.14.254
cache
root@newjersey:~# ip route get 44.135.193.1
44.135.193.1 via 208.110.114.235 dev tunl0 src 44.131.14.254
cache
root@newjersey:~# ip route get 208.110.114.235
208.110.114.235 via 45.63.20.1 dev eth0 src 44.131.14.255
cache root@newjersey:~# ping -w 3 44.135.193.1
PING 44.135.193.1 (44.135.193.1) 56(84) bytes of data.
64 bytes from 44.135.193.1: icmp_seq=1 ttl=51 time=108 ms
64 bytes from 44.135.193.1: icmp_seq=2 ttl=51 time=108 ms
64 bytes from 44.135.193.1: icmp_seq=3 ttl=51 time=107 ms
--- 44.135.193.1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2001ms
rtt min/avg/max/mdev = 107.470/107.997/108.355/0.380 ms
root@newjersey:~# ping -w 3 44.135.193.130
PING 44.135.193.130 (44.135.193.130) 56(84) bytes of data.
--- 44.135.193.130 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2008ms
Thanks,
Mike, M6XCV
On 5 May 2017 at 01:27, Christopher S. Munz-Michielin <christopher(a)ve7alb.ca
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=Ki4chJONuNfM0VomxEE-2BoYpt2g-…
>>> mfX5tr6ez81-2Fejubm4weNAlQoytz2H-2BHtaS0meDwSnNgU-2BpImERKh3
>>> ZrCub-2BbADpbbQ6OyRAEg-3D-3D_hzVA6CorwLLoBNMa4L2WJ-2FCatrCa3
>>> 3kwc-2F5ZLK3-2BWtKN60lvXrgkJHMidNOzydqe6GLLkaSSRPwCwQ4-2BPNs
>>> kl1nCGQ4MjajdweM7LaMpTJq7WtQ49sxIAGbx-2BlOeGDetfgBjhqDLSpTqU
>>> dX01MwCPthge1tzAGigEWl2cd1iF65W8z7-2Fs2QuqXebVpfclUiIiMUjIID
>>> tO7mgQ0pxYvfC-2FFyYUmM9CmGOpLMiJT2uLcU-3D
>>>
>>>