[MLB-WIRELESS] bandwidth issues for the future/internet acces s

[Tony Langdon]

Optus do allow a LAN in the same premises, but not remote access to the
cable connection.

-----Original Message-----
From: Agatha [mailto:agatha at processplant.com]
Sent: Friday, 26 October 2001 9:56
To: melbwireless at melbwireless.dyndns.org
Subject: Re: [MLB-WIRELESS] bandwidth issues for the future/internet acces s


Telstra & Optus both hate this.  In fact if you read the (un)AUP, they both
state that you may not connect any network to the machine that has the cable
modem link.  I have had battles with both these companies to do with exactly
this.  It is irrelevant whether it is a winblows98 box with a second
winblows box attached, or a big fat Gb network, they don't like it and they
don't put up with it IF they find out.  Which they generally don't.
 
----- Original Message ----- 

From: Rohan Fernando <mailto:rohanf at vic.bigpond.net.au>  
To: melbwireless at melbwireless.dyndns.org
<mailto:melbwireless at melbwireless.dyndns.org>  
Sent: Friday, October 26, 2001 9:22 AM
Subject: RE: [MLB-WIRELESS] bandwidth issues for the future/internet acces s

Hi Michael,

No idea about the legalities (that's what lawyers are for) but here's a
suggestion.

A gang of cable modems could be established to provide the feed to the WLAN.
Admittedly there is an overhead to run it, but then someone has to pay for
the data anyway. Would first need to model the estimated data loadings
versus cost to run the modems to determine viability. Also probably require
H/W & S/W to load balance the modems ie keeping them all under the usage
cap.

Not sure how this conflicts with the overall objective to provide a free
service but, a very small annual subscription fee could be charged to all
WLAN users. This could provide economies of scale overall. Could use WLAN
monitoring to boot off / block anyone that abuses an WLAN AUP.

Suspect the underlying issue will be that if there isn't currently an
AUP/law against this application of cable modems, then there may soon be.

Regards,

Rohan Fernando

-----Original Message-----
From: Michael Bailey [ mailto:mbailey at enternet.com.au
<mailto:mbailey at enternet.com.au> ]
Sent: Friday, October 26, 2001 3:49 AM
To: melbwireless at melbwireless.dyndns.org
<mailto:melbwireless at melbwireless.dyndns.org> 
Subject: Re: [MLB-WIRELESS] bandwidth issues for the future/internet
acces s


On Thu, Oct 25, 2001 at 02:39:40PM +1000, Barry Park wrote:
> My understanding is that:
>
> (i) Unless you have express consent from your ISP, feeding your Internet
> service into an open wireless connection will be against both the ISP's
> business model and possibly even the law.

I don't know of any law that prohibits you from letting your neighbour use
your internet connection. This isn't Napster. Not everything fun is illegal.

As far as ISP business models go, the right way to go would be to choose an
ISP that allows you to share your bandwidth. Read your AUP carefully and
even ask them. If your traffic usage rises too much, your ISP will probably
charge you more. So it will be up to you to manage it, just like the
hundreds
of mom and pop ISPs out there. There's not much difference.

- Mike

--
To unsubscribe, send mail to minordomo at melbwireless.dyndns.org
<mailto:minordomo at melbwireless.dyndns.org>  with a
subject of 'unsubscribe melbwireless'
Archive of the Entire mailinst list at:
http://melbwireless.dyndns.org/cgi-bin/minorweb.pl?A=LIST
<http://melbwireless.dyndns.org/cgi-bin/minorweb.pl?A=LIST&L=melbwireless>
&L=melbwireless


--
To unsubscribe, send mail to minordomo at melbwireless.dyndns.org
<mailto:minordomo at melbwireless.dyndns.org>  with a subject of 'unsubscribe
melbwireless'  
Archive of the Entire mailinst list at:
http://melbwireless.dyndns.org/cgi-bin/minorweb.pl?A=LIST
<http://melbwireless.dyndns.org/cgi-bin/minorweb.pl?A=LIST&L=melbwireless>
&L=melbwireless




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wireless.org.au/pipermail/melbwireless/attachments/20011026/384019b2/attachment.html>