44net March 2017

44net@mailman.ampr.org

27 participants
25 discussions

Re: [44net] FW: JNOS2.0K and Netrom problem
by Rob Janssen 15 Mar '17

15 Mar '17

> A couple of weeks ago I downloaded and compiled jnos2.0K and found that > while the compile appeared to be successful, jnos would crash when a nodes > list was sent or I entered "netrom bc xxx" > So I have learn a lot about linux since then but not yet found the problem. > I compiled using Fedora 24 with the most latest updates on two different > PC's and today downloaded the gz file again. As you mention JNOS I presume you are not using the NET/ROM code built into the Linux kernel, but run JNOS as a user program on some tun/tap device. This means, this problem has very little to do with Linux. It is just a bug in the code, maybe combined with a property of the compiler. It sometimes happens that when you compile C code with a newer (or another) compiler than the original developer used, bugs surface that have always been present under the carpet. What happens when it crashes? Segmentation violation? That would indicate a corrupted pointer or -memory. When you type "ulimit -c unlimited" before you start the program you will get a core file (memory dump), and you can find out what is happening using gdb. Of course you need some insight in programming, but it could already help when you just print the stack backtrace (bt) and post it here. I have no personal experience with JNOS under Linux but it kind of surprises me that nowhere in the makefile or compile document there is mention of "64 bits". I would compile a program this age in 32-bit mode (my NETCHL also requires this), and that would be done by adding -m32 to the CFLAGS and installing the 32-bit development libraries first. But I leave it to others to comment if this is required. Unclean code could fail in the way you describe when compiled in 64-bit mode and work perfectly in 32-bit mode. Rob

2 2

FW: JNOS2.0K and Netrom problem
by vk1kw 15 Mar '17

15 Mar '17

Hi All, A couple of weeks ago I downloaded and compiled jnos2.0K and found that while the compile appeared to be successful, jnos would crash when a nodes list was sent or I entered "netrom bc xxx" So I have learn a lot about linux since then but not yet found the problem. I compiled using Fedora 24 with the most latest updates on two different PC's and today downloaded the gz file again. A kind user has helped enormously and sent me a file he compiled last December 11 (I think) and it runs well. Jnos2.0i compiled here today also runs well with no problems using my same config.h file. So it seems that something has changed with the "netrom broadcast" source file since around December. I have discounted Fedora mostly as jnos2.0i still compiles good so a side by side source file compare is the next do. The question is then, has anyone else had netrom crashes after a recent Fedora jnos2.0k compile please? Regards Rob vk1kw -----Original Message----- From: 44Net [mailto:44net-bounces+vk1kw=netspace.net.au@hamradio.ucsd.edu] On Behalf Of vk1kw Sent: Thursday, March 09, 2017 10:28 PM To: 44net(a)hamradio.ucsd.edu Subject: [44net] JNOS2.0K and Netrom problem (Please trim inclusions from previous messages) _______________________________________________ . _________________________________________ 44Net mailing list 44Net(a)hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net

1 0

Re: [44net] TimeFrame
by Rob Janssen 11 Mar '17

11 Mar '17

> What's the timeframe to get a block of IP's, I'd like to start testing > and messing around with AMPRnet. I've got BGP routing available, and I > can't wait to get connected. > I am my Wireless ISP, so that won't be an issue. I have a few different > routes, so I'm hoping for a /23, and put one on each end of my network. Well, it should be mentioned that going directly for BGP routing and mentioning that you are an ISP is probably not going to speed things up! It would be advisable to start experiments with IPIP tunnels or other connectivity and add BGP routing later, as a service to local hams only. There are lots of requests for large blocks to be BGP routed for AMPRnet that really are attempts from ISPs to get IPv4 space that they can no longer obtain from the normal registries, so this kind of requests and formulation will make the coordinator very wary... Rob

3 2

TimeFrame
by Michael W Rhone II 11 Mar '17

11 Mar '17

What's the timeframe to get a block of IP's, I'd like to start testing and messing around with AMPRnet. I've got BGP routing available, and I can't wait to get connected. KB3PEV Michael W Rhone II

4 5

Re: [44net] TimeFrame
by Michael Fox - N6MEF 11 Mar '17

11 Mar '17

> We do service a handful repeaters, and I'm hoping to do a some sort of > RF based TCP/IP solution, haven't found one I like yet. Any > recommendations? I could go Wifi based, 900/2.4,5ghz, but I'm hoping > to find something other then packet to use at 440 or 1.2. Check out NW Digital Radio's UDRX-440 (56kbps IPv6 on 440 MHz) MichaelN6MEF

1 0

Axip and mail
by Shawn Bush 09 Mar '17

09 Mar '17

Hello, I have linbpq32 setup and would like to get more axip connections and chat links. I also would like to get some messages flowing my direction. Could anyone help? I can give you my MAP line... 73's Shawn Bush KD8NCV

2 1

JNOS2.0K and Netrom problem
by vk1kw 09 Mar '17

09 Mar '17

Hi All, Since compiling JNOS2.0 some years ago, I have always had problems with Netrom transmits killing it back to the directory prompt. I have been using JNOS1 version ? in its place for a long time because of the same problem. But today I downloaded and compiled the latest JNOS2.0k and have the very same problem. It all compiles ok on my Fedora (latest updates) it starts and runs perfectly until it does a node transmit and dies immediately. I can poke it with all the netrom commands until I do "netrom bcnodes port" and it crashes. It receives nodes ok and populates the list ok. It also does normal "Connect XX VK1KW-5" ok. So to try another idea, I removed all my netrom options from autoexec.nos and used the defaults. (except interface /call/node name). Same problem and crashed. I notice also in this version, you need to type the whole word eg "connect" vice "con" or "ifconfig" vice "ifc". Maybe something in Fedora is not compiled in or is missing or I haven't read enough yet. There may be a conflict in my config.h but it's pretty much the same as original. So I am open to ideas. Thanks in advance Regards Rob Vk1kw

3 5

[xfbb-bis] - (new/test) mailing list
by SP2L 08 Mar '17

08 Mar '17

Last night launched fully functional mailing list named xfbb-bis and currently widely available at: http://www.sp2l.ampr.org/mailman/listinfo/xfbb-bis I warmly invite everyone wishing/willing to test performance and usability of this site. Best regards. -- Tom - SP2L ------------------------------------ It is nice to be important. But it is more important to be nice!

3 3

bogus entry in encap file
by Brian Kantor 06 Mar '17

06 Mar '17

The encap file currently contains a bogus entry: route addprivate 44.8.1.16/28 encap 0.0.0.0 I've asked Chris to make it impossible to enter this into the portal as it's clearly wrong. The ripsender and amprgw encapsulating daemon discard this already. - Brian

2 1

Re: [44net] Hello
by Tom C 05 Mar '17

05 Mar '17

W4EWH de N2XU. The 172.x.x.x space I use sits within the reserved RFC-1918 172.16.0.0/12 space reserved for private networks. I use it for my home LAN just as I could use 10/8 or anywhere in 192.168/16 space. I use it because some folks are unaware of the allocation and are more likely to see it as you have which is intended to make them shy away from messing with it OR ask questions which I welcome because it's an opportunity to help folks learn something they might not know. Any time we learn more about networks and networking to advance what we know is a good thing. 74 de N2XU Tom Cardinal/MSgt USAF (Ret)/BSCS/Security+ ce -- 73 de N2XU/Tom Cardinal/MSgt USAF (Ret)/BSCS/Security+/IPv6 Certified

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

44net March 2017