[HECnet] SIMH + OpenVMS 7.3 + Multinet 5.4
Mark Pizzolato
Mark at infocomm.com
Fri May 1 05:33:11 PDT 2020
On Friday, May 1, 2020 at 5:17 AM, Serguei wrote:
> I have problem with multinet configuration wifi connection adapter on SIMH +
> OpenVMS :
>
> on windows machine
>
> ipconfig/all
>
>
> Адаптер беспроводной локальной сети Подключение по локальной сети*
> 9:
>
> Состояние среды. . . . . . . . : Среда передачи недоступна.
> DNS-суффикс подключения . . . . . :
> Описание. . . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter
> Физический адрес. . . . . . . . . : F4-6D-04-5D-XX-XX
> DHCP включен. . . . . . . . . . . : Да
> Автонастройка включена. . . . . . : Да
>
> Адаптер беспроводной локальной сети Подключение по локальной сети*
> 10:
>
> Состояние среды. . . . . . . . : Среда передачи недоступна.
> DNS-суффикс подключения . . . . . :
> Описание. . . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter #2
> Физический адрес. . . . . . . . . : F4-6D-04-5D-XX-XX
> DHCP включен. . . . . . . . . . . : Да
> Автонастройка включена. . . . . . : Да
>
> Адаптер беспроводной локальной сети Беспроводная сеть 2:
>
> DNS-суффикс подключения . . . . . :
> Описание. . . . . . . . . . . . . : ASUS USB-N53 802.11a/b/g/n Network Adapter
> Физический адрес. . . . . . . . . : F4-6D-04-5D-XX-XX
>
> IPv4-адрес. . . . . . . . . . . . : 192.168.1.72(Основной)
> Маска подсети . . . . . . . . . . : 255.255.255.0
>
> simh> sim> show xq eth
> ETH devices:
> eth0 \Device\NPF_{FADA2DEF-CA7F-4ED2-B069-4AEAE1F41D93}
> (╧юфъы■ўхэшх яю ыюъры№эющ ёхЄш* 10)
> eth1 \Device\NPF_{CEF74F36-25AA-40AC-806D-2B1955F2AD1F}
> (┴хёяЁютюфэр ёхЄ№ 2)
> eth2 \Device\NPF_{EBA88B87-F500-4424-B6F4-A53E9963AA46}
> (╧юфъы■ўхэшх яю ыюъры№эющ ёхЄш* 9)
> eth3 nat:{optional-nat-parameters} (Integrated NAT (SLiRP) support)
> eth4 udp:sourceport:remotehost:remoteport (Integrated UDP bridge
> support)
>
> so i take MAC from ASUS USB-N53 802.11a/b/g/n Network Adapter and put it
> into vax.ini
>
> SET XQ ENABLED
> SET XQ MAC=F4-6D-04-5D-XX-XX
> ATTACH XQ eth2
>
> inside multinet i see
>
> $ multinet config
> MultiNet Network Configuration Utility V5.4(109) [Reading in MAXIMUM
> configuration from MULTINET:MULTINET.EXE] [Reading in configuration from
> MULTINET:NETWORK_DEVICES.CONFIGURATION]
> NET-CONFIG>show
> Interface Adapter CSR Address Flags/Vector
> --------- ------- ----------- ------------
> se0 (Shared VMS Ethernet/FDDI) -NONE- -NONE- -NONE-
> [TCP/IP: 192.168.1.72, IP-SubNet: 255.255.255.0,
> IP-Broadcast: 192.168.1.255]
> [VMS Device: XQA0, Link Level: Ethernet ]
>
>
> Official Host Name: omega
> Default IP Route: 192.168.1.254
> Timezone: GMT
> Timezone Rules: GMT
> Load UCX $QIO driver: TRUE
> Load PWIP (Pathworks) driver: TRUE
>
>
> $ multinet show/route
> MultiNet IP Routing tables at 1-MAY-2020 15:15:10.24:
> Destination Gateway Flags Refcnt Use Interface MTU
> ------------------------------------
> ------------------------------------ ----- ------ -----
> --------- ----
> DEFAULT-GATEWAY 192.168.1.254 U,G,S
> 0 0 se0 1500
> LOCALHOST LOCALHOST U,H,Local 0
> 0 lo0 1536
> 192.168.1/24 192.168.1.72
> U 0 0 se0 1500 MultiNet IPv6 Routing tables at 1-
> MAY-2020 15:15:10.29:
> Destination Gateway Flags Refcnt Use Interface MTU
> ------------------------------------
> ------------------------------------ ----- ------ -----
> --------- ----
> ::0001 ::0001 U,H,Local 0
> 0 lo0 1536
>
> multinet ping 192.168.1.72 is ok
>
> multinet ping 192.168.1.254 (gateway) says:
>
> MULTINET_PING: wrote 64 chars to 192.168.1.254: %MULTINET-F-
> EHOSTDOWN, Host is down
>
> what i am doing wrong? wrong MAC? wrong eth ? wrong IP?
You don't mention what you're using for pcap on your system.
Is it WinPcap? Is it Npcap? If, Npcap is it the latest version?
The selection of your MAC address may or may not matter
depending on if you've got either DECnet or VMS Clustering
configured on the VAX system.
Beyond this, it also seems that you have possibly configured
MultiNet with the same IP address as your host system.
I recommend starting with a Wired network setup before
trying Wireless. Depending on what you're trying to do,
you may have success with the wireless setup if you use
NAT. If you use NAT, you should ALSO configure
MultiNet with a completely different network address
than the network being used by your WiFi network.
Good Luck,
- Mark
More information about the Hecnet-list
mailing list