Having trouble with DHCP and access point
-
Yes, well the current situation on wireless/AP is that the lil router I flashed works, but wireless doesn't. I can't find any right now where it does work on the E2500 V3, but looking in the dd-wrt forums, it seems tehre are a number of complaints about it being just fine except the wifi. So, at this point, I jsut plan to buy an AP.
-
ohh then in that case i suggest buying R7000 ($140) or a unifi LR ($80)
-
I've looked into them, that unifi actually looks pretty good. Only thing is here, I would have to order it in, but I probably will. thanks for the tip on that.
-
unifi is awesome if you have dead spots (no wifi or low wifi signal) in the house. But usually that's not the case in America unless you have a huge house. The unifi can also have ddwrt but I haven't tried it and not sure how stable it is but wouldn't change it to ddwrt because the webGUI is awesome. If you do change it to ddwrt tell me how it goes ;)
-
Thanks, I ordered the unifi AP-LR today, on rush. Pretty excited. Thats cool it can take dd-wrt too.. but I will probably stick with the mfg interface
-
if you put dd-wrt on it I don't think there is a way to put it back.. So think carefully about that, or validate that you can put it back.
-
Yeah I looked, only briefly, but I think you are right, it seems there is no way (currently) to revert back. I still plan to stick with the original firmware.
I guess my plan, right now is to have 2 different SSIDS and 2 VLANs. Not too experienced with VLANs, but if I get the gist, I will ahve to configure the same (2) vlans on the router and the AP, and assign /link the SSID's to their respective vlan? -
yeah exactly.. So I have my guest wlan run on it a vlan.. Simple enough to do with the unif software. The only 1 complaint that I hear is there is no way to change the management vlan from 1.
I don't see a problem with that in my setup, but it would be a nice feature to be able to do that.
You can run 4 SSIDs with unifi per radio. Then in pfsense you just create that vlan assign it to a physical interface and on your switch trunk the connections so you can carry the vlans you want.
-
actually you can use VLANS if you get the nighthawk with DDWRT. I have 3 access points unifi and 2 VLANS configured on the nighthawk. The only bad thing about that is trying to block webpages because the nighthawk has its own DNSmasq. Its possible to block pages but if lets say VLAN 1(192.168.3.1) i block facebook it will also block VLAN 2 (192.168.40.1).
If you do get the nighthawk ill help you out
-
I have received the Unifi AP-LR. I am trying to configure it but having some issues. However, firstly, I need to sort out this…. When I connect the AP-LR to LAN interface it will detect in Unifi software. but when attached to OPT1 which I want to use for wireless devices, it does not show up. So it seems communication is not working between the 2 interfaces.
My first thought is firewall rules? I did mess around with them a bit.. so I probably screwed it up myself. And a few I added based on some articles but they didn't seem(?) to turn out as the articles suggested. I think this is because the version used for the article was older.
My current FW rules are attachedAs a few additional notes, DHCP is enabled, and I can connect to WAN fine through LAN (Don't know yet with OPT1) I have a domain set, and a router name set and DNS forwarding seems to be working right(I think)
-
From my limited experience with the ubiquitis they like to be managed on the untagged (primary) VLAN. So your management VLAN should reach the access points untagged. If that is in place you can create SSIDs on tagged VLANs to your heart's content.
Other than that, please be more specific.
-
hmm…the lack of experience i have with OPT on pfSense not sure what you did wrong but what i know it should work essentially is first install the software(has its own web server) to configure the unifi https://www.ubnt.com/download/unifi/ install it ( you need java ) after connect it to the the LAN of the pfSense. It should give an IP ex: (192.168.1.80) to find the IP check either in ARP or download a network scanner like netscan. enter the IP on the url and configure the AP. Now if you want to create more SSID with different pool its possible though VLANS but they have to be tagged. If you look at the pic before you can see the config of DDWRT. Tag means that the unifi gets the DHCP of (192.168.1.80) but can also handle another DHCP (192.168.3.80), and untagged it can only handle on DHCP Pool (192.168.1.80). The only thing now is to find how to tag the LAN on pfSense lets say VLAN 3 And VLAN 4 then you put VLAN 3 And 4 on the unifi as the picture before.
-
Ok couple things on your rules - the rule on our lan that allows you to opt1 net is pointless since the rule above that lets you go anywhere.
The rules on your opt 1 you don't need that rule that allows to opt1 net, devices on opt1 don't talk to pfsense to access opt1 network. Your allowing them access to lan net so what is the point of saying !rfc1918 and using ppoe gateway?? Where do you think they are going to go with that 53 rule, when you told them if they are going anything not rfc1918 go out your ppoe gateway?
What exactly do you want to accomplish for this wifi segment?
As mentioned management of the unifi is native vlan 1, no tagging. While you can have your controller on your lan and your AP on opt1 - its easier to put your controller and AP on the same network, atleast for setup - then you can move the AP to different segment if you want. L3 managment http://wiki.ubnt.com/UniFi_FAQ#L3_.28Layer_3.29_Management
But if you run both controller and ap on opt1 network is very simple to get going and you can play with changing that after you get some more experience with it. If you then want to put a ssid on vlan then create vlan on pfsense put it on your opt1 interface and trunk the ports on your switch and then trunk the port going to your AP and your good.
-
Yeah, like I said, some of those rules are farked up, but the one with RFC and PPPOE was something an article had siggested. but not even sure if I had entered it right anyway
-
And again what exactly do you want to happen, and what article did you read that suggested such rules?
-
Good question.. there is a few things I was trying to do, it may have been a attempt at bridging OPT1 to LAN or otherwise getting them to talk. The only link I can find now that I still have in my cache is http://www.cyberciti.biz/faq/how-to-pfsense-configure-network-interface-as-a-bridge-network-switch/
But it was not this link, however, it's going back to the firest day I started running pfsense.. so its' sorta fuzzy now. But I do know the RFC points to an alias which is 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16Anyways, what I want to do is get LAN and OPT1 to communicate.
My roadmap, so to speak is
Get communication between LAN and OPT1
Add VLANs and 2nd distinct wireless networks (SSID's)
(Maybe) Add radius on one VLAN (Not sure yet if it will be the best solution)
Add Security Network VLAN (Probably just a couple cameras, recorder. but it may expand over time)
Add NAS (Abt 16TB)
in the future, I intend to have a web server on a DMZ, and an internal sql server. But that is way off, currently. -
If you need a switch get a switch. Don't waste router ports. You'll just end up with a hub anyway. Not a switch.
-
Yeah bridge is not something you want to do.. And clearly it would not be a "switch" it would be as already stated HUB.. It is very RARE that you would actually want to do something like that.. I really don't understand the fascination with taking a highly valuable interface on your router/firewall and using it as switch port when you can get a 8 port get "SWITCH" for like 20$ if you need more ports. The only time I could see bridging interfaces would be if you want to do a transparent firewall sort of setup. And not a fan of that setup either ;)
The very nature of creating opt1 means it can talk to lan – and vice versa if you want devices to talk between these segments then create the rule on opt1 that allows that, by default lan is any any. Have you changed that?
Post up your rules for lan and opt1 and describe what you want to allow or not to allow devices on each segment or even other vlans to do to the other vlans..
What I would suggest you do any any rules get your stuff talking, have your ssid with its own vlan, etc.. And then lock down your rules to how you want them.. Example my wlan can not talk to my lan except for ntp to my ntp server on that segment, my ipad can do what it wants. My guest wireless on its own vlan can not talk to anything not even pfsense for dns - I hand out public dns for the guest. Only thing it can do is ping the wlanguest pfsense interface for connectivity testing, etc.
So example rules
-
https://doc.pfsense.org/index.php/Firewall_Rule_Troubleshooting
Read and understand that first. You have all sorts of nonsense rules in there.
After that, if you move the AP to another interface, you will almost certainly lose the ability to auto-discover the AP from other networks and will need to specify it by IP address in the unifi "controller" software.
-
ok thanks I'll read that. but yeah, at that time, I didn't know bridging wasn't really a good thing, but found out later, so stopped trying, but at this point, I am looking at keeping it on this interface, and maybe have the security network on a different interface.
My original plan, was to have 3 interfaces (I have more network cards I can add if I want, they have no other real uses right now) one lan, one for wireless and one for home media devices like PS3, netflix boxes etc, and the Nas box would be able to stream on it, (Not sure yet if it will be able to without being physically attached to both interfaces?) then the security would get placed accordingly (Kinda assumed I'd add another nic) But, the more I look at it, the more it seems there isn't much value in having wireless on a separate interface, and it works better in terms of vlan + SSID vs seperate interface + VLAN + SSID… as wifi be needed on both, so might as well just use seperate SSID's and VLAN, and use the other interface for security, eliminating the need for an additional nic.
