Roadshow Update for MorphOS

[olsen]

the addnetinterface fix for bringing the device driver online still doesnt work

Ram Disk:> AddNetInterface DEVS:NetInterfaces/~(#?.info)
Interface "SunGEM" added.
Interface "SunGEM" configured, address = 192.168.0.55, network mask = 255.255.255.0.
Ram Disk:> ping google.com
ping: unknown host google.com
Ram Disk:> online sungem_eth.device unit 0
Ram Disk:> ping google.com
PING google.com (173.194.32.37): 56 data bytes
64 bytes from 173.194.32.37: icmp_seq=0 ttl=54 time=17.487 ms
64 bytes from 173.194.32.37: icmp_seq=1 ttl=54 time=17.047 ms
64 bytes from 173.194.32.37: icmp_seq=2 ttl=54 time=17.291 ms
64 bytes from 173.194.32.37: icmp_seq=3 ttl=54 time=17.105 ms
64 bytes from 173.194.32.37: icmp_seq=4 ttl=54 time=17.078 ms
64 bytes from 173.194.32.37: icmp_seq=5 ttl=54 time=16.872 ms
64 bytes from 173.194.32.37: icmp_seq=6 ttl=54 time=16.965 ms

--- google.com ping statistics ---
7 packets transmitted, 7 packets received, 0% packet loss
round-trip min/avg/max = 16.872/17.120/17.487 ms
Ram Disk:> version c:AddNetInterface
AddNetInterface 4.52
Ram Disk:>

Something's wrong. I'm currently looking into it, but by the looks of it there won't be a better solution until this weekend. This is somewhat embarrassing

AddNetInterface 4.52 will bring the underlying network device driver online if DHCP is used to set up the interface's IPv4 address, routing, etc.

However, if your network interface uses a static IPv4/netmask configuration (and no DHCP), then you must add the line "state=online" to the configuration file. Otherwise, the device will not be switched into online mode and cannot send or receive data.

I'm wondering: how does your network interface configuration file look like?

[olsen]

@cato

I dont use local net for make tests, my problem is download at ridiculous speed.

How do you access the internet from your machine? Specifically, is there a gateway router (talks Ethernet to your local network, talks ATM or Carrier Ethernet with your ISP) or cable modem involved?

Some of these devices are rather simplistic. They can pass traffic between the internet and your local network, but they are not necessarily willing or able to rewrite or reshape the data traffic. This can be problematic if the TCP/IP stack used in your local network does not have certain features which were introduced in the early 1990'ies. AmiTCP and Roadshow are among these, but Roadshow has one or two features which AmiTCP lacks.

If such features are lacking, and your gateway router/cable modem is smart enough to rewrite or reshape the data traffic that passes through it, then you might still get decent data throughput, since this device can (up to a point) make up for the deficiencies of the TCP/IP stack.

But if both your TCP/IP stack and your gateway router/cable modem are unable to compensate for each other's weaknesses, then the results may be disappointing.

[olsen]

Did you guys know that "Roadshow" was supposed to be the original tcp stack for Morphos? I wont go into why it didnt happen but thats why we ended up with nutsack , er, i mean "netstack"

You are correct. This is not an urban legend.

[olsen]

on my macmini where I installed the update :

Thank you. You are indeed using a static IPv4 address and a corresponding network mask. This will completely bypass the online switch logic which I put into the AddNetInterface 4.52 command. The online switch only kicks in if DHCP is enabled (which in your case is disabled). This should explain why you still need to use the "online" shell command.

Could you please add "state=online" (without the double-quotes, of course) to this configuration file, then enter "netshutdown" and "addnetinterface SunGEM"? The "state=online" addition should make AddNetInterface switch the "sungem_eth.device" online, as if you had used the "online" shell command before.

The change would look something like this:

-- 8< --
# Bring "sungem_eth.device" online; never omit this line, as
# "sungem_eth.device" may otherwise refuse to receive or send
# any network traffic at all.
state=online
-- 8< --

If this should do the trick, I will update the documentation, fix the sample SunGEM and VIA-Rhine configuration files, and get new archives online.

[olsen]

adding "state=online" to Devs:NetworkInterfaces/SunGEM worked.

Thank you. This sounds like it will be easy to fix the update archives and the rest

[olsen]

just a quick question, i've noticed if i edit and save config files, and do a typo then log window pops up reporting an error so the stack monitors any change on the fly.

That is correct. Except for the network interface configuration files and the text database files (services, networks, etc.) every other configuration file is tracked and reread whenever its contents change.

So yesterday tried with roadshowcontrol to change tcp.recv/sendspace and windowscaling on/of while downloading an ubuntu iso, to see if there was any difference, but the difference didnt happen before i've aborted the download and redownloaded.
So i made this quick little arexx script that monitors keys and put a tcp.sendspace and tcp.recvspace increase/decrease with c:RoadshowControl to better find the sweetspot,
and seemed to work, but was wondering if such a live autotuning existed already in the  stack ?

It exists, but I do not know the details. The TCP protocol is largely auto-calibrating, optimizing throughput according to how fast the receiver can process incoming data, how many segments have to be retransmitted, how much memory is available for assembling segments which were received out of order, etc.

[olsen]

I must say that I'm quite positively surprised by the MorphOS support shown here!

Great!

You asked for it, didn't you?

[olsen]

Name:   Roadshow MorphOS Update 2
Last file modification:   16.01.2013 - 13:47 (today's date 19.01.2013)

+ identical filename
+ identical readme file inside archive (no new changelog)

Was there any change? And if so, what?

:confused:

As of this writing the archive files which I updated yesterday are not available yet. I don't know what happened, but the new archive files are bound to show up soon.

As for the changes, I updated the ReadMe files in all archives (MorphOS update, demo version, full version) to briefly show what's new.

In this case, the network interface configuration files for MorphOS were all updated to allow them to be used with static IPv4 addresses.

Also, three new MorphOS network interface configuration files have been added for the older "mpc52xx_eth.device", "mv6436x_eth.device" and "rtl_8139pci.device" network device drivers. That should (hopefully) cover everything.

[olsen]

The update 2 file is still the same as the previous one?
Also how can customers of the full version get a newer archive? just redownload through the customer portal? tbh I didn't try that yet, since there's a download limit it seems?

In truth, I haven't figured out yet how to make patch files available yet... I'm open to suggestions, since I haven't quite found the time yet to plan ahead this far.

The recent changes only affected one shell command and a set of two (now five) network configuration files. These files are identical in both the full version and the demo version.

Hence, you could download either the demo version and copy the respective files manually, or you could pick the MorphOS update archive and copy the files from that archive. The recent changes and additions were for the benefit of MorphOS users only, and you're not missing anything if you run Roadshow on a 68k Amiga and have not installed the updated files yet.

The "core" of Roadshow, namely the bsdsocket.library (which is different in the full version and the demo version) has not needed updating yet.

[olsen]

I made an installer for Roadshow on Morphos, since the orginal installer doesnt work and if it worked it would install lots of config files for amiga hardware.
It also lets you skip to install the firewall and ppp/ppoe stuff for adsl users

It doesnt touch anything in your existing Morphos system or network config so if you install you have to manually disable internal netstack and run Roadshow 68K manually (s:Network-Startup is renamed Network-Startup.off) Doubleclick from Ambient to start or rename to Net-Startup to let Roadshow start at next boot.

It also let you tune internal Roadshow settings based on calulations you enter
to better find settings spesific to transfer rates and more suited to system with more memory and not low-mem 68k classic systems, as this stack is aimed at... might boost you browsing speed...

After tuning I got tripple transfer rates in OWB downloads, compared with orginal unaltered Roadshow settings.

you need a working arexx tho...

Cool! I'll have a good look at it. Maybe I can fix the existing installer script for Roadshow myself, so that it works better with MorphOS.