44net

44net@mailman.ampr.org

3196 discussions

ampr-ripd 1.15
by Marius Petrescu 21 Sep '16

21 Sep '16

Hello, Another update... To keep everything as simple as possible and since this seem to work on all systems, only raw socket mode is used (parameter -r is ignored, so you don't have to change anything in your startup scripts). Please note that no functionality has actually changed compared to 1.13, so if you are happy with your current setup, no change is needed. These changes are basically aimed to newcomers and will bring nothing new to existing users. Internet: http://www.yo2loj.ro/hamprojects/ampr-ripd-1.15.tgz 44Net: http://yo2tm.ampr.org/hamprojects/ampr-ripd-1.15.tgz or from GitHub: git clone https://github.com/yo2loj/ampr-ripd.git Have fun, Marius, YO2LOJ

1 0

Re: [44net] ampr-ripd update 1.14
by Rob Janssen 21 Sep '16

21 Sep '16

I think it is a good idea! The password has often confused newcomers and made it harder to debug an intial setup. How about the -r flag? Some time ago it became necessary for me to use it, apparently due to changes in the kernel around multicasting. Is this still the current situation on the latest Debian release? Or can ampr-ripd again work without -r? Depending on this, it may be good to make some change in that default too. Rob

2 1

Greetings from Poland!
by Jakub Kramarz 19 Sep '16

19 Sep '16

Dear 44net group subscribers, My name is Jakub Kramarz (SP0NGE) and I'm writting on behalf of Hackerspace Kraków foundation (callsign SP9HACK) in Poland and I'd like to say hello to this community :-) We're a group of Linux and networking professionals, web and embedded developers, security researchers and finally radioamatours who has recently started our small, personal war to bring HAM radio back to young people in our country. In recent time, we've successfully: - in cooperation with SP9KGP club, we held 3 comprehensive HAM radio courses in Kraków, converting 40 enthusiasts to fully-fledged radio operators (~ the number of Polish Amateur Radio Union's new members in whole country), - held an important role in securing radio communication during World Youth Day 2016, - operated multiple occasional stations (supporting Great Orchestra of Christmas Charity, promoting Woodstock Festival Poland, ...), - supported Radioreaktywacja (Radio Reactivation) initiative, who "infects" the youngest with our hobby, by sharing hardware and knowledge, - and, finally, contributed to numerous open source and open hardware radio-related projects, eg. mcHF QRP firmware I hope we'll be able also take a part in AMPRNet project and contribute to digital communications over radio. Serdecznie pozdrawiam / Best regards, Jakub Kramarz http://about.me/jkramarz Sent from Makita TD090DWE impact driver

1 0

Posting from HamWAN Tampa @ DCC
by Bryan Fields 17 Sep '16

17 Sep '16

I'm on the 15th floor, 17 Miles from Tampa in St Petersburg, getting 20mbit/s with some refraction through glass in the club here. 73's -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net

1 0

rip down ?
by Maiko Langelaar 17 Sep '16

17 Sep '16

Did we loose the rip broadcast ? Maiko

5 5

Re: [44net] getting rip data fron the non ampr address of ucsd gw?
by Rob Janssen 09 Sep '16

09 Sep '16

> Please be aware the protocol is RIP44, **NOT** RIPv2. You must install > and run a daemon that processes RIP44 (e.g. ampr-ripd and rip44d). He uses a solution devised by Marius to work around that problem on a MikroTik router. Rob

1 0

Re: [44net] getting rip data fron the non ampr address of ucsd gw?
by lleachii＠aol.com 08 Sep '16

08 Sep '16

Ronen, Please be aware the protocol is RIP44, **NOT** RIPv2. You must install and run a daemon that processes RIP44 (e.g. ampr-ripd and rip44d). See: http://wiki.ampr.org/wiki/RIP 73, -Lynwood KB3VWG

1 0

cant get rip in MicroTik
by R P 08 Sep '16

08 Sep '16

I tried to follows the instructions that written here http://www.yo2loj.ro/hamprojects/ampr-gw-README.txt www.yo2loj.ro<http://www.yo2loj.ro/hamprojects/ampr-gw-README.txt> www.yo2loj.ro Setup example - please adapt ===== (ASSUMPTIONS: public ip is 89.122.215.236, router's ampr ip 44.182.21.254, WAN interface is PPPoE-In): You ... I have a working tunnel on the router called UCSD (the tunnel interface have no IP adress) my router is in bridge mode because it connect to cable modem before of it and sit on a DMZ address of the cable modem It uses ether1-gateway interface as the 44 net address (4.138.1.1) it uses ether2-master-local as the ip connected to the Cable modem (it uses 192.168.1.180 and default gateway to the cable modem ip which is 192.168.1.1) I have no firewall working and i get no RIP routes I have changed the tunnel interface name in the instructions to meet my interface name .. on the VRF if i chose the tunnel interface the routes (or maybe the tunnel) stop and i cant access anymore the 44 net hosts from the outside world and i see no rip info when i change the interface to the ether1-gateways (the one that have the 44 net address) the routes are ok the hosts are accessible from the outside world but i still not seeing any rip info what is wrong ? how can I debug it ? if needed i can provide password to the router since it is accessible from the outside world Thanks Forward Ronen - 4Z4ZQ http://www.ronen.org Ronen Pinchooks (4Z4ZQ) WebSite<http://www.ronen.org/> www.ronen.org ronen.org (Ronen Pinchooks (4Z4ZQ) WebSite) is hosted by domainavenue.com

2 2

Re: [44net] getting rip data fron the non ampr address of ucsd gw?
by Rob Janssen 08 Sep '16

08 Sep '16

> Let's not forget... > If you are unable to get RIP broadcasts for any reason, you can get the > encap data from the portal as a json file via its API. Sure, but please note that this does not solve the underlying problem of not being able to receive unsolicited IPIP traffic I mentioned. When that is the reason (rather than inability to follow installation and debugging instructions), the result will be a partially-working gateway. That gateway will be usable to contact other stations on the AMPRnet, but those other stations will not be able to contact your systems. Outgoing connects are OK, incoming connects are not. While some people my consider that a usable system, it is not a desirable situation. The AMPRnet is more peer-to-peer than the internet in general, in that anyone is expected to be both a participant and a consumer, not only a consumer as is usual on the internet. Rob

1 0

Re: [44net] getting rip data fron the non ampr address of ucsd gw?
by Rob Janssen 08 Sep '16

08 Sep '16

> So the password is sent from UCSD and compered with the password i put locally and if they identical then the data is processed ? > one more thing i understand the data is sent from UCSD ... how often is it sent ? > I dont see any advertisement here do i need to define something in the portal ? > normal tunneling work well Of course you need to have a gateway entry in the Portal. I.e. you need to have a subnet, and a gateway with external address and that subnet defined. The RIP packets are sent every 5 minutes. When you can manually make a tunnel and ping the remote, but you do not receive anything including RIP broadcasts, the cause often is a stateful firewall inside your internet modem/router. It accepts replies to outgoing packets, but it does not accept unsolicited incoming packets. This is designed as a security feature. To use IPIP tunneling, your modem/router must be able to unconditionally forward protocol-4 traffic to your gateway system. In advanced modem/routers you can forward a protocol, but usually it is only possible to forward TCP and UDP ports. That is something different. It is useless to forward port 4, you have to forward protocol 4. When that cannot be done you can often set a "DMZ host" that is said to get all incoming traffic, however there are examples of modem/routers where this does not work correctly. The DMZ host receives all TCP and UDP traffic but not all other traffic (including IPIP). It does receive (like any host) replies on its own IPIP traffic, but not the unsolicited incoming traffic. When you have such a modem/router, and when it cannot be replaced (e.g. because your provider requires you to use this modem/router), you cannot use IPIP tunnels. Rob

3 2

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

44net