LAN SETUP problem with defect LAN port

[Jean-Claude]

logged in with putty - output of ifconfig :

ifconfig
eth1 Link encap:Ethernet HWaddr 00:08:9B:CF:89:1D
inet addr:172.19.3.32 Bcast:172.19.3.255 Mask:255.255.255.0
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:61616 errors:0 dropped:0 overruns:0 frame:0
TX packets:72337 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:15453024 (14.7 MiB) TX bytes:56845154 (54.2 MiB)
Interrupt:17 Memory:feae0000-feb00000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:263687 errors:0 dropped:0 overruns:0 frame:0
TX packets:263687 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:94427287 (90.0 MiB) TX bytes:94427287 (90.0 MiB)

am I right in supposing that there should also have been an eth0 in this output ?
I entered the following command :
ifconfig eth1 172.19.3.22 netmask 255.255.255.0

after which the cursor didn't return - but this could be normal as I've change the IP address of LAN2.
and indeed, after reconnecting to the new address the UIweb interface reappeared, so did putty

ifconfig now reads as follows :

ifconfig
eth1 Link encap:Ethernet HWaddr 00:08:9B:CF:89:1D
inet addr:172.19.3.22 Bcast:172.19.3.255 Mask:255.255.255.0
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:63117 errors:0 dropped:0 overruns:0 frame:0
TX packets:74549 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:15649419 (14.9 MiB) TX bytes:58443085 (55.7 MiB)
Interrupt:17 Memory:feae0000-feb00000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:266250 errors:0 dropped:0 overruns:0 frame:0
TX packets:266250 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:98966820 (94.3 MiB) TX bytes:98966820 (94.3 MiB)

now I'm gonna try to reboot the server, to see if the IP configuration remains active........ let's hope so

[Jean-Claude]

no go - after rebooting the server, LAN2 is back to a DHCP assigned adress (172.19.3.33 this time)
is there any way to tell ifconfig to "lock" the configuration, or to de-activate DHCP on eth1 ?

I guess I'd better start some googling "ifconfig" to see what it's options are.

[Jean-Claude]

read the "ifconfig" documentation on internet - doesn't look as if there is something I can really use.
is there some configuration file which is read during startup and which I can alter with putty ?

[doktornotor]

What on earth are you trying to do here? ifconfig manual configuration via SSH obviously will NOT stick across reboots. Look at [eth0], [eth1] and [Network] sections of /etc/config/uLinux.conf

[Jean-Claude]

well, maybey that's obvious for you, but up to an hour ago I had hardly used of "ifconfig" so .........

I'm browsing /etc/config, but all I can find with *config* is the following :
ls -lia *config*
6819 -rw-r--r-- 1 admin administ 340 Oct 27 2013 sms_config.conf

but then I did the following :

grep eth1 *
MyUPnPMediaSvr.conf:#network_interface=eth1
NetLinks.conf:Interface2=eth1
uLinux.conf:Default GW Device = eth1
uLinux.conf:[eth1]
uLinux.conf:Group 1 = eth1
[/etc/config] #
[/etc/config] # grep eth0 *
NetLinks.conf:Interface1=eth0
uLinux.conf:[eth0]
uLinux.conf:Interface = eth0
uLinux.conf:Group 0 = eth0
vpn.conf:interface = eth0

uLinux.conf ......... ah yes, "conf", not "config".......
vi I suppose ? Must be 20 years I last used that one. Let's have a go at it, shall we.

[doktornotor]

Code: Select all

cat /etc/config/uLinux.conf

Post the relevant sections mentioned above here.

[Jean-Claude]

I changed some values in the [eth1] section :
[eth1]
Configure = TRUE
Use DHCP = FALSE
Usage = DHCP
IP Address = 172.19.3.22
Subnet Mask = 255.255.0.0
Broadcast = 172.19.255.255
Gateway = 172.19.3.1

I'm not sure about the USAGE switch - what do I need to set to de-activate DHCP ? Or is USE DHCP = FALSE sufficient ?

[Jean-Claude]

