44net

44net@mailman.ampr.org

3 participants
3203 discussions

schema for portal backend database
by Eric Fort 07 Feb '14

07 Feb '14

Could someone provide the existing schema for the portal back end database. I'm taking a database class as well as a web programming class and would like to study it as it presently exists. Eric AF6EP

1 0

Re: [44net] Portal Down ?
by William Lewis 07 Feb '14

07 Feb '14

Same here.. Bill KG6BAJ At 07:45 PM 2/7/2014, you wrote: >(Please trim inclusions from previous messages) >_______________________________________________ >After I login I just get a blank screen. > >-Neil > >-- >Neil Johnson >http://erudicon.com >_________________________________________ >44Net mailing list >44Net(a)hamradio.ucsd.edu >http://hamradio.ucsd.edu/mailman/listinfo/44net

1 0

Apologies for my absence
by VK4AA | VK4TTT Sam 07 Feb '14

07 Feb '14

Hey Guys Apologies for my abscence and if there has been any reqests for space in 44.136.0.0/16. We moved and waiting for someone to leave or be disconnected so we can geta DSL port. We are living in the world of 3g/4g and it is not really that crash hot for a perm connection. We have been advised that they are about to do an upgrade to be told oh we did that last december. Anyway hope to be back online soon Samantha vk4aa|vk4ttt

1 0

Hacking from IP Address 178.33.151.117
by William Lewis 05 Feb '14

05 Feb '14

Just a heads up to the 44 Group who run 44 addressed mail servers. Over the last few days I've had someone trying to break into my mail server. After installing more detection software, I came up with IP Address 178.33.151.117. Just a heads up he's probably scanning the network looking for others, so heads up everyone. Bill / KG6BAJ ========================================== AUTOMATED NOTIFICATION ! The IP 178.33.151.117 has just been banned after several attempts against dovecot. Here are more information about 178.33.151.117: % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '178.33.151.112 - 178.33.151.127' % Abuse contact for '178.33.151.112 - 178.33.151.127' is 'abuse(a)ovh.net' inetnum: 178.33.151.112 - 178.33.151.127 netname: DVC-ITA descr: DoveConviene.it Italian Network country: IT org: ORG-OS43-RIPE admin-c: OTC5-RIPE tech-c: OTC5-RIPE status: ASSIGNED PA mnt-by: OVH-MNT source: RIPE # Filtered organisation: ORG-OS43-RIPE org-name: OVH Srl org-type: OTHER address: Via trieste 25 address: 20097 San Donato Milanese address: Italia abuse-mailbox: abuse(a)ovh.net mnt-ref: OVH-MNT mnt-by: OVH-MNT source: RIPE # Filtered role: OVH IT Technical Contact address: OVH Srl address: Via trieste 25 address: 20097 San Donato Milanese address: Italia admin-c: OK217-RIPE tech-c: GM84-RIPE nic-hdl: OTC5-RIPE abuse-mailbox: abuse(a)ovh.net mnt-by: OVH-MNT source: RIPE # Filtered % Information related to '178.32.0.0/15AS16276' route: 178.32.0.0/15 descr: OVH ISP descr: Paris, France origin: AS16276 mnt-by: OVH-MNT source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.71 (WHOIS1) Lines containing IP:178.33.151.117 in /var/log/mail.log Feb 5 04:15:37 linux1 dovecot: pop3-login: Disconnected (auth failed, 1 attempts): user=<test(a)ampr.org>, method=PLAIN, rip=178.33.151.117, lip=44.2.14.2 Feb 5 04:17:23 linux1 dovecot: pop3-login: Disconnected (auth failed, 1 attempts): user=<test(a)ampr.org>, method=PLAIN, rip=178.33.151.117, lip=44.2.14.2 Feb 5 04:17:41 linux1 dovecot: pop3-login: Disconnected (auth failed, 1 attempts): user=<test(a)ampr.org>, method=PLAIN, rip=178.33.151.117, lip=44.2.14.2 ...... <snip>

3 2

Re: [44net] Hacking from IP Address 178.33.151.117
by William Lewis 05 Feb '14

05 Feb '14

I suspect. I noted he was smart enough to trace the 44.2.14.1 to "gvcity.ampr.org" and then try to access with ".....(a)ampr.org" At 10:11 AM 2/5/2014, you wrote: >(Please trim inclusions from previous messages) >_______________________________________________ >looks like someones box has been hacked it is a shopping site in Italy. > >Lin

1 0

Re: [44net] 44Net Digest, Vol 3, Issue 25
by Steve Wright 02 Feb '14

02 Feb '14

