Posted: Mon Feb 08, 2021 4:08 Post subject: [R7000] CB - Clients have internet, router itself does not
Recently I am having the same issue with the same router.
I am using Client Bridge in Router Mode, gateway IP is filled in with AP gateway IP. When I changed it to Client mode it started working, but obviously none of my devices had internet.
I tried using url, IP. I also tried pinging those both from telnet to no avail. Could also ping router ip, and localhost, but not AP gateway IP.
As a last resort, I assigned my router to same subnet as AP (i.e. AP gateway was 192.168.123.138 and I set router IP to 192.168.123.150 (but I think the bug was I didn't change /24). and now I can't access my router page.
R7000 on r45690
Last edited by Treees on Mon Feb 08, 2021 16:05; edited 1 time in total
Thanks for making a new thread, but it was actually relevant to the last thread, I just had an additional issue.
The br0 interface does not seem to have any internet connectivity. As you can see, this results in ntpclient not running or (although on RB, this issue still exists) resolving dns for OpenVPN.
The last part of the issue is the host router is (gateway) IP 192.168.123.138 and I set the R7000 as 192.168.123.150, and now I cannot access the router.
I have tried setting my IP statically on 192.168.1.x, ....0.x, with various subnet settings, etc. and I cannot access the router at 192.168.123.150.
Joined: 08 May 2018 Posts: 14246 Location: Texas, USA
Posted: Mon Feb 08, 2021 16:33 Post subject:
In wired AP, Switch, CB and RB modes, you have to set the upstream gateway in the basic setup page under network (as well as possibly somewhere under wireless). If you change the router's local IP like you did, you have to have a computer on the same subnet either via dhcp or static ip (192.168.123.x) as the webUI will no longer be accessible @ 192.168.1.1 under a 192.168.1.x subnet ...
In wired AP, Switch, CB and RB modes, you have to set the upstream gateway in the basic setup page under network (as well as possibly somewhere under wireless). If you change the router's local IP like you did, you have to have a computer on the same subnet either via dhcp or static ip (192.168.123.x) as the webUI will no longer be accessible @ 192.168.1.1 under a 192.168.1.x subnet ...
P.S. @egc, I didn't split this because it wasn't necessary
I tried setting static IP on 192.168.123.x and still can't access the router. I will try a reset and see if the ntp/dns issues are existent afterwards.
Also it seems my gateway AP IP changed. It's a mobile phone with mobile hotspot, and I changed no settings besides having it turned off and then back on.
Is that going to cause any issue? Because setting the gateway IP every time the hotspot comes online (and changes IP) seems to be pretty tedious.
Before I noticed the routing issue, I did see that the gateway IP had been cleared in the web UI. Kind of weird considering the internet has been working fine (and still does).
EDIT: I did try something similar to this with the proper IP, but the IP cannot even be pinged from telnet or router interface either.
And how important specifically is time on the router in regards to routing? I am not running cron jobs or anything similar and everything I can think of involving time would be based on a duration wherein the specific time doesn't matter. May be completely wrong, but interested in fixing this.
Joined: 08 May 2018 Posts: 14246 Location: Texas, USA
Posted: Mon Feb 08, 2021 17:52 Post subject:
If you're connecting to a mobile hotspot, you should just use client mode on one of the radios and AP on the other. CB and RB aren't good for that. JMHO. _________________ "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
If you're connecting to a mobile hotspot, you should just use client mode on one of the radios and AP on the other. CB and RB aren't good for that. JMHO.
I understand that the bridged modes are kind of hacky, so I will take your word for it.
I reset and set it up with client mode, but I have a few more questions.
1. How do I find the outgoing interface? (before it was vlan2 iirc)
2. Do you think it would be more optimal to set the phone to output 2ghz or 5ghz (then the router would output 5ghz and 2ghz respectively)
I do not believe that distance is an issue in my current setup, and that all devices can access the 2ghz router AP.
3. Can I use a non-DD-WRT router downstream? (i.e. just use the DD-WRT router to connect to the hotspot and then use ethernet connection to non-DD-WRT router)
Joined: 08 May 2018 Posts: 14246 Location: Texas, USA
Posted: Mon Feb 08, 2021 19:59 Post subject:
Ideally, it would be great if Android and iOS tethering support were fully supported, then you wouldn't have to muck with doing anything wireless, but.
It mainly depends on signal strength and coverage from your hotspot to the router on which radio to use as client and which to use as AP. Keep in mind, you will have to pick one or the other, since I don't think you can add a VAP on the client radio.
If I remember right, it should automatically select which interface is WAN. I would have to break out my R7000P to look into that.
You can use another router downstream with stock firmware, and if it supports switch or wired AP mode, that might even be better so you're not triple NAT. As it stands right now, you will likely be double NAT (phone and DD-WRT router). _________________ "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
Ideally, it would be great if Android and iOS tethering support were fully supported, then you wouldn't have to muck with doing anything wireless, but.
It would be nice. I sort of got it working with an older mega build. I also tested it with OpenWRT, but from what I could tell it is throttled differently by the cellular ISP.
What I mean is that the USB modem connection is detected as mobile tethering data (and thus metered and throttled differently), whereas using the mobile hotspot with DD-WRT router is considered as mobile data (i.e. from within the phone itself). Actually, my phone's hotspot shows no devices connected, even though the router is connected.
Ideally, a VPN connected to by the phone could be bridged with the mobile hotspot. This used to be possible in Android, while using a non-vanilla method to start the hotspot (usually requiring root). I believe it is possible now with root, but I think it still requires a double VPN or something similar. On iPhone there is a similar method with jailbreak.
I have been using this setup for over a year now, so I will take a look into a few different methods for improving the set up. Thanks.
Joined: 18 Mar 2014 Posts: 12915 Location: Netherlands
Posted: Tue Feb 09, 2021 7:20 Post subject:
Like in your earlier thread it was already remarked that some providers will check if you are using a hotspot (when you use client mode i.e. the non -bridged mode) and that there are ways to deal with this.
Like in your earlier thread it was already remarked that some providers will check if you are using a hotspot (when you use client mode i.e. the non -bridged mode) and that there are ways to deal with this.
Thanks for the response. That's actually why I was asking what the outgoing interface is. For CB it was vlan2 and get_wanface was null (obviously wan disabled). So without bridge mode using the raw 'get_wanface' commands will work (seems to show eth2)
Also I'm not sure exactly what these commands do, but I had them saved in my firewall script from last backup.
Something to fix closed nat I think? This isn't needed because I am double nated now I guess?
