Training, Open Source computer languages
PerlPHPPythonMySQLApache / TomcatTclRubyJavaC and C++LinuxCSS 
Search for:
Home Accessibility Courses Diary The Mouth Forum Resources Site Map About Us Contact
 
For 2023 (and 2024 ...) - we are now fully retired from IT training.
We have made many, many friends over 25 years of teaching about Python, Tcl, Perl, PHP, Lua, Java, C and C++ - and MySQL, Linux and Solaris/SunOS too. Our training notes are now very much out of date, but due to upward compatability most of our examples remain operational and even relevant ad you are welcome to make us if them "as seen" and at your own risk.

Lisa and I (Graham) now live in what was our training centre in Melksham - happy to meet with former delegates here - but do check ahead before coming round. We are far from inactive - rather, enjoying the times that we are retired but still healthy enough in mind and body to be active!

I am also active in many other area and still look after a lot of web sites - you can find an index ((here))
How to specify which NIC to use?

Posted by neilvp (neilvp), 25 February 2005
I am attempting to write a test suite in TCL that is to talk via an Ethernet connection to the Device Under Test (DUT). (My 'first program' ambitious or what?)

Our IT people are understandably reluctant to let me talk via the corporate network linked to my desktop. (What could possibly, possibly go wrong) So, they have suggested that they install a second NIC card in my PC (running Windows 2k Pro) and I work over the lab network to the DUT. My question is... can I specify which NIC card my program talks through from within TCL and, if so, how?



Posted by admin (Graham Ellis), 25 February 2005
Being more of a Linux person than a Windows one ...

Unless you're programming at a low level / hardware level, I would suggest you install the second NIC and configure it with its oen networrk number ... for example if your main network was 192.168.200.xxx, configure the second NIC to 192.168.123.xxx. Then if your Tcl program talks to a "192.168.123.xxx" system, it should use the second NIC and network.  

I know that's how it would work on the systems I'm slightly more familiar with at an OS configuration level ....

Posted by neilvp (neilvp), 17 March 2005
I have now found the 'proper' way to do this is to modify /set the route table up within the PC.
Using a command prompt type <route ?> and all the necessary information appears to enable one to set this up using <route add >

Posted by admin (Graham Ellis), 17 March 2005
Glad you sorted that.  And thanks for coming back to complete the thread.

- Graham



This page is a thread posted to the opentalk forum at www.opentalk.org.uk and archived here for reference. To jump to the archive index please follow this link.

You can Add a comment or ranking to this page

© WELL HOUSE CONSULTANTS LTD., 2024: Well House Manor • 48 Spa Road • Melksham, Wiltshire • United Kingdom • SN12 7NY
PH: 01144 1225 708225 • FAX: 01144 1225 793803 • EMAIL: info@wellho.net • WEB: http://www.wellho.net • SKYPE: wellho