Ethernet communication between 2 SAM's

A forum for general AmigaOS 4.x support questions that are not platform-specific
JosDuchIt
Posts: 291
Joined: Sun Jun 26, 2011 6:47 pm
Contact:

Re: Ethernet communication between 2 SAM's

Post by JosDuchIt »

@all
adding 460 partition from 440 would already vz fine but it does not work foe me

Yhis is the commented Snoopy trace


og Generated by; Snoopy 53.32 (14.10.2013)

00001 : Shell Process : o.k. = GetVar("_pchar",0x5AF08D18,32,0x00000200) [22uS]
00002 : Shell Process : o.k. = GetVar("_mchar",0x5AF08D18,32,0x00000200) [9uS]
00003 : Shell Process : o.k. = GetVar("mountStock",0x5986D078,64,0x00000001) [13uS]
00004 : Shell Process : o.k. = GetVar("_pchar",0x5AF08D18,32,0x00000200) [5uS]
00005 : Shell Process : o.k. = GetVar("_mchar",0x5AF08D18,32,0x00000200) [6uS]
00006 : Shell Process : FAIL = FindSegment("c:netmount",0x00000000,USER) [13uS]
00007 : Shell Process : FAIL = FindSegment("c:netmount",0x00000000,SYSTEM) [3uS]
00008 : Shell Process : CurrentDir("<untracked>")
00009 : Shell Process : o.k. = Lock("c:netmount",SHARED) [191uS]
00010 : Shell Process : o.k. = ExamineObject(0x5AF08C88) [52uS]
00011 : ENV/env-handler 52.2 : FAIL = Lock("ENVARC:ELF.LazyBinding",SHARED) [88uS]
00012 : Shell Process : o.k. = LoadSeg("c:netmount") = [0x1679A1E1] [159762uS]
00013 : Shell Process : o.k. = Lock("c:netmount",SHARED) [141uS]
00014 : Shell Process : DIR = ParentDir("c:netmount") [32uS]
00015 : Shell Process : CurrentDir("<untracked>")
00016 : netmount : o.k. = Open("CONSOLE:",OLD) = [0x17277AD6] [245uS]
00017 : netmount : o.k. = IsInteractive("CONSOLE:")
00018 : netmount : 0 = FindSegmentStackSize("c:netmount") [60uS]
00019 : netmount : -----> RunCommand(0x1679A1E1 "c:netmount",,"460 Stock: rh1: handler=l:netfs-handle",40) // handle and not handler xxxxxxxx ????
00020 : netmount : 0 = FindSegmentStackSize("c:netmount") [3uS]
00021 : netmount : o.k. = [exec] OpenLibrary("dos.library",0) [25uS]
00022 : netmount : o.k. = [exec] OpenLibrary("utility.library",37) [11uS]
00023 : netmount : o.k. = [exec] OpenLibrary("bsdsocket.library",2) [62uS]
00024 : netmount : o.k. = Open("DEVS:Internet/services",OLD) = [0x17277BB4] [256uS]

// A long wait here xxxxxxxxxxxxxxxxxxxxxxxxxxx


