Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Network device emulation not working (including uaenet.device) #1487

Open
giantclambake opened this issue Oct 19, 2024 · 5 comments
Open

Network device emulation not working (including uaenet.device) #1487

giantclambake opened this issue Oct 19, 2024 · 5 comments
Assignees

Comments

@giantclambake
Copy link

See #1475 for reference.

Using the Roadshow TCP stack, none of the provided drivers match emulated network cards ;

ex

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.

ex2

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

@midwan
Copy link
Collaborator

midwan commented Oct 19, 2024

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.

@midwan midwan self-assigned this Oct 19, 2024
@giantclambake
Copy link
Author

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 ;)

@midwan midwan added the bug label Oct 24, 2024
@SonnyJim
Copy link

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'

@giantclambake
Copy link
Author

Yeah, this is still currently broken ~ midwan's spun off a separate branch to work on the issues here =)

@midwan
Copy link
Collaborator

midwan commented Jan 15, 2025

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants