Fwd: Secondary IP

13 views

Skip to first unread message

T Gillett

unread,

Jun 10, 2015, 9:41:59 PM6/10/15

to Darío G. Díaz, village-telco-dev

Hi Dario

With the configuration shown in your screenshot, you have two static IP addresses on the WAN interface.

So you should be able to ping either of these addresses from another device attached to the WAN network and set up with the appropriate network configuration to allow it to work on either of the subnets. - 10.100.1.x and 10.200.1.x

I don't think there is a lot of point in using this configuration as the two IPs are essentially providing the same access.

The real purpose of the Secondary WAN IP address is to provide a static address in the situation where the Primary address is set up by DHCP.

The static Secondary IP address allows you to do remote management of the node, even if you do not know what the Primary IP address has been set to from the DHCP server.

The Secondary IP address has no Gateway/Default Route or DNS parameters set, and has a Netmask of 255.255.255.0

It does not need the other parameters as it is only intended to be used for remote management.

Of course, each node has to be set up with a discrete Secondary IP address that is known to the central management device before it is deployed.

Does this make sense?

Regards

Terry

On Thu, Jun 11, 2015 at 10:30 AM, Darío G. Díaz <dario...@gmail.com> wrote:

Hi Terry

Set up a secondary IP in Device3 and not walk ...
I put the IP 10.100.1.22 is another pool of ips that I have for testing. What if they do not also have to add the gateway and which other parameter.

Regards

Dario

Config secondary IP.jpg

Darío G. Díaz

unread,

Jun 10, 2015, 11:50:39 PM6/10/15

to T Gillett, village-telco-dev

Hi Terry

I have two opinions about it:

1- According to your explanation this solves my DeviceXX remote administration, which I've been asking these days. I understand how it works and I feel good, plus I'll try.

2- I intend to of this configuration is that if I drop a route (Primary IP) traffic can leave the other (Secondary IP) or have two routes available to traffic can go out the best route.
Can also be the case that there are two cells mesh network and both are interconnected by the Secondary IP and can carry traffic.

I hope I've explained to you the meaning for me of this feature.

Regards

Dario

T Gillett

unread,

Jun 11, 2015, 1:54:07 AM6/11/15

to Darío G. Díaz, village-telco-dev

Hi Dario

OK I see what you mean about using a second route.

I am not sure how this will work.

The Secondary IP address is set up in a script with the ifconfig command.

So I guess you would have to use the ifconfig command to set up the route and dns parameters.

You will have research how to do this and if it is possible.

Regards
Terry

Darío G. Díaz

unread,

Jun 11, 2015, 8:52:44 AM6/11/15

to T Gillett, village-telco-dev

Hi Terry

This issue requires more development time and also I think it also has to do with the system of dynamic or static routing traffic and you have to think through how.

At the moment I'm going to start testing as an option for remote administration of nodes.

When income from SSH and run a "ifconfig" does not show the IP Secondary or interface that is generated, as I can see this??

Regards

Dario

T Gillett

unread,

Jun 11, 2015, 9:20:31 AM6/11/15

to Darío G. Díaz, village-telco-dev

Hi Dario

The ifconfig output should look something like below.

The WAN secondary IP is shown at eth1:9

You need to have the WAN Port set to Ethernet.

What kind of device are you testing on?

Is it WR841?

Ver 8 or Ver 9?

Could you send ifconfig output please?

Regards

Terry

root@MP2-20:/# ifconfig
bat0      Link encap:Ethernet HWaddr 1E:DC:E0:E2:DB:39
          inet6 addr: fe80::1cdc:e0ff:fee2:db39/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:4 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:29 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:168 (168.0 B) TX bytes:0 (0.0 B)

br-lan    Link encap:Ethernet HWaddr A8:40:41:13:74:0F
          inet addr:10.130.1.20 Bcast:10.130.1.255 Mask:255.255.255.0
          inet6 addr: fe80::aa40:41ff:fe13:740f/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:53 errors:0 dropped:0 overruns:0 frame:0
          TX packets:38 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:5121 (5.0 KiB) TX bytes:4319 (4.2 KiB)

br-lan:9 Link encap:Ethernet HWaddr A8:40:41:13:74:0F
          inet addr:172.31.255.254 Bcast:172.31.255.255 Mask:255.255.255.252
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

eth0      Link encap:Ethernet HWaddr A8:40:41:13:74:0F
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:79 errors:0 dropped:0 overruns:0 frame:0
          TX packets:36 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:10089 (9.8 KiB) TX bytes:3863 (3.7 KiB)
          Interrupt:5

eth1      Link encap:Ethernet HWaddr A8:40:41:13:74:0E
          inet addr:192.168.1.124 Bcast:192.168.1.255 Mask:255.255.255.0
          inet6 addr: fe80::aa40:41ff:fe13:740e/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:72 errors:0 dropped:0 overruns:0 frame:0
          TX packets:44 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:6556 (6.4 KiB) TX bytes:4536 (4.4 KiB)
          Interrupt:4

eth1:9    Link encap:Ethernet HWaddr A8:40:41:13:74:0E
          inet addr:10.0.1.20 Bcast:10.0.1.255 Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          Interrupt:4

lo        Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:65536 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

wlan0     Link encap:Ethernet HWaddr AA:40:41:13:74:0C
          inet6 addr: fe80::a840:41ff:fe13:740c/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:38 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B) TX bytes:5767 (5.6 KiB)

wlan0-1   Link encap:Ethernet HWaddr A8:40:41:13:74:0C
          inet addr:10.10.1.20 Bcast:10.10.1.255 Mask:255.255.255.0
          inet6 addr: fe80::aa40:41ff:fe13:740c/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1532 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:37 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B) TX bytes:3652 (3.5 KiB)

root@MP2-20:/#

T Gillett

unread,

Jun 11, 2015, 9:31:25 AM6/11/15

to Darío G. Díaz, village-telco-dev

Some info on setting default routes and DNS from the command line / scripts:
    http://www.computertechblog.com/assign-a-static-ip-dns-gateway-with-ifconfig-and-route-add/
    http://linux-ip.net/html/basic-changing.html
    http://www.cyberciti.biz/faq/linux-setup-default-gateway-with-route-command/

