Can't access openwrt access point's admin interface











up vote
0
down vote

favorite












I've turned my TP-Link Archer C5 into an access point with this guide, using openwrt. It works correctly, and I can now access the internet through the wlan of the access point.



I've set a static ip for the AP (192.168.1.2), as it said in the tutorial, but after connecting to the AP I have internet but can't reach 192.168.1.2. It just times out, with both ssh and a web browser.



So it seems it no longer has an ip address (it does have an ipv6 ip though, but I can't access it through that either). How can I access the web interface of my AP?










share|improve this question


















  • 1




    Have you tried an IP scan to see which ip addresses are available? Have you rebooted the device? Sometimes a device can crash, but still appear to work mostly. It allows traffic to be go through but the admin interface stops working.
    – LPChip
    Mar 28 '16 at 14:09










  • @LPChip I have. I've rebooted it, and even reset to factory defaults. It seems to be a result of the configuration, and not a bug. I've checked my main router's routing table, and the AP isn't assigned an IP, just a IPV6 address..
    – vkjb38sjhbv98h4jgvx98hah3fef
    Mar 28 '16 at 14:16










  • @LPChip Is it inherent to access points to not have an ip? Do you know of anything I could change to openwrt's config to resolve this issue?
    – vkjb38sjhbv98h4jgvx98hah3fef
    Mar 28 '16 at 14:26






  • 1




    If you set the AP as a repeater, it will repeat all settings and thus not have an IP. If you just make it a regular AP, it should have an IP address.
    – LPChip
    Mar 28 '16 at 14:29










  • @LPChip Hmm ok. There are several types of access point walkthroughs: I've used bridged ap, but there's also dumb ap and routed ap. I'm guessing I would need to set it as a routed ap?
    – vkjb38sjhbv98h4jgvx98hah3fef
    Mar 28 '16 at 17:00















up vote
0
down vote

favorite












I've turned my TP-Link Archer C5 into an access point with this guide, using openwrt. It works correctly, and I can now access the internet through the wlan of the access point.



I've set a static ip for the AP (192.168.1.2), as it said in the tutorial, but after connecting to the AP I have internet but can't reach 192.168.1.2. It just times out, with both ssh and a web browser.



So it seems it no longer has an ip address (it does have an ipv6 ip though, but I can't access it through that either). How can I access the web interface of my AP?










share|improve this question


















  • 1




    Have you tried an IP scan to see which ip addresses are available? Have you rebooted the device? Sometimes a device can crash, but still appear to work mostly. It allows traffic to be go through but the admin interface stops working.
    – LPChip
    Mar 28 '16 at 14:09










  • @LPChip I have. I've rebooted it, and even reset to factory defaults. It seems to be a result of the configuration, and not a bug. I've checked my main router's routing table, and the AP isn't assigned an IP, just a IPV6 address..
    – vkjb38sjhbv98h4jgvx98hah3fef
    Mar 28 '16 at 14:16










  • @LPChip Is it inherent to access points to not have an ip? Do you know of anything I could change to openwrt's config to resolve this issue?
    – vkjb38sjhbv98h4jgvx98hah3fef
    Mar 28 '16 at 14:26






  • 1




    If you set the AP as a repeater, it will repeat all settings and thus not have an IP. If you just make it a regular AP, it should have an IP address.
    – LPChip
    Mar 28 '16 at 14:29










  • @LPChip Hmm ok. There are several types of access point walkthroughs: I've used bridged ap, but there's also dumb ap and routed ap. I'm guessing I would need to set it as a routed ap?
    – vkjb38sjhbv98h4jgvx98hah3fef
    Mar 28 '16 at 17:00













up vote
0
down vote

favorite









up vote
0
down vote

favorite











I've turned my TP-Link Archer C5 into an access point with this guide, using openwrt. It works correctly, and I can now access the internet through the wlan of the access point.



I've set a static ip for the AP (192.168.1.2), as it said in the tutorial, but after connecting to the AP I have internet but can't reach 192.168.1.2. It just times out, with both ssh and a web browser.



So it seems it no longer has an ip address (it does have an ipv6 ip though, but I can't access it through that either). How can I access the web interface of my AP?










share|improve this question













I've turned my TP-Link Archer C5 into an access point with this guide, using openwrt. It works correctly, and I can now access the internet through the wlan of the access point.



I've set a static ip for the AP (192.168.1.2), as it said in the tutorial, but after connecting to the AP I have internet but can't reach 192.168.1.2. It just times out, with both ssh and a web browser.



So it seems it no longer has an ip address (it does have an ipv6 ip though, but I can't access it through that either). How can I access the web interface of my AP?







networking wireless-networking router openwrt






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Mar 28 '16 at 14:03









vkjb38sjhbv98h4jgvx98hah3fef

10817




10817








  • 1




    Have you tried an IP scan to see which ip addresses are available? Have you rebooted the device? Sometimes a device can crash, but still appear to work mostly. It allows traffic to be go through but the admin interface stops working.
    – LPChip
    Mar 28 '16 at 14:09










  • @LPChip I have. I've rebooted it, and even reset to factory defaults. It seems to be a result of the configuration, and not a bug. I've checked my main router's routing table, and the AP isn't assigned an IP, just a IPV6 address..
    – vkjb38sjhbv98h4jgvx98hah3fef
    Mar 28 '16 at 14:16










  • @LPChip Is it inherent to access points to not have an ip? Do you know of anything I could change to openwrt's config to resolve this issue?
    – vkjb38sjhbv98h4jgvx98hah3fef
    Mar 28 '16 at 14:26






  • 1




    If you set the AP as a repeater, it will repeat all settings and thus not have an IP. If you just make it a regular AP, it should have an IP address.
    – LPChip
    Mar 28 '16 at 14:29










  • @LPChip Hmm ok. There are several types of access point walkthroughs: I've used bridged ap, but there's also dumb ap and routed ap. I'm guessing I would need to set it as a routed ap?
    – vkjb38sjhbv98h4jgvx98hah3fef
    Mar 28 '16 at 17:00














  • 1




    Have you tried an IP scan to see which ip addresses are available? Have you rebooted the device? Sometimes a device can crash, but still appear to work mostly. It allows traffic to be go through but the admin interface stops working.
    – LPChip
    Mar 28 '16 at 14:09










  • @LPChip I have. I've rebooted it, and even reset to factory defaults. It seems to be a result of the configuration, and not a bug. I've checked my main router's routing table, and the AP isn't assigned an IP, just a IPV6 address..
    – vkjb38sjhbv98h4jgvx98hah3fef
    Mar 28 '16 at 14:16










  • @LPChip Is it inherent to access points to not have an ip? Do you know of anything I could change to openwrt's config to resolve this issue?
    – vkjb38sjhbv98h4jgvx98hah3fef
    Mar 28 '16 at 14:26






  • 1




    If you set the AP as a repeater, it will repeat all settings and thus not have an IP. If you just make it a regular AP, it should have an IP address.
    – LPChip
    Mar 28 '16 at 14:29










  • @LPChip Hmm ok. There are several types of access point walkthroughs: I've used bridged ap, but there's also dumb ap and routed ap. I'm guessing I would need to set it as a routed ap?
    – vkjb38sjhbv98h4jgvx98hah3fef
    Mar 28 '16 at 17:00








1




1




Have you tried an IP scan to see which ip addresses are available? Have you rebooted the device? Sometimes a device can crash, but still appear to work mostly. It allows traffic to be go through but the admin interface stops working.
– LPChip
Mar 28 '16 at 14:09




Have you tried an IP scan to see which ip addresses are available? Have you rebooted the device? Sometimes a device can crash, but still appear to work mostly. It allows traffic to be go through but the admin interface stops working.
– LPChip
Mar 28 '16 at 14:09












@LPChip I have. I've rebooted it, and even reset to factory defaults. It seems to be a result of the configuration, and not a bug. I've checked my main router's routing table, and the AP isn't assigned an IP, just a IPV6 address..
– vkjb38sjhbv98h4jgvx98hah3fef
Mar 28 '16 at 14:16




@LPChip I have. I've rebooted it, and even reset to factory defaults. It seems to be a result of the configuration, and not a bug. I've checked my main router's routing table, and the AP isn't assigned an IP, just a IPV6 address..
– vkjb38sjhbv98h4jgvx98hah3fef
Mar 28 '16 at 14:16












@LPChip Is it inherent to access points to not have an ip? Do you know of anything I could change to openwrt's config to resolve this issue?
– vkjb38sjhbv98h4jgvx98hah3fef
Mar 28 '16 at 14:26




@LPChip Is it inherent to access points to not have an ip? Do you know of anything I could change to openwrt's config to resolve this issue?
– vkjb38sjhbv98h4jgvx98hah3fef
Mar 28 '16 at 14:26




1




1




If you set the AP as a repeater, it will repeat all settings and thus not have an IP. If you just make it a regular AP, it should have an IP address.
– LPChip
Mar 28 '16 at 14:29




If you set the AP as a repeater, it will repeat all settings and thus not have an IP. If you just make it a regular AP, it should have an IP address.
– LPChip
Mar 28 '16 at 14:29












@LPChip Hmm ok. There are several types of access point walkthroughs: I've used bridged ap, but there's also dumb ap and routed ap. I'm guessing I would need to set it as a routed ap?
– vkjb38sjhbv98h4jgvx98hah3fef
Mar 28 '16 at 17:00




@LPChip Hmm ok. There are several types of access point walkthroughs: I've used bridged ap, but there's also dumb ap and routed ap. I'm guessing I would need to set it as a routed ap?
– vkjb38sjhbv98h4jgvx98hah3fef
Mar 28 '16 at 17:00










1 Answer
1






active

oldest

votes

















up vote
0
down vote













So apparently the problem was that my main router uses 192.168.178.* as the space to assign ip addresses in (which isn't standard, usually it's 192.168.1.*). When I configured my AP like so:



gateway: 192.168.178.1
dns: 192.168.178.1
ip: 192.168.178.2


Where 192.168.178.1 is the ip for my router, and 192.168.178.2 is the desired ip for my AP it worked. Now I can reach the admin interface at the AP's ip when my AP is connected to the router via cable, and I'm connected to the AP over wifi.



All other settings were used from: https://wiki.openwrt.org/doc/recipes/bridgedap






share|improve this answer





















    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "3"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1058212%2fcant-access-openwrt-access-points-admin-interface%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes








    up vote
    0
    down vote













    So apparently the problem was that my main router uses 192.168.178.* as the space to assign ip addresses in (which isn't standard, usually it's 192.168.1.*). When I configured my AP like so:



    gateway: 192.168.178.1
    dns: 192.168.178.1
    ip: 192.168.178.2


    Where 192.168.178.1 is the ip for my router, and 192.168.178.2 is the desired ip for my AP it worked. Now I can reach the admin interface at the AP's ip when my AP is connected to the router via cable, and I'm connected to the AP over wifi.



    All other settings were used from: https://wiki.openwrt.org/doc/recipes/bridgedap






    share|improve this answer

























      up vote
      0
      down vote













      So apparently the problem was that my main router uses 192.168.178.* as the space to assign ip addresses in (which isn't standard, usually it's 192.168.1.*). When I configured my AP like so:



      gateway: 192.168.178.1
      dns: 192.168.178.1
      ip: 192.168.178.2


      Where 192.168.178.1 is the ip for my router, and 192.168.178.2 is the desired ip for my AP it worked. Now I can reach the admin interface at the AP's ip when my AP is connected to the router via cable, and I'm connected to the AP over wifi.



      All other settings were used from: https://wiki.openwrt.org/doc/recipes/bridgedap






      share|improve this answer























        up vote
        0
        down vote










        up vote
        0
        down vote









        So apparently the problem was that my main router uses 192.168.178.* as the space to assign ip addresses in (which isn't standard, usually it's 192.168.1.*). When I configured my AP like so:



        gateway: 192.168.178.1
        dns: 192.168.178.1
        ip: 192.168.178.2


        Where 192.168.178.1 is the ip for my router, and 192.168.178.2 is the desired ip for my AP it worked. Now I can reach the admin interface at the AP's ip when my AP is connected to the router via cable, and I'm connected to the AP over wifi.



        All other settings were used from: https://wiki.openwrt.org/doc/recipes/bridgedap






        share|improve this answer












        So apparently the problem was that my main router uses 192.168.178.* as the space to assign ip addresses in (which isn't standard, usually it's 192.168.1.*). When I configured my AP like so:



        gateway: 192.168.178.1
        dns: 192.168.178.1
        ip: 192.168.178.2


        Where 192.168.178.1 is the ip for my router, and 192.168.178.2 is the desired ip for my AP it worked. Now I can reach the admin interface at the AP's ip when my AP is connected to the router via cable, and I'm connected to the AP over wifi.



        All other settings were used from: https://wiki.openwrt.org/doc/recipes/bridgedap







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Mar 29 '16 at 20:48









        vkjb38sjhbv98h4jgvx98hah3fef

        10817




        10817






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Super User!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.





            Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


            Please pay close attention to the following guidance:


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1058212%2fcant-access-openwrt-access-points-admin-interface%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            How do I know what Microsoft account the skydrive app is syncing to?

            When does type information flow backwards in C++?

            Grease: Live!