[Solved] Zyxel NSA325v2 unreachable on network

Install Arch Linux ARM on other devices.

[Solved] Zyxel NSA325v2 unreachable on network

Postby archon » Thu Aug 28, 2014 6:28 pm

Hi,

I installed Arch Linux on my brand new NSA325v2 using the instructions on this page, then I SSH'd into it using the IP 192.168.0.93, which was assigned to it by my router's DHCP. First things I did was install Samba, configure a static IP (192.168.0.200), then shutdown. On powering it back up, the device was unreachable; it didn't apper on my router's device list, and pinging 192.168.0.93 or 192.168.0.200 returned nothing.

I then hooked up the drive to my Debian laptop and managed to retrieve my bash history from it:
Code: Select all
pacman -Syyu
pacman -S samba
cp /etc/samba/smb.conf.default /etc/samba/smb.conf
nano /etc/samba/smb.conf
hostnamectl set-hostname NSA325v2
nano /etc/hostname
nano /etc/hosts
ip addr add 192.168.0.200/24 broadcast 192.168.0.255 dev eth0
ip route add default via 192.168.0.254
shutdown -h
As you can see, I nano'd into /etc/samba/smb.conf, /etc/hostname and /etc/hosts. Here's what they look like, respectively:

Code: Select all
# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options (perhaps too
# many!) most of which are not shown in this example
#
# Any line which starts with a ; (semi-colon) or a # (hash)
# is a comment and is ignored. In this example we will use a #
# for commentry and a ; for parts of the config file that you
# may wish to enable
#
# NOTE: Whenever you modify this file you should run the command "testparm"
# to check that you have not made any basic syntactic errors.
#
#======================= Global Settings =====================================
[global]

# workgroup = NT-Domain-Name or Workgroup-Name
   workgroup = WORKGROUP

# server string is the equivalent of the NT Description field
   server string = Samba Server

# This option is important for security. It allows you to restrict
# connections to machines which are on your local network. The
# following example restricts access to two C class networks and
# the "loopback" interface. For more examples of the syntax see
# the smb.conf man page
;   hosts allow = 192.168.1. 192.168.2. 127.

# if you want to automatically load your printer list rather
# than setting them up individually then you'll need this
   printcap name = /etc/printcap
   load printers = yes

# It should not be necessary to spell out the print system type unless
# yours is non-standard. Currently supported print systems include:
# bsd, sysv, plp, lprng, aix, hpux, qnx
;   printing = bsd

# Uncomment this if you want a guest account, you must add this to /etc/passwd
# otherwise the user "nobody" is used
;  guest account = pcguest

# this tells Samba to use a separate log file for each machine
# that connects
   log file = /var/log/samba/%m.log

# Put a capping on the size of the log files (in Kb).
   max log size = 50

# Security mode. Most people will want user level security. See
# security_level.txt for details.
   security = user
# Use password server option only with security = server
;   password server = <NT-Server-Name>

# Password Level allows matching of _n_ characters of the password for
# all combinations of upper and lower case.
;  username level = 8

# You may wish to use password encryption. Please read
# ENCRYPTION.txt, Win95.txt and WinNT.txt in the Samba documentation.
# Do not enable this option unless you have read those documents
;  encrypt passwords = yes
;  smb passwd file = /etc/samba/smbpasswd

# The following are needed to allow password changing from Windows to
# update the Linux sytsem password also.
# NOTE: Use these with 'encrypt passwords' and 'smb passwd file' above.
# NOTE2: You do NOT need these to allow workstations to change only
#        the encrypted SMB passwords. They allow the Unix password
#        to be kept in sync with the SMB password.
;  unix password sync = Yes
;  passwd program = /usr/bin/passwd %u
;  passwd chat = *New*UNIX*password* %n\n *ReType*new*UNIX*password* %n\n *passwd:*all*authentication*tokens*updated*successfully*

# Unix users can map to different SMB User names
;  username map = /etc/samba/smbusers

# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting
;   include = /etc/samba/smb.conf.%m

# Configure Samba to use multiple interfaces
# If you have multiple network interfaces then you must list them
# here. See the man page for details.
;   interfaces = 192.168.12.2/24 192.168.13.2/24

# Configure remote browse list synchronisation here
#  request announcement to, or browse list sync from:
#   a specific host or from / to a whole subnet (see below)
;   remote browse sync = 192.168.3.25 192.168.5.255
# Cause this host to announce itself to local subnets here
;   remote announce = 192.168.1.255 192.168.2.44

# Browser Control Options:
# set local master to no if you don't want Samba to become a master
# browser on your network. Otherwise the normal election rules apply
;   local master = no

# OS Level determines the precedence of this server in master browser
# elections. The default value should be reasonable
;   os level = 33

# Domain Master specifies Samba to be the Domain Master Browser. This
# allows Samba to collate browse lists between subnets. Don't use this
# if you already have a Windows NT domain controller doing this job
;   domain master = yes

# Preferred Master causes Samba to force a local browser election on startup
# and gives it a slightly higher chance of winning the election
;   preferred master = yes

# Use only if you have an NT server on your network that has been
# configured at install time to be a primary domain controller.
;   domain controller = <NT-Domain-Controller-SMBName>

# Enable this if you want Samba to be a domain logon server for
# Windows95 workstations.
;   domain logons = yes

# if you enable domain logons then you may want a per-machine or
# per user logon script
# run a specific logon batch file per workstation (machine)
;   logon script = %m.bat
# run a specific logon batch file per username
;   logon script = %U.bat

# Where to store roving profiles (only for Win95 and WinNT)
#        %L substitutes for this servers netbios name, %U is username
#        You must uncomment the [Profiles] share below
;   logon path = \\%L\Profiles\%U

# All NetBIOS names must be resolved to IP Addresses
# 'Name Resolve Order' allows the named resolution mechanism to be specified
# the default order is "host lmhosts wins bcast". "host" means use the unix
# system gethostbyname() function call that will use either /etc/hosts OR
# DNS or NIS depending on the settings of /etc/host.config, /etc/nsswitch.conf
# and the /etc/resolv.conf file. "host" therefore is system configuration
# dependant. This parameter is most often of use to prevent DNS lookups
# in order to resolve NetBIOS names to IP Addresses. Use with care!
# The example below excludes use of name resolution for machines that are NOT
# on the local network segment
# - OR - are not deliberately to be known via lmhosts or via WINS.
; name resolve order = wins lmhosts bcast

# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable it's WINS Server
;   wins support = yes

# WINS Server - Tells the NMBD components of Samba to be a WINS Client
#   Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
;   wins server = w.x.y.z

# WINS Proxy - Tells Samba to answer name resolution queries on
# behalf of a non WINS capable client, for this to work there must be
# at least one   WINS Server on the network. The default is NO.
;   wins proxy = yes

# DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names
# via DNS nslookups. The built-in default for versions 1.9.17 is yes,
# this has been changed in version 1.9.18 to no.
   dns proxy = no

# Case Preservation can be handy - system default is _no_
# NOTE: These can be set on a per share basis
;  preserve case = no
;  short preserve case = no
# Default case is normally upper case for all DOS files
;  default case = lower
# Be very careful with case sensitivity - it can break things!
;  case sensitive = no

#============================ Share Definitions ==============================
[homes]
   comment = Home Directories
   browseable = no
   writable = yes

# Un-comment the following and create the netlogon directory for Domain Logons
; [netlogon]
;   comment = Network Logon Service
;   path = /home/netlogon
;   guest ok = yes
;   writable = no
;   share modes = no


# Un-comment the following to provide a specific roving profile share
# the default is to use the user's home directory
;[Profiles]
;    path = /home/profiles
;    browseable = no
;    guest ok = yes


# NOTE: If you have a BSD-style print system there is no need to
# specifically define each individual printer
[printers]
   comment = All Printers
   path = /var/spool/samba
   browseable = no
# Set public = yes to allow user 'guest account' to print
   guest ok = no
   writable = no
   printable = yes

# This one is useful for people to share files
;[tmp]
;   comment = Temporary file space
;   path = /tmp
;   read only = no
;   public = yes

# A publicly accessible directory, but read only, except for people in
# the "staff" group
;[public]
;   comment = Public Stuff
;   path = /home/samba
;   public = yes
;   read only = yes
;   write list = @staff

# Other examples.
#
# A private printer, usable only by fred. Spool data will be placed in fred's
# home directory. Note that fred must have write access to the spool directory,
# wherever it is.
;[fredsprn]
;   comment = Fred's Printer
;   valid users = fred
;   path = /homes/fred
;   printer = freds_printer
;   public = no
;   writable = no
;   printable = yes

# A private directory, usable only by fred. Note that fred requires write
# access to the directory.
;[fredsdir]
;   comment = Fred's Service
;   path = /usr/somewhere/private
;   valid users = fred
;   public = no
;   writable = yes
;   printable = no

# a service which has a different directory for each machine that connects
# this allows you to tailor configurations to incoming machines. You could
# also use the %u option to tailor it by user name.
# The %m gets replaced with the machine name that is connecting.
;[pchome]
;  comment = PC Directories
;  path = /usr/pc/%m
;  public = no
;  writable = yes

# A publicly accessible directory, read/write to all users. Note that all files
# created in the directory by users will be owned by the default user, so
# any user with access can delete any other user's files. Obviously this
# directory must be writable by the default user. Another user could of course
# be specified, in which case all files would be owned by that user instead.
;[public]
;   path = /usr/somewhere/else/public
;   public = yes
;   only guest = yes
;   writable = yes
;   printable = no

