Avanti/FreeAXP WinPcap 4.1.3 Conflict

Hi,

Win10Pcap seems working with FreeAXP (without real networking test!).
SimH doesn't work. FATAL. Bad memory block.

github.com/simh/simh/issues/341

I'm testing now nmap-7.60 with NCap 0.93. FreeAXP and SimH VAX seem their adapters. Network test is in progress ... (TCP/IP configuration under OpenVMS 7.3 and 8.4)

TIA,

Hi,

The networking doesn't working!

The virtualized Win10 (as host for VAX and AXP) is reachable from both VMS (VAX - 7.3 and AXP - 8.4)
VAX and AXP can communicate to each other.

Traffic from real network doesn't come back. On the target machine I can see ARP requests and no answer arrives back to VMS machines. I don't know why.

VirtualBox (Win10Pro) can communicate both direction.

Today I try to test a much more simple situation. Only FreeAXP its MSI PCAP driver and SimH alone with NCAP 0.93 (or the newer 0.94). I think the problem is with NCAP.
A simplier test would be go back to the real Win10Pro with NCAP + SimH/FreeAXP.
I don't know what is the real problem because the operation is better than WinPCAP 4.1.x or Win10PCAP.

TIA,

Hi,

Oh I forgot to mention: DHCP is working! (both SimH and FreeAXP)
I got good IP address from the DHCP server which is situated on the real (wired) network!
When I got the IP I can't communicate (ping) the DHCP server. Strange...

TCPIP> sh arp
2: U 24 192.168.52.30 #0
TCPIP> sh interface/full
Interface: LO0
IP_Addr: 127.0.0.1 NETWRK: 255.0.0.0 BRDCST:
MTU: 4096
Flags: UP LOOP NOARP MCAST SMPX
RECEIVE SEND
Packets 51 51
Errors 0 0
Collisions: 0

Interface: WE0
IP_Addr: 192.168.52.27 NETWRK: 255.255.255.0 BRDCST: 192.168.52.255
Ethernet_Addr: 0A-00-27-07-6E-77 MTU: 1500
Flags: UP BRDCST NOTRL RUN MCAST SMPX
RECEIVE SEND
Packets 594 9
Errors 0 0
Collisions: 0

.52.30 is the address of DHCP server.
OpenVMS 8.4, switched off NCAP drivers at LAN card properties dialog but not uninstalled. FreeAXP MSI driver installed, Win10 wasn't restarted.
Something very funny thing happened... <img src='../images/smiley/shock.gif' alt='smiley'>

Without NCAP (uninstalled and the machine was rebooted) the situation is the same: DHCP OK and nothing more communication. On the Linux side there is answer for the VMS's ARP request but it doesn't reach Win10(?)/OpenVMS 8.4.
I think the problem between Linux and Win.

TIA,

Hi,

I tested again networking. The result was better than last time.

I used: buit in NCAP driver, NPCAP, Win10Pcap.
The OpenVMS was V7.1-1H2. Network protocol: LAT.
Host OS: Ubuntu Linux 16.04.3 64 bit up-to-date.
Virtual system: VirtualBOX 5.1.28 r117968 in bridged mode. Bridge interface: br0. Emulated network card: Intel PRO/1000 MT Desktop
Guest OS in VirtualBOX: Win10 Pro 64 bit. Network is working!
FreeAXP 3.0.0.164. In pci11 there is a DE435 NIC for OpenVMS. EWA0 is online.

I tried to connect from an other Linux with LAT (llogin &lt;service_name&gt<img src='../images/smiley/wink.gif' alt='smiley'>.
llogin -d shows the service and available after OpenVMS starts.

When I try to connect to the service it becomes UNAVAILABLE! So the connection was unsuccessfull. In some seconds later the service becames AVAILABLE again checking with llogin -d command.

I think the VMS-&gt;real network works and the opposite direction doesn't.

The situation is the same with the other two PCAP driver (NPCAP and WIn10Pcap).

Using an other OpenVMS version (8.4) and TCPIP with VirtualBOX NAT networking, connection is better but it is an absolutelly different networking method, for example there isn't LAT to my real network.

TIA,

Hi,

Will be solved this WinPcap anomaly with FreeAXP sometime?

TIA,
Ruzsi

Yes, no release date yet available.