15 Mar
2022
15 Mar
'22
7:38 a.m.
Marius
The explanation was very informative.
And it appears that the wrong path was taken.
Thank you
Chris
On Tuesday, March 15, 2022, 04:32:11 AM PDT, Marius Petrescu via 44Net
<44net(a)mailman.ampr.org> wrote:
To be a part of the mesh network, a router needs to be able to talk to
all of the mesh partners directly via IPIP tunnels. In Linux
environments the tunnel driver supports multiple peers so this is
transparent to the user and the destinations are maintained via the
ampr-ripd daemon (or similar agents), or manually via an encap file.
Other systems, like the mikrotik routers, create a tunnel endpoint for
every mesh partner via scripting.
The single tunnel to amprgw will only allow you to access/be accessed
from the internet via amprgw using a static 44net address. Other than
that, there is no benefit of using such a tunnel. On the contrary, you
will create useless additional load on the gateway and have a higher
latency. You will not be able to access subnets in the mesh, only those
that are published via BGP on the public internet. So basically you are
better off using your own public IP if it is static, or if you do not
need a static IP, and do not want to access meshed computers.
Marius, YO2LOJ
On 15/03/2022 13:19, C B wrote:
Hi
Please help me to understand, the difference between the single tunnel
and a gateway part of the 44net mesh?
The primary use will be to use is connecting p-25 repeaters and
allstar link repeaters.
Thank you
Chris
N6LXX
On Tuesday, March 15, 2022, 04:13:47 AM PDT, Marius Petrescu
<marius(a)yo2loj.ro> wrote:
The first one only sets up a single tunnel to amprgw, not a gateway part
of the 44net mesh.
Marius, YO2LOJ
On 15/03/2022 13:10, C B via 44Net wrote:
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
HI
The first set was used as they seemed to better match the hardware
being used.
Chris
N6LXX
On Monday, March 14, 2022, 05:25:21 PM PDT, Lee D Bengston via
44Net
<44net(a)mailman.ampr.org> wrote:
Which set of instructions for the Edgerouter did you use? I used
the second
set in the Wiki, which is more complete. I recall
from a previous
discussion in this group that someone else tried the first set,
didn't have
any luck, and started over with the second set,
which worked.
Lee K5DAT
On Mon, Mar 14, 2022, 6:57 PM C B via 44Net <44net(a)mailman.ampr.org>
wrote:
> HI
> Still not able to ping to the internet or from the internet to the
> edgerouter.
> Outbound pings stop at the gateway on the edgerouter.
> When pining from the internet towards the edgerouter (from a different
> location) get as far as 132.239.255.50
> The the IPIP tunnel in the edgerouter appears up with traffic in both
> directions.
> Any help is greatly appreciated.
> Chris
> N6LXX
>
> On Sunday, March 13, 2022, 10:48:50 AM PDT, C B via 44Net <
> 44net(a)mailman.ampr.org> wrote:
>
> Ok cool, i will wait.
> Thanks for the reply!
> Chris
> On Sunday, March 13, 2022, 10:37:28 AM PDT, Chris Smith via
44Net <
> 44net(a)mailman.ampr.org> wrote:
>
> Hi Chris,
>
> Give it 24 hours, updates on the IPIP mesh don’t occur in realtime.
>
> 73,
> Chris - G1FEF
>
>
>
>> On 13 Mar 2022, at 17:18, C B via 44Net <44net(a)mailman.ampr.org>
wrote:
>>
>> Hi
>> The DNS records have been set up (thanks to Ronnie)
>> The DNS records seem to have propagated and are functional.
>> The router seems to have the tunnel active.
>> admin@EdgeRouter-8-Port:~$ show interfaces tunnel tun0tun0@NONE:
> <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1480 qdisc noqueue state
UNKNOWN
group
> default qlen 1 link/ipip 108.178.139.90
peer 169.228.34.84
> Description: Tunnel to AMPRNet gateway
>> RX: bytes packets errors dropped overrun mcast
> 4700856 13768 0 0 0 0 TX:
> bytes packets errors dropped carrier collisions
2586483
> 42788 20 0 20
0admin@EdgeRouter-8-Port
> :~$
>> However the tracert to 8.8.8.8 stops at the local router interface.
>> Any help greatly appreciated.
>> Thank you
>> Chris
>>
>> On Sunday, March 13, 2022, 07:38:18 AM PDT, C B via 44Net <
> 44net(a)mailman.ampr.org> wrote:
>> Thank you for the reply.
>> The request for DNS was sent thru the portal, by sending a message to
> the coordinator.
>> Is this the correct method to make this request? There has been no
> response.
>> Thank you.
>> Chris
>>
>> On Sunday, March 13, 2022, 03:51:20 AM PDT, Chris Smith via
44Net
<
> 44net(a)mailman.ampr.org> wrote:
>> Hi Chris,
>>
>> Did you register your IP in DNS? You need an A record for your IP
> address (any IP addresses you are routing) in order for it to pass
the UCSD
> gateway out to the internet.
>> You can do this by asking your local coordinator or by asking myself.
>>
>> 73,
>> Chris - G1FEF
>>
>>
>>
>>> On 12 Mar 2022, at 19:06, C B via 44Net <44net(a)mailman.ampr.org>
wrote:
>>>
>>> HI
>>> After receiving my ip address assignment i am trying to set 44net up
> on my edgerouter 8.
>>> Following the instructions for the edgerouter on the wiki, and
changing
> the port from eth2 to eth7 i as unable to
ping thru to the internet as
> described in the instructions.
>>> An edge router 4 was also set up using the wiki instructions and the
> same result of not being able to ping thru to 8.8.8.8 on the
edgerouter 4,
> thus i am continuing with the edgerouter 8 as
this would be my final
> configuration.
>>> From the CLI "show interfaces tunnel tun0" the response shows
traffic
> in both directions thus the tunnel appears to
be up.
>>> In order to test my configuration, a edge router 4 was programmed to
> simulate the UCSD end of the tunnel and a Layer 3 switch was used to
> simulate the internet connection.
>>> The test setup as able to pass the IPIP traffic between the
routers
as
> expected, this leads me to believe i may have
the setup correct or
at least
> very close.
>>> now i am at a loss of how to troubleshoot further.
>>> Any advice, tips, troubleshooting methods, or help of any kind is
> greatly appreciated.
>>> Thank you
>>> Chris
>>>
>>>
>>>
>>> _________________________________________
>>> 44Net mailing list
>>> 44Net(a)mailman.ampr.org
>>> https://mailman.ampr.org/mailman/listinfo/44net
>>>
>>> _________________________________________
>>> 44Net mailing list
>>> 44Net(a)mailman.ampr.org
>>> https://mailman.ampr.org/mailman/listinfo/44net
>>>
>>> _________________________________________
>>> 44Net mailing list
>>> 44Net(a)mailman.ampr.org
>>> https://mailman.ampr.org/mailman/listinfo/44net
>>>
>>> _________________________________________
>>> 44Net mailing list
>>> 44Net(a)mailman.ampr.org
>>> https://mailman.ampr.org/mailman/listinfo/44net
>>
>> _________________________________________
>> 44Net mailing list
>> 44Net(a)mailman.ampr.org
>> https://mailman.ampr.org/mailman/listinfo/44net
>>
>> _________________________________________
>> 44Net mailing list
>> 44Net(a)mailman.ampr.org
>> https://mailman.ampr.org/mailman/listinfo/44net
>>
>> _________________________________________
>> 44Net mailing list
>> 44Net(a)mailman.ampr.org
>> https://mailman.ampr.org/mailman/listinfo/44net
>>
> _________________________________________
> 44Net mailing list
> 44Net(a)mailman.ampr.org
> https://mailman.ampr.org/mailman/listinfo/44net
>
> _________________________________________
> 44Net mailing list
> 44Net(a)mailman.ampr.org
> https://mailman.ampr.org/mailman/listinfo/44net