An example to add a default route to the Secondary address:

Before:
root@MP2-20:/# route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
default         192.168.1.254   0.0.0.0         UG    0      0        0 eth1
10.0.1.0        *               255.255.255.0   U     0      0        0 eth1
10.10.1.0       *               255.255.255.0   U     0      0        0 wlan0-1
10.130.1.0      *               255.255.255.0   U     0      0        0 br-lan
172.31.255.252 *               255.255.255.252 U     0      0        0 br-lan
192.168.1.0     *               255.255.255.0   U     0      0        0 eth1

Command:
root@MP2-20:/# route add default gw 10.0.1.1 eth1:9                #<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

After:
root@MP2-20:/# route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
default         10.0.1.1        0.0.0.0         UG    0      0        0 eth1
default         192.168.1.254   0.0.0.0         UG    0      0        0 eth1
10.0.1.0        *               255.255.255.0   U     0      0        0 eth1
10.10.1.0       *               255.255.255.0   U     0      0        0 wlan0-1
10.130.1.0      *               255.255.255.0   U     0      0        0 br-lan
172.31.255.252 *               255.255.255.252 U     0      0        0 br-lan
192.168.1.0     *               255.255.255.0   U     0      0        0 eth1
root@MP2-20:/#

DNS:
root@MP2-20:/# cat /etc/resolv.conf
# Interface lan
nameserver 8.8.8.8
# Interface wan
nameserver 8.8.8.8
nameserver 8.8.4.4
root@MP2-20:/#

Network details:

root@MP2-20:/# ifconfig
bat0      Link encap:Ethernet HWaddr 1E:DC:E0:E2:DB:39
          inet6 addr: fe80::1cdc:e0ff:fee2:db39/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

          RX packets:183 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:70 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:7686 (7.5 KiB) TX bytes:0 (0.0 B)

br-lan    Link encap:Ethernet HWaddr A8:40:41:13:74:0F
          inet addr:10.130.1.20 Bcast:10.130.1.255 Mask:255.255.255.0
          inet6 addr: fe80::aa40:41ff:fe13:740f/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

          RX packets:1010 errors:0 dropped:0 overruns:0 frame:0
          TX packets:650 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:51214 (50.0 KiB) TX bytes:68133 (66.5 KiB)

br-lan:9 Link encap:Ethernet HWaddr A8:40:41:13:74:0F
          inet addr:172.31.255.254 Bcast:172.31.255.255 Mask:255.255.255.252
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

eth0      Link encap:Ethernet HWaddr A8:40:41:13:74:0F
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

          RX packets:905 errors:0 dropped:0 overruns:0 frame:0
          TX packets:785 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:65952 (64.4 KiB) TX bytes:71023 (69.3 KiB)

          Interrupt:5

eth1      Link encap:Ethernet HWaddr A8:40:41:13:74:0E
          inet addr:192.168.1.124 Bcast:192.168.1.255 Mask:255.255.255.0
          inet6 addr: fe80::aa40:41ff:fe13:740e/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

          RX packets:1815 errors:0 dropped:0 overruns:0 frame:0
          TX packets:226 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:124021 (121.1 KiB) TX bytes:19979 (19.5 KiB)

          Interrupt:4

eth1:9    Link encap:Ethernet HWaddr A8:40:41:13:74:0E
          inet addr:10.0.1.20 Bcast:10.0.1.255 Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          Interrupt:4

lo        Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:65536 Metric:1

          RX packets:5 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:560 (560.0 B) TX bytes:560 (560.0 B)

wlan0     Link encap:Ethernet HWaddr AA:40:41:13:74:0C
          inet6 addr: fe80::a840:41ff:fe13:740c/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0

          TX packets:256 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B) TX bytes:20009 (19.5 KiB)

wlan0-1   Link encap:Ethernet HWaddr A8:40:41:13:74:0C
          inet addr:10.10.1.20 Bcast:10.10.1.255 Mask:255.255.255.0
          inet6 addr: fe80::aa40:41ff:fe13:740c/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1532 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0

          TX packets:1824 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B) TX bytes:153904 (150.2 KiB)

root@MP2-20:/#

Darío G. Díaz

unread,

Jun 11, 2015, 9:45:10 AM6/11/15

to T Gillett, village-telco-dev

Terry

I send you the requested information
Here you can see the interface of the "Secondary IP" does not appear

OpenWrt Barrier Breaker 14.07 r44952 TL-WR841N/ND

Village Telco - Small Enterprise Campus Network

Version:     SECN-3_0-RC1b TLWR841 v8 ----- Device
Build date: 2015-05-19-17:32
GitHub:      vt-firmware secn_3.0-RC2-4-g42470342e5

root@TP-22:~# ifconfig
bat0      Link encap:Ethernet HWaddr 5E:78:E4:87:DB:BF
          inet6 addr: fe80::5c78:e4ff:fe87:dbbf/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

          RX packets:161 errors:0 dropped:0 overruns:0 frame:0
          TX packets:120 errors:0 dropped:42 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:14556 (14.2 KiB) TX bytes:12902 (12.5 KiB)

br-lan    Link encap:Ethernet HWaddr F8:1A:67:F6:38:98
          inet addr:10.130.1.22 Bcast:10.130.1.255 Mask:255.255.255.0
          inet6 addr: fe80::fa1a:67ff:fef6:3898/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

          RX packets:261 errors:0 dropped:0 overruns:0 frame:0
          TX packets:52 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:25209 (24.6 KiB) TX bytes:5609 (5.4 KiB)

br-lan:9 Link encap:Ethernet HWaddr F8:1A:67:F6:38:98

inet addr:172.31.255.254 Bcast:172.31.255.255 Mask:255.255.255.252
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

br-wan    Link encap:Ethernet HWaddr 5E:78:E4:87:DB:BF
          inet addr:10.200.1.22 Bcast:10.200.1.255 Mask:255.255.255.0
          inet6 addr: fe80::5c78:e4ff:fe87:dbbf/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

          RX packets:167 errors:0 dropped:0 overruns:0 frame:0
          TX packets:151 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:12382 (12.0 KiB) TX bytes:14444 (14.1 KiB)