# The following two entries demonstrate how to share a directory so that two
# users can place files there that will be owned by the specific users. In this
# setup, the directory should be writable by both users and should have the
# sticky bit set on it to prevent abuse. Obviously this could be extended to
# as many users as required.
;[myshare]
;   comment = Mary's and Fred's stuff
;   path = /usr/somewhere/shared
;   valid users = mary fred
;   public = no
;   writable = yes
;   printable = no
;   create mask = 0765
I don't remember modifying anything here other than the workgroup name yet.

Code: Select all
nsa325v2
I don't think I manually modified this file, since hostnamectl set-hostname NSA325v2 already did that.

Code: Select all
#
# /etc/hosts: static lookup table for host names
#

#<ip-address>   <hostname.domain.org>   <hostname>
127.0.0.1   localhost.localdomain   localhost nsa325v2
::1      localhost.localdomain   localhost

# End of file
Added nsa325v2 after localhost

Maybe someone can figure out what I did wrong. Also, what does the command "ip addr add" do to the filesystem exactly? Does it modify a file?
Last edited by archon on Sat Aug 30, 2014 11:11 pm, edited 1 time in total.
archon
 
Posts: 11
Joined: Thu Aug 28, 2014 5:32 pm

Re: Zyxel NSA325v2 unreachable on network

Postby pepedog » Thu Aug 28, 2014 7:08 pm

The rootfs is already configured to get an ip address via dhcpcd, so hunt for it
It's possibly the interface might not be coming up because of a quirk, plug in USB keyboard and use it blind, log in and poweroff. Disconnect power for 5 seconds
pepedog
Developer
 
Posts: 2431
Joined: Mon Jun 07, 2010 3:30 pm
Location: London UK

Re: Zyxel NSA325v2 unreachable on network

Postby archon » Thu Aug 28, 2014 7:45 pm

So you're saying the device does have an IP address and is reachable from the network, but that address isn't any of those previously mentioned, and somehow it's been assigned a new one? In that case, why doesn't it show up in my router's device list?

So to recap your instructions...

1. Plug in USB keyboard
2. Type "root" + Enter (twice?)
3. Type "init 0" + Enter
4. Unplug the device for 5 seconds

Is this correct?
archon
 
Posts: 11
Joined: Thu Aug 28, 2014 5:32 pm

Re: Zyxel NSA325v2 unreachable on network

Postby pepedog » Thu Aug 28, 2014 8:01 pm

Step 3, the command is poweroff. Arch doesn't use init, it's systemd.
Take your time logging in.
Ctrl alt del works without logging in, but you want poweroff
pepedog
Developer
 
Posts: 2431
Joined: Mon Jun 07, 2010 3:30 pm
Location: London UK

Re: Zyxel NSA325v2 unreachable on network

Postby WarheadsSE » Thu Aug 28, 2014 8:02 pm

Code: Select all
systemctl poweroff

systemd, after all.

And those IP commands add a static ip, for that runtime instances. Not permanently.
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6730
Joined: Mon Oct 18, 2010 2:12 pm

Re: Zyxel NSA325v2 unreachable on network

Postby archon » Thu Aug 28, 2014 8:53 pm

No dice. I made several attempts, took a long break between each step, typed very carefully, tried with different USB ports, tried hooking up the keyboard before or after powering on. No reaction at all from the device, with the exception of when I plugged the keyboard while it was on (green led flashed briefly).

And those IP commands add a static ip, for that runtime instances. Not permanently.

Good to know. Could it be that running that command disabled DHCP though? So not only it didn't keep the static IP I set, but prevented the device from getting a new one?

Also, could the device be bricked?
archon
 
Posts: 11
Joined: Thu Aug 28, 2014 5:32 pm

Re: Zyxel NSA325v2 unreachable on network

Postby WarheadsSE » Thu Aug 28, 2014 9:08 pm

It is not bricked.

And no, they didn't magically disable dhcp. You just added a manually configured IP for a single instance.
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6730
Joined: Mon Oct 18, 2010 2:12 pm

Re: Zyxel NSA325v2 unreachable on network

Postby archon » Thu Aug 28, 2014 9:26 pm

Alright then. I guess I'll have to return the device, since it's of no use to me if I can't access it from the network, and I've already spent hours looking online for a solution. Thanks for the help though.
archon
 
Posts: 11
Joined: Thu Aug 28, 2014 5:32 pm

Re: Zyxel NSA325v2 unreachable on network

Postby WarheadsSE » Thu Aug 28, 2014 9:31 pm

It can be addressed.

The simplest, and most straight forward is to attach a 3.3v TTL serial adapter to it, and bring up the console.
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6730
Joined: Mon Oct 18, 2010 2:12 pm

Re: Zyxel NSA325v2 unreachable on network

Postby archon » Thu Aug 28, 2014 9:49 pm

I might have one of those at the office.

Just out of curiosity, what are the less simple and less straightforward solutions?
archon
 
Posts: 11
Joined: Thu Aug 28, 2014 5:32 pm

Next

Return to [Please read announcement] Community-Supported Devices

Who is online

Users browsing this forum: No registered users and 1 guest