[nos-bbs] Missing something - 44 net
Barry Siegfried
k2mf at nnj.k2mf.ampr.org
Sun Jul 23 17:26:46 EDT 2006
[wa7nwp at jnos.org wrote]:
> In 10 minutes I can set up a new no-ip.com account and get a dynamic
> domain name routed to an Internet gateway (*NOS, linux, etc). In 5
> minutes I can add an entry on one of my existing domains. In an ATU
What is an ATU?
> or 2 I could implement the dynamic dns tools from Sourceforge and have
> a full automatic implementation (ala no-ip.com) of my own.
Also, in about one minute, you could have all of your 44-net frames
rerouted to your new Internet gateway (*NOS, linux, etc.) IP address
using DGipip and a reliable hosting gateway. Your 44-net IP addresses
are fixed and they provide users access to as many services as you'd
like to run without having to rely on how many port forwarding entries
you will be allowed to add into the consumer IP/NAT router that manages
your internet connection.
Yes, there are advantages and disadvantages to ANY solution, and
yours are quite valid. I was just simply trying to point out to
George that the amprnet solution IS available to those of us who
are amateurs if we want to make use of them.
> Why would I want to add the single points of failure, additional
> layers of bureaucracy and added hassles of tunneling and source
> address filtering
Source address filtering can be eliminated by using a tunneling
solution which works quite well if you have a reliable SAFE gateway
to use for this purpose. Ok, so you think that tunneling is a hassle.
Well, yes it is a bit, but once it is set up it does tend to keep
working.
> when I can have 99% of everything so simply without fighting the
> 44/ampr.org battle?
Now which battle and bureaucracy are those? Yes, there certainly ARE
points of failure above using the amprnet solution, but most of them
have become pretty reliable over the last 15 years and nobody has
time to run bureaucracies anymore so as far as I know, I haven't been
shut out of anything that I can discern.
> Most of us in this area, but not all, (Hi Ken) have decided that any
> new on the air operation will be done with non-routable IP's (10.xxx
> or 192.168.x.x) using NAT.
So perhaps that is why the 44.24.110.35 appears to be missing now? :(
If Ken has no plans whatsoever to reactivate that machine it would be
great if you could gently mention to him that it would be appreciated
if he could delete the gateways file entry for that machine.
> It's just so much simpler and cleaner.
No doubt it is, for certain applications. And for others, the amprnet
solution might actually be "cleaner". It all depends what somebody is
trying to accomplish. Different strokes for different folks. And
that's what makes the world go 'round. :)
> Getting JNOS back on the air here. Should be on shortly with 3 RF
> ports. Darn it's one fun program.
Yes, it surely is! :)
> > NAT *can* be incorporated into JNOS. NAT for xNOS was actually
> > developed a long time ago. It is simply a matter of somebody
> > wanting to take the time to port it into JNOS.
>
> Which other *NOS has the NAT? TNOS? This sounds like a useful
> addition to JNOS.
MFNOS has had NAT since 1998, although because the functionality of
NAT for nearly all of us has quickly been migrating to commercially
available consumer IP/NAT routers, it has become used less and less
over the past few years. JNOS *might* benefit from having it ported
but that is a call that only Maiko can make. Like anything else, it
comes down to the issue of need vs. amount of work and time to implement.
In 1998 I obviously thought I had enough of a need to write the code
(I developed the NOS IP/NAT solution from scratch without copying
Linux's implementation). It was a pretty big project but I obviously
felt that the benefits it would provide for me at that time would
outweigh the sacrifices. If I were re-evaluating this today, then
with the consumer IP/NAT router appliances that are currently
commercially available, I probably wouldn't do it.
73, de Barry, K2MF >>
o
<|> Barry Siegfried
+---------/-\---------------------------+
| Internet | bgs at mfnos.net |
| HomePage | http://www.mfnos.net/~bgs |
+----------+----------------------------+
| Amprnet | k2mf at nnj.k2mf.ampr.org |
| PBBS | k2mf at k2ge.#cnj.nj.usa.noam |
+----------+----------------------------+
More information about the nos-bbs
mailing list