Access Web Interface via WiFi (Access Point mode)

Post new topic   Reply to topic    DD-WRT Forum Index -> Atheros WiSOC based Hardware
Goto page Previous  1, 2
Author Message
fritzmg
DD-WRT Novice


Joined: 18 Sep 2015
Posts: 11

PostPosted: Sat Sep 19, 2015 14:57    Post subject: Reply with quote
mwbuss8 wrote:
That is quite a post on the wiki. There is a lot of information, but also a lot of optional (marked as such) steps as well. I had never read through it until now, but I've setup several DD-WRT APs and never come across your issue.

I'd suggest resetting your router. Leave it disconnected from everything but your computer for now. Setup WiFi. Set your SSID and PW, and select a channel if you want, but leave the advanced settings alone. Save your changes. Change LAN IP to 10.0.0.2 and save. Disconnect and reconnect your computer (to obtain new IP address) and login to the router at the new IP. Disable WAN and save. Disable DHCP and save, then go to the admin page and reboot. Connect it to your other router LAN<->LAN. Connect via WiFi and test. It should work now. If there are other settings you want to change or use from the wiki, try one at a time. This way, If the problem comes back, you will know what caused it.

I generally change 1 setting at a time and save, rather than completing a whole page. I've come across issues when trying to change multiple settings at a time.

If this doesnt work, I'm not sure what it could be. As I said, I've never come across this issue, and its how I setup quite a few now.

I have followed your steps exactly, however, as soon as I connect my PC via WiFi and try to access the Web Interface of DD-WRT on http://10.0.0.2 it again redirects me to http://0.0.0.0
So the advanced settings of the Wiki entry do not seem to be the cause of this issue at all.

Furthermore I noticed the following:
  • If my PC was connected to the LAN via cable during the last reboot of DD-WRT, I am able to access the Web Interface without any troubles.
  • If I try to access the Web Interface from a completely different PC which is connected to the LAN via WiFi, I get redirected to http://0.0.0.0 on that PC
  • When I try now on the first PC, which is still connected to the LAN via cable, it also gets redirected to http://0.0.0.0



blaser wrote:
something is wrong, you mac addresses are the same for WAN LAN and WLAN.

This seems to be normal. Right now when I tried mwbuss8 suggestion, I noticed that the LAN and WAN interface had a different MAC address, the LAN and Wireless LAN adapter had the same MAC address by default. As soon as you switch off the WAN adapter in the settings, the WAN adapter gets the same MAC address in the info page.

_________________
TP-Link TL-WR1043ND
Sponsor
mwbuss8
DD-WRT Guru


Joined: 23 Feb 2015
Posts: 751

PostPosted: Sat Sep 19, 2015 17:34    Post subject: Reply with quote
Do you have access to the settings of your main router? Are you using 1 computer in all these attempts, or have you tried with multiple devices?
fritzmg
DD-WRT Novice


Joined: 18 Sep 2015
Posts: 11

PostPosted: Sat Sep 19, 2015 17:36    Post subject: Reply with quote
mwbuss8 wrote:
Do you have access to the settings of your main router?

Some, but which settings of the main router could influence this particular behavior of the DD-WRT Software?


mwbuss8 wrote:
Are you using 1 computer in all these attempts, or have you tried with multiple devices?

1 Computer, except in my previous post (PC1 -> LAN -> DD-WRT -> ok, PC2 -> WiFi -> DD-WRT -> 0.0.0.0, PC1 -> LAN -> DD-WRT -> 0.0.0.0).

_________________
TP-Link TL-WR1043ND
mwbuss8
DD-WRT Guru


Joined: 23 Feb 2015
Posts: 751

PostPosted: Sat Sep 19, 2015 18:13    Post subject: Reply with quote
When connected to the 1043 via WiFi, what does your computer show for IP address, gateway, and DNS?
fritzmg
DD-WRT Novice


Joined: 18 Sep 2015
Posts: 11

