Some users have had issues with new MorphOS 1.4.4 SANA2 drivers and AmiTCP/IP with startnet script. Check that your startnet script has the following line (or something similar):

AmiTCP:bin/online >nil: eth0

The line should be after "ifconfig eth0".


Technical: The new SANA2 drivers are SANA2 spec conforming and don't go online automagically.



NOTE: eth0 is an example, obviously you need to use your specific interface name, if it's not eth0!

[ Edited by Piru on 2005/3/28 23:36 ]

Piru

Thanks for the post and thanks for your work on the MOS release



magnetic

@ magnetic

Hi magnetic! Glad to see your'e alive!

I don't have this line "ifconfig eth0" in my startnet script, so how can i get Genesis now Auto-Online again? I tried to put "AmiTCP:bin/online >nil: eth0" in the startnet script but without success.

you must replace eth0 by the name of your interface name in genesis
prefs.

but it doesn't work either here with mos 1.4.4, the device does not
go online, so i put back the old network device.

I have noch eth0 interface name in that startnet file! With MiamiDx all works fine but Genesis is faster. And it seems that all my problems with moving large Files in my network are gone.

Ok, perhaps you guys having trouble should post your (modified) startnet script. Maybe it's just some small mistake?

in my startnet there is amitcp:bin/bootpconfig ....
There was some complain in log window about some vec=1 is not supported, must be -1. It was during executing mount tcp:. So I removed it. But this didnt help - interface went offline still. So I placed amitcp:bin/online rtl0 after bootpconfig. It works now, but I have unclosable log window with contents like this: ... interface rtl0 went offline
... interface rtl0 is online again. Would like to know how to force this window close :)

@scf

No worries, you can get rid of the log window by editing AmiTCP:db/AmiTCP.config and editing/adding specific line.

ConsoleName = "nil:"

If the line already exists you can edit it, if it doesn't exist, add it.

[ Edited by Piru on 2005/3/29 11:14 ]

where can one find this startnet-file?
why does genesis have an option for auto-online and why is no more supported?

Quote:
It was used with old AmiTCP/IP without GUI.

Quote:
It is no longer supported?

AmiTCP/IP Genesis should go online just fine, if using Genesis to control the AmiTCP/IP.

Here is my Startnet script:

.key DEBUG/S,PROVIDER/K,SCRIPT/K,NOSRV/S,BOOTPOPTIONS/F
.bra {
.ket }
;
; use profile made by AmiTCP Prefs by default
.def PROVIDER "ENV:NetConfig/Provider.conf"
; the default dial script
.def SCRIPT "AmiTCP:db/Dialscript"
;
; AmiTCP/IP DialUp 4.5 NetConnect version startnet script
;
; Copyright © 1996 AmiTCP/IP Group,
; NSDi - Network Solutions Development Inc., Finland
; All rights reserved.
;
; *NOTE* YOU SHOULD NOT NEED TO EDIT ANYTHING BELOW. IF YOU NEED TO START
; *NOTE* UTILITIES, DO IT IN THE ENV:NetConfig/User-Startnet.
; *NOTE* YOU CAN STOP THESE UTILITIES IN ENV:NetConfig/User-Stopnet.
;
; Set the failat level so that the errors can be handled by the script
FailAt 21

If NOT Exists {PROVIDER}
Echo AmiTCP/IP is not configured
Echo Starting the configuration tool...
Run >nil: <nil: NetConnect:AmiTCPPrefs
Quit 20
EndIf

Version bsdsocket.library >nil:
If Warn
If X EQ "X{DEBUG}"
Run >nil: <nil: AmiTCP:bin/AmiTCP.kernel {DEBUG}
Else
Run AmiTCP:AmiTCP {DEBUG}
EndIf
EndIf

AmiTCP:bin/WaitForPort AMITCP
If NOT Warn
; Log in with the default user name (nobody)
AmiTCP:bin/login -f dolphin
; Configure AmiTCP
AmiTCP:bin/bootpconfig PROVIDERFILE={PROVIDER} DIALSCRIPT={SCRIPT} {DEBUG} {BOOTPOPTIONS}
If NOT Warn
;
; Mount TCP:
;
Assign TCP: Exists >NIL:
IF Warn
Mount TCP: from AmiTCP:devs/Inet-Mountlist
EndIf
;
; Start inetd if needed
;
If X EQ "X{NOSRV}"
If X EQ "X{DEBUG}"
Run <NIL: >NIL: AmiTCP:bin/inetd
Else
Run AmiTCP:bin/inetd {DEBUG}
EndIf
EndIf
;
; Start utilities in ENV:NetConfig/User-Startnet
;
If Exists ENV:NetConfig/User-Startnet
Execute ENV:NetConfig/User-Startnet
EndIf
;
; Successfull end
;
Echo AmiTCP/IP DialUp 4.5 is now on-line. Your host name is $HOSTNAME.
Else
Echo AmiTCP/IP DialUp configuration failed!
EndIf
Else
Echo AmiTCP/IP DialUp couldn't be started!
EndIf


; Ask NetConnect to reload the interface
; (and change the state of the start/stop button
Rx >Nil: "address NETCONNECT; refresh"

; EOF

This is a minimal startnet-script for AmiTCP/Genesis,
which works for me with 1.4.4:

---8<---
SYS:C/RexxMast >NIL:
AmiTCP:bin/login -f root >NIL:
AmiTCP:bin/umask 022 >NIL:
run >NIL: AmiTCP:kernel/AmiTCP >NIL:

If NOT Warn
ifconfig lo0 127.0.0.1
ifconfig via_rhine 192.168.0.4 netmask 255.255.255.0 broadcast 192.168.0.255
online via_rhine
If NOT Warn
setenv HOSTNAME `AmiTCP:bin/hostname`
setenv HOST `AmiTCP:bin/hostname`
Run <NIL: >NIL: AmiTCP:bin/inetd
route add default 192.168.0.250 >NIL:
Else
Echo Ethernet interface configuration failed!
EndIf
Else
Echo AmiTCP couldn't be started!
EndIf
---8<---

Pegasos is at 192.168.0.4 and router at 192.168.0.250.
Replace this to fit your needs.

Piru thanx

Ok, I have to correct myself, there indeed is some icky problem introduced by the 1.4.4 SANA2 drivers and Genesis.

Genesis issues S2_ONLINE command before configuting the interface with S2_CONFIGINTERFACE, and then expects the driver to report S2EVENT_ONLINE from S2_ONEVENT.

The current drivers don't allow S2_ONLINE before S2_CONFIGINTERFACE (the spec is perfectly clear that S2_GETSTATIONADDRESS and S2_CONFIGINTERFACE should be the very first commands to send).

Anyway, the end result is that Genesis doesn't go online even if auto online is enabled. This can be worked around by doing manual Quote: (replace eth0 with your interface name) few seconds *after* starting Genesis.

Another option is to downgrade the drivers.

I'm truly sorry for the trouble this has caused. I partly blame the very confusing SANA2 specification: It's a bit too vague at places...

[ Edited by Piru on 2005/3/30 11:05 ]