Re: [44net] Intermittent host connectivity issues

Thanks, Jim Chris On Mon, Feb 27, 2012 at 11:50 AM, Jim Fuller - N7VR <n7vr(a)n7vr.org> wrote: > > Hi Chris: > > The 44.16.2.32/27 subnet is: >        44.16.2.32/27           44.16.2.32 to 44.16.2.63 > > Jim Fuller > N7VR -- http://www.n7vr.org > International TCP/IP Gateways Robot Operator -- http://www.ampr-gateways.org > > MTAPRS NET Server Operator -- http://www.mtaprs.net > CWOP-2 -- http://www.wxqa.com > IRLP Node 3398 - http://irlp.fuller.net > Original ARECC contributor > > -----Original Message----- > From: Chris Maness [mailto:chris@chrismaness.com] > Sent: Sunday, February 26, 2012 5:00 PM > To: w6ray(a)sbcglobal.net; AMPRNet working group > Subject: Re: [44net] Intermittent host connectivity issues > > On Sun, Feb 26, 2012 at 3:44 PM, Chris Maness <chris(a)chrismaness.com> wrote: >> On Sun, Feb 26, 2012 at 12:01 PM, Raymond Quinn <w6ray(a)sbcglobal.net> > wrote: >>> Hmmm. I see you have a link with Brett, WA7V. >>> >>> He also has static addresses, and was able to assign a commercial IP >>> address to his linux box, as well as his NOS side. >>> >>> You might want to consult him on how that is done. >>> >>> In the mean time, does your JNOS have a LAN address of 192.168.x.x ?? >>> >>> It is behind a DSL Modem/Router.  It is a 2wire.  However, I have 5 >>> static IPs.  It does not allow me to use one of the public IPs for >>> Jnos.  It does not add that IP to the local network list for >>> configuration, and therfore does not permit traffic to Jnos.  I >>> therfore had to use the munge script to build tunnels in Linux.  This >>> is ok, because it does protect Jnos from attacks. >>> >>> >>> Chris, >>> >>> It appears that you have the same or quite similar setup that I have. >>> I have my Linux box with a public static IP address and use that in >>> the POINTOPOINT line. Eventually, the Linux box will appear in the >>> 2wire and when it does, should automatically allow all traffic to that > static address. >> >> It does exactly that. >> >>> >>> (Of course, at present JNOS is locking up after a few hours, but that >>> is >>> unrelated) >>> >>> If you don't hear from Brett, I am willing to share what I have worked > out. >>> I still have more to do, but it may get you started. As always, make >>> sure you make a backup of your current setup should it not work as mine > does. >>> >> >> It works just fine save one host on AMPR-NET.  I wouldn't care save he >> is my friend and one of the closest *NOS BBS to my site. >> >> I had also been in touch with AT&T customer service.  The suggested I >> purchase a Motorola router from them.  I wish my Linux box was back >> behind a Cisco on a commercial T1 like it was in the beginning.  I had >> direct 44net-to-inet connectivity.  However, the AT&T network is >> controlled by the packet Gustapo goose stepping with their tight >> firewall rules.  I guess that is good for the brain dead masses, but >> it kind of makes playing with the stuff we do a pain in the toosh. >> >> Thaks es 73's >> de Chris KQ6UP > > My Linux box can ping his Linux box, so that is good.  I am not sure I have > the whole doted quad with a forward slash business down.  I think this is > his encap.txt entry: > > route addprivate 44.16.2.32/27 encap 173.60.166.190 > > Since I believe that 44.16.2.46 is included in that subnet.  Is the above > subnet 44.16.2.32-64? > > Thanks, > Chris Maness > > _________________________________________ > 44Net mailing list > 44Net(a)hamradio.ucsd.edu > http://hamradio.ucsd.edu/mailman/listinfo/44net > > > _________________________________________ > 44Net mailing list > 44Net(a)hamradio.ucsd.edu > http://hamradio.ucsd.edu/mailman/listinfo/44net