44net

44net@mailman.ampr.org

3 participants
3203 discussions

Routing and encap minor issue in JNOS
by Mark Phillips 05 Sep '13

05 Sep '13

Hi all, Firstly, if this has been done to death before please forgive me. I could not find anything in the archive. Secondly, I have noticed an "issue" with the routing and encap within JNOS. It would seem that if a 44 station tries to contact me all works fine. For example I can communicate with N2NOV and GB7CIP exactly how you would expect. However, if a "public" address contacts me, I get their connect requests in encap format via uscd but then I send them my response directly rather than back the same way it came. This means that there can be no public access to my system via the Internet. What have I missed? JNOS will not allow me to set the default route via encap/uscd and I don't really want to send all my traffic (eg DNS lookups) via there anyway. How can I respond to connections in the same way that I received them? Thinking about it, it makes sense that JNOS replies directly. Once it unpacks the packet and discovers an encap'd one inside it will work on that one exclusively. Thanks Mark

4 9

jnos
by Eric Fort 05 Sep '13

05 Sep '13

Does a version of jnos exist that is stripped of all it's networking code thus just offering the the bbs parts? AF6EP

2 2

Something simple
by Rod Ekholm 03 Sep '13

03 Sep '13

I am interested in something simple. I am not interested in creating a Linux box to do my routing, as I see no need for it. It's almost worse than having a network that is vendor specific!! I don't tell you how to run your internet.. you don't tell me what router I have to use. I use Mikrotik for my edge technology, just because it's what I am familiar with. For me it's easy enough. I am interested in creating some links with others, hopefully in the NW towards the Seattle area. I have my own system design that I am planning on implementing starting early this fall. I have no interest however in trying to use some script (nice work on it though..) to make it work, but would rather have some common assembly of networks that can connect to each other. Unfortunatley, until this is done in a large enough fashion, it looks like i am talking static routes to and from some other networks. My intention is not to rock the boat of what has been done here, but it seem like there is little direction of how the network is assembled and coming to a common point of presence. until one person or gorup comes up and offers some stability of how to route the network accordingly, I fear my use of AMPR is only for some of it's tunneling ability with the use of our 44/8 addressing. I had no intentions of it before, so if I end up not using them later, now loss on my end. Let me know if anyone is interested in creating some more static links, and / or trying to do some sort of edge router that can have an open communications standard, and not a customized (could otherwise spelled proprietary) protocol in the middle. Thanks to you all and have a great day! -- Rod Ekholm KC7AAD kc7aad(a)gmail.com Spokane, WA (509) 435-3400

8 23

Chris Smith G1FEF?
by Brian Kantor 02 Sep '13

02 Sep '13

Has anyone heard from Chris Smith, G1FEF in the past few months? All my email to him has gone unanswered so I'm worried that he might be ill. - Brian

4 3

Re: [44net] ripv2
by Rob Janssen 02 Sep '13

02 Sep '13

> Subject: > [44net] ripv2 > From: > Brian Rogers <n1uro(a)n1uro.ampr.org> > Date: > 09/01/2013 12:12 AM > > To: > AMPRNet working group <44net(a)hamradio.ucsd.edu> > > > There appears to be at least one valid route missing in the rip > broadcasts. aa6hf is not received via rip however it is using the munge > script... is there an issue in the portal? I receive the routes from RIP and his route is OK. 44.17.0.128/31 via 67.49.91.65 dev tunl0 proto ampr-ripd onlink

5 5

AMPRNet-config
by Willie Hein WJ3G 01 Sep '13

01 Sep '13

Greetings, I'm again planning the setup of a gateway here at the Balogna Capitol, much to the wonderment of a few. Prelim's are done, ie: static ip, registering in the portal, etc. Now I'm back to a place I've been before, automating the startup, and configuration. Something I'm surprised we haven't overcome with a gui by now, and unfortunately way above my pay scale.:) I did have this working before, so I'm hoping with little changes I'll have the init.d scripts and all updated. I'll certainly make them available, maybe on the wiki when I'm done. I realize that it will take changes to make them work on other distros. Maybe it's time to see what the commonalities are, in hopes of developing a standard config tool. I'd certainly like to take this off list till there is something worth showing. Anyone interested? Best regards, Willie, WJ3G

1 0

Microtik is Broadcasting
by Michael E. Fox - N6MEF 01 Sep '13

01 Sep '13

Someone with a Microtik is evidently broadcasting on the AMPRnet tunnels. Dest address 255.255.255.255 Source address 0.0.0.0 UDP port 5678 Please stop! Michael

1 0

Re: [44net] Off Topic.. NOSview
by kb9mwr＠gmail.com 31 Aug '13

31 Aug '13

I'd like a copy too. Is there anyway we have have a centralized place for stuff like this? I have to admit that wiki's aren't really for me. Editing them I find painful. And there are a number of scripts and software packages that I have been trying to archive. -- And a couple messages ago the question was asked "Has anyone tried to use transverters from 2.4GHz to 432 Mhz?" Does such a transverter exist? A $40 Ubiquiti 2 GHz bullet coupled with a few watt (2.4 Ghz to 432 MHz) transverter might work better than a $170 mini PCI radio card combined with a $85 router board and all that. http://www.xagyl.com/store_us/product.php?productid=31 There are some impressive 802.11 networks being built by European amateurs. There also seems to be quite a lot of talent with microwave design over there.

1 0

rip44d
by Rob Janssen 31 Aug '13

31 Aug '13

Hi Hessu, I am trying to get rip44d working on my Raspberry Pi. For some reason, I cannot get it to receive the 44.0.0.1 -> 224.0.0.9 transmissions. The socket is listening on port 520, when I trace tunl0 I see the packets arriving every 5 minutes, but the rip44d (running with -v) remains absolutely silent. Any idea what that can be? I saw that there is a 2nd set of transmissions, from 169.228.66.251 to my internet address, oddly from port 520 to port 34348. With some small changes to rip44d, to change the source address check and the port number, and to remove the multicast handling, it receives those packets perfectly and the routes are added. Do you have any idea what this can be? The Pi is running Linux 3.6.11+ (raspbian wheezy), and I installed the perl modules just as you explain on the wiki. Of course I could make my changes conditional and add a flag to listen to this alternate transmission, but I don't know about the status (maybe they will stop sometime?). It could be better to fix the problem, if I knew how... 73, Rob PE1CHL

4 3

Re: [44net] 44Net Digest, rip44d
by Rob Janssen 30 Aug '13

30 Aug '13

> Subject: > Re: [44net] rip44d > From: > "Kutche, Jerry (Mitchell) USA" <JKutche(a)lehighcement.com> > Date: > 08/30/2013 12:40 PM > > To: > AMPRNet working group <44net(a)hamradio.ucsd.edu>, Heikki Hannikainen <hessu(a)hes.iki.fi> > > > Is your pi in the DMZ? I had to do that with HP Linux BOX a non-pi.... Might try that? > > Jerry Kutche > Electrical Supervisor My Pi is in a datacenter, directly connected to Internet. Not behind a NAT router, that is. I have not further researched the matter, as I have solved it by using ampr-ripd and not using multicast. I think there is something missing or not configured that is related to multicast. The kernel config is: CONFIG_IP_MULTICAST=y # CONFIG_IP_MROUTE is not set Multicast routing is not enabled. On my home PC (SuSE Linux), it is enabled. Maybe this is a requirement even for the reception of multicast datagrams. Rob

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

44net