On Mon, Dec 10, 2007 at 11:59:50PM -0500, Mike Kershaw wrote: > > No, I'm not using tunneling. I don't use a VPN. > > > > I followed a suggestion from PorkChop to restore my original resolv.conf > > and see what happens. I restored resolv.conf to its original value and > > rebooted. The UDP traffic to port 137 has stopped. > > Rebooting is not necessary, and resets firewall rules. Theres no > telling what might have been open before which isn't now.
And on additional consideration: Changing the resolv.conf will never affect traffic coming into your system. However: 1. It may affect the logging if your system is trying to do lookups 2. If you're not running a netbios name resolver and a system inside your network is trying to connect to a share based on dns resolves, and you're talking to an outside dns server, it may be returning public IPs for internal traffic, causing internal smb browsers to generate traffic leaving your network. -m -- Mike Kershaw/Dragorn <[EMAIL PROTECTED]> GPG Fingerprint: 3546 89DF 3C9D ED80 3381 A661 D7B2 8822 738B BDB1 "We're sorry, Susy won't be attending classes for the rest of this academic year. She caught the measles, and we had her shot."
pgpuCLiILsOrP.pgp
Description: PGP signature
_______________________________________________ Mid-Hudson Valley Linux Users Group http://mhvlug.org http://mhvlug.org/cgi-bin/mailman/listinfo/mhvlug Upcoming Meetings (6pm - 8pm) MHVLS Auditorium Dec 5 - Open Source Show and Tell Jan 2 - TBD Feb 6 - DBUS Mar 5 - Setting up a platform-independent home/small office network using Linux
