I'm working on a presentation about packet networking.
Does anyone have a reasonable estimate of:
-- The number of BBS Systems reachable via AMPRnet
-- The number of BBS Systems reachable via non-AMPRnet BBS forwarding
network
-- The number of BBS systems connected via both networks
Note: This is not an attempt to compare the two. We're connected both
ways. AND, I realize that other BBSs also connect to both, so there will be
duplication. That's o.k. I'd just like to be able to give people a sense
of how big (or small) each of the networks still is.
If you have an estimate for any of the above numbers, can you tell me what
it is and how you arrived at it?
Thanks,
Michael
N6MEF
In Bulgaria start HAM TV via streaming with hamnet IP -
http://lz4ny.ampr.org/cms/index.php?id=ham-tv
73, Miro LZ4NY
-------------------------------------
Mail.BG: Безплатен e-mail адрес. Най-добрите характеристики на българския пазар - 20 GB пощенска кутия, 1 GB прикрепен файл, безплатен POP3, мобилна версия, SMS известяване и други. http://mail.bg
Miro LZ4NY,
The 2 commands would be entered by selecting Administration > Commands
iptables -t nat -I PREROUTING -p ipencap -d AAA.AAA.AAA.AAA -j DNAT
--to-destination BBB.BBB.BBB.BBB
iptables -t filter -I FORWARD -p ipencap -d BBB.BBB.BBB.BBB -j ACCEPT
Then select: "Save Firewall"
73,
Lynwood
KB3VWG
On 12/06/2013, lz4ny(a)mail.bg wrote:
> Hello,
> What command line to ask in DD-WRT router to release protocol IPENCAP (4)
> to my local machine assuming that AAA.AAA.AAA.AAA is my real address of the
> interface WAN of DD-WRT and BBB.BBB.BBB.BBB is the address of the Linux
> machine behind the router.
>
>
> 73, Miro LZ4NY
Hello,
What command line to ask in DD-WRT router to release protocol IPENCAP (4)
to my local machine assuming that AAA.AAA.AAA.AAA is my real address of the
interface WAN of DD-WRT and BBB.BBB.BBB.BBB is the address of the Linux
machine behind the router.
73, Miro LZ4NY
-------------------------------------
Mail.BG: Безплатен e-mail адрес. Най-добрите характеристики на българския пазар - 20 GB пощенска кутия, 1 GB прикрепен файл, безплатен POP3, мобилна версия, SMS известяване и други. http://mail.bg
I need help in the network configuration via eth0 (192.168.x.x)
from WinXP to be able to connect to the addresses 44-Net?
For connoisseurs will send more information ..
--
73 de Janusz / SP1LOP
===== Janusz J. Przybylski, SP1LOP ==================
Poland AMPRNet Co-ordinator [44.165/16] from Mar 2003
=====================================================
Chris,
Please contact me off list.
I've been trying to send you email, for quite a while, but it keeps bouncing
with connection timed out at 44.18.44.3.
Michael
N6MEF
On 11/26/13 5:28 PM, Brian Kantor wrote:
> Not really. We probably should. I'm a little unclear on exactly
> what would be required and how much it's going to cost.
> - Brian
I'm happy to help out, as it's quite easy to fill out the SWIP forms and then
submit it. We could setup rwhois for the 44/net space, but that might be a
bit much for us as the portal is not always available.
ARIN should not charge a fee to administrator resources for legacy users:
10. I have legacy resources registered in ARIN's Whois database but
have no plans to sign the LRSA. Will ARIN continue to maintain my
records, and can I still make database changes to my records if I need to?
ARIN will continue to process requests from the authorized points of contact
of legacy resources for updates to their registration records. Currently,
there is no community driven policy specifically prohibiting ARIN from
processing updates to records that are not covered under a LRSA or RSA,
although that could change in the future.
info on swip is here https://www.arin.net/resources/request/reassignments.html
Basically you could swip the regional blocks to the regional admins, and when
they assign them they swip the assigned blocks to end users. This would fix
the in-addr.arpa mapping too, which as of now does not exist for anything on
AMPRNET.
Thoughts?
--
Bryan Fields
727-409-1194 - Voice
727-214-2508 - Fax
http://bryanfields.net
On 11/26/13 10:39 PM, Antonio Querubin wrote:
> Time has no cost :)
We have a volunteer!
--
Bryan Fields
727-409-1194 - Voice
727-214-2508 - Fax
http://bryanfields.net
Have we considered SWIPing the blocks?
A DMCA notice is not necessarily a violation caused by the registrant of the
IP, but perhaps one of their users.
I've had DMCA notices for unused IP's before, so not all are valid. However
90% of them valid and are people running bit torrent for movies and stuff.
How many DMCA notices are you getting from 44/8 on a monthly basis?
On 11/26/13 3:55 PM, Brian Kantor wrote:
> (Please trim inclusions from previous messages)
> _______________________________________________
> Probably most of you folks haven't seen one of these before.
> This is the kind of notice I receive and have to respond to
> when one of the users of network 44 misbehaves.
>
> Keep in mind that this is a violation of our terms of service and
> is cause to have network access revoked.
>
> Please be careful not to cause me to get more of these.
>
> Thank you.
> - Brian
>
> PS: I've obscured the IP address because the matter is already
> being dealt with by the persons concerned.
>
>
> ----- Forwarded message from IP-Echelon Compliance <notices.warner(a)ip-echelon.com> -----
>
> Date: Tue, 26 Nov 2013 20:19:33 +0000
> From: IP-Echelon Compliance <notices.warner(a)ip-echelon.com>
> To: bk29(a)ucsd.edu
> Subject: Notice of Claimed Infringement - Case ID 1335xxxxx
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Dear bk29(a)ucsd.edu
>
> We are writing this message on behalf of Warner Bros. Entertainment Inc..
>
> We have received information that an individual has utilized the
> below-referenced IP address at the noted date and time to offer
> downloads of copyrighted material.
>
> The title in question is: Pacific Rim
>
> The distribution of unauthorized copies of copyrighted television
> programs constitutes copyright infringement under the Copyright Act,
> Title 17 United States Code Section 106(3). This conduct may also
> violate the laws of other countries, international law, and/or treaty
> obligations.
>
> Since you own this IP address (44.xxx.xxx.xxx),
> we request that you immediately do the following:
>
> 1) Contact the subscriber who has engaged in the conduct described
> above and take steps to prevent the subscriber from further downloading
> or uploading Warner Bros. Entertainment Inc. content without authorization; and
>
> 2) Take appropriate action against the account holder under your Abuse
> Policy/Terms of Service Agreement.
>
> On behalf of Warner Bros. Entertainment Inc., owner of the exclusive rights
> in the copyrighted material at issue in this notice, we hereby state that
> we have a good faith belief that use of the material in the manner
> complained of is not authorized by Warner Bros. Entertainment Inc.,
> its respective agents, or the law.
>
> Also, we hereby state, under penalty of perjury, that we are authorized
> to act on behalf of the owner of the exclusive rights being infringed
> as set forth in this notification.
>
> We appreciate your assistance and thank you for your cooperation in this
> matter. Your prompt response is requested.
>
> Any further enquiries can be directed to copyright(a)ip-echelon.com
> Please include this message with your enquiry to ensure a swift response.
>
> Respectfully,
>
> Michael Lambert
> Enforcement Officer
> IP-Echelon
> Email: copyright(a)ip-echelon.com
> Address: 6715 Hollywood Blvd, Los Angeles, 90028, United States
>
>
> - ------------- Infringement Details ----------------------------------
> Title: Pacific Rim
> Timestamp: 2013-11-26T20:00:37Z
> IP Address: 44.xxx.xxx.xxx
> Port: 51963
> Type: BitTorrent
> Torrent Hash: 0d8c999ddbe439117fbc09899e2fb7fd2ea50bb2
> Filename: Pacific Rim 2013 1080p WEB-DL x264 AC3-JYK
> Filesize: 3413 MB
> - ---------------------------------------------------------------------
> ----- End forwarded message -----
> _________________________________________
> 44Net mailing list
> 44Net(a)hamradio.ucsd.edu
> http://hamradio.ucsd.edu/mailman/listinfo/44net
> http://www.ampr.org/donate.html
--
Bryan Fields
727-409-1194 - Voice
727-214-2508 - Fax
http://bryanfields.net
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 11/26/13 6:46 PM, Marc, LX1DUC wrote:
> On 27/11/2013 00:12, Bryan Fields wrote:
>> > In my example, how can I get 254.98.44.in-addr pointed at my DNS
>> > servers? I don't see an ability to do this via the portal page.
> You just don't. All revDNS for the AMPR/44net addresses end in
> ampr.org. I don't see aproblem with that.
Who says this should be? I can't find anything in the TOS or documents on
ampr.org saying this is a requirement.
I don't agree with this (for CIDR blocks), there are valid reasons to have
forward and reverse matching DNS. If we had SWIP/rwhois working we could do
this ourselves.
Perhaps we need to put an APMRnet use case RFC together, but I'd rather have
policy reached by a consensus if we're going to have non Internet standard
requirements.
Thoughts?
- --
Bryan Fields
727-409-1194 - Voice
727-214-2508 - Fax
http://bryanfields.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (Darwin)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJSlVXzAAoJEGWJwvsug9rS1KsIANZydzWyFWg6n1VCKaKrzo2A
cZLpKhWgimDSjeT+bFX7GnbEWNSZ1peX5p+OQzrCGXqTxD3hDIiCrSB05UZp0p6c
9NhxFH9BtSNlgaVdkV6k9sbcPkY7wieYB9l0AWSgQMnKOJHbWM/6Vu4ndFbJwqig
8diMiIQgbV4Yz1isHGkiVsDsC+qhKAQJUXH3kKCThUSMK3o7ANZk5X2BEU2F94D2
9Q9ai/TNx7cr7YXlYFRiLa7xTR/ExeQEZDzNOSl2Sx1N0YvB9qkdAVEfb1Jf/XB+
ijMFVMMMVISGy5bRUgYXHWLCDvbPJusmUi+JC76lwZWN6qREidQItecavt6ENGQ=
=aqgE
-----END PGP SIGNATURE-----
