I am facing here an issue with my omnios installs. Let's say I have an omnios VPS instance and I have an omniOS NAS in my LAN. I'd like to build a VPN between them. VPS have public IP, while my NAS doesn't. On NAS side the GZ and the NGZ have explicit LAN ip (10.0.0.0/24), no etherstub. However on the VPS side I have an etherstub between the GZ and NGZ.

On both end I have an NGZ as VPN exit point, both running tailscale, configured.

Now ideally I'd liek to easily ssh from one GZ to the other GZ (eg. transparent connectivity.) This is not working yet.

What works: I can ssh from one tailscale NGZ to the other side GZ, and from the other side tailscale NGZ to this side GZ.

Eg. : far side NGZ to near GZ works, also near NGZ to far GZ works.

but near GZ to far GZ doesn't working.

as NGZ to GZ works, it is a pfroof for tailscale to be working just fine. I belive I am routing the packages somewhere incorrectly.

I have created static routed in my GZs to direct the packages into the NGZs, there is no firewall rules to block the comm, but it still not working-

I was messing around with snoop, but failed to find out the problem. I would greatly appreciate any help

Previously I have managed to get this done with my OmniOS NAS + an OpenBSD VPS, but I'd lie kto have OmniOS on both end.

my netstats: paste.omnios.org/?ce0c894a6ac6a090#…jiF8Fm2zUFeFBJPZtCybY7GbXeKESd1AWVd

diagram of the setup would probably help both you and anyone trying to help.

I agree, however it is getting late and i need to wake up pretty erly tomorrow, ilet me do it tomorrrow

Without route entry gz does not know where to route to the other GZ and will route to default router

toasterson: i was inable to follow you, sorry.

you need routing table entries

you didn't mention setting any up

I have created routes in the GZs for to access the other side via the NGZs. That is what you mean or something doifferent?

Yes thats what I mean. And also return routes?

lets talk about this tomorrow...

ok

my thoughts are the same sort of thing as toasterson, it's some sort of routing issue. either missing routes, network/subnet issues or possibly some odd nat happening (that's unexpected)

Or Ip forwarding not enabled in the ngz

ip forwarding is dnabled on both ngz