eth0      Link encap:Ethernet HWaddr F8:1A:67:F6:38:97
          UP BROADCAST MULTICAST MTU:1500 Metric:1

RX packets:0 errors:0 dropped:0 overruns:0 frame:0

TX packets:0 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
          Interrupt:4

eth1      Link encap:Ethernet HWaddr F8:1A:67:F6:38:98

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

          RX packets:366 errors:0 dropped:14 overruns:0 frame:0
          TX packets:43 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:37231 (36.3 KiB) TX bytes:4651 (4.5 KiB)
          Interrupt:5

lo        Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:65536 Metric:1

          RX packets:47 errors:0 dropped:0 overruns:0 frame:0
          TX packets:47 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:4484 (4.3 KiB) TX bytes:4484 (4.3 KiB)

wlan0     Link encap:Ethernet HWaddr FA:1A:67:F6:38:98
          inet6 addr: fe80::f81a:67ff:fef6:3898/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0

          TX packets:248 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B) TX bytes:32373 (31.6 KiB)

wlan0-1   Link encap:Ethernet HWaddr F8:1A:67:F6:38:98

inet addr:10.10.1.20 Bcast:10.10.1.255 Mask:255.255.255.0

inet6 addr: fe80::fa1a:67ff:fef6:3898/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:1532 Metric:1

          RX packets:2133 errors:0 dropped:24 overruns:0 frame:0
          TX packets:1131 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:149492 (145.9 KiB) TX bytes:103740 (101.3 KiB)

Ing. Darío G. Díaz
Cel.: 02344-15-429334
Skype: dariogdiaz

Darío G. Díaz

unread,

Jun 11, 2015, 9:48:56 AM6/11/15

to T Gillett, village-telco-dev

Hi Terry

Thansk for information!!
I will read all this information and try to see how to build the routing of traffic.

Regards
Dario

T Gillett

unread,

Jun 16, 2015, 4:44:47 PM6/16/15

to Darío G. Díaz, village-telco-dev

Hi Dario

Excellent!

So that all appears to be working correctly and you should be able to set it up in your network now.

I will post a new updated firmware to the VT Downloads page later today.

Many thanks for your testing work.

Regards
Terry

---------- Forwarded message ----------
From: "Darío G. Díaz" <dario...@gmail.com>
Date: 17/06/2015 1:16 AM
Subject: Re: Secondary IP
To: "T Gillett" <tgil...@gmail.com>
Cc:

Hi Terry

I am sending you the information after following the instructions you sent me to install the new firmware required.
I see significant progress ... we go for more !!!

root@TP-20:~# brctl show
bridge name     bridge id               STP enabled     interfaces
br-lan         7fff.f81a67f63898         no             eth1
                                                          wlan0
br-wan          7fff.f81a67f63897         no              eth0
                                                          bat0
root@TP-20:~# ifconfig
bat0      Link encap:Ethernet HWaddr D2:6A:87:18:D7:AB
          inet6 addr: fe80::d06a:87ff:fe18:d7ab/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

RX packets:79 errors:0 dropped:0 overruns:0 frame:0

          TX packets:34 errors:0 dropped:72 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:6192 (6.0 KiB) TX bytes:3588 (3.5 KiB)

br-lan Link encap:Ethernet HWaddr F8:1A:67:F6:38:98

inet addr:10.130.1.20 Bcast:10.130.1.255 Mask:255.255.255.0

inet6 addr: fe80::fa1a:67ff:fef6:3898/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

          RX packets:735 errors:0 dropped:0 overruns:0 frame:0
          TX packets:488 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:76613 (74.8 KiB) TX bytes:90373 (88.2 KiB)

br-lan:9 Link encap:Ethernet HWaddr F8:1A:67:F6:38:98
inet addr:172.31.255.254 Bcast:172.31.255.255 Mask:255.255.255.252
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

br-wan    Link encap:Ethernet HWaddr F8:1A:67:F6:38:97
          inet addr:10.200.1.56 Bcast:10.200.1.255 Mask:255.255.255.0
          inet6 addr: fe80::fa1a:67ff:fef6:3897/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

          RX packets:103 errors:0 dropped:0 overruns:0 frame:0
          TX packets:80 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:6236 (6.0 KiB) TX bytes:10840 (10.5 KiB)

br-wan:9 Link encap:Ethernet HWaddr F8:1A:67:F6:38:97

inet addr:10.0.1.20 Bcast:10.0.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

eth0 Link encap:Ethernet HWaddr F8:1A:67:F6:38:97

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

          RX packets:23 errors:0 dropped:0 overruns:0 frame:0
          TX packets:30 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1510 (1.4 KiB) TX bytes:1426 (1.3 KiB)

          Interrupt:4

eth1      Link encap:Ethernet HWaddr F8:1A:67:F6:38:98
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

          RX packets:817 errors:0 dropped:10 overruns:0 frame:0
          TX packets:476 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:94586 (92.3 KiB) TX bytes:89197 (87.1 KiB)

          Interrupt:5

lo        Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:65536 Metric:1

          RX packets:259 errors:0 dropped:0 overruns:0 frame:0
          TX packets:259 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:18272 (17.8 KiB) TX bytes:18272 (17.8 KiB)

wlan0     Link encap:Ethernet HWaddr FA:1A:67:F6:38:98
          inet6 addr: fe80::f81a:67ff:fef6:3898/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0

          TX packets:290 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B) TX bytes:47632 (46.5 KiB)

wlan0-1   Link encap:Ethernet HWaddr F8:1A:67:F6:38:98
          inet addr:10.10.1.20 Bcast:10.10.1.255 Mask:255.255.255.0
          inet6 addr: fe80::fa1a:67ff:fef6:3898/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1532 Metric:1

          RX packets:1615 errors:0 dropped:21 overruns:0 frame:0
          TX packets:838 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:115314 (112.6 KiB) TX bytes:75432 (73.6 KiB)

root@TP-20:~#

Regards
Dario

2015-06-16 3:37 GMT-03:00 T Gillett <tgil...@gmail.com>:

Hi Dario

Attached is an updated firmware for WR841 v8. Would you please try it out on your WR841 device.

Once the new firmware is installed, connect to the device with your browser at 10.130.1.20.

Please test as follows, with no other changes:

