Re: Wireless bridge

2009-06-21 Thread Hugh Irvine


Hello -

On this same topic does anyone have any experience with the Linksys  
WAP200E?


thanks and regards

Hugh


On 19 Jun 2009, at 20:19, Bret Clark wrote:


Justin Sharp wrote:
I didn't read through all of the replies to see if this was  
suggested, apologies if it was.


http://www.solectek.com/products.php?prod=sw7k&page=feat

I implemented a PTP link at about 3 miles using these Solectek  
radios. I get 40Mbps consistently with TCP traffic and ~100Mbps  
UDP. This PTP link has literally been up for 3 years (in 2 weeks)  
without failing. I live in a 4 seaons state, so its seen all sorts  
of weather over those years. I have clean line of site down the  
freeway for what its worth. Its natively powered via POE, power  
injector included. We run all sorts of usual business application  
over this link, including about 30 simultaneous VOIP channels, and  
have not had one issue with stability. I was also told by the VAR  
that sold us the product that a city nearby (can't remember which  
one) connects all of its municipal buildings with Solectek stuff  
and runs its VOIP infrastructure over it as well.


We run it in bridged mode with routers on each end, but it does  
support some rudimentary L3 stuff, static routing and RIP.


IIRC, they were not "cheap" (couple of 1k), but for us have  
definitely been much cheaper than private circuits from carriers of  
comparable throughput capacity.


Hope its helpful.

--Justin

I have to say I did a double take on your speed claims. We use  
Solectek all over the place and have yet to archived those speeds on  
any of our links. Not only that Solectek engineers have told us that  
at a 108mbps radio rate realistically you are only going to see only  
35mbps  data rate on link that's just a mile apart; further you go  
the less bandwidth you will have.


Other then that, I agree they are nice radios and even include  
heaters in them to help maintain temperatures above freezing during  
winter time so that ice buildup doesn't cause a problem.


Bret





NB:

Have you read the reference manual ("doc/ref.html")?
Have you searched the mailing list archive (www.open.com.au/archives/radiator)?
Have you had a quick look on Google (www.google.com)?
Have you included a copy of your configuration file (no secrets),
together with a trace 4 debug showing what is happening?
Have you checked the RadiusExpert wiki:
http://www.open.com.au/wiki/index.php/Main_Page

--
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. Available on *NIX, *BSD, Windows, MacOS X.
Includes support for reliable RADIUS transport (RadSec),
and DIAMETER translation agent.
-
Nets: internetwork inventory and management - graphical, extensible,
flexible with hardware, software, platform and database independence.
-
CATool: Private Certificate Authority for Unix and Unix-like systems.





Re: ipv6 only DNS?

2009-06-21 Thread Stephen Sprunk
Joe Abley wrote:
> Some time ago I checked the ORG and INFO registries and discovered
> that the number of host objects there with IPv6 address attributes was
> very small. I presumed at the time that it was either hard to find a
> registrar that would support IPv6 addresses for hosts, or that people
> were just not paying much attention to v6-only resolution.

At least for now, it's pretty well accepted that basic servers like DNS,
SMTP, IMAP, HTTP proxies, etc. MUST be dual-stacked for the duration of
the transition.  Even if your clients are IPv6-only, they can still
resolve hostnames, send mail, surf the web, etc. to sites that are
IPv4-only via those few servers.  Generic, scalable solutions would be
better rather than protocol-specific proxies of course, and the IETF is
working on that angle, but in the meantime it'll allow the most common
client-server protocols to keep working and get some experience with IPv6.

Also, keep in mind that the vast majority of folks out there still can't
get native IPv6 transit from their upstreams and may not be willing to
trust free tunnel brokers with production traffic to their servers. 
Even if they can, most eyeballs trying to hit them are still IPv4-only
and the few IPv6 eyeballs can be assumed to have proxies since otherwise
they couldn't see 99.% of the Internet.

This is what it looks like before critical mass is achieved.

S

-- 
Stephen Sprunk "God does not play dice."  --Albert Einstein
CCIE #3723 "God is an inveterate gambler, and He throws the
K5SSSdice at every possible opportunity." --Stephen Hawking



smime.p7s
Description: S/MIME Cryptographic Signature


Re: ipv6 only DNS?

2009-06-21 Thread Joe Abley


On 21-Jun-2009, at 10:36, Rui Ribeiro wrote:


An IPv6 only device can "hit" your server if all the DNS hierachy
resolves through IPv6. It works the same way as in IPv4.


"Resolves through IPv6" implies a mixture of IPv6 transport and RRSet  
availability. To add some more details, you need:


 -  records in your hints file, so you can complete a useful  
priming query
 -  glue in the zones being followed to answer your questions,  
from the root down
 - all NS sets above every zone cut to include at least one reachable  
nameserver that can be queried using IPv6 transport
 - the resources you're ultimately looking for to have  records  
(assuming your goal is to find an address)


Some time ago I checked the ORG and INFO registries and discovered  
that the number of host objects there with IPv6 address attributes was  
very small. I presumed at the time that it was either hard to find a  
registrar that would support IPv6 addresses for hosts, or that people  
were just not paying much attention to v6-only resolution.



Joe




Re: ipv6 only DNS?

2009-06-21 Thread Rui Ribeiro
Hi Steve,

An IPv6 only device can "hit" your server if all the DNS hierachy
resolves through IPv6. It works the same way as in IPv4.

Rui

2009/6/21 Steve Pirk :
> Anyone have any experience with dns and ipv6? I did a lookup on a host and
> it came back with only an ipv6 record. Also shows up in ident as a valid
> name. I was curious how an ipv6 only device would be able to hit my server.
>
> Details and more info off list, tonight if possible.
>
> --
> steve
>
>