00025 : netmount : <----- RunCommand(0x1679A1E1 "c:netmount",,"460 Stock: rh1: handler=l:netfs-handle",40) = 10 [0x000
00026 : Shell Process : o.k. = SetMode("<untracked>",[LINE]) [818uS]
00027 : Shell Process : FAIL = GetVar("_Title",0x598B1F0C,256,0x00000200) [28uS]
00028 : Shell Process : FAIL = GetVar("Echo",0x5AF08D38,32,0x00000200) [12uS]
00029 : Shell Process : FAIL = GetVar("OldRedirect",0x5AF08D38,32,0x00000200) [10uS]
00030 : Shell Process : FAIL = GetVar("KeepDoubleQuotes",0x5AF08D38,32,0x00000200) [10uS]
00031 : Shell Process : FAIL = GetVar("Interactive",0x5AF08D38,32,0x00000200) [10uS]
User avatar
nbache
Beta Tester
Beta Tester
Posts: 1744
Joined: Mon Dec 20, 2010 7:25 pm
Location: Copenhagen, Denmark
Contact:

Re: Ethernet communication between 2 SAM's

Post by nbache »

Strange about that "-handle" without the "r". I wonder if your command is just a little bit longer than what SnoopDOS will print in the log. To check that, try without the colons on the device names (it works with or without them). If that prints the "r" at the end of "-handler" and still doesn't work, at least we know it is just a truncation of the line in the log, not a problem with the command itself.

Another idea: Try without specifying the "handler=l:netfs-handler" at all - I never needed that here. I think it is only needed if you put the handler somewhere else than L:

Best regards,

Niels
JosDuchIt
Posts: 291
Joined: Sun Jun 26, 2011 6:47 pm
Contact:

Re: Ethernet communication between 2 SAM's

Post by JosDuchIt »

@nbache

the hadle-r appeared when dropping the colons, it was not a problem of Snoopy's window being larger.

The results were the same also when dropping the ref to the handler;
User avatar
colinw
AmigaOS Core Developer
AmigaOS Core Developer
Posts: 218
Joined: Mon Aug 15, 2011 10:20 am
Location: Brisbane, QLD. Australia.

Re: Ethernet communication between 2 SAM's

Post by colinw »

I've just rechecked and Snoopy's argument buffer was 39 characters long, so the string was truncated for display.
I've just fixed it for the next update.
User avatar
nbache
Beta Tester
Beta Tester
Posts: 1744
Joined: Mon Dec 20, 2010 7:25 pm
Location: Copenhagen, Denmark
Contact:

Re: Ethernet communication between 2 SAM's

Post by nbache »

colinw wrote:I've just rechecked and Snoopy's argument buffer was 39 characters long, so the string was truncated for display.
I've just fixed it for the next update.
Thanks!

But that is strange: If it still truncated when JosDuchIt left out the two colons (and even, if I understand correctly, when leaving out the whole handler argument), it can't have been the full argument buffer causing the truncation. Do you have smaller temporary buffers for each of the arguments somewhere?

Although 39 does match the length of the argument line shown in the previously posted log (with a single byte added, I assume for null-termination).

Hmm ...

Best regards,

Niels
User avatar
colinw
AmigaOS Core Developer
AmigaOS Core Developer
Posts: 218
Joined: Mon Aug 15, 2011 10:20 am
Location: Brisbane, QLD. Australia.

Re: Ethernet communication between 2 SAM's

Post by colinw »

Besides the previous 40 byte display buffer limitation, the displayed argument string will also be truncted
at the first ascii character less than value 0x20 (char 32). That's all.
User avatar
Elwood
Posts: 65
Joined: Sat Jun 18, 2011 7:57 pm
Location: Lyon, France
Contact:

Re: Ethernet communication between 2 SAM's

Post by Elwood »

@JosDuchIt

Did you try with FTP? I want to be sure it's not a bug in Samba.
Philippe "Elwood" Ferrucci
Sam460 owner
AmigaOS 4 betatester
JosDuchIt
Posts: 291
Joined: Sun Jun 26, 2011 6:47 pm
Contact:

Re: Ethernet communication between 2 SAM's

Post by JosDuchIt »

@ elwood,

thanks for popping in
I did not try to use SAMBA
i did try to use netfs056

I have netmount & netfs-serverr in c:
:netfs-handler in l:
I added a host 440 in
==== Sam460 Devs:Internet/ hosts
# DEVS:Internet/hosts
192.168.1.5 440

and a host 460 in

==== SAM 440 Devs:Internet/ hosts
# DEVS:Internet/hosts
# File generated by Internet 53.2 (27.9.2009)
# On zondag, 10-nov-13 at 10:26:13
192.168.1.6 460

Nothing new in
==== SAm 440 & SAM460 Devs:Internet/ groups

My router in

==== SAM 440 & 460 Devs:Internet/ name_resolution
# DEVS:Internet/name_resolution
# File generated by Internet 53.2 (27.9.2009)
# On zondag, 10-nov-13 at 10:26:13
nameserver=192.168.1.1

nothing commented out in

==== both SAMs Devs:Internet/ networks

my router in
==== both SAMs Devs:Internet/ routes
# DEVS:Internet/routes
# File generated by Internet 53.2 (27.9.2009)
# On zondag, 10-nov-13 at 10:26:13
default=192.168.1.1

nothing new in
==== both SAMs Devs:Internet/ rpc


this in
====both SAMs Devs:Internet/ servers
# DEVS:Internet/servers
# File generated by Internet 53.2 (27.9.2009)
# On Mercredi, 13-Nov-13 at 19:38:49
amiganetfs stream stack=65536 Amiga SYS:C/netfs-server


the same line
==== both SAMS Devs:Internet/ services
# DEVS:Internet/services
# File generated by Internet 53.2 (27.9.2009)
# On Mercredi, 13-Nov-13 at 19:38:49
cvspserver 2401/tcp

Nothing new in
==== Devs:Internet/ users
# This is the user database, which associates user names with
# numeric IDs, group numbers and a bunch of other information
# that is primarily of historic value.
#
# Each line in this file is read and parsed according to the
# following template:
#
# NAME/A,PASSWORD/K,UID/A/N,GID/A/N,GECOS,DIR,SHELL
#
# Note that this file is not strictly required for proper
# operation of the TCP/IP stack.
NAME=root UID=0 GID=0
NAME=nobody UID=65534 GID=65534



Last thing i did observe was that netfs-handler & netfs-server were not marked as executable ,

I corrected that using Protect +E

I also wondered if t(here should not be a userinterface 440 on the SAM460 and 460 on the SAM440.(the SNFS docs don't tell us to)

# DEVS:NetInterfaces/440
# File generated by Internet 53.2 (27.9.2009)
# On Vendredi, 15-Nov-13 at 09:58:07
device=ppc460ex_eth.device
hardwaretype=Ethernet
address=192.168.1.101
netmask=255.255.255.0
mtu=0

and similar on the 460
User avatar
Elwood
Posts: 65
Joined: Sat Jun 18, 2011 7:57 pm
Location: Lyon, France
Contact:

Re: Ethernet communication between 2 SAM's

Post by Elwood »

Ok, never tried it as it's a 68k program.

Ok, but if you don't try with something else, we won't know if the problem comes from netfs or elsewhere. As a FTP server you can use:
http://se.os4depot.net/index.php?functi ... server.lha
Philippe "Elwood" Ferrucci
Sam460 owner
AmigaOS 4 betatester
JosDuchIt
Posts: 291
Joined: Sun Jun 26, 2011 6:47 pm
Contact:

Re: Ethernet communication between 2 SAM's

Post by JosDuchIt »

@Elwood

Ok i downloaded the server and started it ups
seetings:
- read&write
-anonymous acces
-path defined to name of one partiotions Stock:

Trying to connect with AmiFtp on the SAM440ep side
defined site
Name 460
Site 192.168.1.6
Port 21
OS UNIX
Main window

Entering 460 in Site: (textin gadget)
hit "connect" button
long wait, Amiftp connect window show "Status connecting" , but then disappears no other result
entering 192.168.1.6 in Site:
same effects
Post Reply