1. Go to the WAN page and a) set the WAN Port to "Mesh" and b) set the IP Mode to "DHCP"
2. Click Save.
3. When the page refreshes, check that the settings were saved correctly.
4. Reboot
5. Connect the WR841 WAN Ethernet port to your LAN router via Ethernet cable, so it can get a DHCP address assigned.
6. Login in with telnet to 10.130.1.20
7. Run the ifconfig command and capture the output. Also the brctl show command.

The WAN port will have eth0 and bat0 bridged, and should be assigned a DHCP address from your LAN router via Ethernet.

The ifconfig command should show br-wan with the DHCP IP address, and br-wan:9 with the static IP address.

The WAN page should display the WAN Primary IP address

Please let me know how it goes and send me the command outputs.

regards
Terry

On Tue, Jun 16, 2015 at 3:22 PM, T Gillett <tgil...@gmail.com> wrote:
I thought it must be late there!

We can talk again tomorrow when you have the new firmware to test.

Ciao.

On Tue, Jun 16, 2015 at 3:17 PM, Darío G. Díaz <dario...@gmail.com> wrote:

Hi Terry

Do not worry, when you finish making corrections in the SECN, you send it to me and then I test it.
It is very late here and I sleep because I had an intense day.

Regards
Dario

2015-06-16 2:07 GMT-03:00 T Gillett <tgil...@gmail.com>:

Hi Dario

OK Good progress.

The command works OK; it is just the script that has some error in it.

I will edit it and test it on my WR842, then send you a new firmware to test.

But it will be a couple of hours time.

Thanks
Terry

On Tue, Jun 16, 2015 at 2:59 PM, Darío G. Díaz <dario...@gmail.com> wrote:
Terry

Sending out commands and introduced config.
I made a ping from my notebook to Device C (ip 10.0.0.22) and responded well.

root@TP-22:~# ifconfig br-wan:9 10.0.0.22 netmask 255.255.255.0
root@TP-22:~# ifconfig
bat0 Link encap:Ethernet HWaddr 62:88:79:D0:E0:F6
inet6 addr: fe80::6088:79ff:fed0:e0f6/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

          RX packets:927 errors:0 dropped:0 overruns:0 frame:0
          TX packets:825 errors:0 dropped:27 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:237346 (231.7 KiB) TX bytes:156422 (152.7 KiB)

br-lan    Link encap:Ethernet HWaddr F8:1A:67:F6:38:98
          inet addr:10.130.1.22 Bcast:10.130.1.255 Mask:255.255.255.0
          inet6 addr: fe80::fa1a:67ff:fef6:3898/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

          RX packets:1716 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1420 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:220155 (214.9 KiB) TX bytes:321737 (314.1 KiB)

br-lan:9 Link encap:Ethernet HWaddr F8:1A:67:F6:38:98
inet addr:172.31.255.254 Bcast:172.31.255.255 Mask:255.255.255.252
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

br-wan Link encap:Ethernet HWaddr 62:88:79:D0:E0:F6

inet addr:10.200.1.22 Bcast:10.200.1.255 Mask:255.255.255.0

inet6 addr: fe80::6088:79ff:fed0:e0f6/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

          RX packets:932 errors:0 dropped:0 overruns:0 frame:0
          TX packets:842 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:224384 (219.1 KiB) TX bytes:157416 (153.7 KiB)

br-wan:9 Link encap:Ethernet HWaddr 62:88:79:D0:E0:F6
          inet addr:10.0.0.22 Bcast:10.0.0.255 Mask:255.255.255.0

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

eth0      Link encap:Ethernet HWaddr F8:1A:67:F6:38:97
          UP BROADCAST MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
          Interrupt:4

eth1      Link encap:Ethernet HWaddr F8:1A:67:F6:38:98
          UP BROADCAST MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

          Interrupt:5

lo        Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:65536 Metric:1

          RX packets:1 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:68 (68.0 B) TX bytes:68 (68.0 B)

wlan0     Link encap:Ethernet HWaddr FA:1A:67:F6:38:98
          inet6 addr: fe80::f81a:67ff:fef6:3898/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

          RX packets:1888 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1417 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:293705 (286.8 KiB) TX bytes:349763 (341.5 KiB)

wlan0-1   Link encap:Ethernet HWaddr F8:1A:67:F6:38:98
          inet addr:10.10.1.20 Bcast:10.10.1.255 Mask:255.255.255.0
          inet6 addr: fe80::fa1a:67ff:fef6:3898/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1532 Metric:1

          RX packets:3074 errors:0 dropped:63 overruns:0 frame:0
          TX packets:1909 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:404338 (394.8 KiB) TX bytes:285102 (278.4 KiB)

root@TP-22:~#

Dario

2015-06-16 1:40 GMT-03:00 T Gillett <tgil...@gmail.com>:
OK

So it is working for the Ethernet setting, but not for the Mesh setting.

That gives us something work on to find the problem.

Would you change it back to Mesh WAN interface and reboot.

Then log in and run ifconfig and capture the output.

The run the command:

    # ifconfig   br-wan:9    10.0.0.22 netmask    255.255.255.0

Then run ifconfig and capture the output.

Please send the two outputs of the ifconfig commands.

Thanks
Terry

On Tue, Jun 16, 2015 at 2:34 PM, Darío G. Díaz <dario...@gmail.com> wrote:

Hi Terry

I think that now appeared, but then change the WAN settings as you suggested me.

root@TP-22:~# ifconfig
bat0 Link encap:Ethernet HWaddr A2:A9:D6:C9:A5:D1
inet6 addr: fe80::a0a9:d6ff:fec9:a5d1/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

          RX packets:617 errors:0 dropped:0 overruns:0 frame:0
          TX packets:369 errors:0 dropped:335 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:68839 (67.2 KiB) TX bytes:53985 (52.7 KiB)

br-lan    Link encap:Ethernet HWaddr F8:1A:67:F6:38:98
          inet addr:10.130.1.22 Bcast:10.130.1.255 Mask:255.255.255.0
          inet6 addr: fe80::fa1a:67ff:fef6:3898/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

          RX packets:2102 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1372 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:144676 (141.2 KiB) TX bytes:309792 (302.5 KiB)

