12 Mar
2022
12 Mar
'22
2:06 p.m.
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
13 Mar
13 Mar
5:57 a.m.
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
10:36 a.m.
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
10:43 a.m.
Chris,
If your coordinator hasn't responded yet, you can contact me off list with
your Call sign and your DNS request. I can take care of that for you now.
--Ronnie
W0rdm
On Sun, Mar 13, 2022 at 9:39 AM 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
12:51 p.m.
Hi Chris,
It is better to contact the coordinator direct, e.g. email, but if you’re not in touch
with your local coordinator or there isn’t one local to you, then feel free to email me:
chris(a)ardc.net
73,
Chris
On 13 Mar 2022, at 14:44, R.D. Montgomery via 44Net
<44net(a)mailman.ampr.org> wrote:
Chris,
If your coordinator hasn't responded yet, you can contact me off list with
your Call sign and your DNS request. I can take care of that for you now.
--Ronnie
W0rdm
On Sun, Mar 13, 2022 at 9:39 AM 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
my
edgerouter 8.
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net 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 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
1:18 p.m.
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
1:36 p.m.
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
1:47 p.m.
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
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
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 
3:02 p.m.
will do
ChrisN6LXX
On Sunday, March 13, 2022, 10:51:45 AM PDT, Rob PE1CHL via 44Net
<44net(a)mailman.ampr.org> wrote:
It would be considerate to others when you add your callsign to your mails
when that is not already part of your fullname or mail address.
Rob PE1CHL
On 3/13/22 18:47, C B via 44Net wrote:
Ok cool, i will wait.
Thanks for the reply!
Chris
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
14 Mar
14 Mar
7:56 p.m.
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
_________________________________________
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
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 
8:14 p.m.
Chris,
What's your domain name? I tried n6lxx.ampr.org and it does not show as a valid name.
73 Jim KY2D
-----Original Message-----
From: 44Net <44net-bounces+jim.kutsch=ky2d.com(a)mailman.ampr.org> On Behalf Of C B
via 44Net
Sent: Monday, March 14, 2022 19:56
To: 44Net general discussion <44net(a)mailman.ampr.org>
Cc: C B <harvard5362(a)yahoo.com>
Subject: Re: [44net] Help with first time setup on a edgerouter
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
_________________________________________
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
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
15 Mar
15 Mar
4:29 a.m.
Try 137.n6lxx.ampr.org thru 142.n6lxx.ampr.org
Chris - G1FEF
On 15 Mar 2022, at 00:14, Jim Kutsch KY2D via 44Net
<44net(a)mailman.ampr.org> wrote:
Chris,
What's your domain name? I tried n6lxx.ampr.org and it does not show as a valid
name.
73 Jim KY2D
-----Original Message-----
From: 44Net <44net-bounces+jim.kutsch=ky2d.com(a)mailman.ampr.org> On Behalf Of C B
via 44Net
Sent: Monday, March 14, 2022 19:56
To: 44Net general discussion <44net(a)mailman.ampr.org>
Cc: C B <harvard5362(a)yahoo.com>
Subject: Re: [44net] Help with first time setup on a edgerouter
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
_________________________________________
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 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
7:13 a.m.
HI the following are the domain names.
137.n6lxx.ampr.org 44.16.0.137138.n6lxx.ampr.org 44.16.0.138139.n6lxx.ampr.org 44.16.0.139140.n6lxx.ampr.org 44.16.0.140141.n6lxx.ampr.org 44.16.0.141
142.n6lxx.ampr.org 44.16.0.142
Chris
N6LXX
On Tuesday, March 15, 2022, 01:21:11 AM PDT, Jim Kutsch KY2D via 44Net
<44net(a)mailman.ampr.org> wrote:
Chris,
What's your domain name? I tried n6lxx.ampr.org and it does not show as a valid name.
73 Jim KY2D
-----Original Message-----
From: 44Net <44net-bounces+jim.kutsch=ky2d.com(a)mailman.ampr.org> On Behalf Of C B
via 44Net
Sent: Monday, March 14, 2022 19:56
To: 44Net general discussion <44net(a)mailman.ampr.org>
Cc: C B <harvard5362(a)yahoo.com>
Subject: Re: [44net] Help with first time setup on a edgerouter
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
_________________________________________
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
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 
14 Mar
14 Mar
8:23 p.m.
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
_________________________________________
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
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 
8:31 p.m.
Yes agreed, use the second set on the wiki
https://wiki.ampr.org/wiki/Installing_ampr-ripd_on_a_Ubiquiti_EdgeRouter_or…
Don't try and use the first or a combination both... It'll lead you
down a very confusing path (ask me how I know ;))
I used the second for an erX and the instructions worked great.
Andrew, K1YMI
On Mon, 2022-03-14 at 19:23 -0500, Lee D Bengston via 44Net 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
_________________________________________
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 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
15 Mar
15 Mar
7:12 a.m.
Hi
Perhaps a dumb question is the second set compatible with a edge router 8?
On Monday, March 14, 2022, 05:32:51 PM PDT, Andrew - K1YMI via 44Net
<44net(a)mailman.ampr.org> wrote:
Yes agreed, use the second set on the wiki
https://wiki.ampr.org/wiki/Installing_ampr-ripd_on_a_Ubiquiti_EdgeRouter_or…
Don't try and use the first or a combination both... It'll lead you
down a very confusing path (ask me how I know ;))
I used the second for an erX and the instructions worked great.
Andrew, K1YMI
On Mon, 2022-03-14 at 19:23 -0500, Lee D Bengston via 44Net 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:
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
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
_________________________________________
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 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 
7:18 a.m.
The ER-8 uses a MIPS64 processor, as the ER3 light.
The setup steps should be similar and the executable for the ER3 should
run just fine.
I had no means to test it on every possible hardware, since I do not own
all ER variants.
Marius, YO2LOJ
On 15/03/2022 13:12, C B via 44Net wrote:
Hi
Perhaps a dumb question is the second set compatible with a edge router 8?
On Monday, March 14, 2022, 05:32:51 PM PDT, Andrew - K1YMI via 44Net
<44net(a)mailman.ampr.org> wrote:
Yes agreed, use the second set on the wiki
https://wiki.ampr.org/wiki/Installing_ampr-ripd_on_a_Ubiquiti_EdgeRouter_or…
Don't try and use the first or a combination both... It'll lead you
down a very confusing path (ask me how I know ;))
I used the second for an erX and the instructions worked great.
Andrew, K1YMI
On Mon, 2022-03-14 at 19:23 -0500, Lee D Bengston via 44Net 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:
_________________________________________
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 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
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net 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
7:26 a.m.
Marius
Thank you for letting me know that it should work with my router.
The original configuration will be reloaded and upon returning tonight from work i will
try the second method.
Thank you for your help.
Chris N6LXX
On Tuesday, March 15, 2022, 04:19:12 AM PDT, Marius Petrescu via 44Net
<44net(a)mailman.ampr.org> wrote:
The ER-8 uses a MIPS64 processor, as the ER3 light.
The setup steps should be similar and the executable for the ER3 should
run just fine.
I had no means to test it on every possible hardware, since I do not own
all ER variants.
Marius, YO2LOJ
On 15/03/2022 13:12, C B via 44Net wrote:
Hi
Perhaps a dumb question is the second set compatible with a edge router 8?
On Monday, March 14, 2022, 05:32:51 PM PDT, Andrew - K1YMI via 44Net
<44net(a)mailman.ampr.org> wrote:
Yes agreed, use the second set on the wiki
https://wiki.ampr.org/wiki/Installing_ampr-ripd_on_a_Ubiquiti_EdgeRouter_or…
Don't try and use the first or a combination both... It'll lead you
down a very confusing path (ask me how I know ;))
I used the second for an erX and the instructions worked great.
Andrew, K1YMI
On Mon, 2022-03-14 at 19:23 -0500, Lee D Bengston via 44Net wrote:
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
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:
_________________________________________
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
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
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net 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
7:33 a.m.
Marius
On the edgerouter 8 that is in use it is running v2.0.9 hotfix2.
Should this firmware be ok as it is not on the list in the wiki?
Thank you
Chris
N6LXX
On Tuesday, March 15, 2022, 04:27:03 AM PDT, C B via 44Net
<44net(a)mailman.ampr.org> wrote:
Marius
Thank you for letting me know that it should work with my router.
The original configuration will be reloaded and upon returning tonight from work i will
try the second method.
Thank you for your help.
Chris N6LXX
On Tuesday, March 15, 2022, 04:19:12 AM PDT, Marius Petrescu via 44Net
<44net(a)mailman.ampr.org> wrote:
The ER-8 uses a MIPS64 processor, as the ER3 light.
The setup steps should be similar and the executable for the ER3 should
run just fine.
I had no means to test it on every possible hardware, since I do not own
all ER variants.
Marius, YO2LOJ
On 15/03/2022 13:12, C B via 44Net wrote:
Hi
Perhaps a dumb question is the second set compatible with a edge router 8?
On Monday, March 14, 2022, 05:32:51 PM PDT, Andrew - K1YMI via 44Net
<44net(a)mailman.ampr.org> wrote:
Yes agreed, use the second set on the wiki
https://wiki.ampr.org/wiki/Installing_ampr-ripd_on_a_Ubiquiti_EdgeRouter_or…
Don't try and use the first or a combination both... It'll lead you
down a very confusing path (ask me how I know ;))
I used the second for an erX and the instructions worked great.
Andrew, K1YMI
On Mon, 2022-03-14 at 19:23 -0500, Lee D Bengston via 44Net wrote:
_________________________________________
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
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:
_________________________________________
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
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
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net 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
7:36 a.m.
Yes, it runs fine.
On my ER3 I use v2.0.9-hotfix.2, too. I will update the wiki page...
And please provide feedback on success so I could add the ER-8 as
supported on the wiki page.
Marius, YO2LOJ
On 15/03/2022 13:33, C B via 44Net wrote:
Marius
On the edgerouter 8 that is in use it is running v2.0.9 hotfix2.
Should this firmware be ok as it is not on the list in the wiki?
Thank you
Chris
N6LXX
On Tuesday, March 15, 2022, 04:27:03 AM PDT, C B via 44Net
<44net(a)mailman.ampr.org> wrote:
Marius
Thank you for letting me know that it should work with my router.
The original configuration will be reloaded and upon returning tonight from work i will
try the second method.
Thank you for your help.
Chris N6LXX
On Tuesday, March 15, 2022, 04:19:12 AM PDT, Marius Petrescu via 44Net
<44net(a)mailman.ampr.org> wrote:
The ER-8 uses a MIPS64 processor, as the ER3 light.
The setup steps should be similar and the executable for the ER3 should
run just fine.
I had no means to test it on every possible hardware, since I do not own
all ER variants.
Marius, YO2LOJ
On 15/03/2022 13:12, C B via 44Net wrote:
Hi
Perhaps a dumb question is the second set compatible with a edge router 8?
On Monday, March 14, 2022, 05:32:51 PM PDT, Andrew - K1YMI via 44Net
<44net(a)mailman.ampr.org> wrote:
Yes agreed, use the second set on the wiki
https://wiki.ampr.org/wiki/Installing_ampr-ripd_on_a_Ubiquiti_EdgeRouter_or…
Don't try and use the first or a combination both... It'll lead you
down a very confusing path (ask me how I know ;))
I used the second for an erX and the instructions worked great.
Andrew, K1YMI
On Mon, 2022-03-14 at 19:23 -0500, Lee D Bengston via 44Net wrote:
_________________________________________
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 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:
_________________________________________
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 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
7:41 a.m.
Marius
Thank you for confirming this.
Chris
N6LXX
On Tuesday, March 15, 2022, 04:37:32 AM PDT, Marius Petrescu via 44Net
<44net(a)mailman.ampr.org> wrote:
Yes, it runs fine.
On my ER3 I use v2.0.9-hotfix.2, too. I will update the wiki page...
And please provide feedback on success so I could add the ER-8 as
supported on the wiki page.
Marius, YO2LOJ
On 15/03/2022 13:33, C B via 44Net wrote:
Marius
On the edgerouter 8 that is in use it is running v2.0.9 hotfix2.
Should this firmware be ok as it is not on the list in the wiki?
Thank you
Chris
N6LXX
On Tuesday, March 15, 2022, 04:27:03 AM PDT, C B via 44Net
<44net(a)mailman.ampr.org> wrote:
Marius
Thank you for letting me know that it should work with my router.
The original configuration will be reloaded and upon returning tonight from work i will
try the second method.
Thank you for your help.
Chris N6LXX
On Tuesday, March 15, 2022, 04:19:12 AM PDT, Marius Petrescu via 44Net
<44net(a)mailman.ampr.org> wrote:
The ER-8 uses a MIPS64 processor, as the ER3 light.
The setup steps should be similar and the executable for the ER3 should
run just fine.
I had no means to test it on every possible hardware, since I do not own
all ER variants.
Marius, YO2LOJ
On 15/03/2022 13:12, C B via 44Net wrote:
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
Hi
Perhaps a dumb question is the second set compatible with a edge router 8?
On Monday, March 14, 2022, 05:32:51 PM PDT, Andrew - K1YMI via 44Net
<44net(a)mailman.ampr.org> wrote:
Yes agreed, use the second set on the wiki
https://wiki.ampr.org/wiki/Installing_ampr-ripd_on_a_Ubiquiti_EdgeRouter_or…
Don't try and use the first or a combination both... It'll lead you
down a very confusing path (ask me how I know ;))
I used the second for an erX and the instructions worked great.
Andrew, K1YMI
On Mon, 2022-03-14 at 19:23 -0500, Lee D Bengston via 44Net wrote:
_________________________________________
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
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:
_________________________________________
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 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
10:09 p.m.
Hi
Having completed the setup up to the point of the following##
If you want to allow access to the router itself, the rules should include the same as for
the forward section.
If router access should not be permitted, then only add rule number 3
(established/related) from above:
##
Being unsure of the firewall rules setup the rest of the instructions were completed up
to
##
Remember to also set up the proper firewall rules to allow or disallow access to your
hosts (if you use the rules as described in the previous chapter, 44net hosts will be
allowed to access your whole network, while access from the internet is prohibited).
##
Questions if i read this correctly i should have access to the 44 net without the internet
having access to my 44 net address.
How can the router be tested? (what can i try to ping for example)
Do i need to wait 24 hours for anything to propagate?
One other note from the other interface (normal interface 10.0.4.1) I can not longer
connect to http://www.ampr.org however the rest of the internet connections seem to work
as normal. As ampr.org resolves to 44.0.0.1 is the router sending the normal traffic for
my other network interfaces to IPIP tunnel for the 44 net?
As the statis wizard sounds like a good thing to have, however thus far i can not figure
out how to install it.
Any help is greatly appreciated.
Chris
N6LXX
On Tuesday, March 15, 2022, 04:41:37 AM PDT, C B via 44Net
<44net(a)mailman.ampr.org> wrote:
Marius
Thank you for confirming this.
Chris
N6LXX
On Tuesday, March 15, 2022, 04:37:32 AM PDT, Marius Petrescu via 44Net
<44net(a)mailman.ampr.org> wrote:
Yes, it runs fine.
On my ER3 I use v2.0.9-hotfix.2, too. I will update the wiki page...
And please provide feedback on success so I could add the ER-8 as
supported on the wiki page.
Marius, YO2LOJ
On 15/03/2022 13:33, C B via 44Net wrote:
Marius
On the edgerouter 8 that is in use it is running v2.0.9 hotfix2.
Should this firmware be ok as it is not on the list in the wiki?
Thank you
Chris
N6LXX
On Tuesday, March 15, 2022, 04:27:03 AM PDT, C B via 44Net
<44net(a)mailman.ampr.org> wrote:
Marius
Thank you for letting me know that it should work with my router.
The original configuration will be reloaded and upon returning tonight from work i will
try the second method.
Thank you for your help.
Chris N6LXX
On Tuesday, March 15, 2022, 04:19:12 AM PDT, Marius Petrescu via 44Net
<44net(a)mailman.ampr.org> wrote:
The ER-8 uses a MIPS64 processor, as the ER3 light.
The setup steps should be similar and the executable for the ER3 should
run just fine.
I had no means to test it on every possible hardware, since I do not own
all ER variants.
Marius, YO2LOJ
On 15/03/2022 13:12, C B via 44Net wrote:
_________________________________________
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
Hi
Perhaps a dumb question is the second set compatible with a edge router 8?
On Monday, March 14, 2022, 05:32:51 PM PDT, Andrew - K1YMI via 44Net
<44net(a)mailman.ampr.org> wrote:
Yes agreed, use the second set on the wiki
https://wiki.ampr.org/wiki/Installing_ampr-ripd_on_a_Ubiquiti_EdgeRouter_or…
Don't try and use the first or a combination both... It'll lead you
down a very confusing path (ask me how I know ;))
I used the second for an erX and the instructions worked great.
Andrew, K1YMI
On Mon, 2022-03-14 at 19:23 -0500, Lee D Bengston via 44Net wrote:
_________________________________________
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
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:
_________________________________________
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 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
10:51 p.m.
Hi,
No need to wait. You can always set up a 44net subnet on one of your
network interfaces.
If you followed the steps described, the rules will allow access to your
44net hosts from amp, but not from the internet.
(rules being 44<->44 ok, 44<->others no).
Regarding the ampr.org/44.0.0.1 access, that is an issue, I'm looking
for a workaround.
To install the wizard, go to the ER wizard tab, and click the small (+)
next to the 'Feature wizard' title on the left.
A dialog will open and then choose "Upload a file" and upload the one
mentioned in the wiki (you need to download it to your machine).
Marius, YO2LOJ
On 16/03/2022 04:09, C B via 44Net wrote:
Hi
Having completed the setup up to the point of the following##
If you want to allow access to the router itself, the rules should include the same as
for the forward section.
If router access should not be permitted, then only add rule number 3
(established/related) from above:
##
Being unsure of the firewall rules setup the rest of the instructions were completed up
to
##
Remember to also set up the proper firewall rules to allow or disallow access to your
hosts (if you use the rules as described in the previous chapter, 44net hosts will be
allowed to access your whole network, while access from the internet is prohibited).
##
Questions if i read this correctly i should have access to the 44 net without the
internet having access to my 44 net address.
How can the router be tested? (what can i try to ping for example)
Do i need to wait 24 hours for anything to propagate?
One other note from the other interface (normal interface 10.0.4.1) I can not longer
connect to http://www.ampr.org however the rest of the internet connections seem to work
as normal. As ampr.org resolves to 44.0.0.1 is the router sending the normal traffic for
my other network interfaces to IPIP tunnel for the 44 net?
As the statis wizard sounds like a good thing to have, however thus far i can not figure
out how to install it.
Any help is greatly appreciated.
Chris
N6LXX
11:33 p.m.
Ok, it seems I had a local setup problem, 44.0.0.1 access should be fine.
To test your setup, you can access the CLI via the button on the top
right of the router's web page.
There you can use ping and traceroute to test.
You could try my VPS host at 44.182.21.1
The described setup was meant to be used only from computers in your LAN
using 44 addresses. For the 44net to be accessible from other LAN
computers, you need to setup a masquerade rule in Firewall/NAT so that
your local addresses are translated to the GW's IP (which is not
necessary the best idea). The proper solution is to assign your subnet
to an ethernet interface and use 44net addresses for your machines...
This is the reason your ampr.org access is not working, since it now
goes through the gateway tunnel which expects 44net addresses for the
hosts behind it.
Marius, YO2LOJ
On 16/03/2022 04:51, Marius Petrescu via 44Net wrote:
Hi,
No need to wait. You can always set up a 44net subnet on one of your
network interfaces.
If you followed the steps described, the rules will allow access to
your 44net hosts from amp, but not from the internet.
(rules being 44<->44 ok, 44<->others no).
Regarding the ampr.org/44.0.0.1 access, that is an issue, I'm looking
for a workaround.
To install the wizard, go to the ER wizard tab, and click the small
(+) next to the 'Feature wizard' title on the left.
A dialog will open and then choose "Upload a file" and upload the one
mentioned in the wiki (you need to download it to your machine).
Marius, YO2LOJ
On 16/03/2022 04:09, C B via 44Net wrote:
Hi
Having completed the setup up to the point of the following##
If you want to allow access to the router itself, the rules should
include the same as for the forward section.
If router access should not be permitted, then only add rule number 3
(established/related) from above:
##
Being unsure of the firewall rules setup the rest of the instructions
were completed up to
##
Remember to also set up the proper firewall rules to allow or
disallow access to your hosts (if you use the rules as described in
the previous chapter, 44net hosts will be allowed to access your
whole network, while access from the internet is prohibited).
##
Questions if i read this correctly i should have access to the 44 net
without the internet having access to my 44 net address.
How can the router be tested? (what can i try to ping for example)
Do i need to wait 24 hours for anything to propagate?
One other note from the other interface (normal interface 10.0.4.1) I
can not longer connect to http://www.ampr.org however the rest of the
internet connections seem to work as normal. As ampr.org resolves to
44.0.0.1 is the router sending the normal traffic for my other
network interfaces to IPIP tunnel for the 44 net?
As the statis wizard sounds like a good thing to have, however thus
far i can not figure out how to install it.
Any help is greatly appreciated.
Chris
N6LXX
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
11:47 p.m.
Marius
44.182.21.1 does not respond to pings and the traceroute stops at the gateway.
Chris
N6LXX
On Tuesday, March 15, 2022, 08:36:29 PM PDT, Marius Petrescu via 44Net
<44net(a)mailman.ampr.org> wrote:
Ok, it seems I had a local setup problem, 44.0.0.1 access should be fine.
To test your setup, you can access the CLI via the button on the top
right of the router's web page.
There you can use ping and traceroute to test.
You could try my VPS host at 44.182.21.1
The described setup was meant to be used only from computers in your LAN
using 44 addresses. For the 44net to be accessible from other LAN
computers, you need to setup a masquerade rule in Firewall/NAT so that
your local addresses are translated to the GW's IP (which is not
necessary the best idea). The proper solution is to assign your subnet
to an ethernet interface and use 44net addresses for your machines...
This is the reason your ampr.org access is not working, since it now
goes through the gateway tunnel which expects 44net addresses for the
hosts behind it.
Marius, YO2LOJ
On 16/03/2022 04:51, Marius Petrescu via 44Net wrote:
Hi,
No need to wait. You can always set up a 44net subnet on one of your
network interfaces.
If you followed the steps described, the rules will allow access to
your 44net hosts from amp, but not from the internet.
(rules being 44<->44 ok, 44<->others no).
Regarding the ampr.org/44.0.0.1 access, that is an issue, I'm looking
for a workaround.
To install the wizard, go to the ER wizard tab, and click the small
(+) next to the 'Feature wizard' title on the left.
A dialog will open and then choose "Upload a file" and upload the one
mentioned in the wiki (you need to download it to your machine).
Marius, YO2LOJ
On 16/03/2022 04:09, C B via 44Net wrote:
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
Hi
Having completed the setup up to the point of the following##
If you want to allow access to the router itself, the rules should
include the same as for the forward section.
If router access should not be permitted, then only add rule number 3
(established/related) from above:
##
Being unsure of the firewall rules setup the rest of the instructions
were completed up to
##
Remember to also set up the proper firewall rules to allow or
disallow access to your hosts (if you use the rules as described in
the previous chapter, 44net hosts will be allowed to access your
whole network, while access from the internet is prohibited).
##
Questions if i read this correctly i should have access to the 44 net
without the internet having access to my 44 net address.
How can the router be tested? (what can i try to ping for example)
Do i need to wait 24 hours for anything to propagate?
One other note from the other interface (normal interface 10.0.4.1) I
can not longer connect to http://www.ampr.org however the rest of the
internet connections seem to work as normal. As ampr.org resolves to
44.0.0.1 is the router sending the normal traffic for my other
network interfaces to IPIP tunnel for the 44 net?
As the statis wizard sounds like a good thing to have, however thus
far i can not figure out how to install it.
Any help is greatly appreciated.
Chris
N6LXX
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
11:52 p.m.
Hi
To make 4.0.0.1 work from 10.0.4.xxx a static route was added 4.0.0.1/32 10
108.xxx.xxx.xxx
Chris
n6lxx
On Tuesday, March 15, 2022, 08:36:29 PM PDT, Marius Petrescu via 44Net
<44net(a)mailman.ampr.org> wrote:
Ok, it seems I had a local setup problem, 44.0.0.1 access should be fine.
To test your setup, you can access the CLI via the button on the top
right of the router's web page.
There you can use ping and traceroute to test.
You could try my VPS host at 44.182.21.1
The described setup was meant to be used only from computers in your LAN
using 44 addresses. For the 44net to be accessible from other LAN
computers, you need to setup a masquerade rule in Firewall/NAT so that
your local addresses are translated to the GW's IP (which is not
necessary the best idea). The proper solution is to assign your subnet
to an ethernet interface and use 44net addresses for your machines...
This is the reason your ampr.org access is not working, since it now
goes through the gateway tunnel which expects 44net addresses for the
hosts behind it.
Marius, YO2LOJ
On 16/03/2022 04:51, Marius Petrescu via 44Net wrote:
Hi,
No need to wait. You can always set up a 44net subnet on one of your
network interfaces.
If you followed the steps described, the rules will allow access to
your 44net hosts from amp, but not from the internet.
(rules being 44<->44 ok, 44<->others no).
Regarding the ampr.org/44.0.0.1 access, that is an issue, I'm looking
for a workaround.
To install the wizard, go to the ER wizard tab, and click the small
(+) next to the 'Feature wizard' title on the left.
A dialog will open and then choose "Upload a file" and upload the one
mentioned in the wiki (you need to download it to your machine).
Marius, YO2LOJ
On 16/03/2022 04:09, C B via 44Net wrote:
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
Hi
Having completed the setup up to the point of the following##
If you want to allow access to the router itself, the rules should
include the same as for the forward section.
If router access should not be permitted, then only add rule number 3
(established/related) from above:
##
Being unsure of the firewall rules setup the rest of the instructions
were completed up to
##
Remember to also set up the proper firewall rules to allow or
disallow access to your hosts (if you use the rules as described in
the previous chapter, 44net hosts will be allowed to access your
whole network, while access from the internet is prohibited).
##
Questions if i read this correctly i should have access to the 44 net
without the internet having access to my 44 net address.
How can the router be tested? (what can i try to ping for example)
Do i need to wait 24 hours for anything to propagate?
One other note from the other interface (normal interface 10.0.4.1) I
can not longer connect to http://www.ampr.org however the rest of the
internet connections seem to work as normal. As ampr.org resolves to
44.0.0.1 is the router sending the normal traffic for my other
network interfaces to IPIP tunnel for the 44 net?
As the statis wizard sounds like a good thing to have, however thus
far i can not figure out how to install it.
Any help is greatly appreciated.
Chris
N6LXX
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
11:55 p.m.
Hi
please excuse my typo
To make 44.0.0.1 work from 10.0.4.xxx a static route was added 44.0.0.1/32 10
108.xxx.xxx.xxx
Chris
n6lxx
On Tuesday, March 15, 2022, 08:53:38 PM PDT, C B via 44Net
<44net(a)mailman.ampr.org> wrote:
Hi
To make 4.0.0.1 work from 10.0.4.xxx a static route was added 4.0.0.1/32 10
108.xxx.xxx.xxx
Chris
n6lxx
On Tuesday, March 15, 2022, 08:36:29 PM PDT, Marius Petrescu via 44Net
<44net(a)mailman.ampr.org> wrote:
Ok, it seems I had a local setup problem, 44.0.0.1 access should be fine.
To test your setup, you can access the CLI via the button on the top
right of the router's web page.
There you can use ping and traceroute to test.
You could try my VPS host at 44.182.21.1
The described setup was meant to be used only from computers in your LAN
using 44 addresses. For the 44net to be accessible from other LAN
computers, you need to setup a masquerade rule in Firewall/NAT so that
your local addresses are translated to the GW's IP (which is not
necessary the best idea). The proper solution is to assign your subnet
to an ethernet interface and use 44net addresses for your machines...
This is the reason your ampr.org access is not working, since it now
goes through the gateway tunnel which expects 44net addresses for the
hosts behind it.
Marius, YO2LOJ
On 16/03/2022 04:51, Marius Petrescu via 44Net wrote:
Hi,
No need to wait. You can always set up a 44net subnet on one of your
network interfaces.
If you followed the steps described, the rules will allow access to
your 44net hosts from amp, but not from the internet.
(rules being 44<->44 ok, 44<->others no).
Regarding the ampr.org/44.0.0.1 access, that is an issue, I'm looking
for a workaround.
To install the wizard, go to the ER wizard tab, and click the small
(+) next to the 'Feature wizard' title on the left.
A dialog will open and then choose "Upload a file" and upload the one
mentioned in the wiki (you need to download it to your machine).
Marius, YO2LOJ
On 16/03/2022 04:09, C B via 44Net wrote:
_________________________________________
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
Hi
Having completed the setup up to the point of the following##
If you want to allow access to the router itself, the rules should
include the same as for the forward section.
If router access should not be permitted, then only add rule number 3
(established/related) from above:
##
Being unsure of the firewall rules setup the rest of the instructions
were completed up to
##
Remember to also set up the proper firewall rules to allow or
disallow access to your hosts (if you use the rules as described in
the previous chapter, 44net hosts will be allowed to access your
whole network, while access from the internet is prohibited).
##
Questions if i read this correctly i should have access to the 44 net
without the internet having access to my 44 net address.
How can the router be tested? (what can i try to ping for example)
Do i need to wait 24 hours for anything to propagate?
One other note from the other interface (normal interface 10.0.4.1) I
can not longer connect to http://www.ampr.org however the rest of the
internet connections seem to work as normal. As ampr.org resolves to
44.0.0.1 is the router sending the normal traffic for my other
network interfaces to IPIP tunnel for the 44 net?
As the statis wizard sounds like a good thing to have, however thus
far i can not figure out how to install it.
Any help is greatly appreciated.
Chris
N6LXX
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
24 Mar
24 Mar
3:14 p.m.
Hi,
Let me follow up on this open topic.
44.0.0.1 is not reachable via tunnel, so it should be dropped in the
command line to use the default gateway instead. Because the RIPv2 data
publishes the 44.0.0.1 endpoint as a /8 subnet, the subnet must be
specified a 44.0.0.1/8 in the -a command option for it to be actually
rejected (if not rejected, it will be added by ampr-ripd as a /32 route
due to special handling of this subnet)
ampr-ripd -s -t 44 -i tun44 -m 90-g pppoe0
-a44.0.0.1/8,44.128.1.0/24,44.128.2.0/24,your.gw.com/(adapt this list to your needs -
commna separated, no spaces)/
I also updated the wiki with the corrected info.
73,
Marius, YO2LOJ
On 16/03/2022 05:55, C B via 44Net wrote:
Hi
please excuse my typo
To make 44.0.0.1 work from 10.0.4.xxx a static route was added 44.0.0.1/32 10
108.xxx.xxx.xxx
Chris
n6lxx
On Tuesday, March 15, 2022, 08:53:38 PM PDT, C B via
44Net<44net(a)mailman.ampr.org> wrote:
Hi
To make 4.0.0.1 work from 10.0.4.xxx a static route was added 4.0.0.1/32 10
108.xxx.xxx.xxx
Chris
n6lxx
On Tuesday, March 15, 2022, 08:36:29 PM PDT, Marius Petrescu via
44Net<44net(a)mailman.ampr.org> wrote:
Ok, it seems I had a local setup problem, 44.0.0.1 access should be fine.
To test your setup, you can access the CLI via the button on the top
right of the router's web page.
There you can use ping and traceroute to test.
You could try my VPS host at 44.182.21.1
The described setup was meant to be used only from computers in your LAN
using 44 addresses. For the 44net to be accessible from other LAN
computers, you need to setup a masquerade rule in Firewall/NAT so that
your local addresses are translated to the GW's IP (which is not
necessary the best idea). The proper solution is to assign your subnet
to an ethernet interface and use 44net addresses for your machines...
This is the reason your ampr.org access is not working, since it now
goes through the gateway tunnel which expects 44net addresses for the
hosts behind it.
Marius, YO2LOJ
8:29 p.m.
Thank you
still trying to get this working.
going to start from scratch soon and see what happens.
On Thursday, March 24, 2022, 12:14:10 PM PDT, Marius Petrescu <marius(a)yo2loj.ro>
wrote:
Hi,
Let me follow up on this open topic.
44.0.0.1 is not reachable via tunnel, so it should be dropped in the command line to use
the default gateway instead. Because the RIPv2 data publishes the 44.0.0.1 endpoint as a
/8 subnet, the subnet must be specified a 44.0.0.1/8 in the -a command option for it to be
actually rejected (if not rejected, it will be added by ampr-ripd as a /32 route due to
special handling of this subnet)
ampr-ripd -s -t 44 -i tun44 -m 90 -g pppoe0 -a
44.0.0.1/8,44.128.1.0/24,44.128.2.0/24,your.gw.com (adapt this list to your needs - commna
separated, no spaces)
I also updated the wiki with the corrected info.
73,
Marius, YO2LOJ
On 16/03/2022 05:55, C B via 44Net wrote:
Hi
please excuse my typo
To make 44.0.0.1 work from 10.0.4.xxx a static route was added 44.0.0.1/32 10
108.xxx.xxx.xxx
Chris
n6lxx
On Tuesday, March 15, 2022, 08:53:38 PM PDT, C B via 44Net
<44net(a)mailman.ampr.org> wrote:
Hi
To make 4.0.0.1 work from 10.0.4.xxx a static route was added 4.0.0.1/32 10
108.xxx.xxx.xxx
Chris
n6lxx
On Tuesday, March 15, 2022, 08:36:29 PM PDT, Marius Petrescu via 44Net
<44net(a)mailman.ampr.org> wrote:
Ok, it seems I had a local setup problem, 44.0.0.1 access should be fine.
To test your setup, you can access the CLI via the button on the top
right of the router's web page.
There you can use ping and traceroute to test.
You could try my VPS host at 44.182.21.1
The described setup was meant to be used only from computers in your LAN
using 44 addresses. For the 44net to be accessible from other LAN
computers, you need to setup a masquerade rule in Firewall/NAT so that
your local addresses are translated to the GW's IP (which is not
necessary the best idea). The proper solution is to assign your subnet
to an ethernet interface and use 44net addresses for your machines...
This is the reason your ampr.org access is not working, since it now
goes through the gateway tunnel which expects 44net addresses for the
hosts behind it.
Marius, YO2LOJ
15 Mar
15 Mar
11:41 p.m.
Hi
The wizard installed easily thank you for your hard work on this project.
The wizard appears to indicate that the RIP is being downloaded as it is very populated
with routes.
A interface was set up with 44.16.0.137 and a 44NET and a computer set to 138 with the
gateway of 137 and using pingplotter a few random 44NET ip addresses (not in my subnet)
where entered and the traceroute did not show past my gateway.
Is there a ip address that should be pingable that can be tried?
Thank you
Chris
N6lxx
On Tuesday, March 15, 2022, 07:51:17 PM PDT, Marius Petrescu <marius(a)yo2loj.ro>
wrote:
Hi,
No need to wait. You can always set up a 44net subnet on one of your
network interfaces.
If you followed the steps described, the rules will allow access to your
44net hosts from amp, but not from the internet.
(rules being 44<->44 ok, 44<->others no).
Regarding the ampr.org/44.0.0.1 access, that is an issue, I'm looking
for a workaround.
To install the wizard, go to the ER wizard tab, and click the small (+)
next to the 'Feature wizard' title on the left.
A dialog will open and then choose "Upload a file" and upload the one
mentioned in the wiki (you need to download it to your machine).
Marius, YO2LOJ
On 16/03/2022 04:09, C B via 44Net wrote:
Hi
Having completed the setup up to the point of the following##
If you want to allow access to the router itself, the rules should include the same as
for the forward section.
If router access should not be permitted, then only add rule number 3
(established/related) from above:
##
Being unsure of the firewall rules setup the rest of the instructions were completed up
to
##
Remember to also set up the proper firewall rules to allow or disallow access to your
hosts (if you use the rules as described in the previous chapter, 44net hosts will be
allowed to access your whole network, while access from the internet is prohibited).
##
Questions if i read this correctly i should have access to the 44 net without the
internet having access to my 44 net address.
How can the router be tested? (what can i try to ping for example)
Do i need to wait 24 hours for anything to propagate?
One other note from the other interface (normal interface 10.0.4.1) I can not longer
connect to http://www.ampr.org however the rest of the internet connections seem to work
as normal. As ampr.org resolves to 44.0.0.1 is the router sending the normal traffic for
my other network interfaces to IPIP tunnel for the 44 net?
As the statis wizard sounds like a good thing to have, however thus far i can not figure
out how to install it.
Any help is greatly appreciated.
Chris
N6LXX
14 Mar
14 Mar
8:32 p.m.
Yes agreed, use the second set on the wiki
https://wiki.ampr.org/wiki/Installing_ampr-ripd_on_a_Ubiquiti_EdgeRouter_or…
Don't try and use the first or a combination both... It'll lead you
down a very confusing path (ask me how I know ;))
I used the second for an erX and the instructions worked great.
Andrew, K1YMI
On Mon, 2022-03-14 at 19:23 -0500, Lee D Bengston via 44Net 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
_________________________________________
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 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
15 Mar
15 Mar
7:10 a.m.
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
_________________________________________
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
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
7:13 a.m.
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:
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
_________________________________________
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 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
7:19 a.m.
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:
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
_________________________________________
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 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
7:31 a.m.
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:
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
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
972
days inactive
985
days old
36 comments
9 participants
participants (9)
-
anpepper＠gmail.com -
C B -
Chris - G1FEF -
Chris Smith
-
Jim Kutsch KY2D -
Lee D Bengston -
Marius Petrescu -
R.D. Montgomery -
Rob PE1CHL