>
> >>>>> Sometimes github.com resolves to 192.30.253.112 and .113 and
> today(at least) they don't allow port 22 ssh, so `git push` fails like
> >>>>> ssh: connect to host github.com port 22: No route to host
>
You can also run qvm-firewal --reload your-github-vm.
I assigned a shortcut in the task bar to reload the firewall of all VMs for
sites with many IP addresses, you could go one step further and do it
constantly:
while sleep 60; do for vm in your-github-vm some-other-vm blah blah;
qvm-firewal --reload "$vm"; done; done
If the VM is currently halted, it does not attempt to start it, and does
not trigger any error :) .
> ok, it's because of Qubes because having a rule in Firewall like "
github.com" "ssh" "tcp" which apparently adds an iptables(?) rule based on
resolved IP at the time(of AppVM start?), and github having changing IPs
("We do not recommend whitelisting by IP address," from:
https://help.github.com/articles/about-github-s-ip-addresses/ )
>From experience, the IP is resolved on VM start.
Cheers,
Georges Dupéron
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/CAKQnwqYyrvZa_L31YEMem8O_Y9wWaDV9fHnsAtT3PbM0xKbd_A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