br-lan:9 Link encap:Ethernet HWaddr F8:1A:67:F6:38:98
inet addr:172.31.255.254 Bcast:172.31.255.255 Mask:255.255.255.252
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

eth0 Link encap:Ethernet HWaddr F8:1A:67:F6:38:97

inet addr:10.200.1.22 Bcast:10.200.1.255 Mask:255.255.255.0

inet6 addr: fe80::fa1a:67ff:fef6:3897/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

          RX packets:2138 errors:0 dropped:0 overruns:0 frame:0
          TX packets:840 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:203967 (199.1 KiB) TX bytes:49676 (48.5 KiB)
          Interrupt:4

eth0:9    Link encap:Ethernet HWaddr F8:1A:67:F6:38:97
          inet addr:10.0.0.22 Bcast:10.0.0.255 Mask:255.255.255.0

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Interrupt:4

eth1 Link encap:Ethernet HWaddr F8:1A:67:F6:38:98

          UP BROADCAST MULTICAST MTU:1500 Metric:1
          RX packets:177 errors:0 dropped:0 overruns:0 frame:0
          TX packets:46 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:19639 (19.1 KiB) TX bytes:3289 (3.2 KiB)

          Interrupt:5

lo        Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:65536 Metric:1

          RX packets:280 errors:0 dropped:0 overruns:0 frame:0
          TX packets:280 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:24248 (23.6 KiB) TX bytes:24248 (23.6 KiB)

wlan0     Link encap:Ethernet HWaddr FA:1A:67:F6:38:98
          inet6 addr: fe80::f81a:67ff:fef6:3898/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

          RX packets:1833 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1826 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:193105 (188.5 KiB) TX bytes:379689 (370.7 KiB)

wlan0-1   Link encap:Ethernet HWaddr F8:1A:67:F6:38:98
          inet addr:10.10.1.20 Bcast:10.10.1.255 Mask:255.255.255.0
          inet6 addr: fe80::fa1a:67ff:fef6:3898/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1532 Metric:1

          RX packets:7451 errors:0 dropped:217 overruns:0 frame:0
          TX packets:3796 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1002625 (979.1 KiB) TX bytes:562103 (548.9 KiB)

root@TP-22:~#

Dario.

2015-06-16 1:12 GMT-03:00 T Gillett <tgil...@gmail.com>:

Hi Dario

Thanks for that.

I can't quite see why it is not working, and that is the script that sets up the static IP address, which looks OK.
I am testing on my WR842 which is almost the same code and it seems to be OK.

Would you be able to change Device C to use "Ethernet" for the WAN interface please?
Change the configuration, save, check and reboot.

Then the output of ifconfig should show the static WAN IP on eth0:9

If you could do that and send me the output of the ifconfig command it might help locate the problem.

Also I am adding the code to show the Primary WAN IP address assigned by an upstream DHCP server and it is looking OK so far. I will have a new firmware with that included for you to test. I want to fix the static Secondary IP at the same time.

Regards
Terry

On Tue, Jun 16, 2015 at 1:58 PM, Darío G. Díaz <dario...@gmail.com> wrote:

Hi Terry

I sent the requested information:

Device C: TP Link WR841N v8

root@TP-22:/# cat /etc/init.d/fallback-ip
#!/bin/sh

# Set up network for WR841 version

WR841VER=`cat /proc/cpuinfo | grep machine | cut -d "v" -f 2`
if [ $WR841VER -lt "9" ]; then
        LANETH="eth1"
        WANETH="eth0"
else
        LANETH="eth0"
        WANETH="eth1"
fi

# Set up Fallback IP
sleep 10 # make sure bridge is up
ifconfig br-lan:9 172.31.255.254 netmask 255.255.255.252

# Set up WAN Port Secondary IP
WANPORT=`uci get secn.wan.wanport`
SECWANIP=`uci get secn.wan.secwanip`
if [ $WANPORT = "Mesh" ]; then
        ifconfig br-wan:9 $SECWANIP netmask 255.255.255.0
elif [ $WANPORT = "Ethernet" ]; then
        ifconfig $WANETH":9" $SECWANIP netmask 255.255.255.0
fi

root@TP-22:/# brctl show
bridge name     bridge id               STP enabled     interfaces
br-lan          7fff.f81a67f63898         no             eth1
                                                          eth0
                                                                          wlan0
br-wan          7fff.4e2d66639f36            no              bat0

Device A: TP Link WR841N v9

root@TP-20:/# cat /etc/init.d/fallback-ip
#!/bin/sh

# Set up network for WR841 version

WR841VER=`cat /proc/cpuinfo | grep machine | cut -d "v" -f 2`
if [ $WR841VER -lt "9" ]; then
        LANETH="eth1"
        WANETH="eth0"
else
        LANETH="eth0"
        WANETH="eth1"
fi

# Set up Fallback IP
sleep 10 # make sure bridge is up
ifconfig br-lan:9 172.31.255.254 netmask 255.255.255.252

# Set up WAN Port Secondary IP
WANPORT=`uci get secn.wan.wanport`
SECWANIP=`uci get secn.wan.secwanip`
if [ $WANPORT = "Mesh" ]; then
        ifconfig br-wan:9 $SECWANIP netmask 255.255.255.0
elif [ $WANPORT = "Ethernet" ]; then
        ifconfig $WANETH":9" $SECWANIP netmask 255.255.255.0
fi

root@TP-20:/# brctl show
bridge name     bridge id               STP enabled     interfaces
br-lan          7fff.14cc20796ac8      no             eth0
                                                             eth1
                                                         wlan0
                                                     bat0
root@TP-20:/#

Regards

Darío

2015-06-15 22:42 GMT-03:00 T Gillett <tgil...@gmail.com>:

Hi Dario

I am trying to work out why you are not getting the br-wan:9 entry in the ifconfig output.

Would you please send me a copy on the file /etc/init.d/fallback-ip from the running device.

Also the output from the command:
# brctl show

Thanks
Terry

ip wan test.jpg

Darío G. Díaz

unread,

Jun 16, 2015, 5:08:06 PM6/16/15

to T Gillett, village-telco-dev

Hi Terry