> > > Although I have finally pulled some strings for commercial tower space > come spring. Good work! > Without one end up high (above the average 100 foot > trees), No. If you have 100 foot trees, you can't run long distance outdoor 802.11 > you need amplifiers to go anywhere, or a MESH node every > couple miles? > No, and no. So far I have not done anything with Mesh, and it sort of makes sense > for the distance/propagation delima.. Till I think, wait a second, > 802.11 is still half duplex, so when you make a (metric) hop using a > mesh topology, aren't you effectively cutting your bandwidth in half? > And in half again, and again with each new node. So there is more to this than throw a bunch of nodes out there. > (bandwidth and hidden transmitter stuff), there is just no easy way > around a decently designed network.. backbones! Then there is the oh, > well we want to expand the network this way (something not in the > original plan), and how to make the subnet and routes all work, short > of re-addressing everything. > You got it in one! Please someone please package this text inside something nice and solid, like a baseball bat, so we can whack the next person with who has this idea. > I watched the HamWAN DCC video.. and I have often thought about 5 GHz > Mikrotik Groove as they way I'd go if I were to invest in equipment > again. No, stick with multi-chain polling stuff, like the MIMO AirMAX, and get 200mbit plus symbol rates, and solid 90mbit ACTUAL throughput. > More so, if bouncing off say a water tower actually is doable. > No, stick with nice clear line-of-sight paths for infrastructure. By all means, play with things as an experiment, but puhleeeaze don't hide such a catastrophe inside a seemingly functional network, or you will bring the rest of the network to its' knees. > Whoever has IP 44.12.3.97, please stop sending UDP 5678 to 255.255.255.255. > I'm getting this every single minute. > Hehe, a single UDP every minute.. If that was over the old 1200 digipeated network it'd DDOS the entire network! lol >

1 0

Mikrotik RouterOS 6.9 bug
by Marius Petrescu 02 Feb '14

02 Feb '14

For those who use Mikrotik routers, please be aware that there is a possible bug with route marks in the latest firmware (6.9). So stay put on 6.7 until this is clarified/solved. 73 de Marius, YO2LOJ

1 0

44.12.3.97 please stop UDP 5678
by Michael E Fox - N6MEF 02 Feb '14

02 Feb '14

Whoever has IP 44.12.3.97, please stop sending UDP 5678 to 255.255.255.255. I'm getting this every single minute. Thanks, Michael N6MEF

7 8

Re: [44net] 44Net Digest, Vol 3, Issue 24
by Steve Wright 02 Feb '14

02 Feb '14

> > Yes. Amateur RF is synonymous with low bandwidth. We have unique > capabilities but it's with low bandwidth like 1200 baud, 9600 baud, > 100K ID1's and hopefully soon UDRX at 56K+. > > BBHN (Broadband hamnet, was HSMM) is generally more interested with > connectivity than performance. Unfortunately too many experimenters > there are new and not familiar with the lessons of 145.01 or 144.39... > Even implemented with good RF design the MESH ad-hoc based system has > compromises. I tried streaming the next episode of Torchwood from > Amazon a couple nights ago and my NW-MESH (based on HSMM-MESH) home > system wouldn't do it. I don't think that's even HD. :( > Precisely. I think it is fine for radio hams to experiment with attaching some cool new experimental toy to the backbone, for whatever they want to do with it! Play with it and and have fun - that's what any hobby is for, and ham radio not the least.. But people really need to remember old the days of digipeaters on a single simplex frequency and make sure we don't return there, or at the very least Ubiquiti M2/M3/M5 dual-chain AirMax nanobridges et al running on the ham bands are the new jesus. Steve

2 1

Re: [44net] 44Net Digest, Vol 3, Issue 24
by kb9mwr＠gmail.com 01 Feb '14

01 Feb '14

> Message: 1 > Date: Fri, 31 Jan 2014 15:33:41 -0800 > From: Bill Vodall <wa7nwp(a)gmail.com> > To: AMPRNet working group <44net(a)hamradio.ucsd.edu> > Subject: Re: [44net] 44Net Digest, Vol 3, Issue 19 <snip> > BBHN (Broadband hamnet, was HSMM) is generally more interested with > connectivity than performance. Unfortunately too many experimenters > there are new and not familiar with the lessons of 145.01 or 144.39... > Even implemented with good RF design the MESH ad-hoc based system has > compromises. I tried streaming the next episode of Torchwood from > Amazon a couple nights ago and my NW-MESH (based on HSMM-MESH) home > system wouldn't do it. I don't think that's even HD. :( Here in Green Bay, WI a few of us have been messing with point to point 802.11 since 1999. Sadly there isn't enough interest (mostly due to the average ham club members age I suspect), for it to advance much beyond that... so far. Although I have finally pulled some strings for commercial tower space come spring. Without one end up high (above the average 100 foot trees), you need amplifiers to go anywhere, or a MESH node every couple miles? So far I have not done anything with Mesh, and it sort of makes sense for the distance/propagation delima.. Till I think, wait a second, 802.11 is still half duplex, so when you make a (metric) hop using a mesh topology, aren't you effectively cutting your bandwidth in half? So there is more to this than throw a bunch of nodes out there. (bandwidth and hidden transmitter stuff), there is just no easy way around a decently designed network.. backbones! Then there is the oh, well we want to expand the network this way (something not in the original plan), and how to make the subnet and routes all work, short of re-addressing everything. I watched the HamWAN DCC video.. and I have often thought about 5 GHz Mikrotik Groove as they way I'd go if I were to invest in equipment again. More so, if bouncing off say a water tower actually is doable. Steve, KB9MWR

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

44net