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@mailman.ampr.org de la part de pete M via 44Net 44net@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@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.orgmailto: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.orgmailto:hotmail.com@mailman.ampr.org> de la part de David Ranch <amprgw@trinnet.netmailto: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-s...
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.orgmailto:44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net _________________________________________ 44Net mailing list 44Net@mailman.ampr.orgmailto:44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
73's for now! DE AF4H
_________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net