I ask you please, if you can build me firmware for V9 WR841N, I do not have this firmware. He who sent me is V8.
This way I can prove it throughout the network.

Remember that if you can help me with the MAC LIST, to control the devices that connect to the node.
Also something very useful that you can add is: put a name to identify the node in the network.

Testing will continue with more today and I am commenting as they go.

Regards

Dario

T Gillett

unread,

Jun 17, 2015, 2:21:37 AM6/17/15

to Darío G. Díaz, village-telco-dev

Hi Dario

1. Device configuration

You can assign a static IP to the WAN Primary address, and also set the static IP of the WAN Secondary IP address.

Either way, this allows you to access each device individually by using its specific IP address.

All newly flashed devices will come up with the same default configuration, including the default IP address, and the WAN Port set to Disable.

A newly flashed device therefore has to be configured via the LAN port, and this can be done manually, or you can use a configuration file that has been previously saved.
See the Advanced / Firmware page for Save/Load Configuration.

So if you have a number of devices in your network, you can have a configuration file set up for each of them, and when you want to set up a new device you can just load its corresponding configuration file.

This makes it easier and less error prone to set up many devices in a network.

The configuration files can be edited, so you can take one saved file and edit it into many copies, each set up for a particular node in your network.

One note of caution: the configuration files do change somewhat for different firmware versions e.g. as new facilities are added, and also they vary somewhat between different hardware devices.
So you have to be a bit careful when editing the files.

2. Host Names

In order to address a node by a host name rather than IP address, you have to be able to resolve the name into an IP address.

You can do this easily on your management workstation by making appropriate entries in the /etc/hosts file (assuming a Linux workstation; there is a Windows equivalent). These entries are just IP Address / Host Name pairs, entered one per line.

Alternatively you may be able to make equivalent entries in a file on your primary LAN DHCP/DNS server (depending on its capabilities) so that workstations that get a DHCP address from this server will be able to resolve the node host names.

Another approach that may be useful is to set the WAN Port mode on the mesh nodes to "DHCP", and allow them to get their IP addresses automatically from the primary LAN DHCP server, and set up entries on the DHCP server for Reserved IP addresses for each particular node, based on their MAC addresses.

This way, the DHCP server will always give the same reserved IP address to each particular device, and so you won't have to set each one up individually for its WAN IP address. If the DHCP server also has the host name resolution file, then you can also access each individual node by name rather than by IP address.

Does this help?

Regards

Terry

On Wed, Jun 17, 2015 at 3:32 PM, Darío G. Díaz <dario...@gmail.com> wrote:

Terry

Ok, that's the point.
But what happens I get to ping all interfaces and also to the secondary interface.
Then to manage teams, I must set the port forwarding and SSL?

I prefer to work with "WAN port = Mesh" and mode = static WAN IP. "I'll try this configuration. But I have no way of identifying nodes (Device-A, B or C) than by the static IP.

Regards
Dario

2015-06-17 2:20 GMT-03:00 T Gillett <tgil...@gmail.com>:

Hi Dario

Thanks for that. I am glad it is working.

You can only get in through the WAN interface once the WAN Port has been configured correctly and Port Forward has been activated.

So if you upgrade the firmware via the WAN connection, you then have to use the LAN interface to set up the configuration again.

Is that the issue you have found?

Regards
Terry

On Wed, Jun 17, 2015 at 3:13 PM, Darío G. Díaz <dario...@gmail.com> wrote:

Hi Terry

Now if it's okay, I had a configuration error.
The problem I have is that to enter the device have to connect to the wireless network you have.
If I do it through the wan not let me in.

root@TP-20:~# brctl show
bridge name bridge id STP enabled interfaces

br-lan          7fff.14cc20796ac8       no              eth0
                                                        wlan0
br-wan          7fff.14cc20796ac9       no              eth1
                                                        bat0
root@TP-20:~# ifconfig
bat0      Link encap:Ethernet HWaddr 4A:DE:97:F6:80:FE
          inet6 addr: fe80::48de:97ff:fef6:80fe/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

          RX packets:30 errors:0 dropped:0 overruns:0 frame:0
          TX packets:610 errors:0 dropped:312 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1260 (1.2 KiB) TX bytes:54815 (53.5 KiB)

br-lan    Link encap:Ethernet HWaddr 14:CC:20:79:6A:C8

inet addr:10.130.1.20 Bcast:10.130.1.255 Mask:255.255.255.0

inet6 addr: fe80::16cc:20ff:fe79:6ac8/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

          RX packets:1396 errors:0 dropped:0 overruns:0 frame:0
          TX packets:927 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:130010 (126.9 KiB) TX bytes:194929 (190.3 KiB)

br-lan:9 Link encap:Ethernet HWaddr 14:CC:20:79:6A:C8

inet addr:172.31.255.254 Bcast:172.31.255.255 Mask:255.255.255.252
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

br-wan    Link encap:Ethernet HWaddr 14:CC:20:79:6A:C9
          inet addr:10.200.1.26 Bcast:10.200.1.255 Mask:255.255.255.0
          inet6 addr: fe80::16cc:20ff:fe79:6ac9/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

          RX packets:1325 errors:0 dropped:0 overruns:0 frame:0
          TX packets:385 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:165837 (161.9 KiB) TX bytes:49778 (48.6 KiB)

br-wan:9 Link encap:Ethernet HWaddr 14:CC:20:79:6A:C9

inet addr:10.0.1.20 Bcast:10.0.1.255 Mask:255.255.255.0

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

eth0 Link encap:Ethernet HWaddr 14:CC:20:79:6A:C8

          UP BROADCAST MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
          Interrupt:5

eth1 Link encap:Ethernet HWaddr 14:CC:20:79:6A:C9

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

          RX packets:1688 errors:0 dropped:0 overruns:0 frame:0
          TX packets:479 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:216476 (211.4 KiB) TX bytes:55258 (53.9 KiB)

          Interrupt:4

lo        Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:65536 Metric:1

          RX packets:16 errors:0 dropped:0 overruns:0 frame:0
          TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1564 (1.5 KiB) TX bytes:1564 (1.5 KiB)

