44net

44net@mailman.ampr.org

3194 discussions

AmprNAT
by Brian 07 Jun '17

07 Jun '17

I have finished documenting and putting up on my website what I call AmprNAT. For those who attempting to get out via amprgate sourcing as their lan IPs, this not only will prevent this from occurring but also it will NAT you out as your gateway's IP... pending you're using a distro of linux. It requires a static route in your route pointing to your gateway, and then 3 lines of iptables rules. You may read about it at: https://n1uro.ampr.org/linuxconf/44nat.html I believe Lynwood is adding info on the wiki for this. -- I was reading a book about the history of glue... I couldn't put it down. ...think about it... -------- 73 de Brian - N1URO/AFT1BR email: (see above) Web: http://www.n1uro.net/ Ampr1: http://n1uro.ampr.org/ Ampr2: http://nos.n1uro.ampr.org Linux Amateur Radio Services axMail-Fax & URONode http://uronode.sourceforge.net http://axmail.sourceforge.net AmprNet coordinator for: Connecticut, Delaware, Maine, Maryland, Massachusetts, New Hampshire, New Jersey, Pennsylvania, Rhode Island, and Vermont.

2 1

Reminder about Amprd for simple configurations
by Marius Petrescu 07 Jun '17

07 Jun '17

Hi, Since everyone seems to like to use the most unusual script with "original" settings without trying ever to understand what's happening, I would remind you that there is a more or less "plug-and-play" solution called amprd... Let's assume a system with: - 44net assignment: 44.128.1.0/24 - WAN on eth0 (let's assume 1.2.3.4) - LAN on eth0 (192.168.1.1/24) - AMPR on eth2 (44.128.1.0/24) - We choose our GW IP to be 44.128.1.1 and that the internet access from the system is already set up, with NAT and default gateway via WAN. Now: 1. compile (make) and install (make install) amprd 2. create the following /etc/amprd.cfg: ----------------------------------------------------------------- [ampr0] prefix = 44.128.1.1 rip_receive = yes rip_save = yes ----------------------------------------------------------------- 3. Set address 44.128.1.1/24 to your eth2 interface 4. Start amprd. And basically that's it: a fully functional mesh gateway. If you want access from the internet to your subnet, too, instead of just starting amprd, create the following ampr startup script: ----------------------------------------------------------------- amprd ip route add default via 169.228.34.84 dev ampr0 onlink table default ip rule add from 44.128.1.1 table default ip rule add from 44.128.1.1 to 44.128.1.0/24 table main ----------------------------------------------------------------- This should do the trick. Marius, YO2LOJ

1 1

Portal IP hasn't changed in a few hours
by lleachii＠aol.com 07 Jun '17

07 Jun '17

All, Once again, my WAN IP and Subnet changed (about 5 hours ago now). I did reboot my GW; but my IP has not yet changed in the portal and I cannot reach other 44subnets or the Internet. I have logged in the Portal, removed the IP from the GW webform and hit save (leaving only the DDNS hostname). - Lynwood KB3VWG

2 1

DDOS attack Monitor Sites
by R P 06 Jun '17

06 Jun '17

I think it might interest us as a users of a big network Maybe it has interest to you Brian as our network Manager http://www.digitalattackmap.com/#anim=1&color=3&country=ALL&list=0&time=173… http://map.norsecorp.com/#/

2 1

Ampr-ripd experimental 2.3 version
by Marius Petrescu 05 Jun '17

05 Jun '17

Hello everyone, Since experimenting goes one, here a new ampr-ripd version that forces the sending of call home data to use the tunnel's IP as its source IP address. Tnx. Lynwood for pointing out that necessity. Interactive map which is available at http://yo2tm.ampr.org/ampr-map/ For those that do not want to participate, there is no need to upgrade. And even if you do, not setting the -L parameter will not send any data, the result being the same behavior like 2.1.1. Download: http://www.yo2loj.ro/hamprojects/ampr-ripd-2.3.tgz http://yo2tm.ampr.org/hamprojects/ampr-ripd-2.3.tgz Have fun, Marius, YO2LOJ

6 19

Odp: Re: Ampr-ripd experimental 2.3 version
by Tomasz Stankiewicz 05 Jun '17

05 Jun '17

Marius et al. Presently my server employs ampr-ripd-2.3 Did not observed any issues so far. encap.txt file at the very beginning contains two entries: # # encap.txt file - saved by ampr-ripd (UTC) Mon Jun 5 03:20:34 2017 # route addprivate 44.0.0.1/32 encap 169.228.34.84 route addprivate 44.0.0.2/32 encap 169.228.66.251 RIP broadcast are coming through as before. Best regards. Tom - SP2L

2 1

Odp: Re: Ampr-ripd experimental 2.3 version
by Tomasz Stankiewicz 05 Jun '17

05 Jun '17

An HTML attachment was scrubbed... URL: <http://hamradio.ucsd.edu/mailman/private/44net/attachments/20170605/f4bb34a…>

1 0

Amprd v2.1 update
by Marius Petrescu 04 Jun '17

04 Jun '17

Hello everyone, To be in line with the latest ampr-ripd & co, here a new amprd version that forces the sending of call home data to use the tunnel's IP as its source IP address. Also, it supports multiple call home info's, one for each tunnel configured. Interactive map which is available at http://yo2tm.ampr.org/ampr-map/ For those that do not want to participate, there is no need to upgrade. Download: http://www.yo2loj.ro/hamprojects/amprd-2.1.tgz http://yo2tm.ampr.org/hamprojects/amprd-2.1.tgz Have fun, Marius, YO2LOJ

1 0

Amprd 2.0 - map functionality and new GW IP
by Marius Petrescu 04 Jun '17

04 Jun '17

Hello, For those using amprd (like myself), here a small update: - added map notification every 5 min. There is a new config file parameter for it, check the example config - modified the default ampr gw address to the new IP. This has actually no effect until the RIP broadcasts for 44.0.0.1 will change to the new IP (44.0.0.1 still uses the old GW address). Older versions, like 1.5 and 1.6 will switch gateways automatically if presented with a new gw for 44.0.0.1 in the RIP data, so unless you want to be on the map with a blue dot, there is no urge to update (live map is at http://yo2tm.ampr.org/ampr-map/) As always: http://www.yo2loj.ro/hamprojects/ http://yo2tm.ampr.org/hamprojects/ Marius, YO2LOJ

6 30

tcpdump
by gm4upx＠gb7jd.co.uk 03 Jun '17

03 Jun '17

Hello, With the changes taking place I have been monitoring both the " old " and the " new " addresses. I'm receiving rip broadcasts from both and additionally similar broadcasts to the two lines below on the " old " address only. amprgw.sysnet.ucsd.edu > 172.16.1.4: IP (tos 0x0, ttl 111, id 14685, offset 0, flags [none], proto UDP (17), length 90) 218-228-138-51f1.osk3.eonet.ne.jp.25465 > mb7njd.ampr.org.3544: [udp sum ok] UDP, length 62 I have little knowledge of the meaning of this and would appreciate someone explaining it to me. Thanks in advance. ( Monitored from eth0 at 172.16.1.4 which is in DMZ ) Regards, Ian..

3 4

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

44net