44net October 2012

44net@mailman.ampr.org

29 participants
14 discussions

It does not act ftp.ampr-gateways
by Janusz Przybylski SP1LOP 07 Oct '12

07 Oct '12

It does not it act: ftp://ftp.ampr-gateways.org/ Did I overlook something ??? -- 73 de Janusz / SP1LOP ===== Janusz J. Przybylski, SP1LOP ================== Poland AmprNet Co-ordinator [44.165/16] from: 03.2003 =====================================================

4 4

Re: [44net] It does not act ftp.ampr-gateways
by Glenn Bursell 07 Oct '12

07 Oct '12

i get the updates vy email and this is the last one i got on 10/02/2012 encap.txt,v 1.816 2012/10/02 05:02:01 gateways Exp $ # On 10/06/12, Janusz Przybylski SP1LOP <44net(a)mail.sp1lop.ampr.org> wrote: > (Please trim inclusions from previous messages) > _______________________________________________ > It does not it act: ftp://ftp.ampr-gateways.org/ > Did I overlook something ??? > > -- > > 73 de Janusz / SP1LOP > ===== Janusz J. Przybylski, SP1LOP ================== > Poland AmprNet Co-ordinator [44.165/16] from: 03.2003 > ===================================================== > > _________________________________________ > 44Net mailing list > 44Net(a)hamradio.ucsd.edu > http://hamradio.ucsd.edu/mailman/listinfo/44net > >

1 0

Re: [44net] 44Net Digest, Vol 1, Issue 79
by kb9mwr＠gmail.com 03 Oct '12

03 Oct '12

Hi, Thanks for writing this program and your support. Turns out I had the wrong netmask on my tunnel interface. Seems to be working now. 73' Steve, KB9MWR

1 0

rip44
by kb9mwr＠gmail.com 02 Oct '12

02 Oct '12

Not all that long ago I installed the new rip44d on a CentOS install. It did receive the broadcasts as I saw them in debug mode. However it didn't seem to install these routes to the local routing table. I assume that has to with networking working slightly different on the various flavor of Linux. So now I am trying with Ubuntu 10.04 server, but I can't even seem to receive the broadcasts. It just sits there in the main loop waiting for broadcasts. Yet when I watch with tcpdump, there are things going on. But I am mostly concerned by the udp port unreachable that I am responding with: (For now) I have the Linux firewall completely disabled (as far as I know... more of a RedHat guy) and connected directly to the outside world. listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes 13:30:00.337401 IP amprgw.sysnet.ucsd.edu.route > cpe-174-103-224-97.new.res.rr.com.38700: RIPv2, Response, length: 504 13:30:00.337442 IP cpe-174-103-224-97.new.res.rr.com > amprgw.sysnet.ucsd.edu: ICMP cpe-174-103-224-97.new.res.rr.com udp port 38700 unreachable, length 540 13:30:00.337454 IP amprgw.sysnet.ucsd.edu > cpe-174-103-224-97.new.res.rr.com: IP gw.ampr.org.route > rip2-routers.mcast.net.route: RIPv2, Response, length: 504 (ipip-proto-4) 13:30:00.337606 IP amprgw.sysnet.ucsd.edu.route > cpe-174-103-224-97.new.res.rr.com.38700: RIPv2, Response, length: 504 13:30:00.337624 IP cpe-174-103-224-97.new.res.rr.com > amprgw.sysnet.ucsd.edu: ICMP cpe-174-103-224-97.new.res.rr.com udp port 38700 unreachable, length 540 13:30:00.337632 IP amprgw.sysnet.ucsd.edu > cpe-174-103-224-97.new.res.rr.com: IP gw.ampr.org.route > rip2-routers.mcast.net.route: RIPv2, Response, length: 504 (ipip-proto-4) 13:30:00.337976 IP amprgw.sysnet.ucsd.edu.route > cpe-174-103-224-97.new.res.rr.com.38700: RIPv2, Response, length: 504 13:30:00.338000 IP cpe-174-103-224-97.new.res.rr.com > amprgw.sysnet.ucsd.edu: ICMP cpe-174-103-224-97.new.res.rr.com udp port 38700 unreachable, length 540 13:30:00.338008 IP amprgw.sysnet.ucsd.edu > cpe-174-103-224-97.new.res.rr.com: IP gw.ampr.org.route > rip2-routers.mcast.net.route: RIPv2, Response, length: 504 (ipip-proto-4) 13:30:00.338015 IP amprgw.sysnet.ucsd.edu.route > cpe-174-103-224-97.new.res.rr.com.38700: RIPv2, Response, length: 504 13:30:00.338026 IP cpe-174-103-224-97.new.res.rr.com > amprgw.sysnet.ucsd.edu: ICMP cpe-174-103-224-97.new.res.rr.com udp port 38700 unreachable, length 540 13:30:00.339133 IP amprgw.sysnet.ucsd.edu > cpe-174-103-224-97.new.res.rr.com: IP gw.ampr.org.route > rip2-routers.mcast.net.route: RIPv2, Response, length: 504 I am looking for tips on what I am doing wrong, or what distribution and steps those who are doing this had success with. Thanks, Steve, KB9MWR

2 1

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

44net October 2012