[pfSense] Wireless Issues

[Chris Brennan]

On Sat, Sep 24, 2011 at 4:31 PM, Chris L <cjl at viptalk.net> wrote:


> On Sep 24, 2011, at 8:22 AM, Chris Brennan wrote:
>
> > On Sat, Sep 24, 2011 at 3:34 AM, Chris L <cjl at viptalk.net> wrote:
> > > Yes, all the clients are assigned IP's via DHCP, so that wouldn't
> matter
> > > anyway.
> >
> > It matters if they're given wrong info.
> >
> > > I've double-checked and even triple-checked all my defaults. My clients
> > > get an IP in the right range, they are given the right gateway and DNS
> > > servers, they just can't go anywhere.
> >
> > I've checked their DHCP assignments, they are getting the right info, I
> can navigate *within* the LAN just fine (wirelessly), I just can't leave it
> (again, wirelessly).
>
> Does that include being able to access the pfSense interface?  Can you ping
> it and bring up the admin interface in a web browser (using the IP address)


Yes, sorta. I plugged https://192.168.0.1 into my android phone's browser
and I got the security certificate warning and then was presented with ddwrt
... then I went wtf!?! I forgot, my old linksys running ddwrt was still
running and it never occurred to me to unplug it.


>


> If so, then you can stop looking at the wireless config and focus on your
> firewall rules for the wireless interface.
>
> You haven't stated what "can't go anywhere" and inability to "leave" the
> WLAN really means.  Are they unable to resolve DNS?  Can they ping outside
> using just IP addresses?
>
> Anything useful being logged in the firewall?


So now that the interferring linksys has been shut down, I checked my iPod
and android phone, both get ip's in the 169.254.40.0 range (not the
192.168.0.0 range of my LAN). I tried assigning a manual IP to my iPod and I
was unable to navigate the LAN at all.

When I go to Services -> DHCP Server I get the following warning at the top.


 **     *The DHCP Server can only be enabled on interfaces configured with
static IP addresses.

Only interfaces configured with a static IP will be shown.
* **

I'm not sure if this applies to me or not and why my devices are not getting
a wireless IP in the proper range (192.168.0.200-192.168.0.245) and I see no
WAN tab under this message, just LAN.

Incidentally, when I reboot, I see the following:

pfSense is now shutting down ...

pflog0: promiscuous mode disabled
Waiting (max 60 seconds) for system process `vnlru' to stop...done
Waiting (max 60 seconds) for system process `bufdaemon' to stop...done
Waiting (max 60 seconds) for system process `syncer' to stop...
Syncing disks, vnodes remaining...0 0 done
All buffers synced.
Uptime: 5d8h11m58s
Rebooting...
© 'ÛKûù§ÿûÚ 6ÿÚ÷²óÿú³:óÚ Þó²>Ûé§Ö`

                                  S_lmmϸ·ïüÿÿ
1   FreeBSD
2   FreeBSD

Boot:   2
...
boot msgs
....
Configuring WIRELESS interface...wlan0: changing name to 'ath0_wlan0' <--
what's this and why? I don't remember seeing this before...

> --
> Chris Brennan
> A: Yes.
> >Q: Are you sure?
> >>A: Because it reverses the logical flow of conversation.
> >>>Q: Why is top posting frowned upon?
> http://xkcd.com/84/ | http://xkcd.com/149/ | http://xkcd.com/549/
> GPG: D5B20C0C (6741 8EE4 6C7D 11FB 8DA8  9E4A EECD 9A84 D5B2 0C0C)

------------------------------------------------------------------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pfsense.org/pipermail/list/attachments/20110924/0ab39c3b/attachment.html>