44net

44net@mailman.ampr.org

2 participants
3201 discussions

WWconvers Chat Clients
by n2nov＠n2nov.ampr.org 13 Dec '20

13 Dec '20

I am looking to put together a list of what can be used as a client interface for the WWconvers servers like Hub_NA, Hub_EU, etc. So far I have: WinConvers (circa 2000) [WINDOWS] http://www.nyc-arecs.org/WinConvers.zip xConvers-0.8.3-26 (updated 2020) [LINUX Fedora/RedHat] https://fedora.pkgs.org/rawhide/fedora-aarch64/xconvers-0.8.3-26.fc33.aarch… COLRCONV-0.99.3-4 [LINUX Debian/Ubuntu/Raspbian] https://packages.debian.org/jessie/colrconv HexChat 2.14.3 [WINDOWS] http://hexchat.github.io Pidgin 2.13.0 [WINDOWS] http://pidgin.im/ WebConvers [ANY O/S AND ANY BROWSER] http://www.n2nov.net/webconvers/frame.php?jsflag=yes KiwiIRC Web Client [ANY O/S AND ANY BROWSER] https://kiwiirc.com/ Mozilla Thunderbird email software built-in chat tab -- 73 de N2NOV

5 4

Can't reach raqi.ca
by Jean-Pierre Desilets 07 Dec '20

07 Dec '20

Hi group We are many ham in the 44.135.0.0 (Canada) who can't reach raqi.ca (radio amateur du Quebec ) using ipip to the ucsd gateway . the reverse way won't work ether . Elsewhere is fine . Can you ping or traceroute to raqi.ca from your 44 address ? Let me know . Need help to solve this issue. The traceroute raqi.ca to ve2se.ampr.org : $ traceroute ve2se.ampr.org traceroute to ve2se.ampr.org (44.135.198.1), 30 hops max, 60 byte packets 1 66.159.41.1 (66.159.41.1) 0.195 ms 0.262 ms 0.294 ms 2 mtl.core-a3.cronomagic.com (66.159.42.25) 1.050 ms 1.133 ms 1.157 ms 3 161-81-55-206.static.cogecodata.net (206.55.81.161) 2.051 ms 2.090 ms 2.340 ms 4 199-167-152-144.beanfield.net (199.167.152.144) 2.507 ms 2.519 ms 2.521 ms 5 hu0-0-1-0.pe04.1250RenelevesqueBl01.YUL.beanfield.com (199.167.152.63) 2.636 ms 2.647 ms 2.709 ms 6 hu0-0-1-0.pe05.1250RenelevesqueBl01.YUL.beanfield.com (199.167.152.65) 2.376 ms 2.976 ms 2.836 ms 7 et52-1.lsr01.1250ReneLevesqueBl01.YUL.beanfield.com (199.167.152.67) 2.269 ms 2.347 ms 2.392 ms 8 lo0-1.bdr01.1250ReneLevesqueBl01.YUL.beanfield.com (72.15.48.50) 2.655 ms 2.775 ms 2.777 ms 9 et-1-0-29.edge2.NewYork6.Level3.net (4.30.176.121) 11.466 ms 11.516 ms 11.496 ms 10 * * * 11 CENIC.ear1.SanJose1.Level3.net (4.15.122.46) 77.857 ms 77.901 ms 76.474 ms 12 dc-svl-agg8--svl-agg10-300g.cenic.net (137.164.11.81) 75.180 ms 75.216 ms 75.823 ms 13 dc-lax-agg8--svl-agg8--100ge--2.cenic.net (137.164.11.20) 76.697 ms lax-agg8--svl-agg8-100g-3.cenic.net (137.164.11.66) 76.713 ms dc-lax-agg8--svl-agg8-100ge-1.cenic.net (137.164.11.0) 77.384 ms 14 * * * 15 dc-sdg-agg4--tus-agg8-300g.cenic.net (137.164.11.85) 77.520 ms 77.092 ms 76.981 ms 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * 73's de Jean-Pierre ve2se

8 11

Re: [44net] GRE tunnels
by Rob Janssen 05 Dec '20

05 Dec '20

