Broken Networking

How do you set up newtroking in RPCEmu and Ro5.20 so it actually WORKS?

I’d been following the instructions here –
http://www.marutan.net/rpcemu/manual/net-ro-bri.html (in respect of the Windows version.)

and when I attempted the ping test it couldn’t see the router across the bridge.

Please provide FULL instructions on how to connect RO 5.20 to a router, because the instructions given don’t actually appear to work right now.

Please provide FULL instructions on how to connect RO 5.20 to a router, because the instructions given don’t actually appear to work right now.

Working on it. What version of OS? Windows XP, Windows 7?
Mac OS X is one that Mike Fowler has done – on extended testing I believe.

Unfortunately the paid¹ work² is taking more of my time than it ought to so the network element of the documents will take a while.

¹ That’s one view
² Mine and my colleagues – he left. Current state of play, I don’t blame him.

Windows XP, I was following the instructions in the tutorial, and the ping test gave errors about not being able to route, even though I’d set up the bridge.

Subsequently RPCEmuu gave me an error about not being able to see the TAP bridge, so I am left wondering if there is an issue with XP SP 3 being pedantic about unsigned drivers can do.

Got to admit that I’ve done limited testing of what I described here for Mac OS X.
- I’ve only used it for connecting to the Internet (via Netsurf), and haven’t done any email fetching (I don’t have Messenger, etc.) or file transfer (I’ve not used Access, etc.).

This isn’t 100% reliable – quite often, surfing stiffs RPCemu, and I resort to stopping and restarting the NAT (as I described in my OP in that thread), and then restarting RPCemu
- however, it does show it works for OS X.

I’m holding off documenting it until I get more experience of it – and with a holiday looming!

Mike

Windows XP, I was following the instructions in the tutorial, and the ping test gave errors about not being able to route, even though I’d set up the bridge.

My first notes on networking include the caveat that XP doesn’t retain the networking settings for the TAP driver over a reset. The information predates the current TAP driver release though.

My first test install sequence walk through is being done on W7, and will then be repeated on that before a sort of backport to XP.

This isn’t 100% reliable – quite often, surfing stiffs RPCemu

If you check the info pages for OpenVPN it mentions issues with lock up where there is an MTU mismatch – maybe?

@ Alex: WinXp is less satisfactory than later Windows versions for networking RPCEmu. According to www.marutan.net/rpcemu/manual/net-win.html: the full configuration of the bridge interface is not preserved on reboot of the host system so the bridge has to be reset each time. A wireless connection is also problematic. I can tell you that here on Win7, RPCEmu0811/520 networking is rock-solid. Unfortunately I don’t have any experience of setting up RPCEmu networking on WinXP. Like you, I followed the standard instructions.

My first test install sequence walk through is being done on W7, and will then be repeated on that before a sort of backport to XP.

OK, first notable item – whatever you do, don’t try and install on a PC running Cisco AnyConnect. Like many things from Cisco it thinks it is the sole owner of anything it touches.

The TAP driver loads, things seem to work but RPCEmu complains about access to the TAP-32 device. I need to sort out an Anyconnect free PC to play on before I can do anything meaningful.

George – perhaps you could write down the sequence in the same style as the initial RPCEmu and OS X/Windows documents?

George – perhaps you could write down the sequence…

I’ll have a stab over the next few days – it’s quite a while since I last set up networking.

‘Stab’ duly had, on my XP laptop. I stepped through all the Marutan instructions, augmented by my own notes, but no joy with 0.8.11/5.20 networking on XP: ping -c 4 XXX.XXX.X.X fails every time. AFAICS the network bridge and RPCEmu setup is exactly as my Win7 ditto in every way, so I cannot explain the failure.