PostPosted: Sat Sep 19, 2015 18:23    Post subject: Reply with quote
LAN:
Code:
Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
Physical Address. . . . . . . . . : 50-E5-49-5B-E3-07
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2a02:8388:8580:…
IPv6 Address. . . . . . . . . . . : 2a02:8388:8580:…
Lease Obtained. . . . . . . . . . : Samstag, 19. September 2015 18:31:29
Lease Expires . . . . . . . . . . : Samstag, 19. September 2015 20:21:18
Temporary IPv6 Address. . . . . . : 2a02:8388:8580:…
Link-local IPv6 Address . . . . . : fe80::2549:c60c:6a1f:d36d%12(Preferred)
IPv4 Address. . . . . . . . . . . : 10.0.0.16(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Samstag, 19. September 2015 16:57:39
Lease Expires . . . . . . . . . . : Samstag, 26. September 2015 18:31:52
Default Gateway . . . . . . . . . : fe80::2abe:9bff:fe9f:e140%12
                                    10.0.0.1
DHCP Server . . . . . . . . . . . : 10.0.0.1
DHCPv6 IAID . . . . . . . . . . . : 290514249
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-16-88-CD-…
DNS Servers . . . . . . . . . . . : 2001:730:3e62::53
                                    10.0.0.1
NetBIOS over Tcpip. . . . . . . . : Enabled


WiFi:
Code:
Description . . . . . . . . . . . : 300Mbps Wireless USB Adapter
Physical Address. . . . . . . . . : 14-CC-20-10-ED-34
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2a02:8388:8580:…
Lease Obtained. . . . . . . . . . : Samstag, 19. September 2015 20:21:45
Lease Expires . . . . . . . . . . : Samstag, 19. September 2015 20:22:45
IPv6 Address. . . . . . . . . . . : 2a02:8388:8580:…
Temporary IPv6 Address. . . . . . : 2a02:8388:8580:…
Link-local IPv6 Address . . . . . : fe80::e58d:8abd:29fa:997b%22(Preferred)
IPv4 Address. . . . . . . . . . . : 10.0.0.20(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Samstag, 19. September 2015 20:21:43
Lease Expires . . . . . . . . . . : Samstag, 26. September 2015 20:21:44
Default Gateway . . . . . . . . . : fe80::2abe:9bff:fe9f:e140%22
                                    10.0.0.1
DHCP Server . . . . . . . . . . . : 10.0.0.1
DHCPv6 IAID . . . . . . . . . . . : 404016160
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-16-88-CD-…
DNS Servers . . . . . . . . . . . : 2001:730:3e62::53
                                    10.0.0.1
NetBIOS over Tcpip. . . . . . . . : Enabled


So pretty much the same, except for the IPv4 and IPv6 address of the client.

I doubt it has anything to do with the clients or the network setup. It's simply: as soon as there is an attempted connection to the web interface via HTTP to the Access Point, the DD-WRT software always sends the aforementioned response header from then on, to any client.

May be the web server crashes when a connection attempt is made via the WiFi adapter and thus from then on it sends this response header. The rest of the system keeps functioning normally (i.e. the functionality of the Access Point is otherwise fine).

_________________
TP-Link TL-WR1043ND
h8red
DD-WRT Guru


Joined: 28 Jun 2011
Posts: 580
Location: Vilnius, Lithuania

PostPosted: Sun Sep 20, 2015 14:38    Post subject: Reply with quote
mwbuss8 wrote:
When connected to the 1043 via WiFi, what does your computer show for IP address, gateway, and DNS?

Primary router resolves when you are in "router" mode

_________________
[Ramips] Nexx WT3020F Openwrt @kernel #4.14.167 (OpenVPN server, Wireguard server, AD blocking, SQM QOS, USB)
ciscodlink
DD-WRT User


Joined: 13 May 2014
Posts: 273

PostPosted: Tue Sep 22, 2015 15:16    Post subject: Reply with quote
I have the same problem with the newest firmware: v3.0-r27805 std (09/11/15). Hardware is TP-Link WR842ND.

I can access the WebUI if I'm wired but not if I'm wireless.

I actually bought 5 of these and set them all up the same way, and they all have the same problem. If I am connected wirelessly to Router1, I can access the WebUI's of all the other routers, but not Router1. If I then connect to Router2, I can access all the WebUI's except Router2. If I connect with a cable to any router, I can access all WebUIs.

The same symptoms happen with Ping. I cannot ping a router's LAN IP if I am connected wireless to it, but I can ping all the other routers.

All routers are set up as Access Points.
thecrater
DD-WRT Novice


Joined: 09 Jul 2013
Posts: 42

PostPosted: Sat Mar 05, 2016 14:45    Post subject: Reply with quote
Hello. Have you managed to resolve this problem? I'm having the same issue with the latest build as well on a Netgear WDR3700v1 (Atheros) and the latest build DD-WRT v3.0-r29193 std.

My primary router is on 192.168.1.1
The secondary one has DHCP disabled, Gateway & DNS set to the primary router's address.

Everything works fine including accessing devices physically and wirelessly connected to the primary router and vice-versa. The only problem is accessing the management GUI of router 2 on 192.168.1.2 when connected via WIFI. LAN connectivity is fine.

Edit: here is the error I get in Chrome
"Google Chrome's connection attempt to 192.168.1.2 was rejected"
tuxero
DD-WRT Novice


Joined: 26 Apr 2022
Posts: 5

PostPosted: Sat Apr 30, 2022 11:33    Post subject: Reply with quote
Sorry for reviving such an old thread. I've got a tl-wr1043nd v4 with exactly the same problem on latest 48741 firm. Did you manage to solve it on dd-wrt or, maybe, with openwrt?
kernel-panic69
DD-WRT Guru


Joined: 08 May 2018
Posts: 14125
Location: Texas, USA

PostPosted: Sat Apr 30, 2022 12:32    Post subject: Reply with quote
Check your wireless settings to see if wifi webUI access is disabled. It shouldn't matter if it is configured as a WAP or not anymore.
_________________
"Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT
Pogo - A minimal level of ability is expected and needed...
DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)

----------------------
Linux User #377467 counter.li.org / linuxcounter.net
tuxero
DD-WRT Novice


Joined: 26 Apr 2022
Posts: 5

PostPosted: Sat Apr 30, 2022 17:49    Post subject: Reply with quote
kernel-panic69 wrote:
Check your wireless settings to see if wifi webUI access is disabled. It shouldn't matter if it is configured as a WAP or not anymore.


The symptoms are the same as of the other people who reported back 6 years ago, I can access ping/webui/etc the AP connected to that same AP over wifi but cannot access the rest of the lan; in contrast with a pc connected over wire to this AP I can access the lan and vice versa to that pc over other devices on the lan (same AP or to the main router, makes no difference).
Goto page Previous  1, 2 Display posts from previous:    Page 2 of 2
Post new topic   Reply to topic    DD-WRT Forum Index -> Atheros WiSOC based Hardware All times are GMT

Navigation

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum