IP address and Winuae
 

Dunno about WinUAE but on Workbench you can use commands like:
http://eab.abime.net/showthread.php?...03#post1592703

@mfilos

Thanks for the reply.

I tried "GetExtIP" with the 68k and indeed the IP address is the correct one.
I guess it's due to bsdsocket.library selected with WinUAE

I could do the same with the 4.1FE it's not hard to do it just rename the files and enable the bsdsocket.library in WinUAE.
But unfortunately it leads to connection blocking very often.

((The one in "Odyssey" Browser with My-Ip is also corrected.

But I don't know how to show it to 4.1FE
because it shows me only the emulated ethernet card.))

I took some small steps

but i can't export the DISPLAY

at least for example with "Firefox"
it's the first time I've done it through WinUAE

so i probably have to change method.
and maybe even the program access program

And all virtualized with VMWare and WinUAE

Suggestions ?

Thanks for any help :-)

If you type "who" at the ubuntu shell prompt, it will tell you the IP address of the pc initiating the connection.

Simple!

@SpaceAce
Hi,
Thank you,
Now I try :-)

here a small test with "FFplay" and "Gedit"

but without exporting the display

https://youtu.be/GEBWZTPnSXk

@SpaceAce
I tried the "who" command
but it gives me the VMWare network adapter "ethernet"

it is not the one of WinUAE

although it seems strange i checked with "Ipconfig" in windows and it's the one from VMWare.

Can you possibly give me an example if you can of the command:
"export DISPLAY" ?

if not that there is probably something to configure in AmiCygnix that I still don't understand.

Of course I have read various guides but I can not grasp the concept.

I wanted to try I also installed to try

"xrdp" which should be fine on "ethernet" networks

but until now I still haven't found a solution.

Thank you.

The IP is correct. What else do you expect?

If you use bsdsocket emulation WinUAE runs as an application on the host system and shares the host's IP address.

If you use SLIRP emulation you always get 10.0.2.15, but this addresss cannot be reached because it is behind a virtual NAT router. In order to access it you would have to open ports in the router. Some standard ports like http and ftp can be opened from the GUI. Other ports can only be opened by editing the config file.

These opened ports appear as listeners on the host, so the IP address again is that of the host.

@thomas
Hi,

so the problem is the ip address of the amiga as you are confirming me.
And that's what I thought from the start.

Thank you for your suggestion.

If you have any other recommendations I greatly appreciate them.

I forget the exact steps that I took, but I set up a virtual NIC and switch using the hypervisor functionality in Windows, and I have WinUAE configured to use that virtual NIC directly along with Roadshow to provide the networking capabilities inside the emulator. No bsdsocket.library emulation.

You need to not only select the appropriate virtual NIC (it'll be "Network adapter 'Hyper-V Virtual Ethernet Adapter #x' on local host" or something similar) but also set an explicit MAC address for your emulated network adapter. And you need to have a network stack installed in your Amiga environment that can use the adapter you've configured.

When this is all correctly set up, your emulated Amiga appears on your local network like any other (physical) device, as your physical NIC gets treated by the Windows hypervisor platform as a switch, and Windows itself getting its own virtual NIC that like the one for WinUAE uses that virtual Hyper-V switch.

The usual *nix syntax for setting the DISPLAY variable is

So, for an example:

I hope that helps.

@All

Thanks everyone for the help,
Now the machines are configured correctly
(linux-amiga)
the IP problem remains because if I export DISPLAY on the amiga network, for example "FFplay" tries to connect for a few seconds but then fails and switches to the output again in the VMWare window (linux) automatically

the command to see the MAC of the virtual networks in "Windows" is:
ipconfig /all

now I have to see if these MAC, for example I also use "VirtualBox" are somehow usable by WinUAE.

any help is welcome.

I don't have an answer for your problem, but check this out.

The more testers, the faster it will run perfectly.

https://eab.abime.net/showthread.php?t=75062&page=29

@Maijestro

Qemu for Sam460ex is an interesting project.
But it proceeds very slowly and unfortunately more than opening windows and using some games it doesn't allow anything else.

I have used Qemu since version 3.1 and apart from the improvements on the code written in practice it has remained the same.

If you try to watch a video you will understand the difference between the speed and 1-fps
it is practically motionless. :-)

I also thought about using Qemu directly from the AmigaOS shell with AmiCygnix :-)

My current idea is to bundle many programs under WinUAE to use 4.1, but this takes time.
And I basically do the tests myself. (few people are interested).

Qemu Remains an interesting project but unfortunately still behind for graphics card support.

But I am convinced that if we mentally deviate a little from the idea of pure amigaOS emulation then we can do a lot.

Even with a specially created fork.

But it is invaluable to report bugs to Toni and he promptly fixes them.
This is true passion and support for us users and Toni, if he can do something, he does it.
Toni is a great person, he imagines the amount of requests that are made continuously.
And he promptly sorts things out.
Too bad he doesn't want to go further to make hacks dedicated to 4.1.

Instead, only the idea of ports written for AmigaOS is carried forward
This is logical for those who have a real car for the 4.1FE.

What I can't do is only due to the fact that I use an emulation.
If I had a Real Amiga I would only have to install and configure the applications.
I wouldn't run into all the problems there are related to emulation.

