WinUAE è NPCAP

[White]

@Toni
@All



Thanks for the latest version of WinUAE :-)


When I use this connection with WinUAE (os 4.1)

NPCAP with "RTL8029"

via "NetWorkMode"

is I choose "NetWorkAdapter" with driver "VmNet8-localhost" of VMWare
and I can get an external IP which works perfectly.

what kind of connection am i using

NAT ?

or else ?

Thank you

[Toni Wilen]

NPCap virtual NIC = direct, not NAT.

[Sani11]

From your setup, it sounds like you're using NAT (Network Address Translation). VMWare's VmNet8 by default implements NAT, allowing your guest OS (AmigaOS 4.1 in WinUAE) to share your host's IP. This is why you're able to get an external IP that works perfectly.

[White]

@Toni
@Sani11
I know the argument is probably not very consistent with WinUAE.

But I would like to ask from an IT point of view how this procedure works to make it work with WinUAE.

Even with a very simplified explanation, just to have a starting point to work from.

I would like to reproduce exactly this in qemu
I don't want to broaden the discussion on the differences between the two emulators.

I do this :
sudo ip tuntap add mode tap dev tap0
sudo ip addr add 172.18.1.1/24 dev tap0
sudo ip link set dev tap0 up

is I get an external IP with RTL8139 with static IP

then the part to start the network:
-netdev user,id=tap0 -device rtl8139,netdev=tap0

everything works the external ip is 172.18.1.1
no hiccups or lag.

i have other ways to do this but this is the simplest one for example.

the problem i cant get over is that if i try to ping
from Amiga to Linux box all packages are lost.

So it works fine with normal network with Amiga Browser, streaming etc.
but it seems that i can't communicate with the "host machine"

as was the case with WinUAE before I used NPCAP with vmnet8 from VMWare to use SSH with AmiCygnix which with WinUAE works fine.

basically to pass the ping from the Amiga to the host machine

What could I use according to your experience?

for example:
sudo sysctl net.ipv4.ip_forward=1
sudo iptables -t nat -A POSTROUTING -s 172.18.1.1 -j MASQUERADE

or again:

sudo iptables -A FORWARD -i tap -o tap0 -m state --state RELATED,ESTABLISHED -j ACCEPT

or do I have to specify the MAC of the emulated card ?

or something like:
hostfwd=tcp::8080-:22,hostfwd=tcp::8080-:80


to be able to ping the host machine

Thanks for any suggestions.

And if the question is out of place I apologize I understand. :-)

note:
Oh I forgot
With the AmigaOS shell I can access the Linux terminal
via AmiCygnix without problems.
So I'm able to use the Linux terminal via SSH through AmiCygnix.

What I need is for ping to work from Amiga to Linux

[Toni Wilen]

Previous answer sounds suspicious..

I meant from WinUAE point of view it is direct. It has direct access to Windows side NIC. NIC might be virtual and it might be NAT routed but WinUAE can't know it.

[White]

@Toni

I was doing more tests. (qemu)

Instead with WinUAE via NPCAP
the only driver provided by VMWare is the "vmnet8"
to be able to work like this (WinUAE)
for example "vmnet1" won't work to get an external ip.
So I assume there are differences between the two drivers that come with VMWare.
This is reported in the official VMWare documentation.
To have other features like "vmnet8" you have to rely on "VMware ESXi" to add other network drivers with the same features as "vmnet8".

Basically only "vmnet8" is enabled to work like that.
And can only be used one at a time with "VMWare Pro"
Only VMware "ESXi" gives the possibility to add more than one.

I thought WinUAE had some "special" enable in its programming to use NPCAP and lean on "vmnet8".

(( I assume NAT and DHCP while the rest are just "host only"
even the VirtualBox driver won't work for an external Ip (host only)

it is probably the DHCP that seems to be absent in my tap configuration ))

I hope I wrote right.


