Using Miami (and probably Genesis) with WinUAE.

Programs needed:
WinUAE
AmigaOS
Miami (or Genesis, or AmiTCP, etc)
WinPCap (Installs on Windows side)


Just writing this because I had some trouble setting it up and had a little trouble finding information on how to get it all running.

I also ran into a couple different problems that other might run into such as using a wireless adapter on my PC while also having an Ethernet port available but not in use (this causes problems), and figuring how to get my router to give my one wireless card 2 different IP address at the same time. Something I didn't even know you could do and caused some grief.

First, you need to install WinUAE and get an AmigaOS install setup with a copy of Miami (or Genesis which again I haven't tested).

The other program you need to install on the Windows side is a little program called WinPCap.
It can be downloaded from http://www.winpcap.org/install/default.htm
This is a small program and doesn’t require any configuration. I assume it just runs in the background as a service.

So now when you run WinUAE in "Misc" settings tab you want to uncheck bsdsocket.library emulation and put a check mark by uaenet.device instead.

Now, uaenet.device is not a real file. There is nothing to put in the /devs folder so don't go searching for anything like I did. Basically it is sort of a virtual device that is in memory.

Now your going to boot into Workbench. Run MiamiInit, and choose "other SANA-II driver" when prompted. The next box will ask you for the device name. Here you will simply type in uaenet.device the device number is 0 should already be filled in.

It should start finding your settings and you can configure Miami as you normally would.


Ok, now problems that I ran into.

1st problem I ran into. When I would put in uaenet.device. It acted like it couldn’t find uaenet.device. So this is where I was certain there must be some file I need to put into /devs folder. Turns out I have 2 network adapters. I have an Ethernet port that is not connected and I have WiFi adapter which I use to connect to my router. WinUAE/WinPCap/uaenet.device automatically made my Ethernet adapter my uaenet.device. So when I was going into Miami and typing it in that is why it was finding no settings, because no cable was plugged in. Easy enough fix, I just disabled the Ethernet by going into the Network settings in the Control Panel and Right Clicking to disable it. Now I just had my Wireless enabled. uaenet.device now went straight to my wireless. Worked great.

2nd problem is that when I connect with Miami my router gives me my IP, great, it's 192.168.1.100. Ok, I switch back over to Windows and now Windows has no internet connectivity. So I reset the connection on the Windows adapter in the network settings and Windows has internet, ip 192.168.1.100, ok great. Go back to the Amiga side and Miami is disconnected. Connect, and now Windows is disconnected. So Windows and the Amiga could not have an internet connection at the same time

So there are probably a couple solutions to this. One solution would be to use 2 different adapters, so I could use the Ethernet adapter just for the Amiga and use my Wifi just for the PC. That's an option, but I use the Wifi so I don't have to run a cable. I guess I could try running 2 wifi cards, but I don't know how well that would work.

2nd option is using my one Wifi card ( one MAC address) and getting the router to assign it 2 different IP addresses at the same time. This is the option I choose.

Here is how I did it. I set my Windows box to get a static IP address, in this case I picked 192.168.1.105.

Then set Miami to just use DHCP like normal. It connected and the router gave it the same old 192.168.1.100.

Now both the PC and the Amiga are both connected to the internet at the same time, but the router is giving them 2 different IPs.

(Note: I first tried to set up Miami to be static, but could figure it out )


So now I'm running Miami instead of using bsdsocket.library emulation. So I'll have to do some tests, but first thing I noticed, and didn't expect at all, is using Miami transfer speed seemed much faster. I always had slower transfer speed than I thought I should have when using bsdsocket.library, but I'll have to test that and it really could be any number of reasons.

Main advantages of course are testing using a real Miami install or real Amiga stack. Also, running several applications that weren't compatible with bsdsocket.library such as Webservers.

Have fun!

_________________
A3000D (16mhz, 2MB Chip, 4MB Fast, SCSI (300+MB), SuperGen Genlock, Kick 3.1)
---------------------------------------------------------------------------
Back in my day, we didn't have water. We only had Oxygen & Hydrogen, & we'd just shove 'em together

@AmigaHeretic

Quote:

I guess I could try running 2 wifi cards, but I don't know how well that would work.

Risk for interference between the cards.


What about the mac-addresses?
How did those look in the first place?
(from the router point of view? (2 identical mac-addresses?) )
What I did with MOL on my A1, so both OSX and Linux could access a single network card, was to set up dhcp-server on Linux-side, with network 192.168.1.x, while the regular Lan was 192.168.0.x.
The OSX was on 192.168.1.x network, and Linux routed it to the regular 192.168.0.x Lan, and all outgoing/incoming traffic was routed by the dhcp-server on the Linux side to and from the regular router.

_________________
Site admins are people too..pooff!

@tomazkid

Quote:

What about the mac-addresses? How did those look in the first place? (from the router point of view? (2 identical mac-addresses?) )

Yeah, from the routers point of view it is giving an IP of 192.168.1.100 and 192.168.1.105 to the same MAC address. From what I can tell the 192.168.1.100 is the only one the routers DHCP leases. Which is where the problem was in the first place.

So when the PC was connected the router's DHCP gave the Wifi 192.168.1.100 based on it's MAC, but when Miami came along and contacted the router with the same Wifi it of course sees the same MAC and knows it's leased 192.168.1.100. So the PC stack gets dropped and Miami got the address.

But strangely enough even though I make the IP static on the PC side, the DHCP in the router doesn't seem to notice the MAC is connected already (I guess because DHCP didn't assign it?) and now when DHCP gets a request (from Miami in this case) it just sends out the first available IP in the range set, which is 192.168.1.100