AmigaOS is a nice system but the machines sell for very high prices.
And we're talking about 2,000 euros to play Doom 3 (maybe).

But it's nice to see that you are passionate about 4.1 :-)


((( Before the basic amiga broke I was getting a PowerPC at that time.

But then I opted for the "playstation 1"

Having played the first Metal Gear Solid in Italian
And to "Final Doom" the version for Playstation 1
It has brought me hours of wonderful fun.

At that point I made a comparison
Final Doom ate Alien Breed 3D The killing Ground completely in one bite.
Amazing I remember Final Doom as one of the best FPS gaming experiences :-)

Certainly remain personal tastes )))

Today, I made a system backup
so I can do the tests more calmly.

Exactly the MAC option in WinUAE

NetWork Adapter as used with "uaedevice"
or without "uaedevice" ? (OS4)

Also do I have to select any "Network" tab?
in WinUAE

or just set the MAC in NetWork Adapter ?
without network card

Also do I have to save the configuration of the MAC I want to use or can I start without saving the configuration with the MAC so it is recognized without saving the configuration ?

Thank you

I configured Hyper-V easily from its GUI
calling the adapter "UAE"

here the screenshots with the relative MAC put in WinUAE:

but it doesn't seem to work

OS4 keeps setting up the same connection over and over again
am i probably doing something wrong?

here instead a Tutorial in Italian for a more detailed configuration
which I still don't use.

https://www.ictpower.it/sistemi-oper...windows-10.htm

But does the WinUAE mask where it says MAC andress work with 4.1 ?

Maybe a suitable driver is missing?

What driver should I use ?

Thank you.

Make sure you have the appropriate adapter set as the "Network mode" setting of the adapter card in WinUAE settings (in your case, "Hyper-V Virtual Ethernet Adapter #2"). Both "Network mode" and "MAC" parameters need to be set for the adapter card.

If you continue having problems you might want to try using a different MAC address in the WinUAE settings, instead of the "physical" address of the Hyper-V adapter provided by ipconfig. I use a custom MAC address in my own configuration. If you take this route, I suggest that the first byte of it ends in 2, 6, A, or E -- this specifies a locally assigned, unicast MAC address (lsb of the first byte is 0, next least significant bit is 1). This should hopefully ensure that you don't come up with an address that conflicts with anything else in your local network.

@coldacid

Thanks for the reply, :)

I can't grasp the concept in WinUAE
choosing for example the "A2065" or "RTL8090" driver with WinUAE is manually setting the MAC .

What should happen ?

Because with "Ranger" the MAC of the A2065 or RTL8029 card
it doesn't change it has its own it's the MAC I enter in WinUAE it doesn't appear in the "Ranger" associated with the cards.
The MAC of my choice does not appear anywhere in WinUAE.

Also that "stack" I have to use the "ethernet" one I imagine by entering the DNS of the virtual Hyper-V card the NetMask etc.

Because I don't have any feedback from the WinUAE side that the "MAC" is associated with something.

An example would really help, if you have the time for it.

Thanks, if you don't succeed it doesn't matter.
I really appreciate your suggestions though :)

an additional question hyper-v allows me to choose between real ethernet and wifi usb adapter.
On the Host PC

Right now I'm using the USB wifi adapter

Do I have to use an ethernet cable for this to work?

@Toni
since you programmed it, how should I use the MAC?

Thank you. :)

I'll have to deep dive when I get home after work, but I'm also using XSurf-100 IIRC. I can't recall if I had to write the MAC somewhere in one of the config files for the network stack, too.

BTW, I didn't use the Hyper-V Manager to set up the virtual network adapter. I remember having to hunt through the docs for the relevant PowerShell commands and setting it up that way. The Hyper-V Manager is actually fairly limited in what you can do compared to the PS commands.


UPDATE: No MAC in the stack config files inside Amiga. Here's the relevant lines from my UAE config:


Looks like this in WinUAE Properties:

https://i.imgur.com/C9caXtU.png

Note also that I have bsdsocket.library and uaenet.device OFF; with the builtin bsdsocket.library you simply can't get WinUAE to show up on the network like any other virtual machine, and uaenet.device has been iffy for me. You'll need to install a proper network stack inside your Amiga environment if it doesn't already have one (I know AOS4.x does, but for classic Amiga OS I suggest Roadshow).

Again, note that the MAC address configured in WinUAE does not match the physical address of the virtual adapter.

https://i.imgur.com/TFZBizy.png

I'm not sure if NPCAP is actually necessary but I think that it might be for this to work with WinUAE. I do see its implementation of wpcap.dll loaded by the WinUAE process, but it might be brought in indirectly rather than something WinUAE looks to load (I bet it is an indirect dependency, but Toni would have to clarify that).

https://i.imgur.com/qzSQ5LS.png

Somehow, all this magically works. :spin

MAC setting overrides selected NIC's MAC address when Amiga side queries emulated card's MAC address.

Manual MAC address is useful if you only have single physical NIC. You can't (obviously) use original MAC because it would conflict with host's networking. (two operating systems would use same MAC simultaneously). But if you select manual MAC (that does not exist in network), it just works. Host OS uses original MAC, emulated Amiga uses manually configured MAC, even if both use same physical NIC.