bruce wrote:
Michael, Hi. As you've by now realized/found out, using a VPN client can often wreck havoc with your system/dns/ip addresses. In fact, you might actually run into an issue where you have device conflicts if you happen to have staticly allocated ip addresses in your network, and you hook to a vpn setup that has used the same subclass... gotta be careful these days!! -----Original Message----- From: fedora-list-bounces@xxxxxxxxxx [mailto:fedora-list-bounces@xxxxxxxxxx]On Behalf Of Michael H. Semcheski Sent: Sunday, July 01, 2007 5:08 PM To: For users of Fedora Subject: Re: DHCP and DNS Thanks for the response, Manuel. Although I've had this problem a few times, I rebooted today, and most things seem to be working. The DNS problem seems to have fixed itself. I think maybe the problem was actually related to an SSL-VPN client I'm using (Juniper Network Connect), which is heavy handed, and changed my DNS suffix and secondary DNS servers.
The new openvpn client associated with NetworkManager seems to work like a charm for many of us at the office. Up until F7 we were forced to use the cisco provided Linux client module.
Now, we can one click NetWorkmanager and get connected to the office. Other benefits: Local network is still active! Passwords stored in local key ring. No need to rebuild a kernel module every kernel upgrade. Much kinder to local config files. Besides all of that, it is just plain crazy slick! It is worth a look! Good Luck. -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
