On Feb 13, 2019, at 1:09 PM, Marius Petrescu <marius(a)yo2loj.ro> wrote: Tom, Your EdgeRouter would be a nice experimentation platform, and a perfect opportunity for a "howto" to get ampr-ripd to run on it. It has basically all it needs and allows addition of third party components... _________________________________________ 44Net mailing list 44Net(a)mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net

Excellent. The processor on the Edgerouter light is a MIPS, and cross compile tools are available. There is also an option to install 3rd party add ons. I will dig into this a little, but unfortunately I can not test since I don't have a Edgerouter. Maybe someone has more experience with this machines... On 14.02.2019 00:08, Tom Cardinal via 44Net wrote: _________________________________________ 44Net mailing list 44Net(a)mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net

I’m willing to work to get the mesh portion of it working. I am fine with flashing software but I do not know much about the software platform it sits on. I’ve only been in the command line a few times. I’ll follow the wiki guide to get it online and contact you when I have it going. — tom Tom Cardinal / MSgt USAF (Ret) / N2XU / BSCS / CASP+

On Feb 14, 2019, at 11:30 AM, Marius Petrescu <marius(a)yo2loj.ro> wrote: The build environment to be used on the router itself can be set up like this.... https://www.ntop.org/nprobe/running-nprobe-and-ntopng-on-ubiquity-edgeroute… _________________________________________ 44Net mailing list 44Net(a)mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net

On Feb 15, 2019, at 3:09 PM, Marius Petrescu <marius(a)yo2loj.ro> wrote: Hi guys, I just ordered a Edgerouter Lite and it will probably arrive on Tuesday. Next week is a little full, but after that, we're gone do this :-) I will keep you up to date. 73s de Marius, YO2LOJ _________________________________________ 44Net mailing list 44Net(a)mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net