some more sections :
[Network]
Interface Number = 2
DNS = 0.0.0.0
WINS IP = 0.0.0.0
WINS Enable = False
BONDING Support = FALSE
BONDING01 = Interface1
BONDING02 = Interface2
Domain Name Server 1 = 193.121.171.135
Domain Name Server 2 = 193.74.208.135
Default GW Device = eth1
DNS type = auto
Advanced Bonding Support = TRUE
uLinux Upgrade = TRUE
IP Security = 3
IPV6 = FALSE
IPV6 Domain Name Server 1 = ::
IPV6 Domain Name Server 2 = ::
[bond0]
Bonding Mode = 1
Configure = FALSE
Use DHCP = TRUE
Usage = DHCP
IP Address = 169.254.100.100
Subnet Mask = 255.255.0.0
Broadcast = 192.168.255.255
Gateway = 169.254.100.100
Speed = auto
MTU = 1500
vlan_id = 0
vlan_enable = FALSE
Enable Autoconf = TRUE
Use DHCPV6 = FALSE
IPV6 Address = /0
IPV6 Gateway = ::/0
Use RADVD = FALSE
RA_PREFIX = /0
[eth0]
Configure = FALSE
Use DHCP = TRUE
Usage = DHCP
IP Address = 169.254.100.100
Subnet Mask = 255.255.0.0
Broadcast = 172.19.255.255
Gateway = 169.254.100.100
Speed = auto
MTU = 1500
Mac Addresss =
vlan_id = 0
vlan_enable = FALSE
Enable Autoconf = TRUE
Use DHCPV6 = FALSE
IPV6 Address = /0
IPV6 Gateway = ::/0
Use RADVD = FALSE
RA_PREFIX = /0
[eth1]
Configure = TRUE
Use DHCP = FALSE
Usage = DHCP
IP Address = 172.19.3.22
Subnet Mask = 255.255.0.0
Broadcast = 172.19.255.255
Gateway = 172.19.3.1
Speed = auto
MTU = 1500
Mac Addresss = 00:08:9b:cf:89:1d
vlan_id = 0
vlan_enable = FALSE
Enable Autoconf = TRUE
Use DHCPV6 = FALSE
IPV6 Address = /0
IPV6 Gateway = ::/0
Use RADVD = FALSE
RA_PREFIX = /0

that should cover everything .......

[Jean-Claude]

right - just had the most ingenious idea to look into the /etc/config/uLinux.conf setup of my other QNAP's
yes, its's USAGE = STATIC

changed the config, rebooted the QNAP, wait and see.

[Jean-Claude]

SUCCESS !
the nas restarted on the requested IP adress, so all my links on the network are active again.
many thanks to all contributers,a nd especially to doktornotor who gave the winning hint.

[doktornotor]

Well, all good then. Is the web GUI network configuration working now?

[Jean-Claude]

no, it's not, it still has the spinner on it. and Qfinder still doesn't show my Qnap.
but it's booting on the correct IP address so for me this is the most important part. I rarely have to go into the web GUI, and the other pages do seem to be working.
I've created a ticket for this earlier on, maybey I'll get some other updates from the support team, who knows.
thanks a lot.

[doktornotor]

Yeah, good luck with QNAP support.

[AlastairStevenson]

You did OK there, well done.
Sorry for the misdirection on ifconfig sticking - and I was forgetting DHCP would still be active. doh!

[Jean-Claude]

got an answer from technical support :

Hi,
it should be the system configuration file failed.
Please follow steps below to recover it.
1. Power off the NAS. Remove the HDD
2. Power on the NAS without any disk attached
3. After a short beep and a long beep,Run QNAP Finder, it will find the NAS.
Note: Do not re-initialize when the QNAP Finder prompt a message, if you have some useful data in the disk
4. Plug all disks back to NAS in original order.
push in till the previous HDD led flashes constantly green.(Not Blinking)
5. Connect the NAS by SSH port 22, login as admin password :admin
(Putty Tutorial: http://www.webmasters-central.com/artic ... sh-client/ )
6. Issue the commands to check disk space
# config_util 1 --> Start mirroring of the first partitions.
# storage_boot_init 1
# df
7. Please issue the following commands to copy back default configfile
# cp /etc/default_config/uLinux.conf /mnt/HDA_ROOT/.config/
# rm -r /etc/config
# ln -sf /mnt/HDA_ROOT/.config /etc/config
# setcfg -f /etc/config/uLinux.conf Misc configured TRUE
# reboot
8. The above procedure will reset the configuration back to default and then you need to reconfigure it.
But all the share should be available now.
Do NOT to re-initialize the HDD,which would wipe out the data.​

If not works, we need a remote session for this issue.
I think we can schedule on Monday to Wednesday before 10 am.
If you are willing to have the remote session.
Please advice the time and TeamViewer access information in advance.