Well, the "SIOCSIFFLAGS: Cannot assign requested address" error was probably caused by my IP address manipulation via ip tool. I tried to set IP address via 'ip' before, in case it would work
Code:
$ ip address add 172.16.172.1/24 dev eth0
[...]
$ ip address delete 172.16.172.1/24 dev eth0
and removing did the trick.
Now I can assign address to eth0:0 and ifconfig recognizes it
Code:
eth0 Link encap:Ethernet HWaddr 00:1A:4D:6E:B0:99
inet addr:1.2.3.4 Bcast:1.2.3.255 Mask:255.255.255.0
inet6 addr: fe80::21a:4dff:fe6e:b099/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:9211629 errors:0 dropped:798 overruns:0 frame:0
TX packets:1943239 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3906439522 (3725.4 Mb) TX bytes:275619695 (262.8 Mb)
Interrupt:41 Base address:0x6000
eth0:0 Link encap:Ethernet HWaddr 00:1A:4D:6E:B0:99
inet addr:172.16.172.1 Bcast:172.16.172.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Interrupt:41 Base address:0x6000
However, when I try to ping something (MIMO in my case) I get this error
Code:
root@router:~# ping 172.16.172.31
PING 172.16.172.31 (172.16.172.31) 56(84) bytes of data.
ping: sendmsg: Operation not permitted
I experienced similar errors few times before (with routerboard-based AP) and solution was put switch between device and router. This time I can't (and don't want to) put switch between MIMO and router.
Of course I tried Google, but all I came across was "is your cable plugged in?", "does your NIC actually work?", etc. I'm pretty sure wiring and NIC are OK, cause there is working network over eth0, but I can't completely rule out hardware malfunction.