Ok, I've run the steps and have some info to report... but first I'll give you my setup. 1. I'm on a NAT behind a pfSense. I do this to shield the AMPR external interface from brute forcers. It worked very well when I ran a linux gateway and it also worked well when I ran my gateway on a Raspberry Pi. 2. I have very old Edgerouter Lite. I bought it in the 2013 - 2014 timeframe. I tried to update firmware and I'm on 1.10.8 (Nov 2018). --- Info to pass: 1. At step two I had to change: Config Tree → system → repository → add “debian” → Update List To Config Tree → system→ package → repository → add “debian” → Update List 2. At step three I changed a couple of typos: apt-get install ampr-rip to apt-get install ampr-ripd Also. The killall ampr-ripd command produced no result. It gave me "Operation not supported". I ran ps-ax and fond ampr-ripd was not running. The service directory was /lib/systemd/service instead of /lib/system so I deleted the added service at /lib/systemd/service/ampr-ripd.service. I'm still experimenting here and will report back tomorrow evening central US time. --tom, n2xu On 2/20/19, 3:33 PM, "44Net on behalf of Marius Petrescu" &lt;44net-bounces+tomc=gulfmail.net(a)mailman.ampr.org on behalf of marius(a)yo2loj.ro&gt; wrote: Hello everyone there with some EdgeRouters available, As promised, here the complete gateway setup for you to try :-) At the moment, it is using ampr-ripd 1.15 (no support for BGP tunnel endpoints in the 44net space, i will update in the bear future)... It should also land in the Wiki, I assume... Have fun, Marius, YO2LOJ EdgeRouter AMPR Configuration Prerequisites: - Make sure to upgrade to firmware 2.0.0 or later. - You have a running, configured internet connection and full access to the router - Make sure to secure your router by setting appropriate firewall rules 1. Add tunnel interface - Config Tree → add tun44 → Update List - tun44: address: <your AMPR gw address>*/32* description: AMPR GW encapsulation: ipip local-ip: <your public gw IP> remote-ip: *0.0.0.0* - Press Preview ans Apply 2. Add debian stretch repository - Config Tree → system → repository → add “debian” → Update List - debian: components: main contrib non-free distribution: stretch url: http://http.us.debian.org/debian - Press Preview ans Apply 3. Install ampr-ripd Open CLI - become superuser: sudo su - update packets: apt-get update - install ampr-ripd: apt-get install ampr-rip - kill the now running daemon: killall ampr-ripd - delete the added service entry: cd /lib/systemd rm ampr-ripd.service - create the route cache folder: cd /var/lib mkdir ampr-ripd 4. Create the daemon startup script: cd /config/scripts/post-config.d touch ampr.sh chmod +x ampr.sh 5. Edit the created script using vi: vi ampr.sh (first press insert to go into edit mode) /#!/bin/sh/ // /MY_IP=`ip addr list dev tun44 | grep inet | awk '{print $2}'`/ // /ip rule add from $MY_IP table default/ // /ip rule add to 44.0.0.0/8 table default/ // /ampr-ripd -s -t default -i tun44 -m 90 -a 44.1.2.3/32/ (press ESC followed by :wq to save the file and exit vi) Important: if your router is connected via NAS you need to edit the -a parameter to suite your network to be excluded. If the router is directly connected, it will autodetect its IPs, so the parameter can be omitted. Also add any local networks to be excluded as you need. 6. run the script: ./ampr.sh To check, use ip route list table default You should get a lot of routes there... Now it is time to restart your router and check everything is ok. 7. Now you can add your needed subnets on vlans or a second interface. Enjoy. _________________________________________ 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 Feb 21, 2019, at 9:01 AM, Tom Cardinal &lt;tomc(a)gulfmail.net&gt; wrote: Please don’t take my edits as criticism, I’m trying to help and was not sure if my firmware version contained a different file system structure. I’ve used your scripts before and they are awesome. I told the system to use the stretch repository so I’m probably broken... I’ll do a system reset when I get home this evening and retry using the Jessie repository. I’m finally starting to get comfortable on this platform, avoided doing so in the past because I didn’t want to brick it. Thank you for working with me on this Marius. I’ll send an update before I turn in for the night. — tom Tom Cardinal / MSgt USAF (Ret) / N2XU / BSCS / CASP+ > On Feb 21, 2019, at 1:52 AM, Marius Petrescu &lt;marius(a)yo2loj.ro&gt; wrote: > > Tnx Tom, > > I wrote up those tings partly fom memory. so errors are possible. > > Regarding 1.10.8: They updated from "jessie" to "stretch" when releasing 2.0.0. > > So there may be some differences, like in the installing of the services. In stretch, the service launches automatically on install. > > I also was not sure if ampr-ripd was in the jessie repository, but it seems it is, which makes this possible on 1.10.8, too. > > Question: did you use the stretch or the jessie repository for the update? > > > I will recheck the document and correct the information. > > >> On 21.02.2019 07:28, Tom Cardinal via 44Net wrote: >> Ok, I've run the steps and have some info to report... but first I'll give you my setup. >> >> 1. I'm on a NAT behind a pfSense. I do this to shield the AMPR external interface from brute forcers. It worked very well when I ran a linux gateway and it also worked well when I ran my gateway on a Raspberry Pi. >> >> 2. I have very old Edgerouter Lite. I bought it in the 2013 - 2014 timeframe. I tried to update firmware and I'm on 1.10.8 (Nov 2018). >> >> --- >> Info to pass: >> >> 1. At step two I had to change: >> >> Config Tree → system → repository → add “debian” → Update List >> >> To >> >> Config Tree → system→ package → repository → add “debian” → Update List >> >> 2. At step three >> >> I changed a couple of typos: >> >> apt-get install ampr-rip >> >> to >> >> apt-get install ampr-ripd >> >> Also. The killall ampr-ripd command produced no result. It gave me "Operation not supported". I ran ps-ax and fond ampr-ripd was not running. >> >> The service directory was /lib/systemd/service instead of /lib/system so I deleted the added service at /lib/systemd/service/ampr-ripd.service. >> >> I'm still experimenting here and will report back tomorrow evening central US time. >> >> --tom, n2xu >> >> On 2/20/19, 3:33 PM, "44Net on behalf of Marius Petrescu" &lt;44net-bounces+tomc=gulfmail.net(a)mailman.ampr.org on behalf of marius(a)yo2loj.ro&gt; wrote: >> >> Hello everyone there with some EdgeRouters available, >> As promised, here the complete gateway setup for you to try :-) >> At the moment, it is using ampr-ripd 1.15 (no support for BGP tunnel >> endpoints in the 44net space, i will update in the bear future)... >> It should also land in the Wiki, I assume... >> Have fun, >> Marius, YO2LOJ >> EdgeRouter AMPR Configuration >> Prerequisites: >> - Make sure to upgrade to firmware 2.0.0 or later. >> - You have a running, configured internet connection and full access to >> the router >> - Make sure to secure your router by setting appropriate firewall rules >> 1. Add tunnel interface >> - Config Tree → add tun44 → Update List >> - tun44: >> address: <your AMPR gw address>*/32* >> description: AMPR GW >> encapsulation: ipip >> local-ip: <your public gw IP> >> remote-ip: *0.0.0.0* >> - Press Preview ans Apply >> 2. Add debian stretch repository >> - Config Tree → system → repository → add “debian” → Update List >> - debian: >> components: main contrib non-free >> distribution: stretch >> url: http://http.us.debian.org/debian >> - Press Preview ans Apply >> 3. Install ampr-ripd >> Open CLI >> - become superuser: >> sudo su >> - update packets: >> apt-get update >> - install ampr-ripd: >> apt-get install ampr-rip >> - kill the now running daemon: >> killall ampr-ripd >> - delete the added service entry: >> cd /lib/systemd >> rm ampr-ripd.service >> - create the route cache folder: >> cd /var/lib >> mkdir ampr-ripd >> 4. Create the daemon startup script: >> cd /config/scripts/post-config.d >> touch ampr.sh >> chmod +x ampr.sh >> 5. Edit the created script using vi: >> vi ampr.sh >> (first press insert to go into edit mode) >> /#!/bin/sh/ >> // >> /MY_IP=`ip addr list dev tun44 | grep inet | awk '{print $2}'`/ >> // >> /ip rule add from $MY_IP table default/ >> // >> /ip rule add to 44.0.0.0/8 table default/ >> // >> /ampr-ripd -s -t default -i tun44 -m 90 -a 44.1.2.3/32/ >> (press ESC followed by :wq to save the file and exit vi) >> Important: if your router is connected via NAS you need to edit the -a >> parameter to suite your network to be excluded. If the router is >> directly connected, it will autodetect its IPs, so the parameter can be >> omitted. Also add any local networks to be excluded as you need. >> 6. run the script: >> ./ampr.sh >> To check, use >> ip route list table default >> You should get a lot of routes there... >> Now it is time to restart your router and check everything is ok. >> 7. Now you can add your needed subnets on vlans or a second interface. >> Enjoy. >> _________________________________________ >> 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

