Local route

[frankive]

Out of the box we can connect but the traffic is not routed to our Veeam PN server and it's network.
if we add the route manually on the standalone computers (or add it to the configfile of vpn) it works as it should.

Shouldn't there be a line somewhere where we can add the route before generating the configfiles for the clients with the routes included?

[HannesK]

Hello,
just to be sure... is it about Client-to-Site VPN and did you follow the instructions?

I assume, that registering the Hub Site was forgotten.

Best regards,
Hannes

[frankive]

yes, at no poin this tutorial can we set the static routes we need.

An alternative is to do full tunnelig, then it will work, but that is not we want to accomplish.

[HannesK]

I just remember that I forgot the Hub Site setup once. So that was my guess.

If that does not do the job for you, then I can only suggest to use the workaround you already found (also described in the thread I linked)

[frankive]

Yes, but hopefully the developers can make it possible to add some custom lines (with example of static routes) to the Veeam PN GUI.

[HannesK]

chances for new features on VeeamPN are low... if you like to use something futureproof, I recommend checking out other VPN products

[frankive]

why is that? veeam pn rocks!

[HannesK]

veeam pn rocks!

thanks - I forwarded that to the developer. But unfortunately, there are not enough resources. Our focus is "backup" (well, restore) not networking

[atakacs]

Well it seems that VeeamPN is pretty much abandonware, which IMHO is a shame (no update for 18 months and the repo http://repository.veeam.com/pn/public has invalid signing keys).

Now I can understand the priorities are elswhere but in that case why not drop the product altogether and open source it ? I don't think there is much - if any - propriatery material in there, just a smart assembly of usefull public domain tools.

[HannesK]

thanks, I will check the key topic.

about open source: we had that idea, but it's complicated with legal department... sorry for that

[HannesK]

the keys should be fine according my colleagues. Expiration date March 2024. Can you maybe provide more details?

GPG keyring http://repository.veeam.com/keys/veeam.gpg

Code: Select all

 gpg veeam.gpg
gpg: WARNING: no command supplied.  Trying to guess what you mean ...
pub   rsa4096 2016-05-06 [SC] [expires: 2024-03-24]
      EFAFF6B44E6880EADDD217E47AFDEEB8FBF8A590
uid           Veeam Software Repository key <support@veeam.com>
sub   rsa4096 2016-05-06 [S] [expires: 2024-03-24]
sub   rsa4096 2018-04-17 [S] [expires: 2024-03-24]

maybe this helps?

Code: Select all

sudo apt-key list
sudo apt-key del <here_old_key_id>
curl -s http://repository.veeam.com/keys/veeam.gpg | apt-key add -