Tony & Jordi,
Thank you for your help. When it comes to DECNET, I don't really care
about that since right now I have a single VMS emulated system. I am
running the current beta version so I will try it without the microcode.
If I'm understanding correctly, unless I do TUN/TAP, VDE or SLiRP (NAT) I
can't even connect to my emulated VAX via telnet or ftp?
Shaun McCloud, MCDST
On Thu, Dec 7, 2017 at 4:39 AM, Jordi Guillaumes Pons <
j...@jordi.guillaumes.name> wrote:
>
>
> On 7 Dec 2017, at 05:24, Shaun McCloud <shaun.thomas.mccl...@gmail.com>
> wrote:
>
> I have OpenVMS VAX 7.3 running in SimH on my Windows laptop, and I am
> trying to use networking using the WiFi on the laptop. However, I am
> getting an IP address of 0.0.0.0/8 in OpenVMS and obviously this is not
> the IP range I use at home (it is 172.16.6.0/24). Below is my current
> vax.ini so I don't have to type all the commands every time. Does anyone
> see anything with it that could cause the problem I'm seeing?
>
> (…)
>
>
> ; Attach Ethernet to a network interface
> set xq mac=00:00:01:00:00:01
> attach xq eth1
> ;
> ; Uncomment the line below to enable auto-boot
> dep bdr 0
> ;
>
>
> Hello Shaun,
>
> What version of simh are you using? With the current beta version (4.0)
> you don’t need to load the microcode (it’s builtin in the simulator). I
> encourage you to try the current development version.
>
> As for your specific problem, the only dubious thing I see in your INI
> file is the MAC address you are setting. I’d say that is not a valid
> Ethernet address. The current version can randomly generate a valid MAC
> address. I’ve attached the relevant HELP information at the end of this
> message.
>
> Please take into account that with your configuration you will NOT be able
> to “see" the simulated VAX from your laptop. To be able to establish
> communication between your host and the guest you should use TUN/TAP, VDE
> or SLiRP (NAT). In the case you go for SLiRP you will be limited to TCP/IP
> networking. Anyway, you can’t do DECNET over WiFi, so that’s probably OK
> with you.
>
>
> XQ Configuration Set commands Subtopic? mac
>
> MAC
> The MAC address of the controller is the Hardware MAC address which on
> real hardware is uniquely assigned by the factory. Each LAN device on
> a
> network must have unique MAC addresses for proper operation.
>
>
> sim> SET XQ MAC=<mac-address>
>
>
> A Valid MAC address is comprised of 6 pairs of hex digits delimited by
> dashes, colons or period characters.
>
>
> The default MAC address for the XQ device is set to a value in the
> range
> from 08-00-2B-00-00-00 thru 08-00-2B-FF-FF-FF.
>
>
> The SET MAC command must be done before the XQ device is attached to a
> network.
>
> Additional information available:
>
> Generated_MAC
>
>
> XQ Configuration Set commands MAC Subtopic? generated
>
> Generated MAC
> Support exists to provide a way to dynamically generate relatively
> unique MAC addresses and to provide a way to save generated addresses
> for subsequent reuse in later simulator invocations.
>
>
> sim> SET XQ MAC=AA:BB:CC:DD:EE:FF{/bits}{>filespec}
>
>
> where:
> 1. All of the AA:BB:CC:DD:EE:FF values must be hex digits
> 2. bits is the number of bits which are to be taken from the
> supplied MAC aa:bb:cc:dd:ee:ff with legal values from 16
> to 48 and a default of 48 bits.
> 3. filespec specifies a file which contains the MAC address
> to be used and if it doesn't exist an appropriate generated
> address will be stored in this file and a subsequent SET MAC
> invocation specifying the same file will use the value stored
> in the file rather than generating a new MAC.
>
>
>
_______________________________________________
Simh mailing list
Simh@trailing-edge.com
http://mailman.trailing-edge.com/mailman/listinfo/simh
