44net-request@hamradio.ucsd.edu wrote:
Subject: [44net] Pirate Packet Radio Node CB0AFU From: Jann Traschewski jann@gmx.de Date: 10/10/2014 09:22 AM
To: 44net@hamradio.ucsd.edu
Hi,
for those of you running a Packet Radio Link to CB0AFU: It seems it is *not* located in Chile but running a gateway to CB-Radio (through two links to Nodes in CB-Nodes in Austria).
Also watch out when stations use an NL prefix, the CB stations in the Netherlands commonly use(d) that, so be careful to check if they are really from Alaska.
Rob
there may be an obvious answer to my question but how are these pirate set-ups getting an allocated IP address for 44 net?
Do they just invent an allocation or do they actually apply to a coordinator who gives them out?
Andy G0HXT
On 10 Oct 2014, at 20:12, Rob Janssen pe1chl@amsat.org wrote:
(Please trim inclusions from previous messages) _______________________________________________ 44net-request@hamradio.ucsd.edu wrote:
Subject: [44net] Pirate Packet Radio Node CB0AFU From: Jann Traschewski jann@gmx.de Date: 10/10/2014 09:22 AM
To: 44net@hamradio.ucsd.edu
Hi,
for those of you running a Packet Radio Link to CB0AFU: It seems it is *not* located in Chile but running a gateway to CB-Radio (through two links to Nodes in CB-Nodes in Austria).
Also watch out when stations use an NL prefix, the CB stations in the Netherlands commonly use(d) that, so be careful to check if they are really from Alaska.
Rob
On 10/10/2014 20:22, Andy Brittain wrote:
there may be an obvious answer to my question but how are these pirate set-ups getting an allocated IP address for 44 net?
Also worth asking whether *IF* CBers are operating correctly within their band (and not wandering anywhere between 25-30MHz) whether we should embrace them onto 44net. I'm not suggesting we do so for pirates.
I realise there may be legislation issue regarding amateurs communicating with non-amateurs but setting that aside, 44net isn't exactly short of addresses and it might be a good way to encourage more people to get full licenses by reaching out.
Hello Jason et al.
This kind of answer is VERY encouraging itself! Yes, very good point of view and way to solve issue as well.
Best regards. Tom - sp2lob
On Sat, Oct 11, 2014 at 3:53 AM, sp2lob sp2lob@tlen.pl wrote:
(Please trim inclusions from previous messages) _______________________________________________ Hello Jason et al.
This kind of answer is VERY encouraging itself! Yes, very good point of view and way to solve issue as well.
Best regards. Tom - sp2lob
I hope some sarcasm was intended here.... but the <sarc> tag seems missing!
it would seem importaint to figure out how these pirates got an address and got connected in the first place so as to prevent it.
Eric - AF6EP
Eric. You're mistaken... I did NOT meant any sort of sarcasm at all! I just fully agree with Jason's point of view. Best regards. Tom - sp2lob
in that case, that opens the discussion about just who or what amprnet ought include and connect with. Personally I've been long inclined to have 44net be just like any other /8 address space and fully internet connected via bgp at multiple peering points, i.e. either we're part of the larger internet with fully routable blocks or we're not. but as of right now, that's not quite the case - amprnet is still largely isolated and amateur to amateur via static tunnels.
so who and what should amprnet/44net be?
eric - af6ep
On Sat, Oct 11, 2014 at 4:23 AM, sp2lob sp2lob@tlen.pl wrote:
(Please trim inclusions from previous messages) _______________________________________________ Eric. You're mistaken... I did NOT meant any sort of sarcasm at all! I just fully agree with Jason's point of view. Best regards. Tom - sp2lob
I think opening up 44 net is potentially a good idea but then we run in to trouble where RF is involved. Would we not be passing traffic that technically doesn’t fit under our license t’s&c’s?
Andy G0HXT On 11 Oct 2014, at 12:44, Eric Fort eric.fort@gmail.com wrote:
(Please trim inclusions from previous messages) _______________________________________________ in that case, that opens the discussion about just who or what amprnet ought include and connect with. Personally I've been long inclined to have 44net be just like any other /8 address space and fully internet connected via bgp at multiple peering points, i.e. either we're part of the larger internet with fully routable blocks or we're not. but as of right now, that's not quite the case - amprnet is still largely isolated and amateur to amateur via static tunnels.
so who and what should amprnet/44net be?
eric - af6ep
On Sat, Oct 11, 2014 at 4:23 AM, sp2lob sp2lob@tlen.pl wrote:
(Please trim inclusions from previous messages) _______________________________________________ Eric. You're mistaken... I did NOT meant any sort of sarcasm at all! I just fully agree with Jason's point of view. Best regards. Tom - sp2lob
Andy et al; On Sat, 2014-10-11 at 13:18 +0100, Andy Brittain wrote:
I think opening up 44 net is potentially a good idea but then we run in to trouble where RF is involved. Would we not be passing traffic that technically doesn’t fit under our license t’s&c’s?
Absolutely. That would easier open us up to pirating (why bother get a license if it's freely available?) and put us in jeopardy for possible violation of 3rd party communications regulations depending what the 3rd party does.
I couldn't agree more Brian On 11 Oct 2014 15:32, "Brian" n1uro@n1uro.ampr.org wrote:
(Please trim inclusions from previous messages) _______________________________________________ Andy et al; On Sat, 2014-10-11 at 13:18 +0100, Andy Brittain wrote:
I think opening up 44 net is potentially a good idea but then we run in
to trouble where RF is involved. Would we not be passing traffic that technically doesn’t fit under our license t’s&c’s?
Absolutely. That would easier open us up to pirating (why bother get a license if it's freely available?) and put us in jeopardy for possible violation of 3rd party communications regulations depending what the 3rd party does. -- 73 de Brian Rogers - N1URO email: n1uro@n1uro.ampr.org Web: http://www.n1uro.net/ Ampr1: http://n1uro.ampr.org/ Ampr2: http://nos.n1uro.ampr.org Linux Amateur Radio Services axMail-Fax & URONode AmprNet coordinator for: Connecticut, Delaware, Maine, Maryland, Massachusetts, New Hampshire, Pennsylvania, Rhode Island, and Vermont.
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
On 10.10.2014 21:22, Andy Brittain wrote:
there may be an obvious answer to my question but how are these pirate set-ups getting an allocated IP address for 44 net?
They didn't get any. The mentioned links are based on commercial IP addresses. Sorry for confusion.
73, Jann DG8NGN
so just how are the links being done?
On Sun, Oct 12, 2014 at 10:31 PM, Jann Traschewski jann@gmx.de wrote:
(Please trim inclusions from previous messages) _______________________________________________ On 10.10.2014 21:22, Andy Brittain wrote:
there may be an obvious answer to my question but how are these pirate set-ups getting an allocated IP address for 44 net?
They didn't get any. The mentioned links are based on commercial IP addresses. Sorry for confusion.
73, Jann DG8NGN
-- Jann Traschewski, Faber-Castell-Str. 9, D-90522 Oberasbach, Germany Tel.: +49-911-99946898, Mobile: +49-170-1045937, E-Mail: jann@gmx.de Ham: DG8NGN / DB0VOX, http://www.qsl.net/dg8ngn _________________________________________ 44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
Hello Rob et al.
Unbelievable! How this may happen?
Best regards. Tom - sp2lob
-
Andy Brittain -
Brian -
Dimitrios Valaris -
Eric Fort -
Jann Traschewski -
Jason flynn G7OCD -
Rob Janssen -
sp2lob