TCP/IP Configuration Blues

[vicchi]

The story so far ...

Got OpenVMS v8.4-2L1 installed, configured, licensed and running under VSI's community PAK. And there was much rejoicing. Seriously, this is an awesome piece of work. Being back at a DCL command prompt is like being reunited with a long lost friend.

TCP/IP configuration, less so. Inception-a-like, my current setup looks like this.

• Physical machine: MacBook Pro running Big Sur 11.3.1
• VirtualBox 6.1.22 running an Ubuntu 20.04 guest with 1024 MB memory, 4 CPUs and a 20 GB HDD
• Two network interfaces:

1. NAT - assigned 10.0.2.15 on enp0s3
2. Bridged (to my Mac's USB-C ethernet adaptor) - assigned 172.20.0.249 by my LAN's DHCP server on enp0s8

• axpbox v1.0 at commit hash 85834441a54d4439907e185a6d53b06335dcd596
• Network config in es40.cfg defined as

pci0.4 = dec21143 
{ 
        adapter = "enp0s3";
        mac = "08-00-DE-AD-BE-EF";
}

TCP/IP allegedly configured in VMS as follows:

$ tcpip show int  
                                                           Packets
Interface   IP_Addr         Network mask          Receive          Send     MTU
 
 LO0        127.0.0.1       255.0.0.0                   8             8    4096
 WE0        10.0.2.25       255.255.255.0               0             7    1500

$ tcpip show route
  
                             DYNAMIC
  
Type           Destination                           Gateway
  
AN    0.0.0.0                               10.0.2.2
AN    10.0.2.0/24                           10.0.2.25
AH    10.0.2.25                             10.0.2.25
AH    127.0.0.1                             127.0.0.1

I'm missing something glaringly obvious I know, but even with port forwarding set up. I can't ping from inside VMS to any external IP nor ping "into" VMS from the Ubuntu guest.

What am I missing?

[lenticularis39]

Communication between the AXPbox VM and host will never work due to how libpcap works on Linux; the NAT gateway (10.0.2.2) should be accessible, though (and the rest of the network through it). Can you at least ping 10.0.2.2?

[vicchi]

@lenticularis39 (scratches head and drinks more coffee) ... initially I couldn't ping 10.0.2.2 but decided to start with a clean slate, so I shutdown VMS cleanly, rebooted the Ubuntu VM and started up axpbox and the VMS instance and ... WTF?

That seemed to kick start things. I can now ping 10.0.2.2, I can ping the VMS instance itself (which I should be able to do but there's no harm in trying) on 10.0.2.25 but can't ping the NAT interface on the Ubuntu VM on 10.0.2.15 (scratches head some more).

I can route out onto the public net, as pinging 1.1.1.1 works fine and DNS is running OK on VMS as well as I can ping by FQDN ...

$ tcpip ping /num=5 github.com
PING github.com (140.82.121.3): 56 data bytes
64 bytes from 140.82.121.3: icmp_seq=0 ttl=63 time=94 ms
64 bytes from 140.82.121.3: icmp_seq=1 ttl=63 time=81 ms
64 bytes from 140.82.121.3: icmp_seq=2 ttl=63 time=96 ms
64 bytes from 140.82.121.3: icmp_seq=3 ttl=63 time=83 ms
64 bytes from 140.82.121.3: icmp_seq=4 ttl=63 time=99 ms


----github.com PING Statistics----
5 packets transmitted, 5 packets received, 0% packet loss
round-trip (ms)  min/avg/max = 81/90/99 ms

So I (still) can't access anything on the 10.0.2.0 NAT network and I can't route into VMS either on ports 22 or 23. I have port forwarding setup in VirtualBox.

Telnetting to 127.0.0.1:2323 from the Ubuntu VM yields connection refused and to 10.0.2.25 yields no route to host.

But progress nonetheless ...