RISC OS Configuration - IP Tunnelling
We now configure RISC OS to use the network we've previously set up.
These screenshots are from RISC OS 4.02, other versions of RISC OS will be similar but not necessarily identical.
Run !Boot and click the Network icon:
Click the Internet icon:
Click Enable TCP/IP Protocol Suite, then click the Interfaces icon.
In 'Interfaces' make sure EtherRPCEm is selected and click the Configure... button.
Choose Manually; and in IP address enter an address on our tunnelling network. In Netmask enter its corresponding netmask. In the example network used in this guide these are 172.31.0.10 and 255.255.0.0 Click Set.
Click Close on the 'Interfaces' window.
Now click the Routing icon in the 'Internet Configuration' window:
Enter the Gateway as the IP address of the other end of the tunnelling network. In the case of the example network this is 172.31.0.1 Click Set.
Now click the Host names icon in the 'Internet Configuration' window:
DNS configuration: You must enter a value for Host name and Local Domain for RISC OS DNS to work, though the exact values are not important. This example uses the values myhost and domain. Enter Primary name server as the IP address of the DNS server available on your network. This is often the IP address of your home router and in the example network is 192.168.0.1
Click Set on the 'Host names' window. Click Close on the 'Internet Configuration' window. You will be prompted to reboot RISC OS and must reboot before networking will be available.
Enter these commands at a RISC OS command prompt.
First check that the interface has been created:
This should have a rpcem0 interface in the output with the IP address of the emulator end of the tunnel.
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384 inet 127.0.0.1 netmask 0xff000000 rpcem0: flags=8863<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST%gt; mtu 1500 inet 172.31.0.10 netmask 0xffff0000 broadcast 172.31.255.255 ether 06:02:03:04:05:06
Next try to ping the Linux end of the IP Tunnel, this will prove the tunnel has been configured correctly.
ping -c 4 172.31.0.1
Next try to ping the gateway of the home network; this will prove the routing has been set up correctly on Linux.
ping -c 4 192.168.0.1
Next try to ping a website by name to test the DNS configuration.
ping -c 4 <a website that you know is up right now, eg. www.marutan.net>
If these all succeeded then networking has been set up successfully.