wlan0     Link encap:Ethernet HWaddr 16:CC:20:79:6A:C8
          inet6 addr: fe80::14cc:20ff:fe79:6ac8/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

          RX packets:1561 errors:0 dropped:0 overruns:0 frame:0
          TX packets:926 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:166713 (162.8 KiB) TX bytes:213397 (208.3 KiB)

wlan0-1   Link encap:Ethernet HWaddr 14:CC:20:79:6A:C8

inet addr:10.10.1.20 Bcast:10.10.1.255 Mask:255.255.255.0

inet6 addr: fe80::16cc:20ff:fe79:6ac8/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:1532 Metric:1

          RX packets:2305 errors:0 dropped:6 overruns:0 frame:0
          TX packets:2505 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:240989 (235.3 KiB) TX bytes:307933 (300.7 KiB)

root@TP-20:~#

Ing. Darío G. Díaz
Cel.: 02344-15-429334
Skype: dariogdiaz

2015-06-17 1:46 GMT-03:00 T Gillett <tgil...@gmail.com>:

Hi Dario

The interface eth1:9 shows up, which seems to indicate that the WAN Port is set to Ethernet rather than Mesh.

Would you please check that it is set to Mesh.

Also could you run the command "brctl show" and send the output.

Thanks
Terry

On Wed, Jun 17, 2015 at 2:26 PM, Darío G. Díaz <dario...@gmail.com> wrote:

Hi Terry

There is something wrong !!!
I sent the data as the previous device. Configure it by following your recommendations and Br-wan interface: 9 does not appear.

DeviceA: Tp-Link WR841N V9

root@TP-20:~# ifconfig
bat0 Link encap:Ethernet HWaddr 1E:07:FD:73:0C:31
inet6 addr: fe80::1c07:fdff:fe73:c31/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

          RX packets:25 errors:0 dropped:0 overruns:0 frame:0
          TX packets:155 errors:0 dropped:54 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1199 (1.1 KiB) TX bytes:16124 (15.7 KiB)

br-lan    Link encap:Ethernet HWaddr 14:CC:20:79:6A:C8

inet addr:10.130.1.20 Bcast:10.130.1.255 Mask:255.255.255.0

inet6 addr: fe80::16cc:20ff:fe79:6ac8/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

          RX packets:753 errors:0 dropped:0 overruns:0 frame:0
          TX packets:542 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:76092 (74.3 KiB) TX bytes:106589 (104.0 KiB)

br-lan:9 Link encap:Ethernet HWaddr 14:CC:20:79:6A:C8

inet addr:172.31.255.254 Bcast:172.31.255.255 Mask:255.255.255.252
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

eth0 Link encap:Ethernet HWaddr 14:CC:20:79:6A:C8

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

          RX packets:790 errors:0 dropped:0 overruns:0 frame:0
          TX packets:560 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:90513 (88.3 KiB) TX bytes:107086 (104.5 KiB)
          Interrupt:5

eth1      Link encap:Ethernet HWaddr 14:CC:20:79:6A:C9

          UP BROADCAST MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
          Interrupt:4

eth1:9 Link encap:Ethernet HWaddr 14:CC:20:79:6A:C9

inet addr:10.0.1.20 Bcast:10.0.1.255 Mask:255.255.255.0

UP BROADCAST MULTICAST MTU:1500 Metric:1

          Interrupt:4

lo        Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:65536 Metric:1

          RX packets:1536 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1536 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:104448 (102.0 KiB) TX bytes:104448 (102.0 KiB)

wlan0     Link encap:Ethernet HWaddr 16:CC:20:79:6A:C8
          inet6 addr: fe80::14cc:20ff:fe79:6ac8/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0

          TX packets:231 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B) TX bytes:30282 (29.5 KiB)

wlan0-1   Link encap:Ethernet HWaddr 14:CC:20:79:6A:C8

inet addr:10.10.1.20 Bcast:10.10.1.255 Mask:255.255.255.0

inet6 addr: fe80::16cc:20ff:fe79:6ac8/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:1532 Metric:1

          RX packets:1729 errors:0 dropped:20 overruns:0 frame:0
          TX packets:1017 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:158293 (154.5 KiB) TX bytes:116314 (113.5 KiB)

root@TP-20:~# brctl show
bridge name bridge id STP enabled interfaces

br-lan          7fff.14cc20796ac8       no              eth0
                                                        wlan0
                                                        bat0
root@TP-20:~#

Regards
Dario

2015-06-16 18:40 GMT-03:00 T Gillett <tgil...@gmail.com>:
Hi Dario

Here is WR841 V9 firmware. It would be good if you can run the same test to check that it is OK.

Thanks
Terry

Darío G. Díaz

unread,

Jun 17, 2015, 11:32:30 AM6/17/15

to T Gillett, village-telco-dev

Hi Terry

I understand the two points that you explain me.
The administration and remote monitoring of the nodes (Device-X) is important because it is about where you have to keep checking.

Once the mesh network is functioning with 1, 2 or 10 nodes and for a correct management and order of it, what I do is to have the main elements of the network:
- Each node IP
- Mac address of the node
- Name of the node.
- assignment of bandwidth for each node;
and then check periodically that the signal does not fall or have other problems.

The network administrator should be able to circulate freely around the network and have the maximum possible security of not having any outside interference. Then each "client" will administer the node from the inside, to authorize devices you want to connect your home.

These are the principles that I have clear to put a mesh network in production.

I need you to give me your opinion ...

Regards

Dario

T Gillett

unread,

Jun 17, 2015, 5:19:21 PM6/17/15

to Darío G. Díaz, village-telco-dev

Hi Dario

Which devices are you testing with ?

Can you ping the WAN Secondary IP address from your management workstation?

This is a critical test. If you can't ping it, then ignore the following steps and we will have to work out what is wrong before going any further.

Have you enabled Port Forwarding with the checkbox on the WAN page?

Have you set the system password so that SSH is enabled?

Can you SSH login from the LAN side?

Have you rebooted after setting up the configuration?

If you can ping the Secondary IP address, and Port Forwarding is enabled, then you should be able to access the device using SSH login. It certainly works here for my devices eg WR842.

If you have done all the above and you still can't connect via SSH, please send the following:

- screenshots of the Advanced page and the WAN page

- output of ifconfig

- output of "brctl show"

Regards