"vmnet8" uses NAT, the simplest networking method, from the host's "VMWare Virtual Ethernet Adapter for VMnet8" virtual network card, connected to the vmnet8 virtual switch, the other port of the virtual switch is connected to the virtual NAT server ( This is also a Vmware component), and one port is connected to the virtual DHCP server, and the other ports are connected to the virtual machine. The gateway of the virtual machine is the machine where the "VMWare Virtual Ethernet Adapter for VMnet8" network card is located. Nonsense, this must be yours Host machine. Similarly, you can also see with ipconfig that the default gateway of your virtual machine also points to your "VMWare Virtual Ethernet Adapter for VMnet8" virtual network card address. In contrast, it can be seen that the difference between the NAT networking mode and the Host-Only mode is whether there is an additional NAT service.

"vmnet1" presents as Host-Only network mode, which is used to establish an isolated network environment, where vmnet1 is also a virtual switch, one port of the switch is connected to your Host, and the other port is connected To the virtual DHCP server (actually a component of vmware), the remaining port is connected to the virtual machine. The virtual network card "VMWare Virtual Ethernet Adapter for VMnet1" serves as the gateway interface of the virtual machine and provides services for the virtual machine. After the virtual machine is started, if you use the ipconfig command, you will clearly see that your default gateway is pointing to the address of the "VMWare Virtual Ethernet Adapter for VMnet1" network card. (In fact, it does not provide routing. This is designed by VMware. It does some things besides providing routing—in fact, I don’t know what it does.) There is no routing provided here. The main manifestation is No NAT service is provided, so that virtual machines cannot access addresses outside the network segment specified in Host-Only mode.

[SpaceAce]

Why don't you create a "Bridged" VMnet adapter in the Virtual Network Editor and use that? The VM will look like any other machine on your subnet and have all the same IP characteristics as your subnet. Pinging other machines should work without any routing configs.

This is what mine looks like:

[White]

@SpaceAce

Sorry for the late reply.

Unfortunately the problem does not refer to WinUAE where the connection works without problems.
Using the "RTL 8039" driver
because using for example the "Ethernet" driver the external ip is not obtained. (os 4.1)
Using NPCAP with WinUAE.

It's not fair for me to talk about qemu in the WinUAE forum

But it's one of the few places where I can talk about AmigaOS
and eventually find a solution.

I was hoping for some helpful hints but clearly it's hard to find.
Because precisely not inherent to WinUAE.

In all the tests I have carried out it seems that even using an external IP the ping does not work.

I think it's a "Routing" problem of any virtual device I try to mount.

For example, if I do 10.0.2.15 with the classic wizard of 4.1
I get the working Ping and also the external connection.

But if I use an external IP always with "qemu" everything works but not the ping.

I thought Toni could help me but from how he explained to me he doesn't have a solution to this.

In summary it seems that using an external IP with qemu something does not work.

The problem I'm trying to solve is with "AmiCygnix"

Therefore:

qemu - external ip is opening "export DISPLAY" with "AmiCygnix"
it does not work.

Basically I'm running into the same problem I was running into with WinUAE before using NPCAP.

I can only open external DISPLAY on Linux
with:

export DISPLAY:0
is not with for example:
export DISPLAY=172.18.1.1:0.0

but the applications open on Linux is not inside AmiCygnix.

I also imported the same VMWare virtual machine that I use with Windows.

To test on Linux with VMWare PRO (Linux version)
where SSH is configured well for use with AmiCygnix
but it still doesn't work.

even using "vmnet8" linux version doesn't work.

example:
-netdev user,id=vmnet8 -device rtl8139,netdev=vmnet8

(( it works i get the external ip but not with export DISPLAY
so it's NPCAP that makes everything work. ))



I apologize to Toni for this post it was not my intention to extend the discussion.

It had seemed like a good idea to ask how NPCAP works
side WinUAE but unfortunately I have not found a solution.

But so far I haven't found anyone yet who has been able to get AmiCygnix working with qemu.

I was thinking "wineHQ 8.0.1"
is trying to use NPCAP through it but it's been years since I've used it anymore.

And I have no idea if it can work the same way NPCAP ?

Apologies again for the post.

[Greyspirit]

seem to recall that in vmware you had to enable promiscuous mode on virtual switch. Not sure if any required additional driver for nic itself in this configuration.