44net

44net@mailman.ampr.org

1 participants
3194 discussions

Re: [44net] Another new board member...
by Fortney, Jim - K6IYK 15 Aug '19

15 Aug '19

Those of us who have been involved in this arena for over 30 years know that Bdale Garbee, KB0G, is not only one of the most technically astute leaders we have had in the hobby, but is an honorable and very respected individual. I fully support his selection. - JimF K6IYK

3 2

amprnet gateway forwarding
by Martinez, Philip 11 Aug '19

11 Aug '19

In the past ampr gateway would only forward packets to the general internet from 44-net address space and not from 44 net to other 44 net addresses. Will the ampr gateway now forward packets for addresses from 44-net to 44.192.0.0/10? Philip KC3IPF

4 3

Hamnet server DNS root
by Frederic Zulian 09 Aug '19

09 Aug '19

Hello, After some time away, I try to get back into the Hmanet network with a server (Raspberry) under Yunohost. I begin the configuration :) Does the Hamnet network have a root DNS server? 73 F1SXO Frédéric ZULIAN -- Frédéric ZULIAN

1 0

And the fraud begins.
by Bryan Fields 08 Aug '19

08 Aug '19

13 15

RouterOS update breaks RIP reception
by Marius Petrescu 06 Aug '19

06 Aug '19

Hello, Please note that the update to Mikrotik ROS 6.45.3 breaks reception of the RIP multicasts used by the gateway scripts. Please do not update unless you need to solve issues described in the change list. Changes in this release: *) certificate - renew certificates via SCEP when 3/4 of lifetime reached; *) crs317 - fixed multicast packet receiving (introduced in v6.45); *) hotspot - fixed default profile values not being used (introduced in v6.45); *) rb4011 - fixed SFP+ interface linking (introduced in v6.45.2); *) smips - reduced RouterOS main package size (disabled LTE modem, dot1x and SwOS support); *) supout - fixed SIM slot printing (introduced in v6.45); *) wireless - improved U-APSD (WMM Power Save) support for 802.11e; Marius, YO2LOJ

1 0

RIP broadcasts
by Jack Eifer 01 Aug '19

01 Aug '19

I'm trying to monitor RIP broadcasts from ucsd using 'tcpdump'. Does anyone know what 44-ip address(s), port, or protocol I should source to monitor incoming broadcasts. Is it 44.0.0.1 ? Thanks, Jack AA6HF

3 2

Re: [44net] mailman.ampr.org new IP address (Jay Nugent)
by Rob Janssen 30 Jul '19

30 Jul '19

> It *should* be a multi-step process: Why so difficult? The TTL in the ampr.org zone is one hour, and it has been for a long time. Rob

4 3

mailman.ampr.org new IP address
by Brian Kantor 30 Jul '19

30 Jul '19

Host mailman.ampr.org (where this and other mailing lists are hosted) has moved from address 199.249.230.93 to 44.76.7.7. This change was made because the 199.249.230.93 address was being blocked by too many blacklists due to other activity on the subnet. Unfortunately, whenever a mail handler such as 'mailman' gets a new address, it loses all the good will and reputation it has previously earned in various spam filters, so some recipients may miss out on a few messages because of over-enthusiastic spam filtering. There is nothing I know of to enhance its reputation except time. Your patience is appreciated. - Brian

5 9

Network Routers for Harsh Environments
by Jason McCormick 28 Jul '19

28 Jul '19

Hello all, I am looking for some recommendations on network routers for harsh environments. By harsh, I mean hot but not particularly dirty. I know there's a number of people on this list who use Mikrotik and Ubiquit EdgeRouters for your deployments and I am looking for thoughts on those product lines, as well as any other similar products. I am looking for a reasonably low-cost device. The key items I am looking for are: - Wide operating temperatures. Some of the sites are tower buildings that don't have A/C and during last week's heatwave the in-room temperature in one of the buildings was 105F-110F (killed an SRX power supply). None of the rooms will freeze in the winter but the temp will get quite low. - RELIABLE -- some of our sites have limited access and frequent power cycles, port failures, etc. are show stoppers - IPv6 support for basic routing and switching functions - Support for BGP and OSPFv3 (routing tables < 100 items) - VLAN tagging - IPSec or OpenVPN tunnels as clients - No firewalling or the ability to pass traffic without firewalls - note I don't mean a "permit any/any", I mean literally the device operates as a router or traffic can bypass a firewall-like function. - The device is a pre-packaged commercial system; I don't want to have to mess around with custom Linux/BSD installs, etc. - A device that can operate as both a router and switch would be nice, but not required As background, our club has a wide-area network around southwest Akron, Ohio-area stretching out to Rittman, Ohio and southeast to Alliance, Ohio with legs planned in other directions. This network supports a number of ham repeaters as well as other related services for the repeaters plus some of the site operations for the tower locations. Most of the gear is showing its age and we're going to start a wholesale replacement of most of it later this summer/autumn. All of the sites are connected with narrow-beam WiFi using point-to-point dishes, currently N but upgrading to AC AirMAX when we do the hardware refresh. Each site has a router or switch or both (depending on size and needs). The gear is a mix of Juniper SSG5s, Juniper SRXs, HP ProCurve switches, and some other random items. As part of the work, we're going to do a complete renumbering of the networks (which have grown up ad-hoc over the years), incorporate better use of 44Net space, and overlay IPv6 across the whole network. The reason for not wanting firewalling between the sites is we've run into problems with link reliability over UDP (losing a few packets) and also certain network device behaviors that don't survive multiple hops through stateful firewalls for a variety of reasons. Any thoughts in this community? I've been looking at the Mikrotik hEX S and the Ubiquiti EdgeRouter X as example devices. I don't have experience with Mikrotik gear although I hear it mentioned here a lot. Thanks Jason N8EI

4 3

Re: [44net] Is this a worry ?
by Rob Janssen 25 Jul '19

25 Jul '19

> < IP 0.0.0.0.5678 > 255.255.255.255.5678: UDP, length 106 > > They say a little knowledge is dangerous ! > At the moment at my tunl0 ( remote location ) I am getting groups of five of the above line every minute in my recently installed gateway. > I have tried without success to stop it appearing using iptables with < -A INPUT -p udp -i tunl0 --sport 5678 -j DROP >. Well, there is no need to do that really. Those packets are not dangerous, they sometimes may be even useful. This is a router discovery protocol that will inform you about manufacturer, version number of software, router name etc of the device sending it. When you have a device that supports it (sends it), you will also have some overview table in the user interface there which shows the decoded info received in the last 2 minutes or so. At first I also disabled this everywhere I saw it, and I am still not sending it on IPIP tunnels (where it actually is a bit troublesome for some cases because every minute such a packets would go out on all 500 tunnels at the same time and would result in a traffic burst that may overflow some queues somewhere and would result in packet loss of other usage). But on the VPN links that we use with our new style connections, I now keep it enabled. It provides a nice overview about who is connected and what software they are running, and I occasionally mail people that never upgrade their software to urge them to do so. As the mechanism for enabling/disabling these broadcasts has changed a little in the recent past in MikroTik firmware, and people not always update their software, some people that run an older YO2LOJ (Marius) script version may unknowingly be sending these things. But they are not dangerous and should not cause any noticable traffic volume. Rob

2 1

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

44net