Re: Neighborhood WiFi?
- From: "Ed" <poseasy@xxxxxxxxx>
- Date: Sat, 25 Mar 2006 01:24:25 -0500
Jeff
Found this on DD-WRT. Couldn't you do this and set the limits and share
across the network so no one person could hog it.
you can share your available bandwidth evenly among you and your brother
using the htb queueing discipline in tc..
I'll explain by example..
tc qdisc del dev eth1 root
tc qdisc add dev eth1 root handle 1: htb default 10
tc class add dev eth1 parent 1: classid 1:1 htb rate 128kbit ceil 128kbit
tc class add dev eth1 parent 1:1 classid 1:10 htb rate 1kbit ceil 1kbit
tc class add dev eth1 parent 1:1 classid 1:20 htb rate 63kbit ceil 128kbit
tc class add dev eth1 parent 1:1 classid 1:30 htb rate 64kbit ceil 128kbit
tc qdisc add dev eth1 parent 1:10 handle 10: sfq
tc qdisc add dev eth1 parent 1:20 handle 20: sfq
tc qdisc add dev eth1 parent 1:30 handle 30: sfq
iptables -F
iptables -A POSTROUTING -t mangle -o br0 -d 192.168.1.100 -j
CLASSIFY --set-class 1:20
iptables -A POSTROUTING -t mangle -o br0 -d 192.168.1.101 -j
CLASSIFY --set-class 1:30
this is meant for at connection with a downstream limit equal to 128kbit
(kbps).
If your ip is .100 and your brothers is .101 the downstream bandwidth will
be shared evenly among you. and as a bonus if you're not using any of your
bandwidth your brother will be able to "borrow" from you
"Jeff Liebermann" <jeffl@xxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:9ai622tv61ipr10d0f285n8sh1jjalusm8@xxxxxxxxxx
On Thu, 23 Mar 2006 00:12:23 -0600, Ed Bailen <n5kzw@xxxxxxxx> wrote:
Continuing onward...
Will we need a bridge on each end
of the backbone, or just a WAP?
Chuckles. How many different types of bridges would you guess there
are? See my list at:
|
http://en.wikibooks.org/wiki/FAQ_for_alt.internet.wireless/Wi-Fi#Wireless_Bridge
Anyway, you have a choice of doing it several ways. Short version
(because I'm busy).
1. Your ISP delivers one routeable IP for every user. Each user
supplies their own firwall for NAT. I think (not sure) that a simple
access point and client radio will work because it only needs to pass
one MAC address. However, methinks a transparent bridge or "wireless
bridge" will be better in case the topology changes.
2. Your ISP delivers one IP address. The NAT router is installed at
the nephew end. The wireless backhaul is a transparent bridge or
"wireless bridge" in order to pass multiple MAC addresses. Each user
has an additional NAT firewall for their multiple machines.
3. Your ISP delivers two IP addresses. The nephew end gets one, and
everyone else has to do NAT to share the other IP address. The nephew
end has a router as does the tower end. The wireless link needs to
only pass one IP address and can therefore live with just about
anything. Each user will have an additional router
3. Some variation in between including mapping routeable IP addresses
to NAT IP's in a Cisco router.
So, what's your prefered topology and we'll figure out what type of
backhaul you need? I recommend number 1.
On the nephew's end, he could use a
wired router to feed a WAP attached to his omni and a bridge(??)
attached to the backbone antenna.
Yes, something like that. The safest is a transparent bridge, which
will pass multiple MAC addresses and will work with just about any
configuration. Something like a Linksys WAP54G.
On my end, I'm not sure what I
would need between the backbone antenna on my end and my omni.
Again, it's topology. The backhaul will probably be two identical
wireless bridge radios (i.e. WAP54G). The ethernet connection from
your WAP54G would go to some kind of common access point (or router)
depending on your IP address layout and topology. Each user would
have some kind of common client adapter to connect. They will
probably also have an NAT router to deal with multiple computers.
I am
assuming that my connectivity to the WAN would be through a 100' run
of cat5 up to whatever is on the tower,
300ft is the maximum CAT5 run for real PoE (power over ethernet). That
will work. Visualize climbing the tower in the rain and snow in order
to placate one your complaining customers.
but what will the customers
need to connect to their antennas:, just a wireless router? (From my
limited understanding it doesn't sound like a bridge would be
appropriate since we wouldn't want any of the customers to have
visibility to each other's (or our) computer resources.
Sorta. Again it depends on your IP address layout. If you can
deliver NAT'ed IP address to each client, then a wireless client
bridge radio and a simple ethernet switch will take care of their
system. Of course that doesn't protect them from attack from the
network, so a single MAC wireless bridge and a router would probably
be more useful. Something like a WAP54G in client mode, with any NAT
ethernet router behind it.
Can anyone offer some suggestions or URLs?
Oh, and what about lightning?
If it hits, you lose. Unless you buy hardware that's specifically
designed for outdoor use, lightning is highly likely to destroy the
devices. Carry lots of spares.
--
Regards,
Ed
# Jeff Liebermann 150 Felker St #D Santa Cruz CA 95060
# 831-336-2558 jeffl@xxxxxxxxxxxxxxxxxxxxxx
# http://802.11junk.com jeffl@xxxxxxxxxx
# http://www.LearnByDestroying.com AE6KS
.
- Follow-Ups:
- Re: Neighborhood WiFi?
- From: Jeff Liebermann
- Re: Neighborhood WiFi?
- References:
- Neighborhood WiFi?
- From: Ed Bailen
- Re: Neighborhood WiFi?
- From: Jeff Liebermann
- Neighborhood WiFi?
- Prev by Date: Re: Dropped Connection
- Next by Date: Re: Wireless Software required
- Previous by thread: Re: Neighborhood WiFi?
- Next by thread: Re: Neighborhood WiFi?
- Index(es):
Relevant Pages
|
