VPN (PPTP) connects successfully but unable to ping some devices in the LAN

Question

When I click on the toggle menu it opens properly and then it automatically closes. I don't know why it is happening. I have only a little knowledge of JS.

How can I solve this problem?

My code

if ($('.nav-menu').length) {
  var $mobile_nav = $('.nav-menu').clone().prop({
    class: 'mobile-nav d-lg-none'
  });
  $('body').append($mobile_nav);
  $('body').prepend('<button type="button" class="mobile-nav-toggle d-lg-none"><i class = "icofont-navigation-menu" > < /i></button > ');
    $('body').append('<div class="mobile-nav-overly"></div>'); $(document).on('click', '.mobile-nav-toggle', function(e) {
      $('body').toggleClass('mobile-nav-active');
      $('.mobile-nav-toggle i').toggleClass('icofont-navigation-menu icofont-close');
      $('.mobile-nav-overly').toggle();
    });

    $(document).on('click', '.mobile-nav .drop-down > a', function(e) {
      e.preventDefault();
      $(this).next().slideToggle(300);
      $(this).parent().toggleClass('active');
    });

    $(document).click(function(e) {
      var container = $(".mobile-nav, .mobile-nav-toggle");
      if (!container.is(e.target) && container.has(e.target).length === 0) {
        if ($('body').hasClass('mobile-nav-active')) {
          $('body').removeClass('mobile-nav-active');
          $('.mobile-nav-toggle i').toggleClass('icofont-navigation-menu icofont-close');
          $('.mobile-nav-overly').fadeOut();
        }
      }
    });
  }
  else if ($(".mobile-nav, .mobile-nav-toggle").length) {
    $(".mobile-nav, .mobile-nav-toggle").hide();
  }

Solution

This is because the source address you are using to connect is in a different subnet and/or the APs don't allow packets having more than one hop. To circumvent this you should:

1. Connect to the AP via some workstation on the LAN, by getting the remote desktop and using a web browser. This is pretty much the silver bullet.
2. If you can't do the above, configure the default gateway on the AP, so it'll send the the traffic originating form outside the LAN to the router (yes, I'm aware of the address scheme you gave, and this will probably not work, because of ARP at play rather than IP routing)
3. If this doesn't work, enable the remote access/remote management (or whatever it is called in your AP) in your APs.

Also, the question is, are you going to access those APs on regular basis, or is it just a once-in-a-while configuration?

Comments

[Admin]

here is the good explanation, I already try to my pptp server pptpclient.sourceforge.net/routing.phtml#all-to-tunnel now I can shutdown my device from cellphone, all connected to one vpn server

[mplungjan]

I made you a snippet Please click edit then scroll down and click "edit above snippet" and add relevant frameworks, CSS and HTML

[Faeemazaz Bhanej]

Edit code and display HTML and CSS

[bobo]

What you mean is, when my home computer accesses the APs, they see the source IP as my home computer public IP rather than the 192.168.1.253 assigned by the Cisco router? I access these APs on regular basis.

[Konrad Gajewski]

No, they see it as 192.168.1.253 all right, but the APs generally refuse such packets on an IP level if they do not originate from the local network.

[bobo]

But after the VPN packets reach the Cisco router, it will unpack the packets before they reach the APs. So the APs should not know these packets in fact do not originate from the local network. Not true?

[Konrad Gajewski]

Do a traceroute to 192.168.1.253 from the local network.

[bobo]

I still haven't done this test but one thing I can confirm is that, when the access points are put in AP mode (yes, they have router / AP mode), the [allow remote management] tick box in the web admin interface will not be available. It seems it's common for different brands of routers to make this option unavailable when in AP mode. So it seems method 3 is not possible.

[bobo]

Method 1 is actually not possible because my working company don't have any workstation. It's a windows WORKGROUP rather than domain environment.

[bobo]

I have also checked that both APs currently already have default gateway set to 192.168.1.1.

[bobo]

Since the problem is that the VPN IP 192.168.1.253 I get is in a different subnet. I am thinking about whether it's possible to do some settings in the Cisco router so that when I request the web admin page, it will request on behalf of me, thereby the access points will see it's 192.168.1.1 rather than 192.168.1.253 who requests the page and since it's the same subnet, they should not complain.

[Konrad Gajewski]

As a last resort you might switch the WANs on on the APs, create a VLAN on the Cisco (lets say 192.168.0.0/24), and connect them to the via some switch to the router (call it OOB management).