Hi Marius, I have a few question and I will ask them in line 1. Add tunnel interface - Config Tree → add tun44 → Update List - tun44: address: <your AMPR gw address>*/32* ​My allocation is 44.135.51.0/26 So From what you are telling here I should use: 44.135.51.0/32 ?? description: AMPR GW encapsulation: ipip local-ip: <your public gw IP> Is that the IP adress that my ISP provide me? or is it the IP adress that I want to show to the internet? like 44.135.51.1 in my case?? remote-ip: *0.0.0.0* - Press Preview ans Apply THanks!! Pierre VE2PF ________________________________ De : 44Net &lt;44net-bounces+petem001=hotmail.com(a)mailman.ampr.org&gt; de la part de Marius Petrescu &lt;marius(a)yo2loj.ro&gt; Envoyé : 27 février 2019 03:03 À : 44net(a)mailman.ampr.org Objet : [44net] Update: EdgeRouter Lite (and probably others) full tunnel setup Hi everyone, I updated the instructions for setting up an EdgeRouter as a full AMPR gateway. 1. Add tunnel interface - Config Tree → add tun44 → Update List - tun44: address: <your AMPR gw address>*/32* description: AMPR GW encapsulation: ipip local-ip: <your public gw IP> remote-ip: *0.0.0.0* - Press Preview ans Apply 2. Download your packages from here: Find the EdgeRouter setup package here: http://www.yo2loj.ro/hamprojects/Ampr_EdgeRouter.tgz (mips64) For the EdgeRouterX setup use this one: http://www.yo2loj.ro/hamprojects/Ampr_EdgeRouterX.tgz (mipsel) Inside those archives, there is a setup.txt file explaining the next steps. NOTE: THE SETUP SCRIPT DOES NOT SECURE YOUR ROUTER. YOU NEED TO SET UP FIREWALL ROUTES YOURSELF. 3. Optionally you can install a status page in the wizzard section. Download here: http://www.yo2loj.ro/hamprojects/Ampr_Status_Wizard.tar I hope this is useful, Marius, YO2LOJ