Might be interesting to try to see how many IPs I could get on one MAC I suppose. Run WinUAE again and set up Miami to get a static IP, say 192.168.1.104 or something. See if the router will give all 3 IPs to the same MAC address.


Works really good though. I kinda needed to set a static IP on the PC side anyway as I RDesktop into it from my laptop all the time and every once in a while I would lose 192.168.1.100 to the Wii or DS or something. So I'd have to figure out what my IP was to get in. Now it's set and I don't have to worry. (And it's just a tick box it's not like it's hard to set up I was just being lazy I suppose)

Quote:

What I did with MOL on my A1, so both OSX and Linux could access a single network card, was to set up dhcp-server on Linux-side, with network 192.168.1.x, while the regular Lan was 192.168.0.x. The OSX was on 192.168.1.x network, and Linux routed it to the regular 192.168.0.x Lan, and all outgoing/incoming traffic was routed by the dhcp-server on the Linux side to and from the regular router.

Yeah, when I fist realized the problem with the Amiga or PC not getting internet at the same time and stealing the 192.168.1.100 back and forth I thought I was going to have to do something like what you're talking about if I wanted to use uaenet.device ( other than trying two network devices in the PC )

But the router seems to have no problems at all. I mean DHCP is not smart enough to know you want 2 address to one MAC, but the router itself I guess will "route" what ever IP's you want wherever you want them to go I suppose.

_________________
A3000D (16mhz, 2MB Chip, 4MB Fast, SCSI (300+MB), SuperGen Genlock, Kick 3.1)
---------------------------------------------------------------------------
Back in my day, we didn't have water. We only had Oxygen & Hydrogen, & we'd just shove 'em together

@AmigaHeretic

I´ve been using uaenet.device since Tony fixed the bug, it works great here with Miami and Genesis too

@AmigaHeretic

Regarding the first problem you had with multiple network adapters, I found that each adapter on my computer has a unique MAC address. You can change the unit number for the uaenet.device configuration in Miami. Then click on the "SANA-II parameters..." button followed by the "Query device" button. Do that until the MAC address shown in the query device window matches the same MAC address of the real network adapter on your computer that you want to use. Finally, just set a static IP address in Miami along with other things that might be needed like subnet, gateway address and DNS servers, and all is well. No need to disable any adapter that I'm not using.

Thanks for the help!

Last edited by SilvrDrgn on 28-Nov-2008 at 11:53 PM.

_________________
Michael

@SilvrDrgn

Quote:

SilvrDrgn wrote: @AmigaHeretic Regarding the first problem you had with multiple network adapters, I found that each adapter on my computer has a unique MAC address. You can change the unit number for the uaenet.device configuration in Miami. Then click on the "SANA-II parameters..." button followed by the "Query device" button. Do that until the MAC address shown in the query device window matches the same MAC address of the real network adapter on your computer that you want to use. Finally, just set a static IP address in Miami along with other things that might be needed like subnet, gateway address and DNS servers, and all is well. No need to disable any adapter that I'm not using. Thanks for the help!

Yeah, thanks for adding that to the thread. I did finally figure that out later after "reading" some directions, but left the ethernet disabled for now anyway as I don't use it. Hit myself for not thinking I could just type unit "1" for the next device. Oh well!!

Yeah, I'll have to try using a static IP in Miami again. It 'should' be simple and I think I entered subnet, DNS, etc in correctly, but no go. I'm sure it's just something small I missed.

So sounds like you got the webserver going in WinUAE 'till the A4000 is brought back to life?

_________________
A3000D (16mhz, 2MB Chip, 4MB Fast, SCSI (300+MB), SuperGen Genlock, Kick 3.1)
---------------------------------------------------------------------------
Back in my day, we didn't have water. We only had Oxygen & Hydrogen, & we'd just shove 'em together