Comet Pro KVM Tailscale Expose LAN Subnet

It doesn’t appear that you can expose the LAN subnet to Tailscale, is there something I’m missing here? My goal is to use Tailscale on the Comet Pro to expose the LAN subnet to my Tailnet…there’s not even a basic router built into this box to route WiFi to LAN for Tailscale access? Is this something that can be done manually or through a firmware update?

To setup a subnet router you would need to advertise the routes and turn on ip forwarding on the KVM device in question

You would have to do this through the kvm terminal by going to toolbox > terminal > access

not sure if this is something supported on the kvm (the forwarding would be the big question)

Yeah, the Comet Pro KVM IS the KVM I’m talking about. :slight_smile: That’s the entire point of the question, CAN it do it.

I tried to run some of the commands on my Rm1 and they failed. The big thing would be figuring out the correct files to run the commands above against. The RM1 at least is running an older EOL kernel (4.9.111 holy old) so ill see if I can figure out how gl inet has tailscale setup on this device.

in theory you could just enable the exit node option in the GUI and that should allow you to access the local ip address on the local network the KVM is sitting on.

Yeah, I don’t think there is a router in the Comet Pro, the LAN port is just a ‘dongle’, there is no routing between the WiFi and the LAN ports on the box. Seems like a big miss to me.

to setup a subnet router, you only need one interface to be plugged into the network. Not both. The ip forward command in the document above turns that forwarding option with tailscale and the interface that is plugged into your network

the ip forwarding is a thing on the kvm if you can enable the exit node on your model. (it also uses ip forwarding). Does your model support that? (tjhe rm1 does, so I assume yours does too)

I don’t think you understand what I’m trying to do. I want to connect the WIFI of the KVM to a public network, connect the LAN to my local subnet (that doesn’t have internet access) and expose that subnet to my Tailnet….you cannot do that it appears. It’s not a router.

(I do this on the daily with a Beyrl and it works great)

Ah yes okay, I would say it could be possible if you mess around with the terminal and play around with NAT settings but getting a gl inet router would be a better option than the KVM. The KVM is for remote access to a single system.

I understand, and I do use routers, but it would have been nice as a single box solution since technically it COULD do it. Even if they just stuck in a cheap router it would be enough.

Would ‘tailscale serve’ work without forwarding maybe? (depending on exactly why you want access to the subnet)

I'm not sure what you mean, the Comet doesn't expose any subnets to Tailnet at all. The WiFi and LAN are separate interfaces, there is no routing.

tailscale serve can proxy requests to a lan device. Like port forwarding on an internet router.

You can port forward ports on the tailscale IP towards other devices. Or set it up as reverse web proxy in front of web servers and so forth.

I dont know what all happens on the backend but the team would have to setup routing/NAT on the KVM to accomplish that which is a pretty niche request. Not sure if they would invest a lot of time in this since they have a whole line of routers that do the captive portal/wireless thing. But you never know if you just ask

But that's not what I'm asking for, I'm asking for the box to route WIFI Tailnet and expose the LAN as a subnet. So it's a dual purpose box that does basic routing from wifi (wan) to the LAN for tailscale and also a KVM.

It would just be nice to be able to do a basic route in a single box rather than lugging around a couple boxes and setting everything up ‘all the time’.

Yeah, that's why I asked, maybe a GLInet guy would answer. :man_shrugging::slightly_smiling_face:

Maybe there is a language barrier here but I thought you were talking about plugging in the WIFI and LAN interface at the same time. You should be able to setup the subnet router on the wifi interface, like I said it would be just finding the right file to edit to get it working

Why do you need the subnet exposed exactly though, appreciate that’s the ideal solution but what is it you are accessing on the other side? Or is it more that you are trying to use the KVM to let the device access something elsewhere in the tailnet? There may be another way to get what you need working in the interim that isn’t routing the subnet.

Everything on the subnet, I want to be able to access all devices that are on that subnet (I’m doing this currently with a Beyrl router) I program AV systems and all our gear would reside on that subnet. It would be like a remote support scenario, where I may not need a KVM specifically to a machine, but just in-case I could have it, but also use it like a standard Tailscale router capable of exposing the LAN as a subnet on my Tailnet while the KVM WiFi is the WAN.

I understand I can do this with two boxes, but if the KVM could work like this as a single box it would be amazing.

1 Like

Again, there is no router in the KVM you cannot route like a WAN/LAN scenario like you might do with a standard router.