Networking RPCEmu 0.9.1 + RISC OS 4.39 (Win 10)

I’m trying to setup networking on RPCEmu 0.9.1 with RISC OS 4.39.
My PC is running Windows 10 Professional x64 build 1903.

This is a clean setup of RPCEmu, the !Boot sequence I used is from here – http://www.riscos.com/ftp_space/439/files/439boot.zip

I followed the networking guide on the RPCEmu site, however in RISC OS when checking to see if the interface has been created, with ‘ifconfig -a’ I get the the following message;

‘IfConfig: ioctl (SIOCGIFFLAGS): No such interface’

I get the same result using both the Interpreter and Recompiler version of RPCEmu.

Any help would be greatly appreciated.

I followed the networking guide on the RPCEmu site, however in RISC OS when checking to see if the interface has been created, with ‘ifconfig -a’ I get the the following message;

I was getting a non-functional RO side on RO5.27 until I did a bit of cleaning.
The RPCEmu networking page here says “From version 0.9.1 of RPCEmu the following steps are no longer required”

What it doesn’t say is that having anything other than the single EtherRPCEm file in !Boot.Resources.Configure.!InetSetup.AutoSense seems to produce a non-working setup on the RO side.
Or at least that was my experience.

I can’t get the Win7 bridging to work properly¹, but I’m making progress (very slowly²) on getting the whole thing working with a RO5.27 build.

¹ Given that the machine in question is an old work machine and has remnants of an AnyConnect VPN install the problem may simply be that.

² Apparently household projects come first at home

Thank you!
I’ll give that a try later tonight.

I can’t get the Win7 bridging to work properly

I never had any problem to make it. But only on wired connection.
To be honest, I don’t think it can work on WiFi.

We really need user mode networking.

How can we distribute a ROS app under Windows if we’re not sure that the user will be able to connect it to Internet?

No joy with the network setup on RISC OS 4.39, there was another file in the folder that Steve mentioned, called EtherS.
I moved this file elsewhere, but I still get the same error.

I’ll give RISC OS 4.02 a go, see if I get better or different results.

I presume the list of loaded modules shows EtherRPCEm loaded and active, so I have to wonder whether Win10 is restricting the permissions on attaching to the “rpcemu” interface to admin accounts.

I wonder if starting the emulator as administrator would change things (usual right-click with shift mystic gestures for one time and appicon > properties > advanced for permanence)

Well, no help to you but I seem to have the bridge through from RO 5.27 to Windows 7 after setting the wireless interface to “disable upon wired connect”
Somewhere along the line both interfaces ended up with the same metric ¹ – I think the upgraded wireless speed on the newer router the other year did the change to bring them in the same band. Doh!

Anyway, working basics, now I wonder if I can plug the wired interface into a wired-wireless bridge device to get a working setup in wireless only locations?

Edit: BTW. Thanks to David Feugey for the comment “I don’t think it can work on WiFi.” which caused me to look at what the wireless NIC was doing at the time and not traffic that shouldn’t have been passing that way.

¹ I normally set a notably different values for wired and wireless or set the wireless to disable itself and I’d got a situation where neither was true and traffic was alternating on egress/ingress path. Seen that a lot at work and then people use the effect as evidence that “wireless is faster”

I have found that by removing the ‘EtherS’ file from the AutoSense folder, networking does indeed work!
However running the command ‘ifconfig -a’ still says there is no such interface….

Broke my build again. Back to no response from the bridged interfaces from the RO side.

Networking stopped for me today too, seems it’s a tad temperamental!

By way of an experiment – a TP-Link WR802N in client mode plugged in to the ethernet port on the laptop, bridge the rpcemu tap interface and the wired network interface…
Set the bridge IP to the next IP on from the IP set in RO5,
Subnet mask as appropriate,
Set the DNS on the bridge IP to 8.8.8.8.
Fire up RO,
Fire up Netsurf,
Browse to and login to riscosopen and here we are.
RPCEmu wirelessly¹ connected to the internet.

Wonder whether this is stable?
Test for a few days methinks.
The high fan state suggests something is making RO do a fair bit of work and hence working RPCEmu and the hardware work a fair bit.

¹ Because I can and so I can sit away from the computer room.

I gave up on networking with RPCEmu under Windows, it seems totally random, working one day, then not the next.

Particularly galling considering how seamless VirtualRPC is in that regard.

Somewhat off-topic, I have been struggling in vain for weeks to set up an internet connection on RPCEmu 0.9.1 running RO5 on a Win7 laptop: I have now succeeded, and the connection has survived several days’ usage and multiple reboots of emulator and host machine, so (crossing fingers) appears to be stable. The key step, on the Windows side, was to update the settings in Control Panel-System and Security-Windows Firewall to allow RPCEmu-Recompiler to bypass the firewall (click on ‘Change Settings’ in ‘Allow programs to communicate through Windows Firewall’ and browse for RPCEmu’s recompiler/interpreter, depending which is in use).
[EDIT] Hope this helps.