44net

44net@mailman.ampr.org

4 participants
3196 discussions

Setup Gateway on RB951 n2 Mikrotik
by Francesco Ciacco 18 Jul '19

18 Jul '19

Hi everyone, I'm trying to migrate the gateway from linux to mikrotik. Given that on Linux the network traffic 44 takes place regularly, I am instead experiencing a great difficulty in configuring the rb 951 n2 following the directions of the wiki.ampr. There is someone on the list who has set up a rb mikrotik as described by the wiki and works regularly. I state that the ipip interface goes in regular running, the setups checked several times seem made for as requested. Someone can give me some info about it. Greetings Francesco IW8PGT

1 0

Re: [44net] Hamnet Web Page List
by Andrzej 18 Jul '19

18 Jul '19

http://sp.ampr.org http://search.sp.ampr.org czw., 18 lip 2019 o 08:23 Frederic Zulian via 44Net <44net(a)mailman.ampr.org> napisał(a): > > > > ---------- Forwarded message ---------- > From: Frederic Zulian <fzulian(a)gmail.com> > To: 44net(a)mailman.ampr.org > Cc: > Bcc: > Date: Thu, 18 Jul 2019 08:22:41 +0200 > Subject: Hamnet Web Page List > Hello, > > When I'm connected to the Hamnet network how can I know the IP addresses of > existing web pages. > > Is there a list or search engine? > > 73 > -- > Frédéric ZULIAN > -- Pozdrawiam Andrzej (www).

1 0

Hamnet Web Page List
by Frederic Zulian 18 Jul '19

18 Jul '19

Hello, When I'm connected to the Hamnet network how can I know the IP addresses of existing web pages. Is there a list or search engine? 73 -- Frédéric ZULIAN

1 0

Re: Untangle
by lleachii＠aol.com 16 Jul '19

16 Jul '19

Ryan N0JEP, I use OpenWrt with the ampr-ripd daemon. It's open source; but Linux. http://wiki.ampr.org/wiki/Setting_up_a_gateway_on_OpenWRT 73, - Lynwood KB3VWG

1 0

Re: [44net] Questions regarding usage off 44/8 parts outside of ampr.org
by Bryan Fields 16 Jul '19

16 Jul '19

On 7/16/19 11:28 AM, Holger Baust via 44Net wrote: > Hi. > > My company plans to use DC/OS from Mesosphere and DC/OS is using > 44.128.0.0/20 per default for overlay networking. > This seems to have no impact since this overlay nets are only used in > DC/OS clusters and not routed to the Internet, but might lead to > problems in some cases... > > Their documentation with this informations can be found at: > https://docs.mesosphere.com/1.10/networking/virtual-networks/ip-per-contain… You're posting using quoted printable, don't do that. I've fixed your link. > Is this already known? News to me, and a really poor idea. There's other networks which could be used for this, without stepping on allocated space. 44.128.0.0/20 isn't used now, but neither was 1/8 or 5/8. I kinda want to announce 44.128.0.0/20 just to mess with them, might freak out if there's a route to that :) -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net

6 5

Re: [44net] Questions regarding usage off 44/8 parts outside of ampr.org
by Brian Kantor 16 Jul '19

16 Jul '19

On Tue, Jul 16, 2019 at 08:28:49AM -0700, Holger Baust via 44Net wrote: > Date: Tue, 16 Jul 2019 08:28:49 -0700 (PDT) > From: Holger Baust <holger(a)dm6hb.de> > To: 44net(a)mailman.ampr.org > Subject: Questions regarding usage off 44/8 parts outside of ampr.org > > Hi. > > My company plans to use DC/OS from Mesosphere and DC/OS is using > 44.128.0.0/20 per default for overlay networking. > This seems to have no impact since this overlay nets are only used in > DC/OS clusters and not routed to the Internet, but might lead to > problems in some cases... > > Their documentation with this informations can be found at: > https://docs.mesosphere.com/1.10/networking/virtual-networks/ip-per-conta= > iner/ > > Is this already known? > > 73, > Holger While I was unaware of DC/OS specifically using this subnet, I do know that for many years software from various companies have used parts of network 44 for "internal-only" networking. In particular, an obsolete document, which is still available via Google searching refers to 44.128.0.0/16 in terms which seem to have lead these firms to believe that it is another RFC1918-style "private network" and they may use it in that way. Most of these firms seem to be ignorant of the various RFC1918 networks that are intended for this use. Many of them should be using the link-local addresses of 169.254.0.0/16, but apparently don't know about them. When contacted by me about the misuse of network 44, some are cooperative and some pull up the obsolete document as justification, while a small number take up a combative stance and tell me to contact their lawyers. Just to make it specific: 44.128.0.0/16 is a subnet currently reserved for testing in the amprnet. It should not be used outside Amateur Radio. - Brian Kantor Network 44 Manager

2 1

Questions regarding usage off 44/8 parts outside of ampr.org
by Holger Baust 16 Jul '19

16 Jul '19

A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 235 bytes Desc: OpenPGP digital signature URL: <https://mailman.ampr.org/mailman/private/44net/attachments/20190716/cae6f3b…>

1 0

Re: [44net] Untangle
by Jeff KC9WSJ 16 Jul '19

16 Jul '19

On Fri, 2019-07-12 at 14:15 +0000, Ryan O'Connor via 44Net wrote: > > Has anyone successfully used AMPRNet with an untangle firewall/router > device? I’m trying to ditch the Cisco 2850 for something quieter. > > Ryan I don't want to 'jack this thread, but it might be helpful to hear from others using /any/ of the open source fw/routers available, in particular anything *BSD-based (I was told a long time ago that "friends don't let friends run Linux as a firewall). OSS Platforms that come to mind are pfSense, Untangle, OPNsense, m0n0wall, smoothwall, etc. -- Jeff KC9WSJ <jeff(a)kc9wsj.us>

