On 21 Mar 2009, at 09:56, Tim Powys-Lybbe wrote:
In message of 20 Mar, Francis Devereux <[email protected]> wrote:
On 17 Mar 2009, at 19:19, Tim Powys-Lybbe wrote:
In message of 17 Mar, Francis Devereux <[email protected]> wrote:
<snip>
I have never been able to get networking working with RISC OS 4.39.
Under both Linux and Mac OS X it hangs when the EtherRPCEm module
is
loaded. Networking works with RISC OS 4.02 for me.
Does this mean that you have networking going on RPCemu running
'natively' on a Mac. I have tried to do this but failed. If you
have
got it working, can you give some guidelines?
Yes, but I had to change the RPCEmu code to get it working and my
changes aren't ready to be included in the main RPCEmu code base.
See
my mails to the list on 11 Feb and 23 Feb for more details. I do
intend to finish this code and submit it, but unfortunately I don't
expect to have time to do this before May.
Thanks for the explanation and delighted to hear that you are
working to
make networking usable by Those That Don't Know.
A while back Tom Hughes published some code that, as I understood it,
was to improve the networking scene on the Linux versions of
RPCemu. To
the best of my knowledge this has yet to be incorporated into the main
code. My experience of the original RPCemu networking on Linux was
that
while it could be made to work, it was cumbersome. I wonder if you
are
able to incorporate Tom's code and what the benefits are to the simple
user?
Tom Hughes' patch adds support for bridged networking, which does make
setting up networking easier but unfortunately I don't think it will
be easy to get bridged networking going on OS X. The FAQ for the tun/
tap driver that my networking code uses (http://tuntaposx.sourceforge.net/faq.xhtml
) says that "Mac OS X does not have ethernet bridging built in" which
means that I would need to write a kernel extension in order to
implement bridging (which would be a lot of effort since it would
involve me learning how to write kernel extensions ;-). I could be
wrong about this though, I haven't researched it thoroughly.
Alternatively, I might be able to make the NAT networking easier to
use by making RPCEmu issue the commands to get NAT going instead of
the user having to enter them manually. I'll see what I can do when I
have time to get stuck in RPCEmu coding again...
Francis
_______________________________________________
Rpcemu mailing list
[email protected]
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
