http://bugzilla.novell.com/show_bug.cgi?id=599059
http://bugzilla.novell.com/show_bug.cgi?id=599059#c0 Summary: Multiple NIC Cards Confuses MonoVS Classification: Mono Product: Mono: Tools Version: MonoVS 1.0.x Platform: x86 OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: Visual Studio Integration AssignedTo: [email protected] ReportedBy: [email protected] QAContact: [email protected] Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/532.5 (KHTML, like Gecko) Chrome/4.1.249.1045 Safari/532.5 MonoVS does not appear to be able to specify which NIC to listen on. Furthermore, it only listens on the first one in the list for TCP. UDP appears to be fine, but UDP reports NIC A, yet is actually listening on NIC B. Maybe wireless is okay, but LAN connections exhibit this behavior. Reproducible: Always Steps to Reproduce: 1. Run MonoVS on a computer with multiple network interface connections. 2. Observe listening distribution using netstat. 3. Observe the reported listening address in VS; compare. Actual Results: Wrong port reported in VS that MonoVS was actually listening on. Expected Results: Listen on the specified NIC or all. Either is acceptable. This can be circumvented by knowing that it is an issue and using the IP that is known to be listened upon. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
