17 Feb
2019
17 Feb
'19
8:07 p.m.
HI every one, I have an alocation and registered a gateway to do ipip encapsulation to
finally be able to run a gateway inside my local lan.
The gateway is a debain 9 computer with 2 nic. one connected to my lan (eth0) and another
wich will have the 44 net address network (eth1) I already put the first adress of the 44
allocation that I have on eth1. eth0 is for now on dhcp.
Now I've been reading, reading and re reading the wiki. there are so much stuff that I
am lost.
In my case, what deamon do I need? looking at this web page:
http://www.yo2loj.ro/hamprojects/ so is it ampr-ripd 2.4?? amprd 2.1??
there are also script that I found out about.. http://wiki.ampr.org/wiki/Startampr#Script
I got this configured. But I am really not sure of what I am supposed to do with it. And
on the wiki page there are allusion to some hourly script running to backup the rip table.
where are those?
Anyone can point me in the good direction so that I can finally have this running?
Thanks
Pierre
VE2PF
17 Feb
17 Feb
9:11 p.m.
Hello Pierre,
HI every one, I have an alocation and registered a
gateway to do ipip encapsulation to finally be able to run a gateway inside my local lan.
Welcome to AMPR! Ok. Log into the AMPR Portal:
- Click on the top level "Home" then "Allocations". Make sure
your
allocation shows up as expected and make sure you denote the subnet size
you have (say a /29). Remember that the first IP is the network
designation and the last IP is the broadcast designation. Neither of
these can be used for anything.
- Click on the top level "Gateways" and second level "Manage".
Here,
you need to add a gateway for your AMPR subnet. This will be your
external facing Internet IP address and this ideally needs to be a
STATIC IP from your ISP. If it's a dynamic IP that changes often,
you're going to need to update this gateway IP either via the AMPR web
interface of the the AMPR API whenever it changes. At the bottom of
this page, you will need to associate this gateway IP with your AMPR
allocation. Click "Add network" when done.
- Now configure your AMPR subnet on your eth1 interface of your
Debian box. Generally speaking this should be the first IP address of
the subnet.
- Next, you need to ask your AMPR coordinator to set a DNS name for
at least one of your AMPR addresses. For example, set the first usable
IP address to something like "ve2-pf-gw". By setting this AMPR name in
DNS, you then enable the RIP broadcasts to go to that IP address (your
Debian machine). If you don't set this DNS name, things can still work
but you'll need to manually load the ENCAPS files into your Debian box
via a script. Whenever the encaps file is updated, you'd need to reload
the file.
- To receive and populate the AMPR routes via the RIP broadcasts (if
you choose to go this route), I recommend to use YO2LOJ's ampr-ripd
program. The setup of the program is pretty strait forward.
After that, to get things working, you can either manually edit a copy
of the script at http://wiki.ampr.org/wiki/Startampr#Script as you
mentioned before but that script doesn't give you a lot of detail nor
comments. Alternatively, you can look at the script I use:
http://www.trinityos.com/HAM/CentosDigitalModes/usr/local/sbin/manual-ampr-…
In this script, you edit in the variables at the top and just manually
run it. It includes comments on how to troubleshoot things, it runs the
ampr-ripd program, etc. If it's working for you and you want it to run
every boot, you can start it from say /etc/rc.local.
To troubleshoot your network setup, you can use various tools websites
mentioned on http://wiki.ampr.org/wiki/Services
http://yo2tm.ampr.org/nettools.php
http://kb3vwg-010.ampr.org/tools
http://speedtest.ampr.org
http://n1uro.ampr.org/do.shtml
--David
KI6ZHD
The gateway is a debain 9 computer with 2 nic. one connected to my lan (eth0) and another
wich will have the 44 net address network (eth1) I already put the first adress of the 44
allocation that I have on eth1. eth0 is for now on dhcp.
Now I've been reading, reading and re reading the wiki. there are so much stuff that
I am lost.
In my case, what deamon do I need? looking at this web page:
http://www.yo2loj.ro/hamprojects/ so is it ampr-ripd 2.4?? amprd 2.1??
there are also script that I found out about..
http://wiki.ampr.org/wiki/Startampr#Script
I got this configured. But I am really not sure of what I am supposed to do with it. And
on the wiki page there are allusion to some hourly script running to backup the rip table.
where are those?
Anyone can point me in the good direction so that I can finally have this running?
Thanks
Pierre
VE2PF
9:28 p.m.
That wasn't from the Wiki.. that was from my fingers.
--David
KI6ZHD
On 02/17/2019 01:14 PM, Bill Vodall via 44Net wrote:
Welcome to
AMPR! Ok. Log into the AMPR Portal:
- Click on the top level "Home" then "Allocations". Make sure
your
Which page on the wiki was this? ;-)
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net 
9:41 p.m.
I've been struggling a bit with setup too. David, thanks for the supplementary setup
steps!
On Sun, Feb 17, 2019, at 2:28 PM, David Ranch wrote:
That wasn't from the Wiki.. that was from my fingers.
--David
KI6ZHD
On 02/17/2019 01:14 PM, Bill Vodall via 44Net wrote:
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
Welcome
to AMPR! Ok. Log into the AMPR Portal:
- Click on the top level "Home" then "Allocations". Make sure your
Which page on the wiki was this? ;-)
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
9:24 p.m.
Hi David,
First thank you for your message and taking the time to answer my question.
Your explaination is really well detailed and I am pretty sure I will get this working.
I dont have a fix IP but I do have a vps at OVH and I was planning on using a vpn bridge
to have a fix adress and have a few other service running on the vps.
But I wanted to first have a working gateway. Thanks again for the time you took to
answer.
Will keep the group posted on the project.
Pierre
VE2PF
________________________________
De : 44Net <44net-bounces+petem001=hotmail.com(a)mailman.ampr.org> de la part de David
Ranch <amprgw(a)trinnet.net>
Envoyé : 17 février 2019 16:11
À : AMPRNet working group
Objet : Re: [44net] Can't seem to grasp something
Hello Pierre,
HI every one, I have an alocation and registered a
gateway to do ipip encapsulation to finally be able to run a gateway inside my local lan.
Welcome to AMPR! Ok. Log into the AMPR Portal:
- Click on the top level "Home" then "Allocations". Make sure
your
allocation shows up as expected and make sure you denote the subnet size
you have (say a /29). Remember that the first IP is the network
designation and the last IP is the broadcast designation. Neither of
these can be used for anything.
- Click on the top level "Gateways" and second level "Manage".
Here,
you need to add a gateway for your AMPR subnet. This will be your
external facing Internet IP address and this ideally needs to be a
STATIC IP from your ISP. If it's a dynamic IP that changes often,
you're going to need to update this gateway IP either via the AMPR web
interface of the the AMPR API whenever it changes. At the bottom of
this page, you will need to associate this gateway IP with your AMPR
allocation. Click "Add network" when done.
- Now configure your AMPR subnet on your eth1 interface of your
Debian box. Generally speaking this should be the first IP address of
the subnet.
- Next, you need to ask your AMPR coordinator to set a DNS name for
at least one of your AMPR addresses. For example, set the first usable
IP address to something like "ve2-pf-gw". By setting this AMPR name in
DNS, you then enable the RIP broadcasts to go to that IP address (your
Debian machine). If you don't set this DNS name, things can still work
but you'll need to manually load the ENCAPS files into your Debian box
via a script. Whenever the encaps file is updated, you'd need to reload
the file.
- To receive and populate the AMPR routes via the RIP broadcasts (if
you choose to go this route), I recommend to use YO2LOJ's ampr-ripd
program. The setup of the program is pretty strait forward.
After that, to get things working, you can either manually edit a copy
of the script at http://wiki.ampr.org/wiki/Startampr#Script as you
mentioned before but that script doesn't give you a lot of detail nor
comments. Alternatively, you can look at the script I use:
http://www.trinityos.com/HAM/CentosDigitalModes/usr/local/sbin/manual-ampr-…
In this script, you edit in the variables at the top and just manually
run it. It includes comments on how to troubleshoot things, it runs the
ampr-ripd program, etc. If it's working for you and you want it to run
every boot, you can start it from say /etc/rc.local.
To troubleshoot your network setup, you can use various tools websites
mentioned on http://wiki.ampr.org/wiki/Services
http://yo2tm.ampr.org/nettools.php
http://kb3vwg-010.ampr.org/tools
http://speedtest.ampr.org
http://n1uro.ampr.org/do.shtml
--David
KI6ZHD
The gateway is a debain 9 computer with 2 nic. one connected to my lan (eth0) and another
wich will have the 44 net address network (eth1) I already put the first adress of the 44
allocation that I have on eth1. eth0 is for now on dhcp.
Now I've been reading, reading and re reading the wiki. there are so much stuff that
I am lost.
In my case, what deamon do I need? looking at this web page:
http://www.yo2loj.ro/hamprojects/ so is it ampr-ripd 2.4?? amprd 2.1??
there are also script that I found out about..
http://wiki.ampr.org/wiki/Startampr#Script
I got this configured. But I am really not sure of what I am supposed to do with it. And
on the wiki page there are allusion to some hourly script running to backup the rip table.
where are those?
Anyone can point me in the good direction so that I can finally have this running?
Thanks
Pierre
VE2PF
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
18 Feb
18 Feb
2:29 a.m.
HI to all,
One last thing before I start the script that David point me to.
my allocation is a /26 so my netmask is 255.255.255.192
But inside the script there is something I am not sure of:
#What is your allocated AMPR IP or AMPR gateway IP address and netmask
AMPRIP="44.135.51.0"
AMPRMASK="255.255.255.192"
# Alternative syntax when using the "ip" command
CIDRNM="32"
The CIDRNM value should it be "26"?
I dont want to fire any thing before being sur that I have it all ok. Not that it will
break something on my side..
I just dont want to break anything anywhere.
So if anyone can help confirm, thanks!
Pierre
VE2PF
________________________________
De : 44Net <44net-bounces+petem001=hotmail.com(a)mailman.ampr.org> de la part de David
Ranch <amprgw(a)trinnet.net>
Envoyé : 17 février 2019 16:11
À : AMPRNet working group
Objet : Re: [44net] Can't seem to grasp something
Hello Pierre,
HI every one, I have an alocation and registered a
gateway to do ipip encapsulation to finally be able to run a gateway inside my local lan.
Welcome to AMPR! Ok. Log into the AMPR Portal:
- Click on the top level "Home" then "Allocations". Make sure
your
allocation shows up as expected and make sure you denote the subnet size
you have (say a /29). Remember that the first IP is the network
designation and the last IP is the broadcast designation. Neither of
these can be used for anything.
- Click on the top level "Gateways" and second level "Manage".
Here,
you need to add a gateway for your AMPR subnet. This will be your
external facing Internet IP address and this ideally needs to be a
STATIC IP from your ISP. If it's a dynamic IP that changes often,
you're going to need to update this gateway IP either via the AMPR web
interface of the the AMPR API whenever it changes. At the bottom of
this page, you will need to associate this gateway IP with your AMPR
allocation. Click "Add network" when done.
- Now configure your AMPR subnet on your eth1 interface of your
Debian box. Generally speaking this should be the first IP address of
the subnet.
- Next, you need to ask your AMPR coordinator to set a DNS name for
at least one of your AMPR addresses. For example, set the first usable
IP address to something like "ve2-pf-gw". By setting this AMPR name in
DNS, you then enable the RIP broadcasts to go to that IP address (your
Debian machine). If you don't set this DNS name, things can still work
but you'll need to manually load the ENCAPS files into your Debian box
via a script. Whenever the encaps file is updated, you'd need to reload
the file.
- To receive and populate the AMPR routes via the RIP broadcasts (if
you choose to go this route), I recommend to use YO2LOJ's ampr-ripd
program. The setup of the program is pretty strait forward.
After that, to get things working, you can either manually edit a copy
of the script at http://wiki.ampr.org/wiki/Startampr#Script as you
mentioned before but that script doesn't give you a lot of detail nor
comments. Alternatively, you can look at the script I use:
http://www.trinityos.com/HAM/CentosDigitalModes/usr/local/sbin/manual-ampr-…
In this script, you edit in the variables at the top and just manually
run it. It includes comments on how to troubleshoot things, it runs the
ampr-ripd program, etc. If it's working for you and you want it to run
every boot, you can start it from say /etc/rc.local.
To troubleshoot your network setup, you can use various tools websites
mentioned on http://wiki.ampr.org/wiki/Services
http://yo2tm.ampr.org/nettools.php
http://kb3vwg-010.ampr.org/tools
http://speedtest.ampr.org
http://n1uro.ampr.org/do.shtml
--David
KI6ZHD
The gateway is a debain 9 computer with 2 nic. one connected to my lan (eth0) and another
wich will have the 44 net address network (eth1) I already put the first adress of the 44
allocation that I have on eth1. eth0 is for now on dhcp.
Now I've been reading, reading and re reading the wiki. there are so much stuff that
I am lost.
In my case, what deamon do I need? looking at this web page:
http://www.yo2loj.ro/hamprojects/ so is it ampr-ripd 2.4?? amprd 2.1??
there are also script that I found out about..
http://wiki.ampr.org/wiki/Startampr#Script
I got this configured. But I am really not sure of what I am supposed to do with it. And
on the wiki page there are allusion to some hourly script running to backup the rip table.
where are those?
Anyone can point me in the good direction so that I can finally have this running?
Thanks
Pierre
VE2PF
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
3:09 a.m.
Hi David,
Comments in line
On Sun, Feb 17, 2019, 9:30 PM pete M via 44Net <44net(a)mailman.ampr.org
wrote:
73's for now! DE AF4H
HI to all,
One last thing before I start the script that David point me to.
my allocation is a /26 so my netmask is 255.255.255.192
But inside the script there is something I am not sure of:
#What is your allocated AMPR IP or AMPR gateway IP address and netmask
AMPRIP="44.135.51.0"
AMPRMASK="255.255.255.192"
# Alternative syntax when using the "ip" command
CIDRNM="32"
It looks to me that AMPRIP should be the 44-net IP address you wish to
assign your gateway - EX: 44.135.51.1.
The CIDRNM value should it be "26"?
Yes, it appears to me that way.
I dont want to fire any thing before being sur that I
have it all ok. Not
that it will break something on my side..
I just dont want to break anything anywhere.
Don't forget to go through the all the steps! For example, step 3 likely
will require you to uncomment (remove the preceding '#' symbol) the 'echo
1...' line.
Don't be afraid to break things too much... Fixing the breakages is a
wonderful way to learn!
So if anyone can help confirm, thanks!
Pierre
VE2PF
________________________________
De : 44Net <44net-bounces+petem001=hotmail.com(a)mailman.ampr.org> de la
part de David Ranch <amprgw(a)trinnet.net>
Envoyé : 17 février 2019 16:11
À : AMPRNet working group
Objet : Re: [44net] Can't seem to grasp something
Hello Pierre,
David, thanks very much for sharing your script! A couple questions for you
(if you see this):
1) would you mind posting this script to the wiki - or at least linking to
it?;
2) would you welcome contributions/patches to your file? If so, how would
you prefer to receive/process such?
HI every one, I have an alocation and registered
a gateway to do ipip
encapsulation to finally be able to run a gateway inside my
local lan.
Welcome to AMPR! Ok. Log into the AMPR Portal:
- Click on the top level "Home" then "Allocations". Make sure
your
allocation shows up as expected and make sure you denote the subnet size
you have (say a /29). Remember that the first IP is the network
designation and the last IP is the broadcast designation. Neither of
these can be used for anything.
- Click on the top level "Gateways" and second level "Manage".
Here,
you need to add a gateway for your AMPR subnet. This will be your
external facing Internet IP address and this ideally needs to be a
STATIC IP from your ISP. If it's a dynamic IP that changes often,
you're going to need to update this gateway IP either via the AMPR web
interface of the the AMPR API whenever it changes. At the bottom of
this page, you will need to associate this gateway IP with your AMPR
allocation. Click "Add network" when done.
- Now configure your AMPR subnet on your eth1 interface of your
Debian box. Generally speaking this should be the first IP address of
the subnet.
- Next, you need to ask your AMPR coordinator to set a DNS name for
at least one of your AMPR addresses. For example, set the first usable
IP address to something like "ve2-pf-gw". By setting this AMPR name in
DNS, you then enable the RIP broadcasts to go to that IP address (your
Debian machine). If you don't set this DNS name, things can still work
but you'll need to manually load the ENCAPS files into your Debian box
via a script. Whenever the encaps file is updated, you'd need to reload
the file.
- To receive and populate the AMPR routes via the RIP broadcasts (if
you choose to go this route), I recommend to use YO2LOJ's ampr-ripd
program. The setup of the program is pretty strait forward.
After that, to get things working, you can either manually edit a copy
of the script at http://wiki.ampr.org/wiki/Startampr#Script as you
mentioned before but that script doesn't give you a lot of detail nor
comments. Alternatively, you can look at the script I use:
http://www.trinityos.com/HAM/CentosDigitalModes/usr/local/sbin/manual-ampr-…
In this script, you edit in the variables at the top and just manually
run it. It includes comments on how to troubleshoot things, it runs the
ampr-ripd program, etc. If it's working for you and you want it to run
every boot, you can start it from say /etc/rc.local.
To troubleshoot your network setup, you can use various tools websites
mentioned on http://wiki.ampr.org/wiki/Services
http://yo2tm.ampr.org/nettools.php
http://kb3vwg-010.ampr.org/tools
http://speedtest.ampr.org
http://n1uro.ampr.org/do.shtml
--David
KI6ZHD
The gateway is a debain 9 computer with 2 nic. one connected to my lan
(eth0) and
another wich will have the 44 net address network (eth1) I
already put the first adress of the 44 allocation that I have on eth1. eth0
is for now on dhcp.
Now I've been reading, reading and re reading the wiki. there are so
much
stuff that I am lost.
In my case, what deamon do I need? looking at this web page:
http://www.yo2loj.ro/hamprojects/ so is it ampr-ripd 2.4?? amprd 2.1??
there are also script that I found out about..
http://wiki.ampr.org/wiki/Startampr#Script
I got this configured. But I am really not sure of what I am supposed to
do with
it. And on the wiki page there are allusion to some hourly script
running to backup the rip table. where are those?
Anyone can point me in the good direction so that I can finally have
this
running?
Thanks
Pierre
VE2PF
_________________________________________
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:34 a.m.
OK things did moved a lot since this morning frustration ;-)
Anyone looking at using that script. dont forget ( like I did) to install the net-tools
package as the script use it and debian 9 does not install it by default. (apt-get install
net-tools) .
On the next run of the script I did got a few interresting result:
root@44gateway:/home/ve2pf# sh manual-ampr-start.sh
-e
creating tunl0 interface
allowing TTL of 64 for traceroute support and Path-MTU discovery
adding default AMPR route to 169.228.34.84
Current number of routes in AMPR44 route table: 1
-e -----------------------------------------------------------------------
default via 169.228.34.84 dev tunl0 src 44.135.51.1 onlink
-e -----------------------------------------------------------------------
Enable Policy routing for traffic from 44 goes back to 44
RTNETLINK answers: File exists
RTNETLINK answers: File exists
-en Adding specific static AMPR routes to:
-en [n1uro]
-en [n6mef]
-en [lu9dce]
-en [ki6zhd-2]
Current number of routes in AMPR44 route table: 5
-e -----------------------------------------------------------------------
default via 169.228.34.84 dev tunl0 src 44.135.51.1 onlink
44.4.2.152/29 via 173.167.109.217 dev tunl0 proto static onlink
44.4.10.48 via 24.4.6.65 dev tunl0 proto static onlink
44.88.0.0/27 via 24.147.182.8 dev tunl0 proto static onlink
44.153.32.97 via 181.16.42.162 dev tunl0 proto static onlink
-e -----------------------------------------------------------------------
-e
Ping tests for specific AMPR hosts: (known previously working hosts)
-e
n1uro:
-e -------------------------------
PING 44.88.0.9 (44.88.0.9) 56(84) bytes of data.
--- 44.88.0.9 ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 4076ms
-e
n6mef
-e -------------------------------
PING 44.4.2.153 (44.4.2.153) 56(84) bytes of data.
--- 44.4.2.153 ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 4098ms
-e
Enabling ampr-ripd for route learning (daemon mode) and loading cached 44.x.x.x routes
-e
ampr-ripd already running; killing and restarting
-e It wont die.. error!
I will leave it running as I read that all the routes wont be loaded before some times.
will see what I will collect from that ;-)
Pierre
VE2PF
________________________________
De : Don McMorris <don.mcmorris(a)gmail.com>
Envoyé : 17 février 2019 22:09
À : AMPRNet working group
Cc : pete M
Objet : Re: [44net] Can't seem to grasp something
Hi David,
Comments in line
On Sun, Feb 17, 2019, 9:30 PM pete M via 44Net
<44net@mailman.ampr.org<mailto:44net@mailman.ampr.org> wrote:
HI to all,
One last thing before I start the script that David point me to.
my allocation is a /26 so my netmask is 255.255.255.192
But inside the script there is something I am not sure of:
#What is your allocated AMPR IP or AMPR gateway IP address and netmask
AMPRIP="44.135.51.0"
AMPRMASK="255.255.255.192"
# Alternative syntax when using the "ip" command
CIDRNM="32"
It looks to me that AMPRIP should be the 44-net IP address you wish to assign your gateway
- EX: 44.135.51.1.
The CIDRNM value should it be "26"?
Yes, it appears to me that way.
I dont want to fire any thing before being sur that I have it all ok. Not that it will
break something on my side..
I just dont want to break anything anywhere.
Don't forget to go through the all the steps! For example, step 3 likely will require
you to uncomment (remove the preceding '#' symbol) the 'echo 1...' line.
Don't be afraid to break things too much... Fixing the breakages is a wonderful way to
learn!
So if anyone can help confirm, thanks!
Pierre
VE2PF
________________________________
De : 44Net
<44net-bounces+petem001=hotmail.com@mailman.ampr.org<mailto:hotmail.com@mailman.ampr.org>>
de la part de David Ranch <amprgw@trinnet.net<mailto:amprgw@trinnet.net>>
Envoyé : 17 février 2019 16:11
À : AMPRNet working group
Objet : Re: [44net] Can't seem to grasp something
Hello Pierre,
HI every one, I have an alocation and registered a
gateway to do ipip encapsulation to finally be able to run a gateway inside my local lan.
Welcome to AMPR! Ok. Log into the AMPR Portal:
- Click on the top level "Home" then "Allocations". Make sure
your
allocation shows up as expected and make sure you denote the subnet size
you have (say a /29). Remember that the first IP is the network
designation and the last IP is the broadcast designation. Neither of
these can be used for anything.
- Click on the top level "Gateways" and second level "Manage".
Here,
you need to add a gateway for your AMPR subnet. This will be your
external facing Internet IP address and this ideally needs to be a
STATIC IP from your ISP. If it's a dynamic IP that changes often,
you're going to need to update this gateway IP either via the AMPR web
interface of the the AMPR API whenever it changes. At the bottom of
this page, you will need to associate this gateway IP with your AMPR
allocation. Click "Add network" when done.
- Now configure your AMPR subnet on your eth1 interface of your
Debian box. Generally speaking this should be the first IP address of
the subnet.
- Next, you need to ask your AMPR coordinator to set a DNS name for
at least one of your AMPR addresses. For example, set the first usable
IP address to something like "ve2-pf-gw". By setting this AMPR name in
DNS, you then enable the RIP broadcasts to go to that IP address (your
Debian machine). If you don't set this DNS name, things can still work
but you'll need to manually load the ENCAPS files into your Debian box
via a script. Whenever the encaps file is updated, you'd need to reload
the file.
- To receive and populate the AMPR routes via the RIP broadcasts (if
you choose to go this route), I recommend to use YO2LOJ's ampr-ripd
program. The setup of the program is pretty strait forward.
After that, to get things working, you can either manually edit a copy
of the script at http://wiki.ampr.org/wiki/Startampr#Script as you
mentioned before but that script doesn't give you a lot of detail nor
comments. Alternatively, you can look at the script I use:
http://www.trinityos.com/HAM/CentosDigitalModes/usr/local/sbin/manual-ampr-…
In this script, you edit in the variables at the top and just manually
run it. It includes comments on how to troubleshoot things, it runs the
ampr-ripd program, etc. If it's working for you and you want it to run
every boot, you can start it from say /etc/rc.local.
To troubleshoot your network setup, you can use various tools websites
mentioned on http://wiki.ampr.org/wiki/Services
http://yo2tm.ampr.org/nettools.php
http://kb3vwg-010.ampr.org/tools
http://speedtest.ampr.org
http://n1uro.ampr.org/do.shtml
--David
KI6ZHD
David, thanks very much for sharing your script! A couple questions for you (if you see
this):
1) would you mind posting this script to the wiki - or at least linking to it?;
2) would you welcome contributions/patches to your file? If so, how would you prefer to
receive/process such?
The gateway is a debain 9 computer with 2 nic. one connected to my lan (eth0) and another
wich will have the 44 net address network (eth1) I already put the first adress of the 44
allocation that I have on eth1. eth0 is for now on dhcp.
Now I've been reading, reading and re reading the wiki. there are so much stuff that
I am lost.
In my case, what deamon do I need? looking at this web page:
http://www.yo2loj.ro/hamprojects/ so is it ampr-ripd 2.4?? amprd 2.1??
there are also script that I found out about..
http://wiki.ampr.org/wiki/Startampr#Script
I got this configured. But I am really not sure of what I am supposed to do with it. And
on the wiki page there are allusion to some hourly script running to backup the rip table.
where are those?
Anyone can point me in the good direction so that I can finally have this running?
Thanks
Pierre
VE2PF
_________________________________________
44Net mailing list
44Net@mailman.ampr.org<mailto:44Net@mailman.ampr.org>
https://mailman.ampr.org/mailman/listinfo/44net
_________________________________________
44Net mailing list
44Net@mailman.ampr.org<mailto:44Net@mailman.ampr.org>
https://mailman.ampr.org/mailman/listinfo/44net
73's for now! DE AF4H
4:02 a.m.
So the tunel do come up. but I dont seem able to use it.
here is a look of the network state:
ip -c a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN
group default qlen 1000
link/ether 00:e0:29:3e:a9:99 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.195/24 brd 192.168.1.255 scope global eth0
valid_lft forever preferred_lft forever
inet6 fe80::2e0:29ff:fe3e:a999/64 scope link
valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen
1000
link/ether f4:ce:46:2b:a3:7b brd ff:ff:ff:ff:ff:ff
4: tunl0@NONE: <NOARP,UP,LOWER_UP> mtu 1480 qdisc noqueue state UNKNOWN group
default qlen 1
link/ipip 0.0.0.0 brd 0.0.0.0
inet 44.135.51.1/26 scope global tunl0
valid_lft forever preferred_lft forever
ANd the output of the script..
sh manual-ampr-start.sh
-e
creating tunl0 interface
allowing TTL of 64 for traceroute support and Path-MTU discovery
adding default AMPR route to 169.228.34.84
Current number of routes in AMPR44 route table: 1
-e -----------------------------------------------------------------------
default via 169.228.34.84 dev tunl0 src 44.135.51.1 onlink
-e -----------------------------------------------------------------------
Enable Policy routing for traffic from 44 goes back to 44
-en Adding specific static AMPR routes to:
-en [n1uro]
-en [n6mef]
-en [lu9dce]
-en [ki6zhd-2]
Current number of routes in AMPR44 route table: 5
-e -----------------------------------------------------------------------
default via 169.228.34.84 dev tunl0 src 44.135.51.1 onlink
44.4.2.152/29 via 173.167.109.217 dev tunl0 proto static onlink
44.4.10.48 via 24.4.6.65 dev tunl0 proto static onlink
44.88.0.0/27 via 24.147.182.8 dev tunl0 proto static onlink
44.153.32.97 via 181.16.42.162 dev tunl0 proto static onlink
-e -----------------------------------------------------------------------
-e
Ping tests for specific AMPR hosts: (known previously working hosts)
-e
n1uro:
-e -------------------------------
PING 44.88.0.9 (44.88.0.9) 56(84) bytes of data.
--- 44.88.0.9 ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 4088ms
-e
n6mef
-e -------------------------------
PING 44.4.2.153 (44.4.2.153) 56(84) bytes of data.
--- 44.4.2.153 ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 4078ms
-e
Enabling ampr-ripd for route learning (daemon mode) and loading cached 44.x.x.x routes
-e
Done
I can ping the ampr gateway (169.228.34.84) so that mean at least that I am not loosing
net connectivity. But a traceroute show that the traffic on the gateway is not using the
tunl0 I am connected by ssh to eth0 and what I find odd is that eth1 loose its IP adress
and seem down from the ip -c a command.
That will be it for tonight.
Thanks again for the help and all the people that help maintening this great tool that is
the 44 network!
Pierre
VE2PF
________________________________
De : 44Net <44net-bounces+petem001=hotmail.com(a)mailman.ampr.org> de la part de pete
M via 44Net <44net(a)mailman.ampr.org>
Envoyé : 17 février 2019 22:34
À : AMPRNet working group
Cc : pete M
Objet : Re: [44net] Can't seem to grasp something
OK things did moved a lot since this morning frustration ;-)
Anyone looking at using that script. dont forget ( like I did) to install the net-tools
package as the script use it and debian 9 does not install it by default. (apt-get install
net-tools) .
On the next run of the script I did got a few interresting result:
root@44gateway:/home/ve2pf# sh manual-ampr-start.sh
-e
creating tunl0 interface
allowing TTL of 64 for traceroute support and Path-MTU discovery
adding default AMPR route to 169.228.34.84
Current number of routes in AMPR44 route table: 1
-e -----------------------------------------------------------------------
default via 169.228.34.84 dev tunl0 src 44.135.51.1 onlink
-e -----------------------------------------------------------------------
Enable Policy routing for traffic from 44 goes back to 44
RTNETLINK answers: File exists
RTNETLINK answers: File exists
-en Adding specific static AMPR routes to:
-en [n1uro]
-en [n6mef]
-en [lu9dce]
-en [ki6zhd-2]
Current number of routes in AMPR44 route table: 5
-e -----------------------------------------------------------------------
default via 169.228.34.84 dev tunl0 src 44.135.51.1 onlink
44.4.2.152/29 via 173.167.109.217 dev tunl0 proto static onlink
44.4.10.48 via 24.4.6.65 dev tunl0 proto static onlink
44.88.0.0/27 via 24.147.182.8 dev tunl0 proto static onlink
44.153.32.97 via 181.16.42.162 dev tunl0 proto static onlink
-e -----------------------------------------------------------------------
-e
Ping tests for specific AMPR hosts: (known previously working hosts)
-e
n1uro:
-e -------------------------------
PING 44.88.0.9 (44.88.0.9) 56(84) bytes of data.
--- 44.88.0.9 ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 4076ms
-e
n6mef
-e -------------------------------
PING 44.4.2.153 (44.4.2.153) 56(84) bytes of data.
--- 44.4.2.153 ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 4098ms
-e
Enabling ampr-ripd for route learning (daemon mode) and loading cached 44.x.x.x routes
-e
ampr-ripd already running; killing and restarting
-e It wont die.. error!
I will leave it running as I read that all the routes wont be loaded before some times.
will see what I will collect from that ;-)
Pierre
VE2PF
________________________________
De : Don McMorris <don.mcmorris(a)gmail.com>
Envoyé : 17 février 2019 22:09
À : AMPRNet working group
Cc : pete M
Objet : Re: [44net] Can't seem to grasp something
Hi David,
Comments in line
On Sun, Feb 17, 2019, 9:30 PM pete M via 44Net
<44net@mailman.ampr.org<mailto:44net@mailman.ampr.org> wrote:
HI to all,
One last thing before I start the script that David point me to.
my allocation is a /26 so my netmask is 255.255.255.192
But inside the script there is something I am not sure of:
#What is your allocated AMPR IP or AMPR gateway IP address and netmask
AMPRIP="44.135.51.0"
AMPRMASK="255.255.255.192"
# Alternative syntax when using the "ip" command
CIDRNM="32"
It looks to me that AMPRIP should be the 44-net IP address you wish to assign your gateway
- EX: 44.135.51.1.
The CIDRNM value should it be "26"?
Yes, it appears to me that way.
I dont want to fire any thing before being sur that I have it all ok. Not that it will
break something on my side..
I just dont want to break anything anywhere.
Don't forget to go through the all the steps! For example, step 3 likely will require
you to uncomment (remove the preceding '#' symbol) the 'echo 1...' line.
Don't be afraid to break things too much... Fixing the breakages is a wonderful way to
learn!
So if anyone can help confirm, thanks!
Pierre
VE2PF
________________________________
De : 44Net
<44net-bounces+petem001=hotmail.com@mailman.ampr.org<mailto:hotmail.com@mailman.ampr.org>>
de la part de David Ranch <amprgw@trinnet.net<mailto:amprgw@trinnet.net>>
Envoyé : 17 février 2019 16:11
À : AMPRNet working group
Objet : Re: [44net] Can't seem to grasp something
Hello Pierre,
HI every one, I have an alocation and registered a
gateway to do ipip encapsulation to finally be able to run a gateway inside my local lan.
Welcome to AMPR! Ok. Log into the AMPR Portal:
- Click on the top level "Home" then "Allocations". Make sure
your
allocation shows up as expected and make sure you denote the subnet size
you have (say a /29). Remember that the first IP is the network
designation and the last IP is the broadcast designation. Neither of
these can be used for anything.
- Click on the top level "Gateways" and second level "Manage".
Here,
you need to add a gateway for your AMPR subnet. This will be your
external facing Internet IP address and this ideally needs to be a
STATIC IP from your ISP. If it's a dynamic IP that changes often,
you're going to need to update this gateway IP either via the AMPR web
interface of the the AMPR API whenever it changes. At the bottom of
this page, you will need to associate this gateway IP with your AMPR
allocation. Click "Add network" when done.
- Now configure your AMPR subnet on your eth1 interface of your
Debian box. Generally speaking this should be the first IP address of
the subnet.
- Next, you need to ask your AMPR coordinator to set a DNS name for
at least one of your AMPR addresses. For example, set the first usable
IP address to something like "ve2-pf-gw". By setting this AMPR name in
DNS, you then enable the RIP broadcasts to go to that IP address (your
Debian machine). If you don't set this DNS name, things can still work
but you'll need to manually load the ENCAPS files into your Debian box
via a script. Whenever the encaps file is updated, you'd need to reload
the file.
- To receive and populate the AMPR routes via the RIP broadcasts (if
you choose to go this route), I recommend to use YO2LOJ's ampr-ripd
program. The setup of the program is pretty strait forward.
After that, to get things working, you can either manually edit a copy
of the script at http://wiki.ampr.org/wiki/Startampr#Script as you
mentioned before but that script doesn't give you a lot of detail nor
comments. Alternatively, you can look at the script I use:
http://www.trinityos.com/HAM/CentosDigitalModes/usr/local/sbin/manual-ampr-…
In this script, you edit in the variables at the top and just manually
run it. It includes comments on how to troubleshoot things, it runs the
ampr-ripd program, etc. If it's working for you and you want it to run
every boot, you can start it from say /etc/rc.local.
To troubleshoot your network setup, you can use various tools websites
mentioned on http://wiki.ampr.org/wiki/Services
http://yo2tm.ampr.org/nettools.php
http://kb3vwg-010.ampr.org/tools
http://speedtest.ampr.org
http://n1uro.ampr.org/do.shtml
--David
KI6ZHD
David, thanks very much for sharing your script! A couple questions for you (if you see
this):
1) would you mind posting this script to the wiki - or at least linking to it?;
2) would you welcome contributions/patches to your file? If so, how would you prefer to
receive/process such?
The gateway is a debain 9 computer with 2 nic. one connected to my lan (eth0) and another
wich will have the 44 net address network (eth1) I already put the first adress of the 44
allocation that I have on eth1. eth0 is for now on dhcp.
Now I've been reading, reading and re reading the wiki. there are so much stuff that
I am lost.
In my case, what deamon do I need? looking at this web page:
http://www.yo2loj.ro/hamprojects/ so is it ampr-ripd 2.4?? amprd 2.1??
there are also script that I found out about..
http://wiki.ampr.org/wiki/Startampr#Script
I got this configured. But I am really not sure of what I am supposed to do with it. And
on the wiki page there are allusion to some hourly script running to backup the rip table.
where are those?
Anyone can point me in the good direction so that I can finally have this running?
Thanks
Pierre
VE2PF
_________________________________________
44Net mailing list
44Net@mailman.ampr.org<mailto:44Net@mailman.ampr.org>
https://mailman.ampr.org/mailman/listinfo/44net
_________________________________________
44Net mailing list
44Net@mailman.ampr.org<mailto:44Net@mailman.ampr.org>
https://mailman.ampr.org/mailman/listinfo/44net
73's for now! DE AF4H
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
5:53 p.m.
Hello Pete,
Anyone looking at using that script. dont forget (
like I did) to install the net-tools package as the script use it and debian 9 does not
install it by default. (apt-get install net-tools)
Ok.. I've made a comment about that in the script. I'll publish that
new version in a bit.
On the next run of the script I did got a few
interresting result:
root@44gateway:/home/ve2pf# sh manual-ampr-start.sh
-e
creating tunl0 interface
allowing TTL of 64 for traceroute support and Path-MTU discovery
adding default AMPR route to 169.228.34.84
Current number of routes in AMPR44 route table: 1
-e -----------------------------------------------------------------------
default via 169.228.34.84 dev tunl0 src 44.135.51.1 onlink
-e -----------------------------------------------------------------------
I'm not sure why you're seeing all these stray "-e" but the setup seems
to be running ok/
Enable Policy routing for traffic from 44 goes back to
44
RTNETLINK answers: File exists
RTNETLINK answers: File exists
Those are ok.
Ping tests for specific AMPR hosts: (known previously
working hosts)
-e
n1uro:
-e -------------------------------
PING 44.88.0.9 (44.88.0.9) 56(84) bytes of data.
--- 44.88.0.9 ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 4076ms
Many remote AMPR stations require to learn known good AMPR routes first
before they will respond to *any* traffic. What many they do is take
the route list either from the RIP announcements or ENCAPS file, parse
them, and then load them into an iptables firewall WHITELIST. This
sometimes can take some time and if your external IP address changes
often, you might have a challenge to have remote stations keep up in
allowing your traffic into their stations.
One station might NOT require that and that's the AMPRGW at 44.0.0.1.
I've added a ping check for that IP into my script.
ampr-ripd already running; killing and restarting
-e It wont die.. error!
I've added a sleep statement in the script to hopefully deal with this
but it's nothing to worry about.
I can ping the ampr gateway (169.228.34.84) so that
mean at least that I am not loosing net connectivity. But a traceroute show that the
traffic on the gateway is not using the tunl0 I am connected by ssh to eth0 and what I
find odd is that eth1 loose its IP adress and seem down from the ip -c a command.
With the setup created by this script, traffic going to an AMPR address will automatically
go through the tunl0 interface. One address you should be able to ping is the AMPR
default gateway. If you do that ping, you should see:
$ ping 44.0.0.1
PING 44.0.0.1 (44.0.0.1) 56(84) bytes of data.
64 bytes from 44.0.0.1: icmp_seq=1 ttl=62 time=31.2 ms
64 bytes from 44.0.0.1: icmp_seq=2 ttl=62 time=29.5 ms
64 bytes from 44.0.0.1: icmp_seq=3 ttl=62 time=28.5 ms
^C
--- 44.0.0.1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 28.538/29.804/31.295/1.136 ms
If you run tcpdump in another terminal window on your AMPR station using the interface
connected to your external ISP, you would see all the protocol 4 encapsulation and the
ICMP ping traffic inside it:
tcpdump -n -i eth0 not port 22 and not port 53 and not ip6 and not arp
--
09:21:53.861892 IP 96.78.144.186 > 169.228.34.84: IP 44.4.10.41 > 44.0.0.1: ICMP
echo request, id 24614, seq 1, length 64 (ipip-proto-4)
09:21:53.892722 IP 169.228.34.84 > 96.78.144.186: IP 44.0.0.1 > 44.4.10.41: ICMP
echo reply, id 24614, seq 1, length 64 (ipip-proto-4)
09:21:54.863001 IP 96.78.144.186 > 169.228.34.84: IP 44.4.10.41 > 44.0.0.1: ICMP
echo request, id 24614, seq 2, length 64 (ipip-proto-4)
09:21:54.892171 IP 169.228.34.84 > 96.78.144.186: IP 44.0.0.1 > 44.4.10.41: ICMP
echo reply, id 24614, seq 2, length 64 (ipip-proto-4)
09:21:55.864410 IP 96.78.144.186 > 169.228.34.84: IP 44.4.10.41 > 44.0.0.1: ICMP
echo request, id 24614, seq 3, length 64 (ipip-proto-4)
09:21:55.892531 IP 169.228.34.84 > 96.78.144.186: IP 44.0.0.1 > 44.4.10.41: ICMP
echo reply, id 24614, seq 3, length 64 (ipip-proto-4)
--
It's critical that you see both the requests AND responses and with that tcpdump
command, you can also use remote sites like http://yo2tm.ampr.org/nettools.php to ping
your AMPR IP address and see unsolicited protocol 4 / IPIP traffic is coming into your
AMPR station. If it's not, your ISP is probably blocking this traffic and you'll
need to either see if they are willing to unblock that traffic or setup a VPN with a IPIP
friendly VPN provider ( http://wiki.ampr.org/wiki/AMPRNet_VPN ).
--David
KI6ZHD
19 Feb
19 Feb
2:35 a.m.
its working!!!!!
got over 700 route when I do
ip route list table 44
I can ping some of the 44 network where none responded before.
but I dont seem to be reachable from the outside.
Anyone can ping 44.135.51.1?? from my windows machine I cant ping that adress and a
traceroute end at the edcu network.
Again a big thank you to David for the help and script.
And to all that works on the 44 network!
Pierre
VE2PF
________________________________
De : 44Net <44net-bounces+petem001=hotmail.com(a)mailman.ampr.org> de la part de David
Ranch <amprgw(a)trinnet.net>
Envoyé : 18 février 2019 12:53
À : AMPRNet working group
Objet : Re: [44net] Can't seem to grasp something
Hello Pete,
Anyone looking at using that script. dont forget (
like I did) to install the net-tools package as the script use it and debian 9 does not
install it by default. (apt-get install net-tools)
Ok.. I've made a comment about that in the script. I'll publish that
new version in a bit.
On the next run of the script I did got a few
interresting result:
root@44gateway:/home/ve2pf# sh manual-ampr-start.sh
-e
creating tunl0 interface
allowing TTL of 64 for traceroute support and Path-MTU discovery
adding default AMPR route to 169.228.34.84
Current number of routes in AMPR44 route table: 1
-e -----------------------------------------------------------------------
default via 169.228.34.84 dev tunl0 src 44.135.51.1 onlink
-e -----------------------------------------------------------------------
I'm not sure why you're seeing all these stray "-e" but the setup seems
to be running ok/
Enable Policy routing for traffic from 44 goes back to
44
RTNETLINK answers: File exists
RTNETLINK answers: File exists
Those are ok.
Ping tests for specific AMPR hosts: (known previously
working hosts)
-e
n1uro:
-e -------------------------------
PING 44.88.0.9 (44.88.0.9) 56(84) bytes of data.
--- 44.88.0.9 ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 4076ms
Many remote AMPR stations require to learn known good AMPR routes first
before they will respond to *any* traffic. What many they do is take
the route list either from the RIP announcements or ENCAPS file, parse
them, and then load them into an iptables firewall WHITELIST. This
sometimes can take some time and if your external IP address changes
often, you might have a challenge to have remote stations keep up in
allowing your traffic into their stations.
One station might NOT require that and that's the AMPRGW at 44.0.0.1.
I've added a ping check for that IP into my script.
ampr-ripd already running; killing and restarting
-e It wont die.. error!
I've added a sleep statement in the script to hopefully deal with this
but it's nothing to worry about.
I can ping the ampr gateway (169.228.34.84) so that
mean at least that I am not loosing net connectivity. But a traceroute show that the
traffic on the gateway is not using the tunl0 I am connected by ssh to eth0 and what I
find odd is that eth1 loose its IP adress and seem down from the ip -c a command.
With the setup created by this script, traffic going to an AMPR address will automatically
go through the tunl0 interface. One address you should be able to ping is the AMPR
default gateway. If you do that ping, you should see:
$ ping 44.0.0.1
PING 44.0.0.1 (44.0.0.1) 56(84) bytes of data.
64 bytes from 44.0.0.1: icmp_seq=1 ttl=62 time=31.2 ms
64 bytes from 44.0.0.1: icmp_seq=2 ttl=62 time=29.5 ms
64 bytes from 44.0.0.1: icmp_seq=3 ttl=62 time=28.5 ms
^C
--- 44.0.0.1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 28.538/29.804/31.295/1.136 ms
If you run tcpdump in another terminal window on your AMPR station using the interface
connected to your external ISP, you would see all the protocol 4 encapsulation and the
ICMP ping traffic inside it:
tcpdump -n -i eth0 not port 22 and not port 53 and not ip6 and not arp
--
09:21:53.861892 IP 96.78.144.186 > 169.228.34.84: IP 44.4.10.41 > 44.0.0.1: ICMP
echo request, id 24614, seq 1, length 64 (ipip-proto-4)
09:21:53.892722 IP 169.228.34.84 > 96.78.144.186: IP 44.0.0.1 > 44.4.10.41: ICMP
echo reply, id 24614, seq 1, length 64 (ipip-proto-4)
09:21:54.863001 IP 96.78.144.186 > 169.228.34.84: IP 44.4.10.41 > 44.0.0.1: ICMP
echo request, id 24614, seq 2, length 64 (ipip-proto-4)
09:21:54.892171 IP 169.228.34.84 > 96.78.144.186: IP 44.0.0.1 > 44.4.10.41: ICMP
echo reply, id 24614, seq 2, length 64 (ipip-proto-4)
09:21:55.864410 IP 96.78.144.186 > 169.228.34.84: IP 44.4.10.41 > 44.0.0.1: ICMP
echo request, id 24614, seq 3, length 64 (ipip-proto-4)
09:21:55.892531 IP 169.228.34.84 > 96.78.144.186: IP 44.0.0.1 > 44.4.10.41: ICMP
echo reply, id 24614, seq 3, length 64 (ipip-proto-4)
--
It's critical that you see both the requests AND responses and with that tcpdump
command, you can also use remote sites like http://yo2tm.ampr.org/nettools.php to ping
your AMPR IP address and see unsolicited protocol 4 / IPIP traffic is coming into your
AMPR station. If it's not, your ISP is probably blocking this traffic and you'll
need to either see if they are willing to unblock that traffic or setup a VPN with a IPIP
friendly VPN provider ( http://wiki.ampr.org/wiki/AMPRNet_VPN ).
--David
KI6ZHD
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
5:18 a.m.
Hello Pete,
Good to hear you're making progress though I can't ping your station:
$ ping -I tunl0 44.135.51.1
PING 44.135.51.1 (44.135.51.1) from 44.4.10.41 tunl0: 56(84) bytes of data.
^C
--- 44.135.51.1 ping statistics ---
6 packets transmitted, 0 received, 100% packet loss, time 5006ms
but YO2TM's system can!
http://yo2tm.ampr.org/nettools.php?host=44.135.51.1&submit=IPv4+Ping&am…
--David
KI6ZHD
6:28 a.m.
For your system to be reachable from the internet, it needs to have a
registered DNS entry at ampr.org.
Otherwise, the ampr gateway will not allow forwarding traffic and it
will be reachable from the 44 network only.
Marius, YO2LOJ
On 19.02.2019 04:35, pete M via 44Net wrote:
its working!!!!!
got over 700 route when I do
ip route list table 44
I can ping some of the 44 network where none responded before.
but I dont seem to be reachable from the outside.
Anyone can ping 44.135.51.1?? from my windows machine I cant ping that adress and a
traceroute end at the edcu network.
11:22 a.m.
Pete;
On 19.02.2019 04:35, pete M via 44Net wrote:
I can ping some of the 44 network where none responded
before.
but I dont seem to be reachable from the outside.
Anyone can ping 44.135.51.1?? from my windows machine I cant ping that adress and a
traceroute end at the edcu network.
n1uro@gw:~$ traceroute !$
traceroute 44.135.51.1
traceroute to 44.135.51.1 (44.135.51.1), 30 hops max, 60 byte packets
1 * * *
2 * * *
3 * * *
4 * * *
5 * * *
6 *^C
n1uro@gw:~$ fping !$
fping 44.135.51.1
44.135.51.1 is unreachable
n1uro@gw:~$
It may have something to do with either your ISP or your CPE. One way to
test is to read:
https://uronode.n1uro.com/linux/amprcable.html
I know many ISPs this side of the Atlantic anyway like to incorporate a
watchdog timer on their customer circuits which may be the cause of your
problem. I've also heard that some ISPs in your area may also limit the
number of tunnel connections you may have.
--
I love Tinder. It used to be I could get rejected by about a
dozen people a night. Thanks to modern technology I can be
rejected by hundreds. It's so much more efficient!
-----
73 de Brian N1URO
IPv6 Certified
SMTP: n1uro-at-n1uro.ampr.org
6:33 p.m.
Thanks Marius.
I already have a domain name (hamrad.ca) and I have a vps in a data center 30-50 km from
my qth.
I am planning on using a vpn to connexion to my vps so that I can use my vps as the entry
point to my segment. (OVH wont bpg annonce my segment already asked)
I will use my own DNS server on the vps. How should i fit all this in place and have my
segment connected to 44 and reachable from the rest of the world.
One of the first thing I want to setup is a machine that will do DMR to Dstar transcoding
and a SDR server for LF/MF/HF/VHF (airspyhf+) And I want user to be able to connect either
from the 44 net and the internet to both machine.
________________________________
De : 44Net <44net-bounces+petem001=hotmail.com(a)mailman.ampr.org> de la part de
Marius Petrescu <marius(a)yo2loj.ro>
Envoyé : 19 février 2019 01:28
À : 44net(a)mailman.ampr.org
Objet : Re: [44net] Can't seem to grasp something
For your system to be reachable from the internet, it needs to have a
registered DNS entry at ampr.org.
Otherwise, the ampr gateway will not allow forwarding traffic and it
will be reachable from the 44 network only.
Marius, YO2LOJ
On 19.02.2019 04:35, pete M via 44Net wrote:
its working!!!!!
got over 700 route when I do
ip route list table 44
I can ping some of the 44 network where none responded before.
but I dont seem to be reachable from the outside.
Anyone can ping 44.135.51.1?? from my windows machine I cant ping that adress and a
traceroute end at the edcu network.
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
7 p.m.
Pete,
Your allocation is 44.135.51.0/26.
It is too small to be announced by BGP. It will never be directly
reachable from the Internet. It *can* be reached from the Internet
via the tunnel encapsulation mechanism at UCSD, but in order for
that to work, you MUST have an address entry in the AMPR.ORG DNS
zone. No other domain will work for that mechanism.
Or you may be able to have a different subnet routed to you by
someone who is already announcing their larger subnet and is willing
to let you use a portion of their netspace via a VPN from their facility.
But you can't do it yourself with what you have.
- Brian
On Tue, Feb 19, 2019 at 06:33:27PM +0000, pete M via 44Net wrote:
Thanks Marius.
I already have a domain name (hamrad.ca) and I have a vps in a data center 30-50 km from
my qth.
I am planning on using a vpn to connexion to my vps so that I can use my vps as the entry
point to my segment. (OVH wont bpg annonce my segment already asked)
I will use my own DNS server on the vps. How should i fit all this in place and have my
segment connected to 44 and reachable from the rest of the world.
One of the first thing I want to setup is a machine that will do DMR to Dstar transcoding
and a SDR server for LF/MF/HF/VHF (airspyhf+) And I want user to be able to connect either
from the 44 net and the internet to both machine.
________________________________
De : 44Net <44net-bounces+petem001=hotmail.com(a)mailman.ampr.org> de la part de
Marius Petrescu <marius(a)yo2loj.ro>
Envoyé : 19 février 2019 01:28
À : 44net(a)mailman.ampr.org
Objet : Re: [44net] Can't seem to grasp something
For your system to be reachable from the internet, it needs to have a
registered DNS entry at ampr.org.
Otherwise, the ampr gateway will not allow forwarding traffic and it
will be reachable from the 44 network only.
Marius, YO2LOJ
On 19.02.2019 04:35, pete M via 44Net wrote:
its working!!!!!
got over 700 route when I do
ip route list table 44
I can ping some of the 44 network where none responded before.
but I dont seem to be reachable from the outside.
Anyone can ping 44.135.51.1?? from my windows machine I cant ping that adress and a
traceroute end at the edcu network.
_________________________________________
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:22 p.m.
Thanks Brain. Now I got this.
How can I have a dns entry on the ampr.org dns?
________________________________
De : Brian Kantor <Brian(a)bkantor.net>
Envoyé : 19 février 2019 14:00
À : AMPRNet working group
Cc : pete M
Objet : Re: [44net] Can't seem to grasp something
Pete,
Your allocation is 44.135.51.0/26.
It is too small to be announced by BGP. It will never be directly
reachable from the Internet. It *can* be reached from the Internet
via the tunnel encapsulation mechanism at UCSD, but in order for
that to work, you MUST have an address entry in the AMPR.ORG DNS
zone. No other domain will work for that mechanism.
Or you may be able to have a different subnet routed to you by
someone who is already announcing their larger subnet and is willing
to let you use a portion of their netspace via a VPN from their facility.
But you can't do it yourself with what you have.
- Brian
On Tue, Feb 19, 2019 at 06:33:27PM +0000, pete M via 44Net wrote:
Thanks Marius.
I already have a domain name (hamrad.ca) and I have a vps in a data center 30-50 km from
my qth.
I am planning on using a vpn to connexion to my vps so that I can use my vps as the entry
point to my segment. (OVH wont bpg annonce my segment already asked)
I will use my own DNS server on the vps. How should i fit all this in place and have my
segment connected to 44 and reachable from the rest of the world.
One of the first thing I want to setup is a machine that will do DMR to Dstar transcoding
and a SDR server for LF/MF/HF/VHF (airspyhf+) And I want user to be able to connect either
from the 44 net and the internet to both machine.
________________________________
De : 44Net <44net-bounces+petem001=hotmail.com(a)mailman.ampr.org> de la part de
Marius Petrescu <marius(a)yo2loj.ro>
Envoyé : 19 février 2019 01:28
À : 44net(a)mailman.ampr.org
Objet : Re: [44net] Can't seem to grasp something
For your system to be reachable from the internet, it needs to have a
registered DNS entry at ampr.org.
Otherwise, the ampr gateway will not allow forwarding traffic and it
will be reachable from the 44 network only.
Marius, YO2LOJ
On 19.02.2019 04:35, pete M via 44Net wrote:
its working!!!!!
got over 700 route when I do
ip route list table 44
I can ping some of the 44 network where none responded before.
but I dont seem to be reachable from the outside.
Anyone can ping 44.135.51.1?? from my windows machine I cant ping that adress and a
traceroute end at the edcu network.
_________________________________________
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 
20 Feb
20 Feb
12:53 p.m.
David,
The -e can be explained because your script doesn't have #!/bin/bash as the
first line, so whatever shell the user is in will run it. If that's a
non-bash shell, echo may not have any options. See
https://mywiki.wooledge.org/Bashism under Builtins for more details and
portable alternatives.
Regards,
Scott
ki4cuw
On Mon, Feb 18, 2019, 11:56 AM David Ranch <amprgw(a)trinnet.net wrote:
Hello Pete,
Anyone looking at using that script. dont forget
( like I did) to
install the net-tools package as the script use it and debian 9
does not
install it by default. (apt-get install net-tools)
Ok.. I've made a comment about that in the script. I'll publish that
new version in a bit.
On the next run of the script I did got a few
interresting result:
root@44gateway:/home/ve2pf# sh manual-ampr-start.sh
-e
creating tunl0 interface
allowing TTL of 64 for traceroute support and Path-MTU discovery
adding default AMPR route to 169.228.34.84
Current number of routes in AMPR44 route table: 1
-e
-----------------------------------------------------------------------
default via 169.228.34.84 dev tunl0 src
44.135.51.1 onlink
-e
-----------------------------------------------------------------------
I'm not sure why you're seeing all these stray "-e" but the setup
seems
to be running ok/
Enable Policy routing for traffic from 44 goes
back to 44
RTNETLINK answers: File exists
RTNETLINK answers: File exists
Those are ok.
Ping tests for specific AMPR hosts: (known
previously working hosts)
-e
n1uro:
-e -------------------------------
PING 44.88.0.9 (44.88.0.9) 56(84) bytes of data.
--- 44.88.0.9 ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 4076ms
Many remote AMPR stations require to learn known good AMPR routes first
before they will respond to *any* traffic. What many they do is take
the route list either from the RIP announcements or ENCAPS file, parse
them, and then load them into an iptables firewall WHITELIST. This
sometimes can take some time and if your external IP address changes
often, you might have a challenge to have remote stations keep up in
allowing your traffic into their stations.
One station might NOT require that and that's the AMPRGW at 44.0.0.1.
I've added a ping check for that IP into my script.
ampr-ripd already running; killing and
restarting
-e It wont die.. error!
I've added a sleep statement in the script to hopefully deal with this
but it's nothing to worry about.
I can ping the ampr gateway (169.228.34.84) so
that mean at least that I
am not loosing net connectivity. But a traceroute show
that the traffic on
the gateway is not using the tunl0 I am connected by ssh to eth0 and what I
find odd is that eth1 loose its IP adress and seem down from the ip -c a
command.
With the setup created by this script, traffic going to an AMPR address
will automatically go through the tunl0 interface. One address you should
be able to ping is the AMPR default gateway. If you do that ping, you
should see:
$ ping 44.0.0.1
PING 44.0.0.1 (44.0.0.1) 56(84) bytes of data.
64 bytes from 44.0.0.1: icmp_seq=1 ttl=62 time=31.2 ms
64 bytes from 44.0.0.1: icmp_seq=2 ttl=62 time=29.5 ms
64 bytes from 44.0.0.1: icmp_seq=3 ttl=62 time=28.5 ms
^C
--- 44.0.0.1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 28.538/29.804/31.295/1.136 ms
If you run tcpdump in another terminal window on your AMPR station using
the interface connected to your external ISP, you would see all the
protocol 4 encapsulation and the ICMP ping traffic inside it:
tcpdump -n -i eth0 not port 22 and not port 53 and not ip6 and not arp
--
09:21:53.861892 IP 96.78.144.186 > 169.228.34.84: IP 44.4.10.41 > 44.0.0.1:
ICMP echo request, id 24614, seq 1, length 64 (ipip-proto-4)
09:21:53.892722 IP 169.228.34.84 > 96.78.144.186: IP 44.0.0.1 > 44.4.10.41:
ICMP echo reply, id 24614, seq 1, length 64 (ipip-proto-4)
09:21:54.863001 IP 96.78.144.186 > 169.228.34.84: IP 44.4.10.41 > 44.0.0.1:
ICMP echo request, id 24614, seq 2, length 64 (ipip-proto-4)
09:21:54.892171 IP 169.228.34.84 > 96.78.144.186: IP 44.0.0.1 > 44.4.10.41:
ICMP echo reply, id 24614, seq 2, length 64 (ipip-proto-4)
09:21:55.864410 IP 96.78.144.186 > 169.228.34.84: IP 44.4.10.41 > 44.0.0.1:
ICMP echo request, id 24614, seq 3, length 64 (ipip-proto-4)
09:21:55.892531 IP 169.228.34.84 > 96.78.144.186: IP 44.0.0.1 > 44.4.10.41:
ICMP echo reply, id 24614, seq 3, length 64 (ipip-proto-4)
--
It's critical that you see both the requests AND responses and with that
tcpdump command, you can also use remote sites like
http://yo2tm.ampr.org/nettools.php to ping your AMPR IP address and see
unsolicited protocol 4 / IPIP traffic is coming into your AMPR station. If
it's not, your ISP is probably blocking this traffic and you'll need to
either see if they are willing to unblock that traffic or setup a VPN with
a IPIP friendly VPN provider ( http://wiki.ampr.org/wiki/AMPRNet_VPN ).
--David
KI6ZHD
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
1902
days inactive
1905
days old
18 comments
9 participants
participants (9)
-
Bill Vodall -
Brian -
Brian Kantor -
David Ranch -
Don McMorris -
KN4CUV -
Marius Petrescu -
pete M -
Scott Nicholas