Amiga.org
Amiga News and Community Announcements => Amiga News and Community Announcements => Amiga Software News => Topic started by: AndreasM on October 09, 2016, 09:56:34 AM
-
The Roadshow TCP/IP stack for the Amiga has been updated to version 1.12 and is available immediately. An updated demonstration version is available, too, as well as the updated software development kit.
A free update is available for customers who are using Roadshow 1.11, upgrading it to version 1.12. Note: if you are still using Roadshow 1.8 you need to upgrade to version 1.11 first before you can upgrade it to version 1.12.
The changes in Roadshow 1.12 are as follows:
1. A buffer overflow bug has been fixed which could occur when
querying network interface hardware addresses. This bug could
cause the "ShowNetStatus" command to crash.
2. The ftp command has been reworked, fixing bugs which had been
present for years (buffer overflows, etc.).
3. Overlapping name resolution operations can no longer collide
with each other so easily and produce corrupt query data. This
problem could occur only very rarely.
4. New API functions for name resolution have been added, which are
common in the Unix world, for which no alternatives had been
available before. These enhancements are new for Amiga
TCP/IP software in general.
5. If Roadshow sets up a network interface using the DHCP protocol
it can now request that the DHCP server sends its responses
directly to Roadshow (unicast) instead of broadcasting them to
the local network.
6. Changing the system clock time (e.g. during daylight saving
time transitions) no longer affect Roadshow's internal
time keeping.
7. A new ready-made network configuration file for PCMCIA cards
using the "cnet16.device" driver is provided under
"Storage/NetInterfaces/CNet16").
8. The reference documentation has been updated.
More detailed descriptions of the changes can be found in the "ReadMe" file of the Roadshow archive, and the SDK archive.
http://roadshow.apc-tcp.de
-
Thanks for this! Looking forward to trying it.
-
Great work! I need to purchase this.
-
Fantastic, maybe now I can use the CLI ftp client on the regular. The GUI ones are nice, but take so long to start up on my 1230.
-
I still need to get NFS set up on my Amiga like I do my Falcon. Seems simpler to use once it's set up than pulling things over via FTP. Granted on the Amiga I have a browser that'll pull in things from Aminet. I've yet to get a browser working correctly on the Falcon, though I do have most other things set up nicely.
-
Great job!! :D
-
Purchased! Will be able to try it out later today.
I'm sure this has been asked already somewhere, but can I install the full version over the demo or should I clean out the demo version first?
-
Purchased! Will be able to try it out later today.
I'm sure this has been asked already somewhere, but can I install the full version over the demo or should I clean out the demo version first?
I'm pretty sure it will let you uninstall the current version. After that you run the installation again. You should have the option to backup your settings.
-
Great!
I'm pretty sure it will let you uninstall the current version. After that you run the installation again. You should have the option to backup your settings.
-
Is this a free update for current registered users?
-
Is this a free update for current registered users?
Yes.
-
Does this work with ioblix ethernet? Dont see any config file
-
Didn't know they made one. Not in the Big Book.
-
Its an add on card to the ioblix, check the cech website
http://amiga.resource.cx/exp/ioblix
-
Does this work with ioblix ethernet? Dont see any config file
I do not know if it works, but a configuration file would look something like this (save the contents as a text file by the name of "IOBlix" and move that file into the "DEVS:NetInterface" drawer, then restart your Amiga):
# $VER: IOBlix 1.1 (12.10.2016)
#
# Configuration for the optional Ethernet hardware add-on
# for the IOBlix serial/parallel card, using the
# "ioblixether.device" driver (http://aminet.net/driver/other/IOBlixUsr.lha)
# The device name is mandatory
device=ioblixether.device
# If not provided, unit number 0 will be used. You may
# have to change this if there are multiple cards of the
# same type installed in your machine, or if your network
# hardware supports several independent connections
#unit=0
# You must either pick a fixed (static) IPv4 address and
# a corresponding subnet mask, or request DHCP (dynamic)
# network address configuration.
# You can combine address/netmask/dhcp, which has the effect
# of asking the DHCP server to assign the requested IPv4
# address and subnet mask to this interface, if possible.
#address=192.168.0.1
#netmask=255.255.255.0
configure=dhcp
# If no DHCP server is present in your network, you can
# use automatic interface IPv4 address assignment through
# the ZeroConf protocol. Note that this will not set up
# default route and DNS servers for you, only the interface
# address is configured.
#configure=auto
# This variant of automatic IPv4 address assignment should
# be used in a wireless network instead of 'configure=auto'
#configure=fastauto
# You can enable diagnostic messages which can be helpful in
# tracking down configuration errors.
#debug=yes
# You can choose how much memory will be used when handling
# incoming and outgoing network traffic for this device.
# The default is to reserve 32 buffers of 1500 byte each, both
# inbound and outbound traffic. Larger values may provide
# better performance.
#iprequests=32
#writerequests=32
# For diagnostic and monitoring purposes it can be helpful to
# capture network traffic that flows through this interface.
# To enable this option, select one of filter=local,
# filter=ipandarp or filter=everything
#filter=local
#filter=ipandarp
#filter=everything
# This option disables a workaround required for the Ariadne
# network hardware, which, if enabled, would otherwise cause
# the interface setup procedure to take longer than really
# necessary.
requiresinitdelay=no
-
awesome ! Thanks my friend :)
I see the 37.20 drivers available on Aminet are buggy, latest known to work are 37.17, so hunting them down now. Maybe the 37.14 ones from the install disks is why it freezes once I click on the workbench after going online with a couple of different ICP stacks, including above.
-
According to http://www.amigafuture.de/viewtopic.php?t=41040&sid=f51159b95c5a7e96b9a0ab0565138218 every update archive downloaded befor oct. 16 didn't work, since the tool (cedpatch) wasn't executable. The installer didn't show any errors.
-
It worked fine, you just had to set the execute flag on some of the files. Anyway, it's solved now.
-
duga, your response makes no real sense. The original script simply did not work, and the installer did not reflect this fact to the user. midway, many months ago I too noticed the problem with ioblix, I did some experiments with lower network buffer sizes, thankyou olsen, but didnt follow up on the issue back then, sorry olsen. midway, if you still need the ioblix 37.17 archive, let me know, I have it somewhere. olsen, thankyou for the update, I just bought my 2nd. license as I appreciate your continued effort very much. -omgas
-
Thanks Omgas, I found an archive with 37.17 and the card works nicely with Miami now, still trying to get AmiFTP to run with Roadshow, somehow it never makes it to pulling the filelists, it just goes on endlessly without showing anything. With Miami I get online now with the
37.17 version, up to 200 kb/s from aminet which is ok, not great. That's why I want RoadShow :laugh1: (once working)
-
duga, your response makes no real sense. The original script simply did not work, and the installer did not reflect this fact to the user. -omgas
The original script didn't do what it should do unless you first manually had set the execute flag on the necessary files.
-
midway, yes, I too have had the ioblix ethernet working with MiamiDX, unfortunately it seems the ioblix software was never finalized, and perhaps Miami(DX) bends the specs a bit somehow. Let us know if you manage to get Roadshow working with it. I will try once more when time permits. -omgas
-
Absolutely! 37.20 didnt work for me at all, although on a1k.org someone said it did for him... Will post more once i get to it again:)
-
I'm just now planning on updating my 1.9 version from 2013. I can find a 1.11 update and 1.12 update, but no 1.10 update. Is there such a thing?
Also, am I correct in assuming I need to run the updates in order? I didn't want to update to 1.11 before I receive confirmation that there's no 1.10 update. :)
Thanks.
-
Can you not just download newest Roadshow and install it over what you have?
-
@kolla
I had a look in the upgrades and they patch into existing installation files, so I don't think that would work as it's my registered files that need to be patched, not demo ones.
-
I'm just now planning on updating my 1.9 version from 2013. I can find a 1.11 update and 1.12 update, but no 1.10 update. Is there such a thing?
Also, am I correct in assuming I need to run the updates in order? I didn't want to update to 1.11 before I receive confirmation that there's no 1.10 update. :)
Thanks.
Unless I made a very embarrassing mistake (wouldn't be the first time, mind you), you should be fine applying first the 1.11 update, and then the 1.12 update. Note: you cannot directly apply the 1.12 update to the 1.9 installation and must apply the 1.11 update before the 1.12 update can be used.
The 1.11 patch files modify the ftp command and bsdsocket.library (well, there's a set of patches for the ppp ethernet/serial device drivers, but I reckon you aren't using them - hardly anybody does).
The 1.12 patch contains another update for the ftp command and bsdsocket.library, with new patches thrown in for the AddNetInterface and ConfigureNetInterface commands.
You might want to make backups of these files before you use the upgrades. The commands can be found in "C:", and the library is stored in "LIBS:".
The patch process might not report failed upgrade attempts well. After applying the 1.11 patch, please check if the files I mentioned have indeed been modified (look at the respective file modification times first, but you can also use "version c:ftp full" and "version libs:bsdsocket.library file full").
-
Thanks Olsen. I'll give it a go this afternoon and I'll get SnoopDOS on the job too.
-
@kolla
I had a look in the upgrades and they patch into existing installation files, so I don't think that would work as it's my registered files that need to be patched, not demo ones.
I thought that as registered buyers, we have free access to download registered versions? Oh well, guess I must store my copy somewhere safe.
-
(well, there's a set of patches for the ppp ethernet/serial device drivers, but I reckon you aren't using them - hardly anybody does).
Well, I am - serial port is still the most universally available option for all Amiga systems, and these days I build ARM systems (pi zero) inside all my Amiga computers, Roadshow works great with PPP over serial :)
(look at the respective file modification times first, but you can also use "version c:ftp full" and "version libs:bsdsocket.library file full").
It is not at all obvious what version of bsdsocket.library etc that belong to what version of Roadshow - it would be nice if all files, in addition to their own revisions numbers, could have "version full" strings that say something about version of Roadshow they belong to.
-
I thought that as registered buyers, we have free access to download registered versions? Oh well, guess I must store my copy somewhere safe.
I went back to APC-TCP and was able to get my registered download fixed. But, yeah, keep your download safe. I wound up creating a special directory for purchased software.
-
All went smoothly.
After running the 1.11 update installer it yields:
ftp 1.8
bdsocket.library 4.310
ppp_connector 52.2
ppp_dialer 52.2
ppp_sample 52.2
ppp-ethernet.device 52.4
ppp-serial.device 52.10
Then, after running the 1.12 update installer it yields:
ftp 1.9
bdsocket.library 4.321
AddNetInterface 4.53
ConfigureNetInterface 4.36
I think I'm all up to date now. If something looks wrong then please let me know. Thanks for your help. ;-)
(Posting this on my super A1200, aka Carl!)
-
Well, I am - serial port is still the most universally available option for all Amiga systems, and these days I build ARM systems (pi zero) inside all my Amiga computers, Roadshow works great with PPP over serial :)
I'm glad that the PPP drivers are still useful :)
Writing them turned out to be both easier and harder than expected. The PPP design is well-documented, but in the early 2000's so many different "server-side" PPP implementations were in use that you were in for a lot of surprises writing an implementation from scratch.
I bought James Carlson's book "PPP design, implementation and debugging" in November 2001 because it seemed to be the right thing to do, and it was: it shows in painful detail how many PPP implementation options were deployed and discarded during the IETF standardization process. Features which were only briefly used in-house, or showed up in an RFC which was quickly "obsoleted" by a newer RFC document were still in use around 2001-2002. PPP "client-side" code had to be aware of these "quirks".
It is not at all obvious what version of bsdsocket.library etc that belong to what version of Roadshow - it would be nice if all files, in addition to their own revisions numbers, could have "version full" strings that say something about version of Roadshow they belong to.
Good point. Roadshow is still very much what it was (except with fewer bugs) when it became a stand-alone product in 2013.
The library version of "bsdsocket.library" as the central core of the TCP/IP stack cannot be conveniently changed during each Roadshow release, with each Roadshow file (commands, scripts, configuration files) then getting bumped to use the same version. This worked for Commodore (V37 = Workbench/Kickstart 2.04, V38 = Workbench 2.1, V39 = Workbench/Kickstart 3.0, V40 = Workbench/Kickstart 3.1), but I can't use the same approach.
I'll likely have to go with adding extra information to the version text embedded in each file.