Re: Testing WR841 Ver 9 firmware
19 views
Skip to first unread message
T Gillett
Jun 5, 2015, 5:33:43 PM6/5/15
to Darío G. Díaz, village-telco-dev
Hi Dario
Thanks for the suggestions.
1. IP assigned by DHCP to the WAN interface - I will look at including this in the RC2 firmware to be displayed in an information field on the WAN page.
2. Static IP address,
Not sure what you mean by this. Could you clarify please?
Which IP address do you mean?
The main static IP address is shown on the Basic and Adv pages in the entry field, and the mesh IP interface IP is shown on the Adv page.
3. QoS
The wshaper package is included in recent SECN builds for devices with 8MB+ flash memory.
As an alternative, there is also the qos-scripts package which might be useful.
Configuration of these packages is by editing the respective config files.
I would be interested in your results if you try these packages.
We could look at including some config in the SECN web UI if they prove useful.
4. HTTPS
Not sure what you mean by this. Could you clarify please.
The SECN web interface will use HTTPS if you enable SSL by ticking the checkbox at the bottom of the Basic page and restart.
Note that the SECN device will use a self generated certificate that will not be known to your browser, so it will give a warning and you will need to review and accept the certificate in order to have access to the web page.
Regards
Terry
On Fri, Jun 5, 2015 at 1:14 PM, Darío G. Díaz <dario...@gmail.com> wrote:
Hi Terry
I'll try this firmaware and then you'll do the comments.
I want to give my opinion about some items that could be included in future versions. Post somewhere on the web configuration items:
1- IP address that is assigned by a DHCP external server to SECN the equipment that we have as a mesh node.
2- main display static IP address that is assigned to the node by which it identifies in the mesh network. This would allow central control of the nodes of the mesh network, where the main router can assign bandwidth to each node.
3- Implement a basic QoS to SECN, to allocate bandwidth to handle mesh node to within your own LAN to supply Internet access to some devices.
4- Allow entry to the web config SECN with https in the browser.
I hope you understand me what I tell it.Dario2015-06-04 21:13 GMT-03:00 T Gillett <tgil...@gmail.com>:TerryYou should be able to load the Ver 8 and Ver 9 firmware onto your respective WR841 devices and the Ethernet ports should operate correctly.This is the same firmware version that I sent you earlier for testing. It detects the hardware version of the device and adjusts the networking configuration depending on whether it is Version 9 or later, as we previously discussed.Hi DarioHere is the correct link for the WR841 SECN 3.0 RC1b firmware.
http://download.villagetelco.org/firmware/secn/unstable/tp-link/SECN-3/SECN-3.0-RC1/SECN-3.0-RC1-WR841/There are no other changes in this version. I will release RC2 over the next month with some minor changes, prior to releasing it as Stable firmware along with firmware for all the other supported devices.RegardsOn Thu, Jun 4, 2015 at 3:17 PM, T Gillett <tgil...@gmail.com> wrote:TerryRegardsThe only changes were for the automatic detection of the version number between Ver 8 and Ver 9 so thatthe Ethernet ports are set up correctly.I have posted the new firmware for V8 and V9 to the VT Downloads page here:
http://download.villagetelco.org/firmware/secn/unstable/tp-link/SECN-3/SECN-3.0-RC2/On Wed, Jun 3, 2015 at 2:51 PM, Darío G. Díaz <dario...@gmail.com> wrote:TerryDario
You have updated some other firmware of TP-Link wr841 v8 or v9?2015-05-19 21:20 GMT-03:00 T Gillett <tgil...@gmail.com>:
Darío G. Díaz
Jun 6, 2015, 1:35:58 AM6/6/15
to T Gillett, village-telco-dev
Hi Terry
I will answer point by point.
1_ This inclusion in the web configuration of SECN would be useful. I hope to RC2.
2_ This very clear your explanation and answered me that was what I asked.
3_ Thanks for this information. I will try to install this package and test QoS, then you will comment the results.I will answer point by point.
1_ This inclusion in the web configuration of SECN would be useful. I hope to RC2.
2_ This very clear your explanation and answered me that was what I asked.
4_ This is correct and I understood your explanation.
After this I have some opinions to make you, because there are things I do not understand yet.
I have attached a picture of the mesh network tests that I have and I emerge the following questions:
From the PC connected to the switch did a scan of the network and where I could find:
IP Router
IP PC
IP Device A(wan)
IP bat0 -> device B (which is not equal to the IP Device B) (IP Device B(wan) is the ip with which entry to the administration of the device).
IP bat0 -> device C (which is not equal to the IP Device C) (IP Device C(wan) is the ip with which entry to the administration of the device).
Also I have internet in all devices A, B and C.
Why do not you show me the scan I make the IP Device IP Device B and C, which are those that configure each ??
In my opinion the IPbat0 and IP (wan) device A, B or C, should be the same for a correct administration of the devices or in any case should show the IP (wan) A, B or C.
Darío.
T Gillett
Jun 7, 2015, 7:02:22 AM6/7/15
to Darío G. Díaz, village-telco-dev
Hi Dario
>>>
Why do not you show me the scan I make the IP Device IP Device B and C, which are those that configure each ??
In my opinion the IPbat0 and IP (wan) device A, B or C, should be the same for a correct administration of the devices or in any case should show the IP (wan) A, B or C.
<<<
The devices you are using for the mesh nodes are WR841 as I understand.
So they have one WAN Ethernet port (blue) and several LAN Ethernet ports (yellow).On Sat, Jun 6, 2015 at 3:35 PM, Darío G. Díaz <dario...@gmail.com> wrote:
Hi Terry
T Gillett
Jun 8, 2015, 6:30:52 PM6/8/15
to Darío G. Díaz, village-telco-dev
Hi Dario
I notice that the WAN and LAN interfaces on Device B have IP addresses in the same subnet.
In the ifconfig output below you can see:
- br-lan is at 10.200.1.21
- br-wan is at 10.200.1.11
This is not a valid configuration for the router function.
The LAN and WAN interfaces must be in different subnets.
You probably want to change the LAN IP address, perhaps to the default 10.130.1.20, and try your tests again.
It would be useful if you could update the network diagram with the new IP addresses so that we can see the picture of your network.
Regards
Terry
root@TP-21:/# ifconfig
bat0 Link encap:Ethernet HWaddr C2:78:AE:E2:02:B9
inet6 addr: fe80::c078:aeff:fee2:2b9/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:113139 errors:0 dropped:0 overruns:0 frame:0
TX packets:83139 errors:0 dropped:1341 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:124256614 (118.5 MiB) TX bytes:11476557 (10.9 MiB)
br-lan Link encap:Ethernet HWaddr 64:66:B3:A6:1D:4C
inet addr:10.200.1.21 Bcast:10.200.1.255 Mask:255.255.255.0
inet6 addr: fe80::6666:b3ff:fea6:1d4c/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:85190 errors:0 dropped:0 overruns:0 frame:0
TX packets:102305 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:10726035 (10.2 MiB) TX bytes:123616657 (117.8 MiB)
br-lan:9 Link encap:Ethernet HWaddr 64:66:B3:A6:1D:4C
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 C2:78:AE:E2:02:B9
inet addr:10.200.1.11 Bcast:10.200.1.255 Mask:255.255.255.0
inet6 addr: fe80::c078:aeff:fee2:2b9/64 Scope:Link---------- Forwarded message ----------
From: Darío G. Díaz <dario...@gmail.com>
Date: Tue, Jun 9, 2015 at 2:10 AM
Subject: Re: Testing WR841 Ver 9 firmware
To: T Gillett <tgil...@gmail.com>
From: Darío G. Díaz <dario...@gmail.com>
Date: Tue, Jun 9, 2015 at 2:10 AM
Subject: Re: Testing WR841 Ver 9 firmware
To: T Gillett <tgil...@gmail.com>
Terry
I sent the data files you asked.
Following the scheme of network that I have already sent, I send data from two devices A and B. I want to clarify some data on the network arm to try:
Network: 10.200.1.1/255.255.255.0
Router Gateway: 10.200.1.1
Device A: 10.200.1.20/255.255.255.0
SSID: VT-SECN-AP_20
Device B: 10.200.1.21/255.255.255.0
SSID: VT-SECN-AP_21
I attached two pictures WAN settings for each device. The cable connecting the router to the device A, was added to a LAN port on this device. The deviceB is connected to the deviceA through the mesh network.
Network: 10.200.1.1/255.255.255.0
Router Gateway: 10.200.1.1
Device A: 10.200.1.20/255.255.255.0
SSID: VT-SECN-AP_20
Device B: 10.200.1.21/255.255.255.0
SSID: VT-SECN-AP_21
I attached two pictures WAN settings for each device. The cable connecting the router to the device A, was added to a LAN port on this device. The deviceB is connected to the deviceA through the mesh network.
Regards
Dario
2015-06-07 8:13 GMT-03:00 T Gillett <tgil...@gmail.com>:
As well as the output of the 'ifconfig' command on Device A, would you also send the /etc/config/secn file please?
T Gillett
Jun 8, 2015, 9:47:41 PM6/8/15
to Darío G. Díaz, village-telco-dev
Dario
That config looks better.
That config looks better.
You should be able to ping the WAN interface of Device B on 10.200.1.56 from your PC.
Does this work?
Assuming you can ping the Device B on its WAN port:
To access the configuration interface for Device B, you will need to forward the SSH and HTTPS ports on the device (see Adv/WAN page).
Does this work?
Assuming you can ping the Device B on its WAN port:
To access the configuration interface for Device B, you will need to forward the SSH and HTTPS ports on the device (see Adv/WAN page).
Then you should be able to connect to Device B command line interface with the ssh command:
$ ssh -p 2222 10.200.1.56
(Assuming a Linux command line on the PC, or the equivalent in a Windows utility. Note that you have to specify the port number 2222)
(Assuming a Linux command line on the PC, or the equivalent in a Windows utility. Note that you have to specify the port number 2222)
Does that work?
Regards
Terry
On Tue, Jun 9, 2015 at 10:50 AM, Darío G. Díaz <dario...@gmail.com> wrote:
TerrySo is the new configuration of the IP addresses of the devices.DeviceB
root@TP-21:~# ifconfig
bat0 Link encap:Ethernet HWaddr 76:C4:35:AF:D0:0D
inet6 addr: fe80::74c4:35ff:feaf:d00d/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:576 errors:0 dropped:0 overruns:0 frame:0
TX packets:428 errors:0 dropped:101 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:46650 (45.5 KiB) TX bytes:40066 (39.1 KiB)
br-lan Link encap:Ethernet HWaddr 64:66:B3:A6:1D:4C
inet addr:10.130.1.21 Bcast:10.130.1.255 Mask:255.255.255.0
inet6 addr: fe80::6666:b3ff:fea6:1d4c/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1322 errors:0 dropped:0 overruns:0 frame:0
TX packets:599 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:114476 (111.7 KiB) TX bytes:233751 (228.2 KiB)
br-lan:9 Link encap:Ethernet HWaddr 64:66:B3:A6:1D:4C
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 76:C4:35:AF:D0:0D
inet addr:10.200.1.56 Bcast:10.200.1.255 Mask:255.255.255.0
inet6 addr: fe80::74c4:35ff:feaf:d00d/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:546 errors:0 dropped:0 overruns:0 frame:0
TX packets:512 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:35471 (34.6 KiB) TX bytes:49321 (48.1 KiB)
eth0 Link encap:Ethernet HWaddr 64:66:B3:A6:1D:4B
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:361 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:54612 (53.3 KiB)
Interrupt:4
eth1 Link encap:Ethernet HWaddr 64:66:B3:A6:1D:4C
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:689 errors:0 dropped:0 overruns:0 frame:0
TX packets:689 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:47364 (46.2 KiB) TX bytes:47364 (46.2 KiB)
wlan0 Link encap:Ethernet HWaddr 66:66:B3:A6:1D:4C
inet6 addr: fe80::6466:b3ff:fea6:1d4c/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1643 errors:0 dropped:0 overruns:0 frame:0
TX packets:589 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:209600 (204.6 KiB) TX bytes:244571 (238.8 KiB)
wlan0-1 Link encap:Ethernet HWaddr 64:66:B3:A6:1D:4C
inet addr:10.10.1.20 Bcast:10.10.1.255 Mask:255.255.255.0
inet6 addr: fe80::6666:b3ff:fea6:1d4c/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1532 Metric:1
RX packets:2275 errors:0 dropped:152 overruns:0 frame:0
TX packets:2337 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:211959 (206.9 KiB) TX bytes:258109 (252.0 KiB)
DeviceA
root@TP-20:/# ifconfig
bat0 Link encap:Ethernet HWaddr 76:86:AC:11:C2:12
inet6 addr: fe80::7486:acff:fe11:c212/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:6830 errors:0 dropped:0 overruns:0 frame:0
TX packets:7253 errors:0 dropped:32 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1552559 (1.4 MiB) TX bytes:3427254 (3.2 MiB)
br-lan Link encap:Ethernet HWaddr 14:CC:20:79:6A:C8
inet addr:10.200.1.20 Bcast:10.200.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:782 errors:0 dropped:0 overruns:0 frame:0
TX packets:714 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:58210 (56.8 KiB) TX bytes:96574 (94.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
eth0 Link encap:Ethernet HWaddr 14:CC:20:79:6A:C8
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:6768 errors:0 dropped:0 overruns:0 frame:0
TX packets:6288 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3352784 (3.1 MiB) TX bytes:1504229 (1.4 MiB)
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
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:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:86 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:6762 (6.6 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:7824 errors:0 dropped:58 overruns:0 frame:0
TX packets:8255 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1784568 (1.7 MiB) TX bytes:3831550 (3.6 MiB)Now I'm connected to a PC on the network switch with an IP segment 10.200.1.xxx, but I can not enter the conf. the DeviceB, that the main router DHCP assigned IP 10.200.1.56. If he answers the ping.Dario2015-06-08 21:11 GMT-03:00 Darío G. Díaz <dario...@gmail.com>:TerryDarioThe router connects to Device A, DHCP assigns IP, then the device A broadcasts to the other nodes.
Now I will make the change that you suggest me and then update the network scheme.
T Gillett
Jun 9, 2015, 12:10:53 AM6/9/15
to Darío G. Díaz, village-telco-dev
Hi Dario
OK that sounds like it as all working properly. I will make a patch to display the DHCP assigned WAN IP address on the WAN page for you to try. I should be able to do this over the next couple of days.
br-wan Link encap:Ethernet HWaddr C2:78:AE:E2:02:B9
inet addr:10.200.1.11 Bcast:10.200.1.255 Mask:255.255.255.0
inet6 addr: fe80::c078:aeff:fee2:2b9/64 Scope:Link
Regards
TerryYou should be able to ping the WAN interface of Device B on 10.200.1.56 from your PC.
Does this work?
If this works and doing well
Assuming you can ping the Device B on its WAN port:
To access the configuration interface for Device B, you will need to forward the SSH and HTTPS ports on the device (see Adv/WAN page).Then you should be able to connect to Device B command line interface with the ssh command:$ ssh -p 2222 10.200.1.56
(Assuming a Linux command line on the PC, or the equivalent in a Windows utility. Note that you have to specify the port number 2222)Does that work?
This worked well and also https://(wan ip=10.200.1.xxx):4433. The problem with this is that as IP Wan assigned by DHCP router, always changing.
It does not work in the following way: https://(wan ip=10.130.1.xxx):4433.
You can put on the WAN tab provisionally display some form of IP Wan or IP BR-WanRegardsTerry
Darío G. Díaz
Jun 9, 2015, 12:43:17 AM6/9/15
to T Gillett, village-telco-dev
Hi Terry
Ok, that suggestion I make you so that you can implement when you can and what you consider convenient. It's just to see it more clearly how they will allocate the IP network.
Currently for the BR-WAN, I do it for command line on the device.
Ok, that suggestion I make you so that you can implement when you can and what you consider convenient. It's just to see it more clearly how they will allocate the IP network.
Currently for the BR-WAN, I do it for command line on the device.
Regards
Dario
Reply all
Reply to author
Forward
0 new messages