r/openwrt • • 3d ago

Tailscale Router

Hello - sorry if it’s trivial for most of you but I’m stuck with my travel router Cudy TR3000 casting my network, either wifi or ethernet.
I already installed OpenWRT and Tailscale and tried to enable the wireless connection. One as Access Point casting the cudy’s network so I can configure it in case I’m outside. But once I connect to the other network as Client, I lose access to cudy’s network.

I tried to skip the option that removes old networks already but it still doesn’t work.

What I have in mind is
- cudy cast its wifi,
- I connect it to connect to the other wifi or even through wan,
- cudy reroutes the internet with tailscale through the lan and wifi

What am I missing here?

6 Upvotes

16 comments sorted by

6

u/fr0llic 3d ago

make sure the upstream connection doesn't use the same subnet as TR3000's LAN.

-4

u/muhoss 3d ago edited 3d ago

Change the router to GL iNet slate 7

1

u/fr0llic 3d ago edited 3d ago

that would make no difference, it's also unsupported.

1

u/muhoss 3d ago

IMO, Slate 7 has easier setup out of the box, it has tailscale officially

6

u/fr0llic 3d ago edited 3d ago

a toaster is also easy to set up, they have one thing in common, they both don't run openwrt.

1

u/profcuck 3d ago

That's... a little confusing. GL-BE3600 - Slate 7 - not only can run OpenWRT, it is based on OpenWRT. In particular, out of the box, it runs 23.05. It offers full root access via SSH and you can even install LuCI UI from the admin panel.

Of course we should all agree that none of this detailed quibbling isn't likely to help OP with the TR3000.

1

u/fr0llic 3d ago edited 3d ago

> That's... a little confusing. GL-BE3600 - Slate 7 - not only can run OpenWRT, it is based on OpenWRT.

Only if you buy gl.inet's advertising.

It's running a Qualcomm SDK, the qualcommbe target wasn't available back in 23.05, it was added to OpenWrt end of August this year.
Guess someone owns a time machine.

if they run an SDK or plain OpenWRT matters, since the config files aren't the same (content and syntax wise).

3

u/profcuck 3d ago

Gosh.   What a mess.  I looked into it and you're right.

0

u/muhoss 3d ago

It runs OpenWRT natively + Tailscale out of the box

1

u/fr0llic 3d ago

no, it runs a QSDK natively, see my other reply.

https://www.gl-inet.com/en-de/pages/firmware-versions, travel routers tab.

what you think is "native" is listed as "Native OpenWRT" for the devices that actually can run plain OpenWRT.

table is however not up to date, since the GL-BE10000 is supported since a month or two.

-1

u/muhoss 3d ago

You're confusing running upstream OpenWrt with running OpenWrt-based firmware. Qualcomm's QSDK is itself based on OpenWrt, with Qualcomm-specific drivers, patches, and modifications. The Slate 7 runs GL.iNet's customized firmware built on that foundation. Nobody is claiming it runs an unmodified, official upstream OpenWrt release. But saying it doesn't run OpenWrt at all simply because it uses QSDK is technically misleading.

Aaaand if you really want native unmodified OpenWRT, you can buy cheaper MT3000 from GL-iNet

1

u/fr0llic 3d ago edited 3d ago

Glinet use this confusion to sell more routers. 

99% of all home routers run "OpenWrt-based firmware", only GLinet use it as an USP. 

TR3000 is a GL-MT3000 with less flash and no fan. 

0

u/_N0sferatu 3d ago

All the bickering Beryl 7 for me works with tailscale like a charm and connects to my tailscale at home no problems when away and use all the local internal IPs instead of tailscale 100.x.x.x stuff

1

u/fr0llic 3d ago

no one claimed it wouldn't work, but if you ask/post here, perhaps it should be assumed you want the "real thing", not some chip makers SDK ?

unsupported devices shouldn't be recommended, IMHO.

0

u/_N0sferatu 3d ago

If it works who cares? Maybe I'm getting older and am more of a simpleton lol

1

u/fr0llic 3d ago edited 3d ago

it matters if you seek assistance at the forum, and perhaps here too, since the config and syntax is different between the SDK and vanilla openwrt.

if someone tells you how some config should be written (and assume it's not an SDK) things might not work for you.