7 6

Re: [44net] Untangle
by Randy Neals 15 Jul '19

15 Jul '19

Yes, OPNsense is not one of Vultr’s standard images, but I was successful in loading a custom ISO of OPNsense on a Vultr server. I was also successful in getting ZeroTier to work with a customer IP subnet rather than RFC1918 space. My next step in to load the dynamic routing missilery in OPNsense and test originating of a /24 block to Vultr using a private AS number. If that is successful, then I plan to deploy another OPNsense VM at a different Vultr data center. The objective is to have 2 OPNsense gateways, each announcing the same block to Vultr, and extending that /24 via ZeroTier to our client devices. If the OPNsense server fails, the BGP announcement will likely also drop, however the other OPNsense fm in the other data center should pick up the traffic. Randy On Mon, Jul 15, 2019 at 3:51 PM pete M via 44Net <44net(a)mailman.ampr.org> wrote: > > > > ---------- Forwarded message ---------- > From: pete M <petem001(a)hotmail.com> > To: AMPRNet working group <44net(a)mailman.ampr.org> > Cc: > Bcc: > Date: Mon, 15 Jul 2019 22:49:32 +0000 > Subject: RE: [44net] Untangle > This sound pretty interresting. > > > > Could this be impremented on a vultur vps? > > > > > > > > > > ________________________________ > De : 44Net <44net-bounces+petem001=hotmail.com(a)mailman.ampr.org> de la > part de Randy Neals <randy(a)neals.ca> > Envoyé : Monday, July 15, 2019 5:04:31 PM > À : AMPRNet working group > Objet : Re: [44net] Untangle > > I'm currently experimenting with OPNSense on a cloud server, with ZeroTier > VPN. > > I'm intending to run OPNSense on a small i386 device at a repeater site, > with VPN back to the cloud server. > Thus extending 44. IP addresses to a variety of radio sites. > > Randy, W3RWN > Seattle. > > On Mon, Jul 15, 2019 at 1:42 PM Jeff KC9WSJ <jeff(a)kc9wsj.us> wrote: > > > On Fri, 2019-07-12 at 14:15 +0000, Ryan O'Connor via 44Net wrote: > > > > > > Has anyone successfully used AMPRNet with an untangle firewall/router > > > device? I’m trying to ditch the Cisco 2850 for something quieter. > > > > > > Ryan > > > > I don't want to 'jack this thread, but it might be helpful to hear from > > others using /any/ of the open source fw/routers available, in particular > > anything *BSD-based (I was told a long time ago that "friends don't let > > friends run Linux as a firewall). > > OSS Platforms that come to mind are pfSense, Untangle, OPNsense, > m0n0wall, > > smoothwall, etc. > > > > -- > > Jeff KC9WSJ <jeff(a)kc9wsj.us> > > > > > > _________________________________________ > > 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 > > > > ---------- Forwarded message ---------- > From: pete M via 44Net <44net(a)mailman.ampr.org> > To: AMPRNet working group <44net(a)mailman.ampr.org> > Cc: pete M <petem001(a)hotmail.com> > Bcc: > Date: Mon, 15 Jul 2019 22:49:32 +0000 > Subject: Re: [44net] Untangle > _________________________________________ > 44Net mailing list > 44Net(a)mailman.ampr.org > https://mailman.ampr.org/mailman/listinfo/44net > -- Sent from mobile.

1 0

Re: [44net] Comcast Xfinity Routing
by David Ranch 12 Jul '19

12 Jul '19

Hello Nate, >Even in bridge mode I wasn't getting any traffic from AMPRGW. Tomorrow I >will try bridge mode again, it is possible that I may have set up the >firewall rules on my edgerouter incorrectly. I have Comcast Business here to get static IPv4 addresses and it's worth noting that with these cablemodems (a rebadged Cisco DPC3941B), it doesn't support static IPs in bridging. You *must* leave the modem in "Bridge: Off" aka.. NAT mode. In this mode, the inside Ethernet ports or Wifi connections offer both 10.1.0.x NATed address space but also offer my static IP subnet. I infer that for my static addresses, the Comcast box is doing some sort of 1:1 NATing but it does seem to support protocol 4. Externally initiated proto-4 traffic comes in ok so the NATing isn't screwing anything up. A few more things I recently became aware of from a Comcast support rep if it's helpful to you: - When enabling or disabling bridging mode, my external IP would get assigned to vastly different subnets. I have no idea why putting the cablemodem into L2 mode would do this but it does. Something worth considering. - Pseudo mode: It seems that Comcast silently pushes new firmware and does reboots on you. No notifications or release notes are offered up as far as I can tell I noticed the other day that under the bridging configuration area of the cablemodem, it nows shows OFF, Pseudo, ON. I have no idea what this new Pseudo means but it does sound similar to what I described above. - Uptime: I've been having my cablemodem just stop forwarding traffic after about 70 days of uptime. Working fine and fast one minute, zero packet forwarding after that. The front facing LEDs still look happy, web interface still works, but zero forwarding. According to Comcast, they recommend to their users to reboot the cablemodem every 60 days to avoid issues with memory fragmentation. This is pretty lame if you ask me but this is what they told me and it's something I'm looking to automate if I can find a decent way to automate their web interface (no CLI or API interfaces offered). --David KI6ZHD

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

44net