>GRE works just fine depending on your system. We've never had any problems with GRE except using Mikrotik devices. There is a bug in the GRE implementation on MikroTiks where you will experience a 20-30% packet loss when the system is under any non-trivial use (e.g. multiple audio streams or a file transfer). Several versions of the OS and several different hardware platforms all experienced the same issue. We changed to IPIP and IPIP6 and the issue disappeared with no other reconfiguration. We're using a mix of IPIP, IPIP6, and GRE6 tunnels to a number of sites fed out of our VPS gateway. I cannot confirm that at all. We use GRE tunnels inside our network to connect isolated areas back to our gateway over internet tunnels, and it works very well. The gateway router is a MikroTik CCR1009 and most users use MikroTik RB750Gr3 or comparable routers. No packet loss issues at all. There are of course a couple of things you need to watch for: - the "keepalive" mechanism is a defacto-standard thingy that is not working in standard Linux systems so it has to be kept disabled when the other side is not a MikroTik or maybe Cisco or comparable router - as for any tunnel, the MTU is always lower than 1500 and you cannot send fullsize packets through it without fragmentation. it is best to install a TCP MSS clamping rule to limit the MTU of most traffic - there is a bug in the firewall of more recent RouterOS versions which causes GRE traffic not to be matched by Established/Related firewall rules, and be stamped as Invalid. So when you have the default ruleset of "accept Established/Related, drop Invalid, then accept certain incoming traffic" you need to insert a rule that accepts GRE traffic from your peers BEFORE the "drop Invalid" rule. Of course you can always use IPIP instead. I have chosen GRE in the hope that it is more widely available on other makes of routers, and also it can transport IPv6 in the future. But as GRE usually requires fixed public addresses on each end of the tunnel and also is often a bit troublesome to pass through NAT routers, we also offer the additional option of L2TP/IPsec tunnels, which can be setup from a dynamic address and have no issues with NAT on the client side. (the gateway router itself of course is directly on a fixed address) Rob

4 3

GRE tunnels
by pete M 04 Dec '20

04 Dec '20

Hi everyone, Anyone been playing with GRE tunneling? I am looking at that solution to bring part of my /24 to sites where I have multiple machine that each need a 44 address. GRE have no encryption, it is only an encapsulation of a Layer 2 packet. This lower the actual possible MTU size lowering the throughput slightly. But it is an easy way to connect a site to the VPS. At the same time, we dont need encryption as all the data that are passing into that tunnel is supposed to be ok to route on the internet. and if they contain special thing they should already be encrypted with tls/ssl or other mean of securing the connection. Anyone have experience with this? I would then use openvpn is its normal way for simple client. Then I imagine I will need to bridge both tunnel so that every one could talk to each other at the VPS level. Sounds plausible? Pierre VE2PF

6 16

Re: [44net] OT: Any OpenVPN Guru here?
by lleachii＠aol.com 30 Nov '20

30 Nov '20

Pierre, I'd personally suggest OpenVPN Access Server. There's a straightforward web GUI to setup everything. I think DHCP/Layer 2 requires Windows clients. https://openvpn.net/download-open-vpn/ 73, - Lynwood KB3VWG

3 3

OT: Any OpenVPN Guru here?
by pete M 30 Nov '20

30 Nov '20

Hi, me again with an OT kind of topic. I have been pretty happy with the way the vps at vultr and the bgp announce been doing, this did not missed a beat since it been fix, again thanks to every one that helped. Now I need a push in the right direction for OpenVpn. Went on the openvpn forum, asked a noob question, got shamed post by a prick, waited for someone else to try to help me. Now I am asking the ham community for help. I have seen many tutorial/video/explanation and how to's for OpenVpn. Most are tutorial where, you start a script, enter some magic numbers its start installing package after package and it start working. Youhou! NOT! That ain't the kind of stuff I am looking for. If I want to support the server and be able to debug it in case it fail I need to know where and how all this works. Let me tell you my goal. I will have multiple site that will connect to the vpn server. on those site Multiple machine will need a 44net address. some will have fix address but I want to also have some assigned by dhcp. Now I could also have some simple client that will connect and those will have dhcp address. How do I manage that into OpenVpn. Does the dhcp vs fix address is managed by the OpenVpn config? Or does I need to have a local dhcp server at the site (the router that will connect as the client) will I have to do some bridging between my site (client to client communication)? And finally is there a real good how to that is not 300 page long, as hard to read as the U.N. whole bylaws and treaty and that a layman can understand somewhere& hopefully that is not a recipe that say, add some pixi dust here, open notepad 3 time while typing "I will not read my sister's diary in front of the whole class" Copyright the Simpson's . 200 time, without saving the file between each opening and closing, and hoping that it will do the job. >From a pretty tired guy of searching the answer to life. Yeah I know its 42. Pierre VE2PF

