[OpenWrt-Devel] [PATCH 4/4] ar8216: Fix issue with autoneg being disabled under 3.14, revert 43332
Patch reverts 43332 which seems to cause issues with VLAN functionality.
Add a specific check to check whether ANEG is still enabled and re-enable
it if necessary. Disable generic phy soft reset for kernel >=3.16.
Signed-off-by: Heiner Kallweit
---
.../linux/generic/files/drivers/net/phy/ar8216.c | 49 +-
1 file changed, 47 insertions(+), 2 deletions(-)
diff --git a/target/linux/generic/files/drivers/net/phy/ar8216.c
b/target/linux/generic/files/drivers/net/phy/ar8216.c
index 1d58f3a..5e93a1f 100644
--- a/target/linux/generic/files/drivers/net/phy/ar8216.c
+++ b/target/linux/generic/files/drivers/net/phy/ar8216.c
@@ -36,6 +36,7 @@
#include
#include
#include
+#include
#include "ar8216.h"
@@ -342,6 +343,29 @@ ar8xxx_phy_poll_reset(struct mii_bus *bus)
return -ETIMEDOUT;
}
+static int
+ar8xxx_phy_check_aneg(struct phy_device *phydev)
+{
+ int ret;
+
+ if (phydev->autoneg != AUTONEG_ENABLE)
+ return 0;
+ /*
+* BMCR_ANENABLE might have been cleared
+* by phy_init_hw in certain kernel versions
+* therefore check for it
+*/
+ ret = phy_read(phydev, MII_BMCR);
+ if (ret < 0)
+ return ret;
+ if (ret & BMCR_ANENABLE)
+ return 0;
+
+ dev_info(&phydev->dev, "ANEG disabled, re-enabling ...\n");
+ ret |= BMCR_ANENABLE | BMCR_ANRESTART;
+ return phy_write(phydev, MII_BMCR, ret);
+}
+
static void
ar8xxx_phy_init(struct ar8xxx_priv *priv)
{
@@ -2774,7 +2798,7 @@ ar8xxx_phy_config_init(struct phy_device *phydev)
return -ENODEV;
if (chip_is_ar8327(priv) || chip_is_ar8337(priv))
- return 0;
+ return ar8xxx_phy_check_aneg(phydev);
priv->phy = phydev;
@@ -2848,6 +2872,15 @@ ar8xxx_phy_read_status(struct phy_device *phydev)
return ret;
}
+static int
+ar8xxx_phy_config_aneg(struct phy_device *phydev)
+{
+ if (phydev->addr == 0)
+ return 0;
+
+ return genphy_config_aneg(phydev);
+}
+
static const u32 ar8xxx_phy_ids[] = {
0x004dd033,
0x004dd034, /* AR8327 */
@@ -3010,6 +3043,15 @@ ar8xxx_phy_remove(struct phy_device *phydev)
ar8xxx_free(priv);
}
+#if LINUX_VERSION_CODE >= KERNEL_VERSION(3,16,0)
+static int
+ar8xxx_phy_soft_reset(struct phy_device *phydev)
+{
+ /* we don't need an extra reset */
+ return 0;
+}
+#endif
+
static struct phy_driver ar8xxx_phy_driver = {
.phy_id = 0x004d,
.name = "Atheros AR8216/AR8236/AR8316",
@@ -3019,8 +3061,11 @@ static struct phy_driver ar8xxx_phy_driver = {
.remove = ar8xxx_phy_remove,
.detach = ar8xxx_phy_detach,
.config_init= ar8xxx_phy_config_init,
- .config_aneg= genphy_config_aneg,
+ .config_aneg= ar8xxx_phy_config_aneg,
.read_status= ar8xxx_phy_read_status,
+#if LINUX_VERSION_CODE >= KERNEL_VERSION(3,16,0)
+ .soft_reset = ar8xxx_phy_soft_reset,
+#endif
.driver = { .owner = THIS_MODULE },
};
--
2.1.3
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH 1/4 v2] luci2: fix null pointer exception
On 21 November 2014 03:01, Álvaro Fernández Rojas wrote:
> + if(val != null) {
Please follow the standard (whatever it is) and use a space after "if".
> + if ((val.length == 0 && !d.opt))
Btw. you could drop the extra pair of braces there :)
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Configuring OVS on OpenWRT
On 21 November 2014 10:03, Yilun Zhou wrote:
> Hi,
>
>
> I have installed OVS on my router and I want to connect it with a Floodlight
> controller. The IP address of the laptop on which Floodlight is running is
> 192.168.1.161 and Floodlight is running on port 6633. Here is what I am
> doing.
>
>
> First, I start Floodlight controller (the vanilla version without any
> change). Then I turn on the router and ssh into it. Executing "ifconfig" on
> it will give me:
>
>
> br-lanLink encap:Ethernet HWaddr 4E:60:DE:E6:B2:8F
> inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
> inet6 addr: fe80::4c60:deff:fee6:b28f/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:14712 errors:0 dropped:0 overruns:0 frame:0
> TX packets:16189 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:2100036 (2.0 MiB) TX bytes:10682748 (10.1 MiB)
>
> eth0 Link encap:Ethernet HWaddr 4E:60:DE:E6:B2:8F
> inet6 addr: fe80::4c60:deff:fee6:b28f/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:2902 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:0 (0.0 B) TX bytes:400010 (390.6 KiB)
> Interrupt:4
>
> eth0.1Link encap:Ethernet HWaddr 4E:60:DE:E6:B2:8F
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:2897 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:0 (0.0 B) TX bytes:386971 (377.9 KiB)
>
> eth1 Link encap:Ethernet HWaddr 4C:60:DE:E6:B2:90
> inet addr:10.181.27.151 Bcast:10.181.27.255 Mask:255.255.252.0
> inet6 addr: fe80::4e60:deff:fee6:b290/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:58936 errors:0 dropped:328 overruns:0 frame:0
> TX packets:11874 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:17323683 (16.5 MiB) TX bytes:1944846 (1.8 MiB)
> Interrupt:5
>
> loLink encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> inet6 addr: ::1/128 Scope:Host
> UP LOOPBACK RUNNING MTU:16436 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:3578 (3.4 KiB) TX bytes:3578 (3.4 KiB)
>
> wlan0 Link encap:Ethernet HWaddr 4C:60:DE:E6:B2:8F
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:392 errors:0 dropped:0 overruns:0 frame:0
> TX packets:501 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:61323 (59.8 KiB) TX bytes:125276 (122.3 KiB)
>
> wlan1 Link encap:Ethernet HWaddr 4C:60:DE:E6:B2:91
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:6925 errors:0 dropped:0 overruns:0 frame:0
> TX packets:8214 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:1138837 (1.0 MiB) TX bytes:7156326 (6.8 MiB)
>
> Specifically wlan0 is 2.4GHz wifi and wlan1 is 5GHz wifi. I want to use
> Floodlight to control 2.4GHz wifi (wlan0). I do not know exactly what br-lan
> is. So if anyone can explain it to me that would be great.
>
>
> Then I use "ovs-vsctl del-br" to delete any remaining bridge so that
> "ovs-vsctl show" will report nothing.
OpenWrt's default firewall policy will block any incoming and forward
traffic and lan network is an exception so that user from LAN can
access 192.168.1.1:{20,80}. br-lan is the bridge interface of LAN
consisting of eth0 and wlan0 in your case.
> Then I have the following
> configuration file that I execute.
>
>
> ovs-vsctl add-br br0;
> ovs-vsctl add-port br0 wlan0;
> ovs-vsctl add-port br0 br-lan;
> ifconfig br-lan 0.0.0.0;
> ifconfig br0 192.168.1.1;
> ovs-vsctl set-controller br0 tcp:192.168.1.161:6633;
I am not familiar with ovs-vsctl, but replace above commands with the
following line should work.
ovs-vsctl set-controller br-lan tcp:192.168.1.161:6633;
>
> However, after I execute this program, the only connection that I have is
> SSH. I can't browse the Internet anymore. However, my Floodlight controller
> shows the connection from br0
Output traffic is allowed by default.
Regards.
yousong
> and if I were to capture PacketIn events, I
> can see that it receives some packets from time to time. Nevertheless, it is
> more like periodic update than network request because rapidly refreshing my
> webpage will not significantly increase the packets received.
>
> Could
[OpenWrt-Devel] [PATCH 2/4 v2] luci2/network.switch: display switch port status icon
Signed-off-by: Álvaro Fernández Rojas
---
v2: fix typo
diff --git a/luci2/htdocs/luci2/view/network.switch.js
b/luci2/htdocs/luci2/view/network.switch.js
index 057955e..9391b3d 100644
--- a/luci2/htdocs/luci2/view/network.switch.js
+++ b/luci2/htdocs/luci2/view/network.switch.js
@@ -318,17 +318,19 @@ L.ui.view.extend({
return
self.getSwitchStatus(swname).then(function(ports) {
for (var j = 0; j <
ports.length; j++)
{
+ var i =
'/icons/port_down.png';
var s = L.tr('No link');
var d = ' ';
if (ports[j].link)
{
+ i =
'/icons/port_up.png';
s =
'%dbaseT'.format(ports[j].speed);
d =
ports[j].full_duplex ? L.tr('Full-duplex') : L.tr('Half-duplex');
}
$('#portstatus-%s-%d'.format(swname, j))
-
.empty().append(s + '' + d);
+
.empty().append($('').attr('src', L.globals.resource + i)).append('' + s + '' + d);
}
});
}, 5000);
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH 2/4 v2] luci2/network.switch: display switch port status icon
Signed-off-by: Álvaro Fernández Rojas
---
v2: fix typo
diff --git a/luci2/htdocs/luci2/view/network.switch.js
b/luci2/htdocs/luci2/view/network.switch.js
index 057955e..9391b3d 100644
--- a/luci2/htdocs/luci2/view/network.switch.js
+++ b/luci2/htdocs/luci2/view/network.switch.js
@@ -318,17 +318,19 @@ L.ui.view.extend({
return
self.getSwitchStatus(swname).then(function(ports) {
for (var j = 0; j <
ports.length; j++)
{
+ var i =
'/icons/port_down.png';
var s = L.tr('No link');
var d = ' ';
if (ports[j].link)
{
+ i =
'/icons/port_up.png');
s =
'%dbaseT'.format(ports[j].speed);
d =
ports[j].full_duplex ? L.tr('Full-duplex') : L.tr('Half-duplex');
}
$('#portstatus-%s-%d'.format(swname, j))
-
.empty().append(s + '' + d);
+
.empty().append($('').attr('src', L.globals.resource + i)).append('' + s + '' + d);
}
});
}, 5000);
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Frequent adsl disconnections with BTHOMEHUBV2B (lantiq xway danube)
On Nov 20, 2014 3:50 PM, "Sebastian Moeller" wrote: >> On Nov 20, 2014, at 17:26 , Jaime T wrote: > > Does anyone know if I can force a slower/lower connection speed from > > my side? (I would happily sacrifice some speed for more stability!) > > Maybe https://forum.openwrt.org/viewtopic.php?pid=222065 works for you? Increasing the SNR ,arhin should make your link more resilient... One of the reasons why I like my ST516 is you can tune SNR http://www.dslreports.com/forum/r17718637-SpeedTouch-516-Tweaking- ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Configuring OVS on OpenWRT
Hi, I have installed OVS on my router and I want to connect it with a Floodlight controller. The IP address of the laptop on which Floodlight is running is 192.168.1.161 and Floodlight is running on port 6633. Here is what I am doing. First, I start Floodlight controller (the vanilla version without any change). Then I turn on the router and ssh into it. Executing "ifconfig" on it will give me: br-lanLink encap:Ethernet HWaddr 4E:60:DE:E6:B2:8F inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::4c60:deff:fee6:b28f/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:14712 errors:0 dropped:0 overruns:0 frame:0 TX packets:16189 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2100036 (2.0 MiB) TX bytes:10682748 (10.1 MiB) eth0 Link encap:Ethernet HWaddr 4E:60:DE:E6:B2:8F inet6 addr: fe80::4c60:deff:fee6:b28f/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:2902 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:400010 (390.6 KiB) Interrupt:4 eth0.1Link encap:Ethernet HWaddr 4E:60:DE:E6:B2:8F UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:2897 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:386971 (377.9 KiB) eth1 Link encap:Ethernet HWaddr 4C:60:DE:E6:B2:90 inet addr:10.181.27.151 Bcast:10.181.27.255 Mask:255.255.252.0 inet6 addr: fe80::4e60:deff:fee6:b290/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:58936 errors:0 dropped:328 overruns:0 frame:0 TX packets:11874 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:17323683 (16.5 MiB) TX bytes:1944846 (1.8 MiB) Interrupt:5 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 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:3578 (3.4 KiB) TX bytes:3578 (3.4 KiB) wlan0 Link encap:Ethernet HWaddr 4C:60:DE:E6:B2:8F UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:392 errors:0 dropped:0 overruns:0 frame:0 TX packets:501 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:61323 (59.8 KiB) TX bytes:125276 (122.3 KiB) wlan1 Link encap:Ethernet HWaddr 4C:60:DE:E6:B2:91 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:6925 errors:0 dropped:0 overruns:0 frame:0 TX packets:8214 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1138837 (1.0 MiB) TX bytes:7156326 (6.8 MiB) Specifically wlan0 is 2.4GHz wifi and wlan1 is 5GHz wifi. I want to use Floodlight to control 2.4GHz wifi (wlan0). I do not know exactly what br-lan is. So if anyone can explain it to me that would be great. Then I use "ovs-vsctl del-br" to delete any remaining bridge so that "ovs-vsctl show" will report nothing. Then I have the following configuration file that I execute. ovs-vsctl add-br br0; ovs-vsctl add-port br0 wlan0; ovs-vsctl add-port br0 br-lan; ifconfig br-lan 0.0.0.0; ifconfig br0 192.168.1.1; ovs-vsctl set-controller br0 tcp:192.168.1.161:6633; However, after I execute this program, the only connection that I have is SSH. I can't browse the Internet anymore. However, my Floodlight controller shows the connection from br0 and if I were to capture PacketIn events, I can see that it receives some packets from time to time. Nevertheless, it is more like periodic update than network request because rapidly refreshing my webpage will not significantly increase the packets received. Could anyone tell me what might go wrong? Thanks, Yilun ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH 1/4 v2] luci2: fix null pointer exception
This fixes system/system not properly loading due to themes being null.
Signed-off-by: Álvaro Fernández Rojas
---
v2: fix broken validation
diff --git a/luci2/htdocs/luci2/luci2.js b/luci2/htdocs/luci2/luci2.js
index 040f1e5..6eab8fa 100644
--- a/luci2/htdocs/luci2/luci2.js
+++ b/luci2/htdocs/luci2/luci2.js
@@ -5190,17 +5190,19 @@ function LuCI2()
{
delete validation.message;
- if ((val.length == 0 && !d.opt))
- {
- rv = d.self.setError($elem, L.tr('Field
must not be empty'));
- }
- else if (val.length > 0 &&
!vstack[0].apply(val, vstack[1]))
- {
- rv = d.self.setError($elem,
validation.message, vstack[1]);
- }
- else
- {
- rv = d.self.setError($elem);
+ if(val != null) {
+ if ((val.length == 0 && !d.opt))
+ {
+ rv = d.self.setError($elem,
L.tr('Field must not be empty'));
+ }
+ else if (val.length > 0 &&
!vstack[0].apply(val, vstack[1]))
+ {
+ rv = d.self.setError($elem,
validation.message, vstack[1]);
+ }
+ else
+ {
+ rv = d.self.setError($elem);
+ }
}
}
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH 4/4] luci2-shairplay: add new package
Signed-off-by: Álvaro Fernández Rojas
---
diff --git a/luci2-shairplay/Makefile b/luci2-shairplay/Makefile
new file mode 100644
index 000..53105a8
--- /dev/null
+++ b/luci2-shairplay/Makefile
@@ -0,0 +1,36 @@
+include $(TOPDIR)/rules.mk
+
+PKG_NAME:=luci2-shairplay
+PKG_RELEASE:=1
+
+include $(INCLUDE_DIR)/package.mk
+
+define Package/luci2-shairplay
+ SECTION:=luci2
+ CATEGORY:=LuCI2
+ TITLE:=LuCI2 shairplay module
+ DEPENDS:=luci2 +shairplay
+endef
+
+define Package/luci2-shairplay/description
+ LuCI2 module for shairplay
+endef
+
+define Build/Compile
+endef
+
+define Package/luci2-shairplay/install
+ $(INSTALL_DIR) $(1)/usr/share/rpcd/menu.d
+ $(INSTALL_DATA) ./files/usr/share/rpcd/menu.d/services.shairplay.json
$(1)/usr/share/rpcd/menu.d/
+
+ $(INSTALL_DIR) $(1)/usr/share/rpcd/acl.d
+ $(INSTALL_DATA) ./files/usr/share/rpcd/acl.d/services.shairplay.json
$(1)/usr/share/rpcd/acl.d/
+
+ $(INSTALL_DIR) $(1)/www/luci2/template
+ $(INSTALL_DATA) ./files/www/luci2/template/services.shairplay.htm
$(1)/www/luci2/template
+
+ $(INSTALL_DIR) $(1)/www/luci2/view
+ $(INSTALL_DATA) ./files/www/luci2/view/services.shairplay.js
$(1)/www/luci2/view
+endef
+
+$(eval $(call BuildPackage,luci2-shairplay))
diff --git a/luci2-shairplay/files/usr/share/rpcd/acl.d/services.shairplay.json
b/luci2-shairplay/files/usr/share/rpcd/acl.d/services.shairplay.json
new file mode 100644
index 000..6242e12
--- /dev/null
+++ b/luci2-shairplay/files/usr/share/rpcd/acl.d/services.shairplay.json
@@ -0,0 +1,15 @@
+{
+ "shairplay": {
+ "description": "Shairplay management",
+ "read": {
+ "uci": [
+ "shairplay"
+ ]
+ },
+ "write": {
+ "uci": [
+ "shairplay"
+ ]
+ }
+ }
+}
diff --git
a/luci2-shairplay/files/usr/share/rpcd/menu.d/services.shairplay.json
b/luci2-shairplay/files/usr/share/rpcd/menu.d/services.shairplay.json
new file mode 100644
index 000..74fc794
--- /dev/null
+++ b/luci2-shairplay/files/usr/share/rpcd/menu.d/services.shairplay.json
@@ -0,0 +1,11 @@
+{
+ "services": {
+ "title": "Services",
+ "index": 40
+ },
+ "services/shairplay": {
+ "title": "shairplay",
+ "acls": [ "shairplay" ],
+ "view": "services/shairplay"
+ }
+}
diff --git a/luci2-shairplay/files/www/luci2/template/services.shairplay.htm
b/luci2-shairplay/files/www/luci2/template/services.shairplay.htm
new file mode 100644
index 000..ad19e7d
--- /dev/null
+++ b/luci2-shairplay/files/www/luci2/template/services.shairplay.htm
@@ -0,0 +1 @@
+
diff --git a/luci2-shairplay/files/www/luci2/view/services.shairplay.js
b/luci2-shairplay/files/www/luci2/view/services.shairplay.js
new file mode 100644
index 000..038b49c
--- /dev/null
+++ b/luci2-shairplay/files/www/luci2/view/services.shairplay.js
@@ -0,0 +1,85 @@
+L.ui.view.extend({
+ execute: function() {
+ var self = this;
+
+ var m = new L.cbi.Map('shairplay', {
+ caption: L.tr('Shairplay (AirPlay server)')
+ });
+
+ var s = m.section(L.cbi.TypedSection, 'shairplay', {
+ caption: L.tr('Shairplay'),
+ addremove:true,
+ add_caption: L.tr('Add shairplay service …'),
+ });
+
+ s.option(L.cbi.CheckboxValue, 'disabled', {
+ caption: L.tr('Enabled'),
+ initial: 1,
+ enabled: '0',
+ disabled:'1'
+ });
+
+ s.option(L.cbi.CheckboxValue, 'respawn', {
+ caption: L.tr('Respawn'),
+ description: 'Specifies if the server should restart on
crash',
+ initial: 1,
+ enabled: '1',
+ disabled:'0'
+ });
+
+ s.option(L.cbi.InputValue, 'apname', {
+ caption: L.tr('Airport Name'),
+ description: L.tr('Specifies the AirServer name'),
+ });
+
+ s.option(L.cbi.InputValue, 'port', {
+ caption: L.tr('Port'),
+ description: L.tr('Specifies the listening port'),
+ datatype:'port'
+ });
+
+ s.option(L.cbi.PasswordValue, 'password', {
+ caption: L.tr('Password'),
+ description: L.tr('Specifies the server password'),
+ optional:true
+ });
+
+ s.option(L.cbi.InputValue, 'hwaddr', {
+ caption: L.
[OpenWrt-Devel] [PATCH 2/4] luci2/network.switch: display switch port status icon
Signed-off-by: Álvaro Fernández Rojas
---
diff --git a/luci2/htdocs/luci2/view/network.switch.js
b/luci2/htdocs/luci2/view/network.switch.js
index 057955e..9391b3d 100644
--- a/luci2/htdocs/luci2/view/network.switch.js
+++ b/luci2/htdocs/luci2/view/network.switch.js
@@ -318,17 +318,19 @@ L.ui.view.extend({
return
self.getSwitchStatus(swname).then(function(ports) {
for (var j = 0; j <
ports.length; j++)
{
+ var i =
'/icons/port_down.png';
var s = L.tr('No link');
var d = ' ';
if (ports[j].link)
{
+ i =
'/icons/port_up.png');
s =
'%dbaseT'.format(ports[j].speed);
d =
ports[j].full_duplex ? L.tr('Full-duplex') : L.tr('Half-duplex');
}
$('#portstatus-%s-%d'.format(swname, j))
-
.empty().append(s + '' + d);
+
.empty().append($('').attr('src', L.globals.resource + i)).append('' + s + '' + d);
}
});
}, 5000);
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH 3/4] luci-p910nd: select p910nd
Signed-off-by: Álvaro Fernández Rojas --- luci2-p910nd/Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/luci2-p910nd/Makefile b/luci2-p910nd/Makefile index 50aeadc..e59ed21 100644 --- a/luci2-p910nd/Makefile +++ b/luci2-p910nd/Makefile @@ -9,7 +9,7 @@ define Package/luci2-p910nd SECTION:=luci2 CATEGORY:=LuCI2 TITLE:=LuCI2 p910nd module - DEPENDS:=luci2 p910nd + DEPENDS:=luci2 +p910nd endef define Package/luci2-p910nd/description ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH 1/4] luci2: fix Null pointer exception
This fixes system/system not properly loading due to themes being null.
Signed-off-by: Álvaro Fernández Rojas
---
diff --git a/luci2/htdocs/luci2/luci2.js b/luci2/htdocs/luci2/luci2.js
index 040f1e5..a92aaeb 100644
--- a/luci2/htdocs/luci2/luci2.js
+++ b/luci2/htdocs/luci2/luci2.js
@@ -5190,13 +5190,15 @@ function LuCI2()
{
delete validation.message;
- if ((val.length == 0 && !d.opt))
- {
- rv = d.self.setError($elem, L.tr('Field
must not be empty'));
- }
- else if (val.length > 0 &&
!vstack[0].apply(val, vstack[1]))
- {
- rv = d.self.setError($elem,
validation.message, vstack[1]);
+ if (val) {
+ if ((val.length == 0 && !d.opt))
+ {
+ rv = d.self.setError($elem,
L.tr('Field must not be empty'));
+ }
+ else if (val.length > 0 &&
!vstack[0].apply(val, vstack[1]))
+ {
+ rv = d.self.setError($elem,
validation.message, vstack[1]);
+ }
}
else
{
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] I'd like to donate a Netgear N150 WNR1000 v3
On 20 November 2014 18:03, Kristjan Onu wrote: > I am attaching the output of nvram show from a WGR614v10. I think it is very > similar to the WNR1000v3. > > Please let me know if you have any questions. Could you send e-mails as text/plain, please? I've commited changes that should fix/improve WGR614 V10 situation, see: https://dev.openwrt.org/changeset/43336/ Could you try booting OpenWrt version with these patches included? And provide us a boot log, please? Serial console may be required of course. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] (BACKPORT to 3.14) mtd: bcm47xxpart: only register partitions if the trx header was filled
On 20 November 2014 22:02, Stephen G. Parry wrote: > Thanks for heads up. I am very busy at the moment with day job, but will > rework the patch as soon as I can find time. As I said, I've already backported that patch. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] (BACKPORT to 3.14) mtd: bcm47xxpart: only register partitions if the trx header was filled
Hi, Thanks for heads up. I am very busy at the moment with day job, but will rework the patch as soon as I can find time. Stephen On 08/11/14 21:44, Rafał Miłecki wrote: > On 31 October 2014 19:31, Stephen Parry wrote: >> Sometimes the trx offsets are 0, in that case there is no partition and >> we should not try to add one. > Hi Stephen, > > Please note this patch should be packported as 0xx according to the > rules defines in the target/linux/generic/PATCHES. It also means, that > 431-mtd-bcm47xxpart-support-TRX-data-partition-being-UBI.patch should > be updated, not the other way. > > I've backported that patch in r43223 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Frequent adsl disconnections with BTHOMEHUBV2B (lantiq xway danube)
Hi Jaime, not an expert on adel modem errors, let alone lantiq, here is my attempt at helping out: On Nov 20, 2014, at 17:26 , Jaime T wrote: > On 17 November 2014 18:36, Sebastian Moeller wrote: >> Hi Jaime, >> maybe you should also look at the rror counters. Especially the CRC and HEC >> errors short before the connection drops might be interesting. >> Best Regards >>Sebastian > > Hi everyone. > > I've set lcp-echo-failure to "10" and lcp-echo-interval to "3" and I'm > still getting the disconnections. The logs fill with the following > now: > > Thu Nov 20 15:29:55 2014 kern.warn kernel: [15746.372000] leave showtime Ooops, the modem somehow lost ist DSL connection to the DSLAM > Thu Nov 20 15:29:56 2014 daemon.info pppd[7651]: Terminating on signal 15 > Thu Nov 20 15:29:56 2014 daemon.info pppd[7651]: Connect time 6.0 minutes. > Thu Nov 20 15:29:56 2014 daemon.info pppd[7651]: Sent 89186 bytes, > received 46470 bytes. > Thu Nov 20 15:29:56 2014 daemon.notice netifd: Network device > 'pppoa-wan' link is down > Thu Nov 20 15:30:01 2014 daemon.notice netifd: Interface 'wan' is now down > Thu Nov 20 15:30:11 2014 daemon.warn dnsmasq[1503]: no servers found > in /tmp/resolv.conf.auto, will retry > Thu Nov 20 15:30:24 2014 kern.err kernel: [15775.136000] > [DSL_BSP_Showtime 894]: Datarate US intl = 924903, fast = 0 > Thu Nov 20 15:30:24 2014 kern.warn kernel: [15775.14] enter > showtime, cell rate: 0 - 2181, 1 - 2181, xdata addr: 0x82e9 This looks like the modem just entered showtime (basically you can only transfer data in showtime, so the was a loss of the DSL link as well as the PPP link that sits on top of it) I would guess the DSL link went away from under the PPP connection so PPPD was forced to exit as well. > Thu Nov 20 15:30:26 2014 daemon.notice netifd: Interface 'wan' is setting up > now > Thu Nov 20 15:30:26 2014 daemon.info pppd[7835]: Plugin pppoatm.so loaded. > Thu Nov 20 15:30:26 2014 daemon.info pppd[7835]: PPPoATM plugin_init > Thu Nov 20 15:30:26 2014 daemon.info pppd[7835]: PPPoATM > setdevname_pppoatm - SUCCESS:0.38 > Thu Nov 20 15:30:26 2014 daemon.notice pppd[7835]: pppd 2.4.7 started > by root, uid 0 > Thu Nov 20 15:30:26 2014 daemon.info pppd[7835]: Using interface pppoa-wan > > Perhaps the "lcp echo request" thing just be a red herring caused by > the dsl link losing sync? I agree with that interpretation. > > I've also tried to find some info on how to get the error counters out > for the lantiq dsl connection (using dsl_cpe_control), and the best > info I can get hold of is: > > pmcctg 0 0 > nReturn=15 nChannel=0 nDirection=0 nElapsedTime=18031 bValid=1 > nCodeViolations=14662 nFEC=5910810 code violations are caused by CRC errors of transmitted packets, these require retransmission from sender to receiver (these are bad as they cost bandwidth). FEC is forward error correction (basically reed salomon code with potential interleaving of cells to spread out error bursts). The elapsed time I assume to be in seconds so ~5 hours … and 14662/18031 = 0.81 errors per second, quite a lot... > > pmdpctg 0 0 > nReturn=15 nChannel=0 nDirection=0 nElapsedTime=18058 bValid=1 > nHEC=10735 nTotalCells=256128475 nUserTotalCells=1896600 nIBE=0 > nTxUserTotalCells=0 nTxIBE=0 > > pmlsc1dg 0 0 > nReturn=15 nDirection=0 nHistoryInterval=0 nElapsedTime=58145 bValid=1 > nES=432 These are errored seconds a count of the seconds with CRC errors (multiple CRCs per second will just increase ES by one so it removes bursty errors to some degree from the statistics), if elapsed time is in seconds the ES accumulated inside of ~16 hours. > nSES=256 nLOSS=22 nUAS=2433 nLOFS=1868 SES means severely errored seconds (not sure how they are counted, but they typically increase way slower than ES), • UAS: Unavailable Seconds - Seconds where you had no sync (from http://en.wikipedia.org/wiki/G.992.1) this most likely is the culprit for your pop to go away. I do not know whether you can make pop wait long enough for your line to resync so your pppd disconnects would go away, but I also do not know whether your ISP would allow that since their PPPD also sees you go and might not allow to reconnect but enforce a new connection (I have no clue at all). Also I think you should try to improve the quality of the DSL link to make the PPP issue rare enough o just ignore it. > > The problem I now have is that I don't know how to interpret these > results: are they good, or bad? (And do they explain why I'm getting > dozens of disconnections every day?) I think they record your disconnects, but not necessarily tell you what caused the del link to go out for lunch... > > Does anyone know if I can force a slower/lower connection speed from > my side? (I would happily sacrifice some speed for more stability!) Maybe https://forum.openwrt.org/viewtopic.php?pid=222065 works for you? Increasing the SNR ,arhin should mak
[OpenWrt-Devel] [PATCH] mpc85xx: fix missing dts target for kernel 3.14
With kernel 3.14 dts target p1010rdb was renamed to p1010rdb-pa.
To maintain compatibility define p1010rdb-pa as new standard and
copy p1010rdb.dts to p1010rdb-pa.dts under 3.10.
Signed-off-by: Heiner Kallweit
---
target/linux/mpc85xx/image/Makefile| 2 +-
.../mpc85xx/patches-3.10/150-dts-p1010rdb-pa.patch | 87 ++
2 files changed, 88 insertions(+), 1 deletion(-)
create mode 100644 target/linux/mpc85xx/patches-3.10/150-dts-p1010rdb-pa.patch
diff --git a/target/linux/mpc85xx/image/Makefile
b/target/linux/mpc85xx/image/Makefile
index 0f8373a..dcb2620 100644
--- a/target/linux/mpc85xx/image/Makefile
+++ b/target/linux/mpc85xx/image/Makefile
@@ -21,7 +21,7 @@ endef
zImage:=$(BIN_DIR)/$(IMG_PREFIX)-zImage
-DTS_TARGETS = mpc8548cds_32b p1010rdb tl-wdr4900-v1 p1020rdb
+DTS_TARGETS = mpc8548cds_32b p1010rdb-pa tl-wdr4900-v1 p1020rdb
BOOT_IMAGES:=zImage cuImage.tl-wdr4900-v1
define Image/Prepare
diff --git a/target/linux/mpc85xx/patches-3.10/150-dts-p1010rdb-pa.patch
b/target/linux/mpc85xx/patches-3.10/150-dts-p1010rdb-pa.patch
new file mode 100644
index 000..0d2f0b9
--- /dev/null
+++ b/target/linux/mpc85xx/patches-3.10/150-dts-p1010rdb-pa.patch
@@ -0,0 +1,87 @@
+From 41ec72d74b9453cd0d4b60d188ae894b8bdc4ca6 Mon Sep 17 00:00:00 2001
+From: Heiner Kallweit
+Date: Thu, 20 Nov 2014 18:33:47 +0100
+Subject: [PATCH] create dts target p1010rdb-pa
+ With kernel 3.14 dts target p1010rdb was renamed to p1010rdb-pa.
+ Create a copy of p1010rdb.dts to maintain compatibility.
+
+---
+ arch/powerpc/boot/dts/p1010rdb-pa.dts | 66 +++
+ 1 file changed, 66 insertions(+)
+ create mode 100644 arch/powerpc/boot/dts/p1010rdb-pa.dts
+
+diff --git a/arch/powerpc/boot/dts/p1010rdb-pa.dts
b/arch/powerpc/boot/dts/p1010rdb-pa.dts
+new file mode 100644
+index 000..b868d22
+--- /dev/null
b/arch/powerpc/boot/dts/p1010rdb-pa.dts
+@@ -0,0 +1,66 @@
++/*
++ * P1010 RDB Device Tree Source
++ *
++ * Copyright 2011 Freescale Semiconductor Inc.
++ *
++ * This program is free software; you can redistribute it and/or modify it
++ * under the terms of the GNU General Public License as published by the
++ * Free Software Foundation; either version 2 of the License, or (at your
++ * option) any later version.
++ */
++
++/include/ "fsl/p1010si-pre.dtsi"
++
++/ {
++ model = "fsl,P1010RDB";
++ compatible = "fsl,P1010RDB";
++
++ memory {
++ device_type = "memory";
++ };
++
++ board_ifc: ifc: ifc@ffe1e000 {
++ /* NOR, NAND Flashes and CPLD on board */
++ ranges = <0x0 0x0 0x0 0xee00 0x0200
++0x1 0x0 0x0 0xff80 0x0001
++0x3 0x0 0x0 0xffb0 0x0020>;
++ reg = <0x0 0xffe1e000 0 0x2000>;
++ };
++
++ board_soc: soc: soc@ffe0 {
++ ranges = <0x0 0x0 0xffe0 0x10>;
++ };
++
++ pci0: pcie@ffe09000 {
++ reg = <0 0xffe09000 0 0x1000>;
++ ranges = <0x200 0x0 0xa000 0 0xa000 0x0 0x2000
++0x100 0x0 0x 0 0xffc1 0x0 0x1>;
++ pcie@0 {
++ ranges = <0x200 0x0 0xa000
++0x200 0x0 0xa000
++0x0 0x2000
++
++0x100 0x0 0x0
++0x100 0x0 0x0
++0x0 0x10>;
++ };
++ };
++
++ pci1: pcie@ffe0a000 {
++ reg = <0 0xffe0a000 0 0x1000>;
++ ranges = <0x200 0x0 0x8000 0 0x8000 0x0 0x2000
++0x100 0x0 0x 0 0xffc0 0x0 0x1>;
++ pcie@0 {
++ ranges = <0x200 0x0 0x8000
++0x200 0x0 0x8000
++0x0 0x2000
++
++0x100 0x0 0x0
++0x100 0x0 0x0
++0x0 0x10>;
++ };
++ };
++};
++
++/include/ "p1010rdb.dtsi"
++/include/ "fsl/p1010si-post.dtsi"
+--
+2.1.3
+
--
2.1.3
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Hooks on wifi up/down for starting/stopping dependent functionality?
Thanks for the ubus pointers, Bastian. That should solve it :) Johan On Mon, Nov 17, 2014 at 10:34 AM, Bastian Bittorf wrote: > * Johan Almbladh [17.11.2014 10:22]: > > The hotplug scripts receive events for interface names, but they know > > nothing about the underlying configuration. Is there any way to map a > WLAN > > interface name, e.g. wlan0, to the corresponding UCI config entry in > > /etc/config/wireless? > > /sbin/hotplug-call exports some global shell-vars, which you > can use in your script, e.g.: > > ACTION - e.g. 'ifup' > INTERFACE - e.g. 'mywan' > DEVICE - e.g. eth0.2 > > if you need some more, you can query them in your > script with e.g. > > ubus call network.interface.mywan status > > you can parse the JSON with e.g. > > . /usr/share/libubox/jshn.sh > OUT="$( ubus call network.interface.mywan status )" > eval $( jshn -r "$OUT" ) > echo $JSON_VAR_status > > bye, bastian > ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] I'd like to donate a Netgear N150 WNR1000 v3
Hello Rafał and others, Could you provide us NVRAM dump once you get this device? I am attaching the output of nvram show from a WGR614v10. I think it is very similar to the WNR1000v3. Please let me know if you have any questions. Regards, Kristjan $ telnet 192.168.1.1 Trying 192.168.1.1... Connected to 192.168.1.1. Escape character is '^]'. BusyBox v0.60.0 (2012.09.18-10:09+) Built-in shell (msh) Enter 'help' for a list of built-in commands. # nvram show wan2_dns= wlan_acl_dev24= wl_radius_port=1812 wlan_acl_dev25= gui_check_enable=1 wan_unit=0 wlan_acl_dev26= wla_ssid_2=NETGEAR-Guest wl0_wmf_bss_enable=0 wlan_acl_dev27= wan_route= wlan_acl_dev28= wla_temp_ssid=NETGEAR as_genie=0 wl0_frameburst=on pppoe2_keepalive=0 wlan_acl_dev29= wla_region=11 wl_txstreams=0 bs_trustedip=192.168.1.0 wla_wmm_advert_2=1 bs_keywords= potValue=4320 wla_repeater=0 auto_enable=1 log_ipaddr= wla_temp_temp_broadcast=ssid_bc bs_enable=0 sel_region=0 boardrev=0x1403 wan2_gateway=0.0.0.0 il0macaddr=C0:3F:0E:61:4B:1E wl0.14_hwaddr=C2:3F:0E:61:4B:1C br0_ifnames=vlan2 eth1 wl_nctrlsb=none telnet_enable=0 wl_version=5.10.56.62 gui_Internet_state=0 wl0_leddc=0x64 et0macaddr=C0:3F:0E:61:4B:1E wla_temp_key1= ddns_enable=0 wla_temp_key2= wla_temp_passphrase= wiz_dhcp_wait_time=5 pppoe2_east_username=guest@flets pppoe2_bs_keyword= wla_temp_key3= traffic_enable=0 wl0_radarthrs=0 0x6a8 0x6c8 0x6ac 0x6c7 wla_temp_key4= wl_maxassoc=128 wl0_akm= watchdog=3000 boot_wait=off wla_sec_profile_enable_2=0 wl_phytypes= wl_leddc=0x64 wps_modelname=WGR614v10 pptp_idletime=5 wl0_infra=1 traffic_restart_hour=00 pppoe_localnetmask=... gui_Wireless_Radio_state=none et0mdcport=0 fw_disable=0 pppoe_tmp_mtu=1454 wl0_country_code=US pppoe_keepalive=1 wps_aplockdown_ageout=300 emf_rtport_entry= wps_config_command=0 ddns_wildcard=0 wla_wds_ptp_mac= wl_infra=1 rip_multicast=1 reset_gpio=3 run_test=0 wl0_bcn_rotate=1 pmon_ver=CFE 5.10.56.46 wlan_acl_dev30= first_wan_status=0 wlan_acl_dev31= restore_defaults=0 vlan2ports=0 1 2 3 5* wlan_acl_dev32= wl0.1_hwaddr=C2:3F:0E:61:4B:1F wlan_acl_dev33= wlan_acl_dev34= wl0_wme_sta_be=15 1023 3 0 0 off off wan_lease=86400 wlan_acl_dev35= wla_temp_sec_profile_enable_2= str_tbl_non_en_tag= wl0_nctrlsb=none wl0_version=5.10.56.62 wlan_acl_dev36= wl_wme_apsd=on str_tbl_non_en_ver= activeuser_ip= http_wanport= wlan_acl_dev37= wl_radius_ipaddr= ddns_hostname= bs_trustedip_temp=192.168.1.0 wl0.7_hwaddr=C2:3F:0E:61:4B:15 wan2_netmask=0.0.0.0 wlan_acl_dev38= wl0_ifname=eth1 wlan_acl_dev39= wla_key3_2= upnp_DHCPServerConfigurable=1 qos_rule_count=-1 ofdm2gpo=0x8822 lan_domain= pppoe2_bs_enable=0 wl0_wme_sta_bk=15 1023 7 0 0 off off timer_interval=3600 lan1_ipaddr=192.168.2.1 wl_net_reauth=36000 pptp_username= wl0_rxstreams=0 pppoe_mtu=1492 wla_temp_enable=enable_ap upnp_advert_period=30 second_wan_status=0 lan_route= wl0.1_wps_mode=disabled wl0_mrate=0 schedule_daylightadjust=0 wps_device_pin=42681847 fw_email_email_enable=0 wan_gateway=0.0.0.0 wla_secu_type=None wps_lan_led=0 gui_GuestNetwork_sec_profile=none wl0_mode=ap wan2_dns1= dhcp_start=192.168.1.2 mcs2gpo0=0x wan_hwaddr_sel=0 mcs2gpo1=0xaaa2 lan1_route= pppoe2_bs_keywords= wl0_ap_isolate=0 wl_msglevel=0x1 mcs2gpo2=0x8000 ntp_update_interval=86400 dhcp_end=192.168.1.254 auto_conn_24hr=Disable wl_mrate=0 traffic_warning_state=0 mcs2gpo3=0xccc8 wla_temp_ssid_2= wl_wmf_bss_enable=0 wl_akm= show_firmware_info=0 wl0.15_hwaddr=C2:3F:0E:61:4B:1D wl0_wme_no_ack=off wl0_ampdu=auto wl0_gmode=1 sromrev=3 qos_l7_apps=5:3 6:3 3:0 2:0 4:0 1:0 wla_allow_access_2=0 wla_temp_region=11 wla_wds_enable=0 boardtype=0x0505 pppoe2_mtu=1454 pppoe2_demand=0 pptp_passwd= aa2g=3 is_default=1 wla_autochannel=enable wl_wme_bss_disable=0 wl_ampdu_rr_rtylimit_tid=2 2 2 2 2 2 2 2 wl0.1_wme_bss_disable=0 wl0_nband=2 et1macaddr=C0:3F:0E:61:4B:1F wl_gmode=1 wl_ampdu=auto wps_uuid=0x7396027a6636acda33ca4a160b9f153c wps_perm_lock=0 wan_status=down wps_start=none stats_server= wlan_acl_dev40= traffic_cntime_monthly_limit=0 static_route= wlan_acl_dev41= wla_auth_type=automatic wl0_nreqd=0 wlan_acl_dev42= bs_enable_temp=0 ver_check_ftp_password=WGR614v10@ lan_netmask=255.255.255.0 wlan_acl_dev43= ver_check_enable=1 wl0_wme_txp_be=7 3 4 2 0 lan1_ifname= wlan_acl_dev44= wl_nband=2 wan_ipaddr_old=0.0.0.0 lan1_hwnames= pppoe2_west_passwd=flets wlan_acl_dev45= http_username=admin wl_wme_sta_vi=7 15 2 6016 3008 off off LangTagChinese=0 wl0_ssid=NETGEAR wl0_dtim=2 wlan_acl_dev46= super_passwd=Geardog wla_ap_isolate=0 wlan_acl_dev47= wl_nreqd=0 wl_wme_ap_be=15 63 3 0 0 off off wl0_dfs_preism=60 os_date=Sep 18 2012 pppoe_tmp_servicename= wlan_acl_dev48= http_rmenable=0 pptp_serv_ip=10.0.0.138 pppoe_user_ip=... access_mac_record=78-D6-F0-33-7E-B5 wla_wps_tmp_lock_flag=0 wlan_acl_dev49= wl0_wme_txp_bk=7 3 4 2 0 http_lanport=80 wl_plcphdr=long wl_wme_sta_vo=3 7 2 3264 1504 off off lan1_wins= wl_macmode=disabled wl_mimo_preamble=gfbcm wan_hwaddr2=C0:3F:0E:61:4B:1F wan_hwname= wan_domain= wlan_acl_d
Re: [OpenWrt-Devel] Frequent adsl disconnections with BTHOMEHUBV2B (lantiq xway danube)
On 17 November 2014 18:36, Sebastian Moeller wrote: > Hi Jaime, > maybe you should also look at the rror counters. Especially the CRC and HEC > errors short before the connection drops might be interesting. > Best Regards > Sebastian Hi everyone. I've set lcp-echo-failure to "10" and lcp-echo-interval to "3" and I'm still getting the disconnections. The logs fill with the following now: Thu Nov 20 15:29:55 2014 kern.warn kernel: [15746.372000] leave showtime Thu Nov 20 15:29:56 2014 daemon.info pppd[7651]: Terminating on signal 15 Thu Nov 20 15:29:56 2014 daemon.info pppd[7651]: Connect time 6.0 minutes. Thu Nov 20 15:29:56 2014 daemon.info pppd[7651]: Sent 89186 bytes, received 46470 bytes. Thu Nov 20 15:29:56 2014 daemon.notice netifd: Network device 'pppoa-wan' link is down Thu Nov 20 15:30:01 2014 daemon.notice netifd: Interface 'wan' is now down Thu Nov 20 15:30:11 2014 daemon.warn dnsmasq[1503]: no servers found in /tmp/resolv.conf.auto, will retry Thu Nov 20 15:30:24 2014 kern.err kernel: [15775.136000] [DSL_BSP_Showtime 894]: Datarate US intl = 924903, fast = 0 Thu Nov 20 15:30:24 2014 kern.warn kernel: [15775.14] enter showtime, cell rate: 0 - 2181, 1 - 2181, xdata addr: 0x82e9 Thu Nov 20 15:30:26 2014 daemon.notice netifd: Interface 'wan' is setting up now Thu Nov 20 15:30:26 2014 daemon.info pppd[7835]: Plugin pppoatm.so loaded. Thu Nov 20 15:30:26 2014 daemon.info pppd[7835]: PPPoATM plugin_init Thu Nov 20 15:30:26 2014 daemon.info pppd[7835]: PPPoATM setdevname_pppoatm - SUCCESS:0.38 Thu Nov 20 15:30:26 2014 daemon.notice pppd[7835]: pppd 2.4.7 started by root, uid 0 Thu Nov 20 15:30:26 2014 daemon.info pppd[7835]: Using interface pppoa-wan Perhaps the "lcp echo request" thing just be a red herring caused by the dsl link losing sync? I've also tried to find some info on how to get the error counters out for the lantiq dsl connection (using dsl_cpe_control), and the best info I can get hold of is: pmcctg 0 0 nReturn=15 nChannel=0 nDirection=0 nElapsedTime=18031 bValid=1 nCodeViolations=14662 nFEC=5910810 pmdpctg 0 0 nReturn=15 nChannel=0 nDirection=0 nElapsedTime=18058 bValid=1 nHEC=10735 nTotalCells=256128475 nUserTotalCells=1896600 nIBE=0 nTxUserTotalCells=0 nTxIBE=0 pmlsc1dg 0 0 nReturn=15 nDirection=0 nHistoryInterval=0 nElapsedTime=58145 bValid=1 nES=432 nSES=256 nLOSS=22 nUAS=2433 nLOFS=1868 The problem I now have is that I don't know how to interpret these results: are they good, or bad? (And do they explain why I'm getting dozens of disconnections every day?) Does anyone know if I can force a slower/lower connection speed from my side? (I would happily sacrifice some speed for more stability!) If not, I'm going to have to buy a dsl modem with a broadcom chipset and use that instead... J :-) ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] mysterious wl_exe.o
On Nov 20 06:35 +0100, Rafał Miłecki wrote: > I guess it's simply closed source. You can use "wlc" as a replacement. > > -- > Rafał closed source indeed. who's maintaining broadcom-wl anyway? don't see anything related in Makefile's headers/comments but i see patches signed-off by nbd and jow@openwrt and couple of folks @znau.edu.ua wlc would be the last resort i suppose. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] kernel: unset CONFIG_ARM_CCN
oldconfig kept asking for that config symbol... Signed-off-by: Daniel Golle --- target/linux/generic/config-3.18 | 1 + 1 file changed, 1 insertion(+) diff --git a/target/linux/generic/config-3.18 b/target/linux/generic/config-3.18 index ad8ea95..cb3760e 100644 --- a/target/linux/generic/config-3.18 +++ b/target/linux/generic/config-3.18 @@ -216,6 +216,7 @@ CONFIG_ARCH_FLATMEM_ENABLE=y # CONFIG_ARM_ARCH_TIMER is not set # CONFIG_ARM_AT91_ETHER is not set # CONFIG_ARM_CCI is not set +# CONFIG_ARM_CCN is not set CONFIG_ARM_CPU_TOPOLOGY=y CONFIG_ARM_DMA_MEM_BUFFERABLE=y # CONFIG_ARM_ERRATA_326103 is not set -- 2.1.3 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH 1/2] gemini: update ethernet driver, register ethernet on nas4220 board
On 22 October 2014 00:47, Roman Yeryomin wrote: > Signed-off-by: Roman Yeryomin > --- > target/linux/gemini/config-3.10|3 +- > .../120-net-add-gemini-gmac-driver.patch | 4181 > > .../121-arm-gemini-add-ethernet-device.patch | 82 - > .../121-arm-gemini-nas4220-register-ethernet.patch | 79 + > .../135-arm-gemini-nas4220-register-usb.patch |6 +- > 5 files changed, 2696 insertions(+), 1655 deletions(-) > delete mode 100644 > target/linux/gemini/patches-3.10/121-arm-gemini-add-ethernet-device.patch > create mode 100644 > target/linux/gemini/patches-3.10/121-arm-gemini-nas4220-register-ethernet.patch > Not sure why but seems this one didn't make it to patchwork. Regards, Roman ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
