Problem with two lan networks and access to ap



  • I do not know if the question fits this forum
    If not
    Delete it

    Until two days ago
    I had pfsense 2.0.3
    I have one wan connection
    And two lan connections
    Wired network 192.168.0.1
    {Wireless network 192.168.2.1 connects to Router used as ap}

    from a Computer on the wired
    I punch in the address of the ap
    192.168.2.101
    Address is outside the dhcp

    And reaches The router's management interface

    I just upgraded the pfsense
    from Version 2.0.3
    To version 2.1

    Now for some reason it does not happen
    I get an error {Attached Image}

    I do not have access to the management interface of the The router through the wired network

    Have access only through a computer connected to the wireless

    How can I fix it and return to the previous state
    I also have access from the Wired network




  • I think its possible you may have DHCP running on the AP.  If you do, need to turn that off.
    OR
    Its possible that "AP Isolation mode" is running on the AP.
    If so, turn that off.



  • The dhcp not working on the AP

    I had access to everything was normal

    After doing an upgrade from pfsense 2.0.3
    To version 2.1  {I forgot to mention it in the first post and added it}

    now I do not have access to the AP



  • Are there rules on both interfaces to pass any from any for any protocol?



  • I do not know
    When I plugged the ap it just worked

    I guess there was something automatically tuned

    Maybe something deleted in upgrading



  • Check your firewall rules.  Makes sure you have rules on each interface to pass/allow traffic.



  • The only thing I can think of
    It is the first line of the wifi interface
    I'm pretty sure it was like the first line of the lan interface
    But I do not remember






  • Can you post Diagnostics > ARP Table?



  • Of course

    In the first line where registered address 192.168.0.1
    Registered home.plex

    It 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 network

    With it I check the wireless network is working
    And have access to the management interface of the ap


  • Banned

    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?



  • @kejianshi:

    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

    @doktornotor:

    Well, I would suggest to flush the traffic shaping down the drain for starters.

    what  traffic shaping ?


  • Banned

    All that "$foo computer is limited to $bar MB download" stuff.



  • Do not know if it is related to
    Before I upgraded to 2.1

    Everything 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.


  • Banned

    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.



  • @kejianshi:

    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


  • Netgate Administrator

    IPv4/IPv6 issue? I don't think v6 is enabled by default in release, not sure though.

    Steve



  • @doktornotor:

    Well, I would suggest to flush the traffic shaping down the drain for starters.

    @kejianshi:

    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 result

    @stephenw10:

    IPv4/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?



  • @kejianshi:

    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 problem

    It 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 upgrading

    Could it be because the gateway

    The new package appears under Services Status

    apinger – Gateway Monitoring Daemon


  • Banned

    @kejianshi:

    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 pfsense

    The only thing there is a network name ssid
    And password to the network

    And again it worked properly for six months
    Just two days ago after upgraded the pfsense
    I do not have access to the management interface

    I 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.



  • @kejianshi:

    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 cards

    Downloaded from the website of pfsense
    Version 2.0.3 to burn to disc

    I 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 AP

    I 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 earlier

    I currently browses through the operating system disk

    Still no access



  • Netgate Administrator

    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



  • @stephenw10:

    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 package

    Still no access


  • Netgate Administrator

    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


  • Netgate Administrator

    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 Network

    And Reverse

    i can ping from a computer that Connected to the Wireless Network
    to a computer connected to the wired Network


Log in to reply