amiberry
amiberry copied to clipboard
BlitterStudio
Network device emulation not working (including uaenet.device)
See #1475 for reference.
Using the Roadshow TCP stack, none of the provided drivers match emulated network cards ;
It does however identify the uaenet.device correctly, and provide the applicable driver file to which you can attach the tcp stack, but it doesn't work (see discussion above) as no packets flow.
AFAICT, the emulated ethernet device is not being built ; slirp is providing mac_addr, but all other network device functionality is missing, and thus Roadshow cannot find a qualifying device.
TIA
Only uaenet.device will be injected by Amiberry during runtime, for the other emulated hardware boards, you'll need the proper .device file from Roadshow or similar software.
However, the implementation probably needs more - pcap might be required to make use of uaenet.device, or other cards.
Of course, bsdsocket.library should work without any further requirements.
Yeah, if you enable A2065 in Amix, bootup stalls completely twiddling it's thumbs over net_if init.... unfortunately, the bsdsocket.library doesn't work in Amix ....but ofc Amix with A2065 enabled in WinUAE works ;)
Just to add I updated to 7, imported over my working WinUAE Amix setup and whilst it boots, I couldn't get the network to do anything. I suspect a lot of uaenet.device is not exactly 'platform independent'
Yeah, this is still currently broken ~ midwan's spun off a separate branch to work on the issues here =)
Yeah, this one requires a pcap implementation like the one on WinUAE, but for Linux/macOS.
That is some work that I haven't had time to look into yet, so I left this issue open for a future attempt at fixing it.
@giantclambake
Even though PCAP is not implemented yet, I just fixed an issue with the SLIRP implementation, which might affect this case as well.
Can you run a new test when you have a chance, to see if it's any better with the latest from master ?
Did a quick test myself, using the A2065 device driver from Aminet: https://aminet.net/driver/net/a2065v216a.lha
And it works, at least basic functionality like browsing a website.
Well... one can't use that device in amix (I don't think?), and amix still fails to load -- that said, output in the logfile has changed, so maybe there is a clue there .... (I'll attach it, disregard filesystem checks)....
@giantclambake I tested with NetBSD 9 and it seems to work, at least in the sense that I could open an SSH connection from there to another machine in my LAN, without problems. I used the A2065 network card with SLIRP network mode, and had to enable the DHCP client manually, to get an IP in the system. Otherwise, it worked as expected, after the fixes I mentioned above.
@midwan I'll restest in the next few days ~ bit hard atm, with the cyclone having hit, and our power going on/off like a yo-yo ;^/
Just one question ~ which SLIRP mode did you use?... SLIRP User mode NAT ..or.. SLIRP + Open ports ?
Thanks
@midwan I'll restest in the next few days ~ bit hard atm, with the cyclone having hit, and our power going on/off like a yo-yo ;^/
Just one question ~ which SLIRP mode did you use?... SLIRP User mode NAT ..or.. SLIRP + Open ports ?
Thanks
Either SLIRP mode should work - in NetBSD, I used the User mode NAT.
Decided to reinstall everything again + patch disk.
The network interface is detected, and can be configured, and seems to be able to ping self, however, using wireshark I see no packets coming from the guest emulation at all. I was looking at this thread for clues, but nothing seems to work as expected.
Decided to reinstall everything again + patch disk.
The network interface is detected, and can be configured, and seems to be able to ping self, however, using wireshark I see no packets coming from the guest emulation at all. I was looking at this thread for clues, but nothing seems to work as expected.
I have exactly the same problem with Raspbian :( No connection what so ever. bsdsocket.library works, but i need an ip address :)
I'm not entirely sure how it's all supposed to route (at a tcp/ip level) ~ as midwan said above, User mode NAT seemed to work wrt NetBSD, and I should try that in Amix (but I'm in no way hopeful ;). AFAIK some form of NAT has to take place (because) you've got the conundrum of the $HOST tcp/ip connection to the outside world...like, sure you could do eth0:0 eth0:1 and filter by mac_addr...but in theory the NAT routing should take care of this....I'll have to muck around a bit more....
Hoping midwan gets uaenet.device to work :) Then i should get an iP using a TCP/IP stack like AmiTCP or Miami :) Thought this should work out of the box, so bought a Raspberry Pi 5 to use as a Telnet BBS using Ami-Express within Amiberry.
Just pulled the latest git and compiled on my Linux box, gave it my Amix hardfile and working WinUAE config. Unsurprisingly still no network, although it boots and I can ping 127.0.0.1 / whatever address was assigned to the NIC, it can't ping anything outside of itself (ie can't ping host computer). Tried running SLIRP on the host PC and didn't seem to make a huge chunk of difference.
I've added some initial support for uaenet.device using libpcap (new dependency, you'll need to install that before building). The changes are in a separate branch, until they are tested. I didn't have time to do any proper tests so far, besides building and running, to ensure nothing crashes.
Feel free to test using that branch and provide any feedback.
Thank for working on this. Just tried it out, together with Roadshow:
It correctly enumerate all pcap devices, and Roadshow is configured with uaenet.device unit 2.
Finally had a chance to test and compare this with WinUAE.
Using the same Workbench installation in both, and the same emulator configuration (disable bsdsocket emulation, enable uaenet.device), I got it to work in the same way.
AddNetInterface reported the same thing, and got an IP correctly.
uaenet was configured with unit 0, which is the default.
I could then open IBrowse and get to Aminet as expected.
I still can't get uaenet.device to work. Neither using a unit that corresponds to my network device or unit 0. I don't know what SLIRP is or how to configure it in Linux, do you have any guides/information about this?
@dlundqvist I didn't have to use any SLIRP mode for this to work. Did you follow the same steps in WinUAE? I only did what I mentioned above, and it seemed to work with IBrowse.