44net

44net@mailman.ampr.org

2 participants
3201 discussions

rip44d seg faults
by Jason R Begley 10 Jul '14

10 Jul '14

I am having an issue running rip44d on Arch after a recent update (perl (5.18.2-2 -> 5.20.0-5) I suspect). Please see the below BT and let me know if you can help. gdb -args perl rip44d GNU gdb (GDB) 7.7.1 Copyright (C) 2014 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-unknown-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from perl...(no debugging symbols found)...done. (gdb) r Starting program: /usr/bin/perl rip44d warning: Could not load shared library symbols for linux-vdso.so.1. Do you need "set solib-search-path" or "set sysroot"? [Thread debugging using libthread_db enabled] Using host libthread_db library "/usr/lib/libthread_db.so.1". Program received signal SIGSEGV, Segmentation fault. 0x00007ffff67019ce in boot_IO__Interface () from /usr/lib/perl5/site_perl/auto/IO/Interface/Interface.so (gdb) bt #0 0x00007ffff67019ce in boot_IO__Interface () from /usr/lib/perl5/site_perl/auto/IO/Interface/Interface.so #1 0x00007ffff7aeb93b in Perl_pp_entersub () from /usr/lib/perl5/core_perl/CORE/libperl.so #2 0x00007ffff7ae41f6 in Perl_runops_standard () from /usr/lib/perl5/core_perl/CORE/libperl.so #3 0x00007ffff7a6dde5 in Perl_call_sv () from /usr/lib/perl5/core_perl/CORE/libperl.so #4 0x00007ffff7a70133 in Perl_call_list () from /usr/lib/perl5/core_perl/CORE/libperl.so #5 0x00007ffff7a53d51 in S_process_special_blocks () from /usr/lib/perl5/core_perl/CORE/libperl.so #6 0x00007ffff7a67592 in Perl_newATTRSUB_x () from /usr/lib/perl5/core_perl/CORE/libperl.so #7 0x00007ffff7a6a630 in Perl_utilize () from /usr/lib/perl5/core_perl/CORE/libperl.so #8 0x00007ffff7a9d0b9 in Perl_yyparse () from /usr/lib/perl5/core_perl/CORE/libperl.so #9 0x00007ffff7b1d942 in S_doeval () from /usr/lib/perl5/core_perl/CORE/libperl.so #10 0x00007ffff7b2a72c in Perl_pp_entereval () from /usr/lib/perl5/core_perl/CORE/libperl.so #11 0x00007ffff7ae41f6 in Perl_runops_standard () from /usr/lib/perl5/core_perl/CORE/libperl.so #12 0x00007ffff7a6dde5 in Perl_call_sv () from /usr/lib/perl5/core_perl/CORE/libperl.so #13 0x00007ffff7a70133 in Perl_call_list () from /usr/lib/perl5/core_perl/CORE/libperl.so #14 0x00007ffff7a53d51 in S_process_special_blocks () from /usr/lib/perl5/core_perl/CORE/libperl.so #15 0x00007ffff7a67592 in Perl_newATTRSUB_x () from /usr/lib/perl5/core_perl/CORE/libperl.so #16 0x00007ffff7a9d781 in Perl_yyparse () from /usr/lib/perl5/core_perl/CORE/libperl.so #17 0x00007ffff7b1d942 in S_doeval () from /usr/lib/perl5/core_perl/CORE/libperl.so #18 0x00007ffff7b29510 in Perl_pp_require () from /usr/lib/perl5/core_perl/CORE/libperl.so #19 0x00007ffff7ae41f6 in Perl_runops_standard () from /usr/lib/perl5/core_perl/CORE/libperl.so #20 0x00007ffff7a6dde5 in Perl_call_sv () from /usr/lib/perl5/core_perl/CORE/libperl.so #21 0x00007ffff7a70133 in Perl_call_list () from /usr/lib/perl5/core_perl/CORE/libperl.so #22 0x00007ffff7a53d51 in S_process_special_blocks () from /usr/lib/perl5/core_perl/CORE/libperl.so #23 0x00007ffff7a67592 in Perl_newATTRSUB_x () from /usr/lib/perl5/core_perl/CORE/libperl.so #24 0x00007ffff7a6a630 in Perl_utilize () from /usr/lib/perl5/core_perl/CORE/libperl.so #25 0x00007ffff7a9d0b9 in Perl_yyparse () from /usr/lib/perl5/core_perl/CORE/libperl.so #26 0x00007ffff7a74215 in perl_parse () from /usr/lib/perl5/core_perl/CORE/libperl.so #27 0x0000000000400d9b in main () (gdb)

