I'm sorry to keep bringing this up but maybe this will help someone out
later. Again, the AP interface was originally bridged to the LAN
interface. I did this because I wanted my server 2k3 box to be the only
dhcp server on the network. But, for testing, I took down the bridge and
let pfsense do the dhcp for the AP. This made a very significant
difference in the time it took for the desktop to get an IP aside from
the fact that it got an IP at all. Traffic didn't start flowing however
until I rebooted pfsense. Currently I have internet and can still get to
other machines on the network however not with their dns name. I would
be happy with this except it worked the other way at one point and I'd
like it that way again. I notice that browsing the net is much smoother
now that the interface is unbridged. Probably I'm missing something but
I just wondered if it was a bug somewhere that during bridging traffic
isn't getting routed/passed right. Upon Scott's advice I did a cvs_sync
this morning so I assume I'm running the very latest build. As always I
would appreciate very much your suggestions and comments. Thank you
Jonathan
Jonathan Woodard wrote:
I also have a router that is on my workbench that is acting as a
wireless client and it is also giving the same problems. I live in the
middle of 3 acres in a very small town so I know there is no other
AP's in distance. There is really nothing else here that causes a
problem. When I turn my old netgear "b" AP on everything works great
with it. The AP card might very well be crappy but it would surpsrise
me since it's worked like a champ until now. Thank you for your
suggestions however. :-) Any other advice I would welcome.
Jonathan
Holger Bauer wrote:
Sounds like noise to me. Check out your neighbourhood for interfering
channels (you can do so for example by scanning with
http://netstumbler.com/ for other accesspoint). Also other devices
can interfere with wireless that won't be listed with netstumbler
(like for example wireless home video transmitters; Check your
environment for devices that might cause noise). Also maybe the
wireless card of the client that is having issues is just crappy as
another one works.
Holger
-----Original Message-----
From: Jonathan Woodard [mailto:[EMAIL PROTECTED]
Sent: Sunday, June 25, 2006 1:30 AM
To: [email protected]
Subject: Re: [pfSense Support] Wireless problems...spoke too soon
Well, apparantly that didn't fix it completely. I can no longer get
an IP from the wireless. Again, the AP connects fine but dhcp will
not give me an IP. I tried with my laptop and it didn't work then i
moved it closer and it gave me an address so I'm assuming is a range
issue. However everything suggests that the range is very good to
excellent. I walked farther away with my laptop and got an IP but the
connections timed out several times when I tried browsing the
internet. Again any suggestions would be appreciated.
Btw, this is the card I'm using. It is an Atheros chipset. EDIMAX
EW-7325IG PCI Wireless LAN Card - Retail
Jonathan
Scott Ullrich wrote: On 6/24/06, Jonathan Woodard
<[EMAIL PROTECTED]> wrote:
Well, I am able to get an IP with the desktop now so I would assume
that fixed it. I would still like to know what was happening but if
no one knows I'll be happy it works for now. :-)
thanks for the quick help Scott.
Let's just say there where some pretty obvious bugs with non ath cards.
Scott
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED] For
additional commands, e-mail: [EMAIL PROTECTED]
____________
Virus checked by G DATA AntiVirusKit
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
