Internet not working. sharing from linux computer via ethernet

OK, repeatable error if I reboot again and then go in to configuration as if to configure the Interface but cancel the invalid message comes up again.

I have reverted back to the standard RunImage for now.

Note this is with a standard ARMX6 network setup and with DHCP set.

This implements the ideas discussed above.

I’m hoping someone’s going to take a look at the BOOTP RFC’s to appreciate why it is possible to enter a gateway at the same time as DHCP is enabled; it’s quite deliberate. That’s not to say getting the priority logic right (and not erroring) if both are set wouldn’t be nice at boot time, though.

it’s quite deliberate

Ditto DNS – one might prefer OpenDNS instead of whatever their provider offers (especially if they live in a country where it’s okay to block content by filtering DNS).

However, it might be more logical to, by default, clear these entries when switching to DHCP unless there’s a box ticked, like “Always use this gateway” etc to force them. That way, DHCP is less likely to fail because stuff got missed.

Even XP has a checkbox pair to select ‘’DNS servers from DHCP’’ and ‘’Use these DNS servers’’

Don’t bother downloading the InetSetup executable – it has some problems that I didn’t notice.

More info later.

I’m hoping someone’s going to take a look at the BOOTP RFC’s to appreciate why it is possible to enter a gateway at the same time as DHCP is enabled;

+1, also here is the link to read about the BOOTP RFC: https://datatracker.ietf.org/doc/html/rfc951

In the specifics:

BOOTP Protocol, fields:

giaddr  4       gateway IP address,
                      used in optional cross-gateway booting.

The system has to be able to use a BOOTP provided gateway address, not be forced to use the DHCP provided one only.

But, besides the BOOTP specifics, there are other reasons why one may need to have a “default gateway” different than the one passed by the DHCP, for instance:

1) Security gateway in the middle, certain computers should be addressed to use a different gateway than the DHCP provided one for security reasons
2) Subnetting with DHCP relay, in this case the default gateway HAS to be different than the one passed by a DHCP server if the DHCP Server has not been configured to server different CDIR subnets. So, for instance, a client may receive an IP from the DHCP, but the default gateway and the subnet mask have to be manually configured.

On top of that, there is also what Stewart mentioned:

Even XP has a checkbox pair to select ‘’DNS servers from DHCP’’ and ‘’Use these DNS servers’’

Which is another good point, to have even more possibilities (not just the manual gateway).

With all of this said, I agree with Sprow other comment:

That’s not to say getting the priority logic right (and not erroring) if both are set wouldn’t be nice at boot time, though.

So, probably another approach is to improve the FrontEnd to inform the user that, after setting DHCP, he/she has left the Gateway field populated and so RISC OS will use that instead of the gateway IP received from the DHCP?

just my 0.5c

there are other reasons why one may need to have a “default gateway” different than the one passed by the DHCP

Meanwhile, back on Earth, has anyone ever actually done this with a RISC OS machine? They would have had to manually edit the Choices.Internet.Startup file, AFAICS. If you’ve set RISC OS up with DHCP but using a different gateway, please pipe up!

Is there ever a case for having more than one gateway, or does that not even make sense since it’s the default gateway and you can only have one default? The present InetSetup code can only cope with one, regardless of how many interfaces are present. I can only imagine that routing via anything other than the default gateway is the province of the Routes file.

Possibly needs deferring until the new network stack drops.

I’ve uploaded a new InetSetup executable to my web site: https://davehigton.me.uk/Progs/insetup.zip

This fixes all the bugs I’ve found in the previous version. (I confirm the existence of the Invalid Object Id bug – I had referred to the Routing window object without first checking for null, which it would be if it hadn’t yet been opened.)

So have a play and let me know if you think it’s an improvement over the standard one.

Other then fixing any genuine bugs that I’ve introduced, I think I’ve played enough with it for now, so, if anyone else wants to take it a stage further, I’ll happily send them the four files that I’ve modified.

Possibly needs deferring until the new network stack drops.

Drops?!

Meanwhile, back on Earth, has anyone ever actually done this with a RISC OS machine?

Yes actually, trying to boot my RISC OS cluster using BOOTP… but never-mind, apparently this is a God like use (as you said, on Earth humans don’t do these things) XD

They would have had to manually edit the Choices.Internet.Startup file, AFAICS.

Yes and then the UI would report what exactly?

I think you’re confusing the Protocol with the UX experience. The best way to implement this is to change the ancestral InetSetup for something more modern. But ok, I’ll end this discussion here because I can see the it’s getting in the wrong direction as always.

For who is actually interested in making RISC OS better and more usable, please have a look at any MS Windows (from basically 95 onwards IIRC) network configuration, macOS (from 10 onwards), Linux both Gnome and KDE, BSD any GUI, iPad OS, watchOS, even Apple TV…

Have a nice day on Earth Dave! :)

Even XP has a checkbox pair to select ‘’DNS servers from DHCP’’ and ‘’Use these DNS servers’’

“Even XP” sounds like “even something as old as XP” – but XP is from 2001, while RISC OS networking UI is from around 1995. So we’d need to look at Windows NT 4, Windows 95 or even Windows 3.1 with Trumpet Winsockets :-)