3 3

tunl0
by gm4upx＠gb7jd.co.uk 09 Jul '14

09 Jul '14

Hello, While waiting for my allocation to be actioned and having little or no experience I decided to experiment to learn more about the use of the tunnel interface and what would be possible with it. I have all ports forwarded from my ISP's modem to a PC I am using as a router. I have a tunnel set up on a one to one basis with a forwarding partner and it works well. My router PC has three network cards, one with a 192.x.x.x/24 address and the other two with a 44.x.x.x/29 and 44.x.x.x/27 address. Connections between both 44.x.x.x addresses work with my forwarding partner and I can forward between my 44.x.x.x addresses using [ eth0 ] but not when I set the route at each via [ tunl0 ]. Is it something simple I have missed ?? Regards, Ian..

2 1

New member - VE5EIS
by Jim MacKenzie 23 Jun '14

23 Jun '14

Hi all, Just joining the list... I applied for a 44net subnet last week and am beginning the steps to do something cool and interesting with this. I'm a new ham as of April 2013 (VE5EIS) and work on both VHF/UHF and the HF bands. I also am involved with a hobby project in Canada called the Metanetwork, where we link disparate networks together and learn about networking, route advertising, and so on. The project has gotten me to learn about all sorts of useful networking things such as using OpenVPN and deploying IPv6. My routers and my most interesting computers run Linux or BSD. I'm hoping to learn more about packet radio and deploy some RF hops on my subnet. I have some ideas of some useful projects that could be done, e.g. UUCP over RF for email links between sites that don't have Internet or telephone connectivity. At this point I'm working on getting either a tunnel or permission to set up BGP advertising for my subnet, and then it'll be time to figure out what to do with this project. I'm hoping to have a lot of fun with it and learn from you guys - see what you're doing, grab some great ideas, maybe leverage them with some of my own experience and knowledge. Thanks, Jim VE5EIS Regina, Saskatchewan, Canada DO70

2 2

Re: [44net] Draytek Vigor 2710Vn
by kb9mwr＠gmail.com 07 Jun '14

07 Jun '14

The solution is in section 3.3.2 of the user guide : DMZ Host http://www.draytek.co.uk/support/downloads Another option is is to put the modem in a Bridge Mode see page 35.

1 0

Draytek Vigor 2710Vn
by demetre.sv1uy 07 Jun '14

07 Jun '14

Hi all, Does anyone know if a Draytek Vigor 2710Vn ADSL router can do IPENCAP (Protocol 4) so that I can use it in my AMPRnet GATEWAY? I can't make it work, although my GATEWAY works OK when I use a TP-Link WR1043ND Broadband Router with DD-WRT Firmware! -- 73 de Demetre - SV1UY e-mail: demetre.sv1uy(a)gmail.com Radio e-mail: sv1uy(a)winlink.org AMPRnet e-mail: sv1uy(a)sv1uy.ampr.org PACKET mail: SV1UY(a)SV1UY.ATH.GRC.EU WEB: http://www.qsl.net/sv1uy

1 0

AMPR Gateway down?
by lx1duc＠laru.lu 28 May '14

28 May '14

Good afternoon/morning, I'm unable traceroute from the internet to 44.161.200.11, the trace stops at ebu3b-6509-nodem-core-interconnect-vl910-bcast-255-131.ucsd.edu (132.239.255.131). Is anybody experiencing similar issues? 73 de Marc, LX1DUC

4 4

Gateways to where?
by kb9mwr＠gmail.com 28 May '14

28 May '14

