[nos-bbs] Re: nos-bbs Digest, Vol 26, Issue 33

Wed Sep 27 18:46:05 EDT 2006

nos-bbs-request at lists.tapr.org wrote:

>Send nos-bbs mailing list submissions to
>	nos-bbs at lists.tapr.org
>
>To subscribe or unsubscribe via the World Wide Web, visit
>	https://lists.tapr.org/cgi-bin/mailman/listinfo/nos-bbs
>or, via email, send a message with subject or body 'help' to
>	nos-bbs-request at lists.tapr.org
>
>You can reach the person managing the list at
>	nos-bbs-owner at lists.tapr.org
>
>When replying, please edit your Subject line so it is more specific
>than "Re: Contents of nos-bbs digest..."
>
>
>Today's Topics:
>
>   1. Virtual Machine Network Driver (wa7nwp at jnos.org)
>   2. Re: Virtual Machine Network Driver (Mark Phillips)
>   3. Re: Virtual Machine Network Driver (Jaye Inabnit, ke6sls)
>   4. Re: Virtual Machine Network Driver (Mark Phillips)
>   5. Re: Virtual Machine Network Driver (wa7nwp)
>   6. Re: Virtual Machine Network Driver (Barry Siegfried)
>   7. Re: Virtual Machine Network Driver (Mark Phillips)
>
>
>----------------------------------------------------------------------
>
>Message: 1
>Date: Tue, 26 Sep 2006 19:25:12 -0500 (CDT)
>From: wa7nwp at jnos.org
>Subject: [nos-bbs] Virtual Machine Network Driver
>To: nos-bbs at lists.tapr.org
>Message-ID: <56932.131.107.0.74.1159316712.squirrel at www.jnos.org>
>Content-Type: text/plain;charset=iso-8859-1
>
>
><http://www.microsoft.com/downloads/details.aspx?FamilyID=dc8332d6-565f-4a57-be8c-1d4718d3af65&DisplayLang=en>
>
>Hopefully that link works.  It's to the Virtual Machine Network Driver for
>Microsoft Device Emulator.
>
>Since JNOS on Windows is like a virtual device, it might work for our
>network connectivity issue.
>
>Another idea might be to run a Virtual PC session in Windows with this
>Virtual Network Driver and run NOS in that session.
>
>A couple shots in the dark I know.
>
>Bill - WA7NWP
>
>
>
>------------------------------
>
>Message: 2
>Date: Tue, 26 Sep 2006 21:48:39 -0400
>From: Mark Phillips <g7ltt at g7ltt.com>
>Subject: Re: [nos-bbs] Virtual Machine Network Driver
>To: TAPR xNOS Mailing List <nos-bbs at lists.tapr.org>
>Message-ID: <1159321719.5320.13.camel at earth.g7ltt.com>
>Content-Type: text/plain
>
>Anyone tried JNOS in a VMWare session?
>
>Just a thought.
>
>Mark
>
>On Tue, 2006-09-26 at 19:25 -0500, wa7nwp at jnos.org wrote:
>  
>
>><http://www.microsoft.com/downloads/details.aspx?FamilyID=dc8332d6-565f-4a57-be8c-1d4718d3af65&DisplayLang=en>
>>
>>Hopefully that link works.  It's to the Virtual Machine Network Driver for
>>Microsoft Device Emulator.
>>
>>Since JNOS on Windows is like a virtual device, it might work for our
>>network connectivity issue.
>>
>>Another idea might be to run a Virtual PC session in Windows with this
>>Virtual Network Driver and run NOS in that session.
>>
>>A couple shots in the dark I know.
>>
>>Bill - WA7NWP
>>
>>_______________________________________________
>>nos-bbs mailing list
>>nos-bbs at lists.tapr.org
>>https://lists.tapr.org/cgi-bin/mailman/listinfo/nos-bbs
>>    
>>
>
>
>
>
>------------------------------
>
>Message: 3
>Date: Tue, 26 Sep 2006 18:59:53 -0700
>From: "Jaye Inabnit, ke6sls" <ke6sls at cox.net>
>Subject: Re: [nos-bbs] Virtual Machine Network Driver
>To: nos-bbs at lists.tapr.org
>Message-ID: <200609261859.53788.ke6sls at cox.net>
>Content-Type: text/plain;  charset="utf-8"
>
>On Tuesday 26 September 2006 18:48, Mark Phillips wrote:
>  
>
>>Anyone tried JNOS in a VMWare session?
>>
>>Just a thought.
>>
>>Mark
>>    
>>
>
>Why?   heehee
>
>73
>
>
>
>------------------------------
>
>Message: 4
>Date: Tue, 26 Sep 2006 22:08:12 -0400
>From: Mark Phillips <g7ltt at g7ltt.com>
>Subject: Re: [nos-bbs] Virtual Machine Network Driver
>To: TAPR xNOS Mailing List <nos-bbs at lists.tapr.org>, ke6sls at arrl.net
>Message-ID: <1159322892.5320.27.camel at earth.g7ltt.com>
>Content-Type: text/plain
>
>Why not? 
>
>Sure beats using some sort of crappy Microsnot driver. Not only that but
>you could run a Linux build on a winders box then.
>
>
>
>On Tue, 2006-09-26 at 18:59 -0700, Jaye Inabnit, ke6sls wrote:
>  
>
>>On Tuesday 26 September 2006 18:48, Mark Phillips wrote:
>>    
>>
>>>Anyone tried JNOS in a VMWare session?
>>>
>>>Just a thought.
>>>
>>>Mark
>>>      
>>>
>>Why?   heehee
>>
>>73
>>
>>_______________________________________________
>>nos-bbs mailing list
>>nos-bbs at lists.tapr.org
>>https://lists.tapr.org/cgi-bin/mailman/listinfo/nos-bbs
>>    
>>
>
>
>
>
>------------------------------
>
>Message: 5
>Date: Tue, 26 Sep 2006 19:25:35 -0700
>From: wa7nwp <wa7nwp at jnos.org>
>Subject: Re: [nos-bbs] Virtual Machine Network Driver
>To: TAPR xNOS Mailing List <nos-bbs at lists.tapr.org>
>Message-ID: <4519E11F.20801 at jnos.org>
>Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
>Mark Phillips wrote:
>  
>
>>Why not? 
>>
>>Sure beats using some sort of crappy Microsnot driver. Not only that but
>>you could run a Linux build on a winders box then.
>>    
>>
>
>The biggest problem with JNOS on Windows is that there's no easy and 
>good connectivity between JNOS and the Windows system - like we get with 
>Maiko's TUN0 or a virtual tty on Linux.   All the other virtual drivers 
>have issues.  The only real solution is a second hardware network card 
>and that defeats my idea of a clean and simple virtual machine that can 
>be cut and pasted between systems.   VMware or Virtual PC may both work 
>but that depends on how the networking and serial ports are handled.
>
>I would love to hear if anybody has tried and had success with a JNOS on 
>Linux on windows under either VMware or VPC...
>
>73
>Bill - WA7NWP
>
>
>
>------------------------------
>
>Message: 6
>Date: Wed, 27 Sep 06 02:53:52 EDT
>From: "Barry Siegfried" <k2mf at nnj.k2mf.ampr.org>
>Subject: Re: [nos-bbs] Virtual Machine Network Driver
>To: TAPR xNOS Mailing List <nos-bbs at lists.tapr.org>
>Message-ID: <13251.nosbbs at nnj.k2mf.ampr.org>
>
>[From: wa7nwp <wa7nwp at jnos.org> wrote]:
>
>  
>
>>The biggest problem with JNOS on Windows is that there's no easy and
>>good connectivity between JNOS and the Windows system - like we get
>>with Maiko's TUN0 or a virtual tty on Linux.   All the other virtual
>>drivers have issues.  The only real solution is a second hardware
>>network card and that defeats my idea of a clean and simple virtual
>>machine that can be cut and pasted between systems.  VMware or Virtual
>>PC may both work but that depends on how the networking and serial
>>ports are handled.
>>
>>I would love to hear if anybody has tried and had success with a JNOS
>>on Linux on windows under either VMware or VPC...
>>    
>>
>
>I have not tried NOS in a Linux VPC window but I have tried it in a
>DOS VPC window and yes, it works fine.  I am no fan of Microsoft or
>its products but VPC happens to be one incredible piece of software
>and it does something very magical with regard to how it handles
>ethernet NIC sharing between itself and the parent windows operating
>system (as well as OTHER VPC windows in the same machine).
>
>Unlike SwsVpkt, which causes an IP connectivity issue between itself
>and the parent windows operating system because it shares the same
>ethernet NIC (and MAC address), VPC actually somehow CHANGES the
>MAC address it sees for the SAME ethernet NIC!  And if you put
>multiple VPC windows in the same machine, each one can share the
>same ethernet NIC and will get a different MAC address!  This
>means that there are absolutely no IP connectivity issues between
>the parent windows operating system and its VPC windows.
>
>If you are interested in just how VPC accomplishes this MAC address
>change, the best description I have found is the follow blog post
>made by one of the guys working on VPC at Microsoft:
>
>http://blogs.msdn.com/virtual_pc_guy/archive/2005/04/01/404816.aspx
>
>I had always assumed that MAC addresses are written in stone on the
>NIC.  Apparently, they aren't, and even on most older NICs you can
>send out packets with a user defined MAC address.  As a matter of
>fact, the friend of mine who introduced me to VPC has also told me
>that he has used 'ifconfig' in Linux to change a MAC address on
>several occasions to force IP address changes from his provider
>and he also tells me that in windows most ethernet NIC drivers
>will allow you to enter any MAC address you wish.
>
>This was all astonishing info I never knew!  It's too bad SwsVpkt
>(which I actually prefer to use over VPC because of its simplicity)
>won't allow us to do that.  :(
>
>But the above information brings to my mind that it COULD be
>possible to change an ethernet adaptor address from NOS, presuming
>that NOS gave us the ability to do that which means that we might
>be able to do it through SwsVpkt as well.  I have to give that a
>whirl and see if it can be done.
>
>But back to VPC, if you decide to install VPC you will want to
>follow the directions for adding the "extensions", which gives
>you things like file-sharing with the parent operating system and
>being able to move your mouse between the VPC window and the parent
>operating system without having to left click to get into or escape
>via keyboard to get out of the VPC window.
>
>73, de Barry, K2MF >>
>           o
>          <|>      Barry Siegfried
>+---------/-\---------------------------+
>| Internet | bgs at mfnos.net              |
>| HomePage | http://www.mfnos.net/~bgs  |
>+----------+----------------------------+
>| Amprnet  | k2mf at nnj.k2mf.ampr.org     |
>| PBBS     | k2mf at k2ge.#cnj.nj.usa.noam |
>+----------+----------------------------+
>
>
>
>------------------------------
>
>Message: 7
>Date: Wed, 27 Sep 2006 10:00:49 -0400
>From: Mark Phillips <g7ltt at g7ltt.com>
>Subject: Re: [nos-bbs] Virtual Machine Network Driver
>To: TAPR xNOS Mailing List <nos-bbs at lists.tapr.org>
>Message-ID: <1159365649.5320.65.camel at earth.g7ltt.com>
>Content-Type: text/plain
>
>I dont think one would need to go to all the trouble of installing a
>full Linux/VMware on Winderz.
>
>VMware's engine is not free. It's designed to run just enough stuff to
>keep the desired application going and so the footprint is very small.
>
>I'll be doing some paid VMware work here shortly. Maybe I'll give it a
>try when the project is over before I have to rebuild the host machine.
>
>On Tue, 2006-09-26 at 19:25 -0700, wa7nwp wrote:
>  
>
>>Mark Phillips wrote:
>>    
>>
>>>Why not? 
>>>
>>>Sure beats using some sort of crappy Microsnot driver. Not only that but
>>>you could run a Linux build on a winders box then.
>>>      
>>>
>>The biggest problem with JNOS on Windows is that there's no easy and 
>>good connectivity between JNOS and the Windows system - like we get with 
>>Maiko's TUN0 or a virtual tty on Linux.   All the other virtual drivers 
>>have issues.  The only real solution is a second hardware network card 
>>and that defeats my idea of a clean and simple virtual machine that can 
>>be cut and pasted between systems.   VMware or Virtual PC may both work 
>>but that depends on how the networking and serial ports are handled.
>>
>>I would love to hear if anybody has tried and had success with a JNOS on 
>>Linux on windows under either VMware or VPC...
>>
>>73
>>Bill - WA7NWP
>>
>>_______________________________________________
>>nos-bbs mailing list
>>nos-bbs at lists.tapr.org
>>https://lists.tapr.org/cgi-bin/mailman/listinfo/nos-bbs
>>    
>>
>
>
>
>
>------------------------------
>
>_______________________________________________
>nos-bbs mailing list
>nos-bbs at lists.tapr.org
>https://lists.tapr.org/cgi-bin/mailman/listinfo/nos-bbs
>
>
>End of nos-bbs Digest, Vol 26, Issue 33
>***************************************
>
>  
>
I run knoppix linux live DVD no problem in ms'es virtual machine..I just 
point it to the 4 gig .iso on the hard drive..