NAS Zyxel 325v2 - wake on lan problems

is there sth with kernel 3.13.1-kirkwood-tld-2 which I am still using that make problems in WOL working ?
I was searching for many hours how to trigger my NAS from directly attached router, read many many articles, with no results...

LED on the interface is blinking when packets arrives interface, but Zyxel doesn't boot ...

on serial console connected to this NAS i have:

NAS# ethtool eth0
Settings for eth[ 862.121840] mv643xx_eth_port mv643xx_eth_port.0 eth0: link down
0:
Supported p[ 862.128297] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 1000 Mb/s, full duplex, flow control disabled
orts: [ TP MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supported pause frame use: No
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Speed: 1000Mb/s
Duplex: Full
Port: MII
PHYAD: 1
Transceiver: external
Auto-negotiation: on
Supports Wake-on: g
Wake-on: g
Link detected: yes


when system is goning down halt is called as: halt -d -f -p

NAS# ip addr ls
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
link/ether 00<MACADDRESS_HERE> brd ff:ff:ff:ff:ff:ff
inet 192.168.111.22/24 brd 192.168.1.255 scope global eth0
valid_lft forever preferred_lft forever
inet6 fe80::250:43ff:fe00:202/64 scope link
valid_lft forever preferred_lft forever


I give up ... this post is my last resort, please help me

if this matters - system is booted every time from pendrive, as in thread:
http://forum.doozan.com/read.php?2,14351,15594#msg-15594

but I dont think so that this has any importance for WOL

marcint43,

The NSA325 has 2 different MAC addresses (Zyxel changed it). So when you run etherwake, it should use the Marvell MAC address (look for it outside on the box case, or in original boot log if you have the log).

Mostl likely, it starts with 4C:9E

etherwake 4C:9E:FF:xx:xx:xx

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

no any sticker outside :(

some network related variables:

Marvell>> printenv

ipaddr=10.4.52.165
serverip=10.4.52.7
rootpath=/srv/ubuntu
netmask=255.255.255.0

PRODUCT_NAME=NSA-325v2

ethprime=egiga0
bootargs_root=root=/dev/nfs rw
bootargs_end=:::DB88FXX81:eth0:none

ethaddr=00:50:43:<here is my mac on my linux>
ethmtu=1500

mvPhoneConfig=mv_phone_config=dev[0]:fxs,dev[1]:fxo
mvNetConfig=mv_net_config=(00:11:88:0f:62:81,0:1:2:3),mtu=1500
usb0Mode=host
yuk_ethaddr=00:00:00:EE:51:81
netretry=no
rcvrip=169.254.100.100
loadaddr=0x02000000
autoload=no
image_multi=yes
ethact=egiga0



egiga0 ?? I have eth0 interface after boot

marcint43,

Look for this original MAC address. Perhaps it is inside the box. WOL will not work without it.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

YEAH :))) That was solution :)

Thank you so much !!! :)

FYI:
mac addres starts with: 60:d8:19:xx:xx:xx

Company Hon Hai Precision Ind. Co.,Ltd.
Address Shanghai 201613 CHINA

marcint43 Wrote:
-------------------------------------------------------
> FYI:
> mac addres starts with: 60:d8:19:xx:xx:xx
>
> Company Hon Hai Precision Ind. Co.,Ltd.
> Address Shanghai 201613 CHINA

That's Hon Hai MAC address starts with 60:d8:19

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

my mistake, I pasted not this MAC, my zyxel starts with: 10:7b:ef:xx:xx:xx


PS. ...few minutes ago stopped to work (not booting after shutdown)... for now I dont know why

Hi marcint43,

have you flashed the uboot from bodhi?

After I flashed the latest uboot on my NSA325v2, my WOL MAC was switched to the default
MAC 00:50:43:00:xx:xx. I' ve tried to change the MAC in the uboot settings, without success.

But the WOL on the default MAC works fine for me now.