I have been reading this common thread on the.broadband hamnet forums. "Are there any lists with available tunnel connections?" On the portal, unless noted in the notes area, the only way to really tell is from looking up the geographic area for the listed subnet. This is probably something we should re-think. You shouldn't have to do all that leg work to see what areas have tunnels available. If we can make that easier to determine, I'd like to think more people will find what we are doing here on 44net more useful to them. Back to painful data loss recovery..

3 2

Strange route entry: 44.140.0.0/16
by Marius Petrescu 23 May '14

23 May '14

Just peeked in th RIP broadcasts today: 44.140.0.0/16 via 44.140.0.1 This entry is invalid, since the gateway is in its own subnet and no other entry for 44.140.0.1 exists. Please correct the entry. Marius, YO2LOJ

6 8

Re: [44net] 802.11 link planning
by Steve Wright 22 May '14

22 May '14

On Thu, May 22, 2014 at 7:00 AM, <44net-request(a)hamradio.ucsd.edu> wrote: > http://www.scc-ares-races.org/mesh/preso/Basic_WiFi_Net_Planning_v140516.pdf That's a really good document. This really needs to be in the wiki, or else no one can find it. It can be dangerous for total newbs to read this, because it suggests the process is fraught with danger, which of course it's not. We all agree that it's actually completely trivial to put up an AP and connect to it from miles away. rmonline is also a good tool to quickly check links for LOS. There is also some Android app as well. http://www.ve2dbe.com/rmonline.html I don't do link calcs any more - there's just no need to. A pair of Nanobridges will work real well over a huge distance provided there is line-of-sight. Really, this stuff is point-and-shoot trivial now. A really important consideration with an 802.11 ham network, is keeping the snake-oil protocols separate from the ones that actually work! Viz, don't run mesh on an AirMax channel. AirMax can push a huge amount of data, even on a busy channel. Advice I'd give to a group of total newbies who want to build a network, is ignore all the tech talk and go buy a 2.4GHz AirMax sector access point, install on a nice high line-of-sight location, and just play with connecting to it from all around the place. There's nothing complicated about it at all. The tricky stuff does come later, but you'll get to that once you see the network up and alive, and your enthusiasm starts to take off. Newbs giving up early because it looks too hard is an avoidable tragedy. Steve ZL1BHD

1 0

Re: [44net] 44Net Digest, Vol 3, Issue 104
by Rob Janssen 21 May '14

21 May '14

44net-request(a)hamradio.ucsd.edu wrote: > Subject: > Re: [44net] 44Net Digest, Vol 3, Issue 103 > From: > Pedro Converso <pconver(a)gmail.com> > Date: > 05/21/2014 12:17 AM > > To: > AMPRNet working group <44net(a)hamradio.ucsd.edu> > > > Hello Rob et all crew aboard this 44 ship, > > Thanks for taking time to answer, > > If I ping from my jnos> ping pe1chl.ampr.org then ping is answered. > > If I ping from any operating system pe1chl.ampr.org or using remote ping > fromhttps://www.wormly.com/test_remote_ping then ping is not answered. > > Therefore any other function as web, telnet, nntp, etc are not answered or > handled using a PC with any operating system other than a linux with encap. > > This is my concern that also happens to others ampr system including yours. Oh but that is because pe1chl.ampr.org allows only traffic from net-44. It is a NET system and I don't want to open it to the abusers and portscanners. Try sys2.pe1chl.ampr.org or www.pe1chl.ampr.org. Those are Linux systems and you can ping them both from net-44 and from the entire internet. > > In fact a ping to any ampr.org does go to amprgw (169.228.66.251) as shown > by traces, and that happens using any system being or not a linux. > > Question is how to resolve this, and reason of seeking help/advice from > amprnet experts to guide toward finding a solution. > > Best 73, > lu7abf, Pedro Converso What I deduced from your trace was that incoming the packets were encapped as IP-in-IP but outgoing they were not. But maybe it is a characteristic of the way you traced, sometimes those extra encapsulations are not shown in a trace. I think the best solution today is to handle the net-44 routing in Linux and then when you want to run jnos put that behind an extra address that you route locally. Rob

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

44net