Terry

On Thu, Jun 18, 2015 at 1:53 AM, Darío G. Díaz <dario...@gmail.com> wrote:

Terry

What does not work is the Secondary IP, since I can not join the team in any way.
I tested for SSH, port forward+SSL, webserver, etc. and in any way I can't access the device.

Darío

Darío G. Díaz

unread,

Jun 18, 2015, 4:39:12 PM6/18/15

to T Gillett, village-telco-dev

Terry

My workstation is connected to the switch in the network of the picture(IP_Network_4) I sent.

Which devices are you testing with ?

TP-Link WR841N v8 and v9.

Can you ping the WAN Secondary IP address from your management workstation?

No, I can't

This is a critical test. If you can't ping it, then ignore the following steps and we will have to work out what is wrong before going any further.

Have you enabled Port Forwarding with the checkbox on the WAN page?

Yes, in both devices.

Have you set the system password so that SSH is enabled?
Can you SSH login from the LAN side?

Yes, in both devices. I could access the LAN side SSH on both devices, but only if it was connected to the wifi network each device.

Have you rebooted after setting up the configuration?

Yes

If you can ping the Secondary IP address, and Port Forwarding is enabled, then you should be able to access the device using SSH login. It certainly works here for my devices eg WR842.

If you have done all the above and you still can't connect via SSH, please send the following:

- screenshots of the Advanced page and the WAN page
- output of ifconfig
- output of "brctl show"

I sent WR841N configurations v8 and v9 equipment.
I have also noticed that at times if a device is connected for 4 hours then much access device settings difficult. I have to reboot and there it can enter the settings.
From the position of the workstation, when I ping the IP Secondary never answered and I can not be accessed by ssh.

Regards

Dario.

TPL WR841N v8.rar

TPL WR841N v9.rar

IP_Network_4.jpg

T Gillett

unread,

Jun 18, 2015, 5:03:16 PM6/18/15

to Darío G. Díaz, village-telco-dev

Hi Dario

OK We have to fix the ping before anything else.

The ifconfig output shows that both Primary and Secondary IP addresses are active on the WAN interface,

Can you ping the Primary address?

I assume that you can, so the problem is likely with the network configuration of your workstation.

The Secondary address is 10.0.1.20. So your workstation should be configured with an IP address in the range 10.0.1.x with netmask 255.255.255.0 in order to be able to ping the device on its secondary IP address.

How is your workstation network port configured?

Regards

Terry

What is the

Darío G. Díaz

unread,

Jun 18, 2015, 5:31:52 PM6/18/15

to T Gillett, village-telco-dev

Terry

OK We have to fix the ping before anything else.

The ifconfig output shows that both Primary and Secondary IP addresses are active on the WAN interface,

Can you ping the Primary address?

Yes

I assume that you can, so the problem is likely with the network configuration of your workstation.

The Secondary address is 10.0.1.20. So your workstation should be configured with an IP address in the range 10.0.1.x with netmask 255.255.255.0 in order to be able to ping the device on its secondary IP address.

How is your workstation network port configured?

For the range of the Secondary IP: 10.0.1.25 / 255.255.255.0

Dario

Darío G. Díaz

unread,

Jun 18, 2015, 5:53:05 PM6/18/15

to T Gillett, village-telco-dev

Terry

Only it comes to ping the IP Secondary if you connect with the workstation by WIFI or LAN device you want to ping.

If I want to ping from the workstation through the mesh network to any device X, I can not reach.

Regards

Dario

T Gillett

unread,

Jun 18, 2015, 7:28:51 PM6/18/15

to Darío G. Díaz, village-telco-dev

Hi Dario

I think your network diagram is not quite up to date for this test set up.

Your network diagram shows that the Workstation has two IP addresses configured:

- IP1 10.130.1.x

- IP2 10.200.1.x

Are these addresses set up as Static IP addresses?

What are the actual IP addresses used?

One address should be 10.0.1.x (eg .25) in order to be able to ping the Secondary IP addresses of Nodes B and C.

What addresses the WAN Secondary IP addresses of Node B and C?

They should be set to something like 10.0.1.20 and 10.0.1.21 so that they are different and on the same subnet as the corresponding IP address on the workstation.

If you log on to the command line of Node A via SSH, can you ping the WAN Secondary IP addresses of Nodes B and C?

Regards

Terry

PS Would you be able to use ZIP or TAR files instead or RAR files please?

On Fri, Jun 19, 2015 at 8:21 AM, T Gillett <tgil...@gmail.com> wrote:

Hi Dario

When you ping the WAN Primary or Secondary from the LAN side via wifi or Ethernet, the ping packets travel via NAT. So that is expected behaviour and shows that the Secondary IP address is active.

But we have to work out why you can ping the Primary address from the WAN side but not the Secondary.

Is the workstation configured with
just a single static IP address?

Are there other nodes on the mesh with the same Secondary IP address?

You need to set each node with its own Secondary address otherwise there will be IP address conflict.

Regards
Terry

T Gillett

unread,

Jun 18, 2015, 8:00:04 PM6/18/15

to Darío G. Díaz, village-telco-dev

Hi Dario

Please try this basic test to check that the WAN Secondary IP is operating correctly, and that the workstation is correctly configured :

- Switch off all mesh nodes except one test Node.

- Reflash the test Node so that it has the default settings.

- Set the WAN Port to Ethernet.

- Check that the test Node has its WAN Secondary IP correctly configured ie 10.0.1.20

- Reboot the test Node.

- Log in to the test Node (with telnet, or set the password and use ssh).

Run ifconfig and check that eth0:9 (WR841 V8) or eth0:9 (WR841 V9) exists and has the WAN Secondary address.

- Disconnect your workstation from the switch and connect it directly to the WAN port on the test Node with an Ethernet cable.

- Make sure that the test Node has no other Ethernet connections.

- If the workstation has wifi, disable it. You want to have a single network connection, on the Ethernet port.

- Set up the workstation with a single static IP address on its Ethernet port, set to be in the same subnet as the test Node WAN Secondary IP address eg 10.0.1.1

- Try to ping the test node on 10.0.1.20

Please let me know the result.

Regards

Terry

Reply all

Reply to author

Forward

0 new messages