Problem with two lan networks and access to ap
-
Of course
In the first line where registered address 192.168.0.1
Registered home.plexIt should be listed also in the last line where the registered address 192.168.2.1
Not?
-
What is 192.168.2.8?
-
This laptop computer
Connected to the wireless networkWith it I check the wireless network is working
And have access to the management interface of the ap -
Well, I would suggest to flush the traffic shaping down the drain for starters. Took too long to respond sounds like you've shaped something to almost 0.
-
So, DHCP works on wireless?
DHCP works on wired LAN?
You can access the AP web interface on wireless?But not wired?
But internet works from either wired or wireless?
Is all that correct?
-
So, DHCP works on wireless?
DHCP works on wired LAN?
You can access the AP web interface on wireless?But not wired?
But internet works from either wired or wireless?
Is all that correct?
Is all that correct? – yes
Well, I would suggest to flush the traffic shaping down the drain for starters.
what traffic shaping ?
-
All that "$foo computer is limited to $bar MB download" stuff.
-
Do not know if it is related to
Before I upgraded to 2.1Everything worked properly with all these laws
Furthermore there was no law on the computer from which I am trying to access the interface
-
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.
-
Yeah, that may have well worked before but not after upgrade. (Also completely unclear what you've actually done there.) Simplify the configuration to barebones for troubleshooting!
-
And with that - I'll check back in after some sleep… Alot of it.
-
And with that - I'll check back in after some sleep… Alot of it.
Thank you both for your help
I will try to suspend the rules, or remove them and see if i have access
-
IPv4/IPv6 issue? I don't think v6 is enabled by default in release, not sure though.
Steve
-
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.
