Buffalo NAS-Central Forums

Welcome to the Linkstation Wiki community
It is currently Fri Aug 17, 2018 9:49 am

All times are UTC+01:00




Post new topic  Reply to topic  [ 2 posts ] 
Author Message
PostPosted: Thu Jul 21, 2011 11:44 pm 
Offline
Total Newbie

Joined: Thu Jul 21, 2011 11:23 pm
Posts: 1
Hi all,

I'm struggling to gain root access to my Linkstation, and haven't managed to find any posts here with quite the same symptoms.
The overall goal is quite simple - enable NFS access to the shares.

I have a Linkstation HS-DGL, running stock firmware 1.49.

Attempting to establish contact via acp_commander sort of works - the initial Discovery works (it returns the correct name of the box), but the actual command is ignored:
Code:
ubuntu@ubuntu:~$ sudo java -jar acp_commander.jar -t 192.168.1.4 -pw theWebAdminPassword -c "ls" -ip 192.168.1.4
ACP_commander out of the nas-central.org (linkstationwiki.net) project.
Used to send ACP-commands to Buffalo linkstation(R) LS-PRO.

WARNING: This is experimental software that might brick your linkstation!


Using random connID value = 67997B2FEE5F
Using target:   192.168.1.4/192.168.1.4
Starting authentication procedure...
Sending Discover packet...   
Found:   HUTCH (/192.168.1.4)    HS-DGL(IEHARU) (ID=0008)    mac: 00:00:00:00:00:00   Firmware=  1.490   Key=012B5F6E
A SocketTimeoutException usually indicates bad firewall settings.
Check especially for *UDP* port 22936 and make sure that the connection to your LS is working.
ERROR: Exception: SocketTimeoutException (Receive timed out) [ACP Send/Receive (Packet:80A0 = SPECIAL_CMD_EN_ONECMD)]


This test was performed using a crossover cable linking the laptop (running stock Ubuntu 10.04 live CD) directly to the Linkstation (hard-coded IP address). ACP_Commander was freshly downloaded from Sourceforge, and reports
Code:
Version 0.4.1 (beta)


Using tcpdump on the laptop, I can see:
- initial discovery packet sent to port 22936
- response from Linkstation (to IP 255.255.255.255)
- command packet sent to port 22936
(no response; after 5s timeout, then:)
- command packet resent to port 22936

Looking back through the forums, I can see people having trouble after Buffalo changed the authentication mechanism, but I understood the combination of the v0.4.1 of acp_commander, in conjunction with the -ip option to have solved this problem. I've also read of the combination of initial discovery OK + ACP_STATE problems, but not this loss of communication halfway through a single acp_commander run.

I'm at a loss now - there is obviously some communication, or acp_commander couldn't know I'd named the Linkstation "HUTCH".

Has anyone else experienced this? (Or can anyone else suggest another way to get NFS running?)

Many thanks in advance,

Tom


Top
   
PostPosted: Fri Jul 22, 2011 6:34 am 
Offline
Moderator

Joined: Fri Jun 29, 2007 10:39 am
Posts: 2604
Maybe your Ubuntu system blocks global broadcasts on the
receiving side internally (just a guess)?
Do you have a different operating system at hand to try?

_________________
Please do not use private mail (PN/M) to ask questions. Use the proper forum instead. (me)

If there is no verified backup of a dataset, the dataset, by definition, is unimportant. (c't 2012)

RAID (no matter which level) never ever substitutes a backup. (me)


Top
   
Display posts from previous:  Sort by  
Post new topic  Reply to topic  [ 2 posts ] 

All times are UTC+01:00


Who is online

Users browsing this forum: No registered users and 2 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Powered by phpBB® Forum Software © phpBB Limited