I'm noticing the same issue running Pfsense Beta2 on the WRAP platform. I
confess that I haven't tried WPA, but WEP doesn't seem to want to work.  I
noticed a post on the forums talking about it, but hasn't had a reply yet...
http://forum.pfsense.org/index.php?PHPSESSID=640755670ff1943851e202742423222
0&topic=770.0

 I guess I'm just chiming in..  I don't much more information at this time.
If someone needs some to help this issue along, I would be more than happy
to supply whatever is needed

Barry

> -----Original Message-----
> From: news [mailto:[EMAIL PROTECTED] On Behalf Of Gil Freund
> Sent: Saturday, March 18, 2006 3:01 PM
> To: support@pfsense.com
> Subject: [pfSense Support] Re: hostap question(s)
> 
> Gil Freund wrote:
> > Platform:
> > RELENG_1_SNAPSHOT_03-10-2006 On Wrap
> > Wireless (Philips/IBM):
> > ath0: <Atheros 5212> mem 0x80000000-0x8000ffff irq 12 at 
> device 13.0 
> > on pci0
> > ath0: Ethernet address: 00:05:4e:47:c2:b6
> > ath0: mac 5.6 phy 4.1 5ghz radio 1.7 2ghz radio 2.3
> > 
> > I have three local networks:
> > sis0: 192.168.1.0
> > sis2: 192.168.2.0
> > ath0: 192.168.3.0
> > All with DHCP services.
> > 
> > Systems connected to the sis interfaces have no issue 
> acquiring a DHCP address.
> > 
> > From the wireless I can only associate using WPA (which is 
> OK, for the 
> > time being), but not using WEP (for older systems).
> 
> Follow up:
> 
> DHCP works if I use WPA. Does this make any sense?
> 
> Gil
> 
> 
> > 
> > Once the system does associate, it does not acquire an address from 
> > the DHCP. I see no errors in the system log or any blocks 
> on the firewall log. Netstat shows:
> > udp4       0      0  *.bootps               *.*
> > and ps shows:
> > dhcpd  21576  0.0  1.5  2152  1784  ??  INs   7:16PM   0:00.00
> > /usr/local/sbin/dhcpd -user dhcpd -group _dhcp -chroot 
> /var/dh cat of 
> > /var/dhcpd/etc/dhcpd.conf:
> > subnet 192.168.1.0 netmask 255.255.255.0 {
> >         pool {
> >                 range 192.168.1.10 192.168.1.100;
> >         }
> >         option routers 192.168.1.1;
> >         option domain-name-servers 192.168.1.1; } subnet 
> 192.168.2.0 
> > netmask 255.255.255.0 {
> >         pool {
> >                 range 192.168.2.10 192.168.2.100;
> >         }
> >         option routers 192.168.2.1;
> >         option domain-name-servers 192.168.2.1; } subnet 
> 192.168.3.0 
> > netmask 255.255.255.0 {
> >         pool {
> >                 range 192.168.3.10 192.168.3.100;
> >         }
> >         option routers 192.168.3.1;
> >         option domain-name-servers 192.168.3.1; }
> > 
> > Any ideas?
> > 
> > Thanks
> > 
> > Gil
> 
> 
> ---------------------------------------------------------------------
> 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]

Reply via email to