Problem with two lan networks and access to ap
-
Well, I would suggest to flush the traffic shaping down the drain for starters.
I think doktornotor is right. Traffic seems to be working and allowed for the most part on both interfaces. All I can imagine is that your limiter is breaking the AP interface access.
I tried without rules
I tried to freeze them
Or removing them
Still the same resultIPv4/IPv6 issue? I don't think v6 is enabled by default in release, not sure though.
Steve
Indeed ipv6 off
I tried to run it but it requires ipv6
How do I fill it
-
OK - So now I need to ask some dumb questions.
Have you power-cycled the AP? What model AP is it? Are you running squid or snort or any packages? Which packages?
-
OK - So now I need to ask some dumb questions.
Have you power-cycled the AP? What model AP is it? Are you running squid or snort or any packages? Which packages?
I turned off and turned it on several times during attempts to look at why I do not have access to it
I do have a snort and squid
The interface with access to ap installed after the installation of packages
And there was no problemIt works just right
level one WBR-3406TX Wireless Broadband NAT Router
The only difference I see in Dashboard
It is in
Services Status
Appears apinger Gateway Monitoring Daemon was not in 2.0.3
-
Usually when I see someone troubleshooting a problem with SNORT running I just abandon the thread, however…
In services > proxy Server:
can you check the box for "Bypass proxy for Private Address Space (RFC 1918) destination" and save.
Then can you reboot pfsense and the AP
Then try again.
-
Still no access
weird
-
I do not think it is blocked
Because it worked great before upgradingCould it be because the gateway
The new package appears under Services Status
apinger – Gateway Monitoring Daemon
-
Usually when I see someone troubleshooting a problem with SNORT running I just abandon the thread, however…
Disable snort? Works? Disable both snort and squid? Works? And with that, I'm out of this thread, following the good advice above, essential for mental sanity.
-
This thing is a full-on broadband router - Are you 100% sure your are NOT running any of its many functions that will break its ability to play well with pfsense?
level one WBR-3406TX Wireless Broadband NAT Router
Please do me a favor… Draw me a diagram how this this is connected also.
-
When I changed this router to ap
I followed online Guide
I canceled the dhcp
I canceled the firewall
I plugged to the lan port
I gave him a fixed address outside the range of dhcp addresses of pfsenseThe only thing there is a network name ssid
And password to the networkAnd again it worked properly for six months
Just two days ago after upgraded the pfsense
I do not have access to the management interfaceI have not changed anything there
again
Thanks for the help -
OK - I'm going to go ahead and join you in not knowing whats wrong.
Is this a stand alone machine?
Could you boot this pfsense from livecd with no packages and no rules and try?
This way can know if 2.1 works for you but maybe your settings or packages are just screwed up.
-
Is this a stand alone machine?
I did not understand what it means stand alone machine ?
I will describe what I have
I took a computer without an operating system with nothing
I added three network cardsDownloaded from the website of pfsense
Version 2.0.3 to burn to discI turned on the computer and installed the system
Beyond that I do not have much access to this computer
One network card connected to the modem
Second network card is connected to the switch
Third network card connected to API do not have a disk with version 2.1
I'll have to download and burn -
I would try it with a livecd. This way you don't have to go changing settings to experiment to find out if its just the settings or packages.
You can tinker and the changes will not be permanent. -
OK
I downloaded the file, burn it
I turned on the system from the disk
I defined the interfaces according to what I wrote earlierI currently browses through the operating system disk
Still no access
-
The IPv4/v6 thing is not relevant here. With it enabled by default in the beta and RC images it sometime caused odd connection problems when people had broken IPv6 implenmentations at their ISP or router/AP.
My money is on Snort. Do the Snort get correctly copied across the update? Check the logs, what is being blocked?
Steve
-
My money is on Snort. Do the Snort get correctly copied across the update? Check the logs, what is being blocked?
I currently browses through the live cd
No packageStill no access
-
Lost that bet then! ::)
Check the firewall logs anything blocked? You've unchecked 'block private networks'?
Forget accessing the webgui of the AP. Try some basic pinging. Try to ping everything from everything else! Check the logs again.
Steve
-
There Pings
Both to ap
Well as computer connected wirelessly to ap -
Sorry I'm not sure quite what you mean there. What can ping what? :-\
Steve
-
i can ping from a computer that Connected to the Wired network
to the AP
to a computer connected to the Wireless NetworkAnd Reverse
i can ping from a computer that Connected to the Wireless Network
to a computer connected to the wired Network -
Ok.
Can you ping from the pfSense box to the AP? to a wireless client?
Can you ping from the AP to the pfSense box or a wired client?I have a router I use as an access point that behaves exactly as yours is doing and the reason is that it has no route to get packets back to clients on the other subnet. The AP/router usually uses it's WAN port for anything that isn't in its LAN subnet but in this scenario it has no WAN so it has no route. I have successfully worked around this by setting a subnet mask on the AP that contains all the local subnets, i.e. /16 However I have an AP this doesn't work for.
That doesn't explain why it worked fine under 2.0.3 though. :-\Steve
