I would be happy to let an AP do what it's best at, and have a router behind
it, but I've got a solar powered WIPOP, where power is at an extreme
premium, so I need to use the routing functionality in the AP(s). That
said, I'm going to go to a 5.8 backbone this summer, and I'm thinking about
Mikrotik or StarOS because of their imbedded routing functionality. (Anyone
had experience with either as a backhaul using 5.8GHz?)
Norm
----- Original Message -----
From: "Bob Hrbek" <bhrbek@jagwireless.net>
To: "Karlnet Mailing List" <karlnet@WISPNotes.com>
Sent: Wednesday, June 09, 2004 9:34 AM
Subject: Re: [Karlnet] Broadcast storms
> Or just enable RIP and do some of the below. Or...use a router for a
> router...and an AP for an AP. ;)
>
>
>
>
> ----- Original Message -----
> From: "Andy Henckel" <ahenckel@transaria.com>
> To: "Norm Young" <lists@applegatebroadband.net>; "Karlnet Mailing List"
> <karlnet@WISPNotes.com>
> Sent: Wednesday, June 09, 2004 11:31 AM
> Subject: RE: [Karlnet] Broadcast storms
>
>
> You create direct routes for those net works on interface 4. So
174.18.4.1
> and 5.1. All the clients and KN-50's point to their respective gateway,
the
> 5.1 or 4.1.
>
> Then on the Ethernet interface of your TC base, you set it to 174.18.0.10,
> again a direct route.
>
> On your upstream router, of course it must have an ip, if only a
secondary,
> on its interface... let's say 174.18.0.10. And then you make a route on
> that device for the .4.0 and .5.0 nets to the 174.18.0.10.
> Set NAT pool access list to allow the 174.18.0.0 0.0.255.255
>
>
> And there you be.
> If you want to give customers a public network inside their SOHO router.
> Then you add a route on the upstream router to the 174.18.0.10, and then
an
> indirect route on the TC Router to the IP of their wan port, in this
example
> 174.18.5.2 being the first customer. Then assign the public network to
the
> LAN interface on their SOHO, and turn of NAT, and they have public
network.
>
> I also had problems with the older Karlnet firmware versions and routing..
> some screwy thing about the device not wanting to route for different
> subnets.. but it's fixed in V4.
>
> Andy
> -----Original Message-----
> From: karlnet-bounces@WISPNotes.com [mailto:karlnet-bounces@WISPNotes.com]
> On Behalf Of Norm Young
> Sent: Tuesday, June 08, 2004 8:12 PM
> To: Karlnet Mailing List
> Subject: Re: [Karlnet] Broadcast storms
>
> Ok, routing champions, say I've got a bunch of 174.18.5.X clients (the WAN
> IP of their routers) off radio interface #4, the radios (bridges, all
> KN-50s) at 174.18.4.X, and the Ethernet (#1) interface is looking back at
> the border router which is NATing all the 174.18.5.X clients from
> 174.18.5.1. How would I set up the routing on this AP to make this work?
>
> Norm
>
>
> ----- Original Message -----
> From: "Martin Madsen" <martin@belairinternet.com>
> To: "'Karlnet Mailing List'" <karlnet@WISPNotes.com>
> Sent: Tuesday, June 08, 2004 5:31 PM
> Subject: RE: [Karlnet] Broadcast storms
>
>
> > Im interested in why some of the WISP's out there, using karlnet, are
> > running bridgeing mode. We only use it when we assign public ip's.
> >
> > Regards,
> >
> > Martin Madsen
> >
> > PH:(818) 380-8170
> > FX: (818) 380-8175
> >
> >
> >
> > -----Original Message-----
> > From: karlnet-bounces@WISPNotes.com
> > [mailto:karlnet-bounces@WISPNotes.com] On Behalf Of Andy Henckel
> > Sent: Friday, June 04, 2004 10:38 AM
> > To: Norm Young; Karlnet Mailing List
> > Subject: RE: [Karlnet] Broadcast storms
> >
> >
> > I have usually been able to isolate these problems to customer PC's.
> > Either a Virus or Trojan. Can you look at ip cache flo on a cisco
> > router? Look for 1 k packets and a lot of them. Or just look at
> > station stats after a reboot to find the offending link.
> >
> > -----Original Message-----
> > From: karlnet-bounces@WISPNotes.com
> > [mailto:karlnet-bounces@WISPNotes.com] On Behalf Of Norm Young
> > Sent: Friday, June 04, 2004 10:55 AM
> > To: Karlnet Mailing List
> > Subject: [Karlnet] Broadcast storms
> >
> > I have a bridged network that I've recently changed over to all
> > KN-2XX's
> > acting as base stations in TC mode. I'm seeing occasional storms of
> > packets hitting all interfaces at once. Any good way to stop this?
> > I've
> > looked at the storm threshold settings, but it looks like it affects all
> > traffic, and besides, the storm peaks are below what the network sees
> > for
> > good traffic. Would going to routing solve this?
> >
> > Norm
> >
> >
> > _______________________________________________
> > Karlnet mailing list
> > Karlnet@WISPNotes.com
> > http://lists.wispnotes.com/mailman/listinfo/karlnet
> >
> >
> > _______________________________________________
> > Karlnet mailing list
> > Karlnet@WISPNotes.com
> > http://lists.wispnotes.com/mailman/listinfo/karlnet
> >
> >
> > _______________________________________________
> > Karlnet mailing list
> > Karlnet@WISPNotes.com
> > http://lists.wispnotes.com/mailman/listinfo/karlnet
>
>
> _______________________________________________
> Karlnet mailing list
> Karlnet@WISPNotes.com
> http://lists.wispnotes.com/mailman/listinfo/karlnet
>
>
> _______________________________________________
> Karlnet mailing list
> Karlnet@WISPNotes.com
> http://lists.wispnotes.com/mailman/listinfo/karlnet
>
> _______________________________________________
> Karlnet mailing list
> Karlnet@WISPNotes.com
> http://lists.wispnotes.com/mailman/listinfo/karlnet
>
_______________________________________________
Karlnet mailing list
Karlnet@WISPNotes.com
http://lists.wispnotes.com/mailman/listinfo/karlnet
|