3 2

Re: [44net] Proposed WWconvers Channel Scheme
by n2nov＠n2nov.ampr.org 27 Nov '20

27 Nov '20

That is why the discussion and exposing the long dormant system to new users. These are not rules but logical suggestion on using the system while playing nice in the sandbox called the entire planet. Time will tell, but not if we do not talk about it in the open. I agree about chat clients. I use HexChat. -- 73 de N2NOV

3 2

Proposed WWconvers Channel Scheme
by n2nov＠n2nov.ampr.org 27 Nov '20

27 Nov '20

PROPOSED WWCONVERS CHANNEL SCHEME There are 32767 possible channels in the WWconvers with channel 0 reserved for a local bbs to use as it's default when users log onto their system. Finding other stations by area, interest or any other special use can get a little confusing. Some countries have settled on a scheme where their users can find each other based on the second number of their assigned 44Net (AMPR) address. For example, Greece is assigned 44.154.0.0/16 and they can be found on channel 154. In the USA (because of sheer numbers of systems over the years) the second number in the address is typically an entire state with some having multiple subnets (California has 6). There has been an effort in recent years to clean up the numbers and subnets no longer in use and this resulted in the range from 44.191.0.0/16 to 44.255.0.0/16 to be sold to Amazon. To make things easier, I am proposing a somewhat logical layout to the channel usage, not only by the 44Net addresses but also by specilized uses for activities and watering holes like HF/VHF/UHF frequencies. As you can see, there will be plenty of space for adhoc arrangements. Discussions are welcomed and encouraged as how to use this space for the benefit of many different groups and interests. DEFAULT Channel 0 . default local use and not propagated across the WWconvers system. REGIONAL Channel 1 through 190 . based on second number in the 44Net/AMPR addresses MATCHING TO RF FREQUENCY USED (ie: net on 7240 kHz would use channel 7240) 1800-1999 160m Channels 3500-3999 80m Channels 7000-7299 40m Channels 10100-10149 30m Channels 14000-14349 20m Channels 18068-18167 17m Channels 21000-21449 20m Channels 24890-24989 12m Channels 28000-29699 10m Channels 5000-5399 6m Channels 14400-14799 2m Channels 22200-22499 1.25m Channels 4200-4499 70cm Channels 9020-9279 33cm Channels 12400-12999 23cm Channels CURRENT SPECIALTY USERS 625 . UHF Amateur TV Channel in UK 10177 . OK2KOJ Club Channel in Czech Republic 14736 . WC2OEM Channel for NYC Amateur Radio Emergency Communications Service SET AS LOCAL BBS USE (ie. JNOS Systems, etc) 211 . Local NCS/ALT Channel for nets 411 . Local WX Event Channel (Skywarn nets) 911 . Local Emergency Net Activation Channel -- 73 de N2NOV

2 1

Re: [44net] Routing from and to the internet
by Andy Holland 26 Nov '20

26 Nov '20

Andy, I have the ExgeRouter X… would the config file also work on my router? Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10

1 0

Hub_NA WWconvers Available For Use
by n2nov＠n2nov.ampr.org 25 Nov '20

25 Nov '20

For those who have the capability to link their systems for WWconvers/chat, I host the Hub_NA chat server that links to various chat hubs in Europe. We are hoping that systems in other parts of the world get set up for chat. Hub_NA can be reached at 44.68.41.2 or convers.n2nov.net, both on port 3600. If you are using the non-44Net address, you have to contact me first at n2nov(a)n2nov.net to be added to the permissions file. -- 73 de N2NOV

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

44net