On May 11, 2009, at 09:59, Pablo Sanchez wrote:
Yes, you want to affect the change on the `host'
Again, since sshd isn't running on the host, I don't see
that changing sshd_config there should have any effect.
I tried it, and it didn't help.
Should I:
o disconnect from VPN and restart the guest (easy enough)
o edit /etc/resolv.conf on the guest?
None of the above ... :) ... the problem is on the host. Let's first
try setting `UseDNS no' on the host. Let's see if that resolves the
issue.
Also, simplify the problem: do not use the key at first. Once you
get everything working sans key, add the key into the mix. You _may_
need to generate two keys depending on the whether you're in the VPN
environment or not.
I tried removing the key previously; it didn't affect the behavior.
I concluded I was looking in the wrong place.
I can much improve the behavior by tweaking /etc/resolv.conf on the
guest. But I'm not sure I can find a value that works well both when
the host is VPN-connected and disconnected. The Cisco VPN client
modifies the host's /etc/resolv.conf on connection, and restores it
on disconnection, but, of course, the guest is unaware of all this,
and doesn't track.
DNS is clearly a culprit: unless I fix /etc/resolv.conf, the guest
may be unable to make any internet connections.
Thanks again,
gil
_______________________________________________
vbox-users mailing list
[email protected]
http://vbox.innotek.de/mailman/listinfo/vbox-users
