Re: [OpenWrt-Devel] WiFi on Linksys WRT54GL
Hi, I tried 2.4 kernel and the problem of the driver is the same as why it was removed in 2.5 kernels, I suppose. WiFi stops working if the router is burdened with some task for some time (for example if PC in LAN is downloading something and the router is busy with transferring data during about 5 minutes). Also I couldn't manage with openl2tp thing started under 2.4. Is there some work doing about this issue? Thank, Vladimir -Original Message- From: openwrt-devel-boun...@lists.openwrt.org [mailto:openwrt-devel- boun...@lists.openwrt.org] On Behalf Of Jo-Philipp Wich Sent: Friday, September 18, 2009 6:23 PM To: OpenWrt Development List Subject: Re: [OpenWrt-Devel] WiFi on Linksys WRT54GL -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi. As far as I understand, in release 8.09 b43 driver is removed. Right. So the question is - when these drives be fixed or replaced with the working ones? Working drivers are in the brcm-2.4 builds of OpenWrt. Also b43 support is available in bcm47xx trunk builds. Regards, JoW -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkqzl7IACgkQdputYINPTPNyzgCgoHcsDMSRxDj7McBf26JEvweB L3YAoKOYe8RGRUHq5/BlbGTVs+cjabqy =5kAe -END PGP SIGNATURE- ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] WiFi on Linksys WRT54GL
Actually I didn't compile 2.4, I just tried the binary from the site. I have no idea what kind of driver is there. Nevertheless I can't use 2.4 kernel because openl2tp doesn’t compile for it because of kernel-mode implementation of pppol2tp doesn't exist for kernel 2.4 and openl2tp-1.6 which I use. -Original Message- From: openwrt-devel-boun...@lists.openwrt.org [mailto:openwrt-devel- boun...@lists.openwrt.org] On Behalf Of edgar.sol...@web.de Sent: Monday, September 21, 2009 1:00 PM To: OpenWrt Development List Subject: Re: [OpenWrt-Devel] WiFi on Linksys WRT54GL You have the proprietary _and_ the open source driver under 2.4. Do both show this issue? ... ede On 21.09.2009 10:05, Vladimir Voronkov wrote: Hi, I tried 2.4 kernel and the problem of the driver is the same as why it was removed in 2.5 kernels, I suppose. WiFi stops working if the router is burdened with some task for some time (for example if PC in LAN is downloading something and the router is busy with transferring data during about 5 minutes). Also I couldn't manage with openl2tp thing started under 2.4. Is there some work doing about this issue? Thank, Vladimir -Original Message- From: openwrt-devel-boun...@lists.openwrt.org [mailto:openwrt-devel- boun...@lists.openwrt.org] On Behalf Of Jo-Philipp Wich Sent: Friday, September 18, 2009 6:23 PM To: OpenWrt Development List Subject: Re: [OpenWrt-Devel] WiFi on Linksys WRT54GL -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi. As far as I understand, in release 8.09 b43 driver is removed. Right. So the question is - when these drives be fixed or replaced with the working ones? Working drivers are in the brcm-2.4 builds of OpenWrt. Also b43 support is available in bcm47xx trunk builds. Regards, JoW -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkqzl7IACgkQdputYINPTPNyzgCgoHcsDMSRxDj7McBf26JEvweB L3YAoKOYe8RGRUHq5/BlbGTVs+cjabqy =5kAe -END PGP SIGNATURE- ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] WiFi on Linksys WRT54GL
Guys, As far as I understand, in release 8.09 b43 driver is removed. I really like OpenWrt firmware but my router isn't working in its' all capabilities. Moreover, I can't use any other firmware because of some troubles with my ISP and I could solve them only with openwrt. So the question is - when these drives be fixed or replaced with the working ones? Thanks for understanding. Vladimir Voronkov ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] ppp switch to version 2.4.4
This patch changes version of ppp to 2.4.4, which is required for openl2tp-1.6
to work.
Patch with integration of openl2tp will be sent in my next email.
All current patches to ppp-2.4.3 are changed according to a new version of ppp,
some of them are removed (namely 102, 202, 205, 207) because they already exist
in ppp-2.4.4.
Also kmod-pppol2tp kernel module has been added in configuration.
Signed-off-by: Vladimir Voronkov voronkovv at mail.ru
---
Index: package/kernel/modules/network.mk
===
--- package/kernel/modules/network.mk (revision 16973)
+++ package/kernel/modules/network.mk (working copy)
@@ -367,6 +367,7 @@
FILES:= \
$(LINUX_DIR)/drivers/net/pppoe.$(LINUX_KMOD_SUFFIX) \
$(LINUX_DIR)/drivers/net/pppox.$(LINUX_KMOD_SUFFIX)
+ AUTOLOAD:=$(call AutoLoad,40,pppox pppoe)
endef
define KernelPackage/pppoe/description
@@ -376,6 +377,22 @@
$(eval $(call KernelPackage,pppoe))
+define KernelPackage/pppol2tp
+ SUBMENU:=$(NETWORK_SUPPORT_MENU)
+ TITLE:=PPPoL2TP support
+ DEPENDS:=kmod-ppp +kmod-pppoe
+ KCONFIG:=CONFIG_PPPOL2TP
+ FILES:=$(LINUX_DIR)/drivers/net/pppol2tp.$(LINUX_KMOD_SUFFIX)
+ AUTOLOAD:=$(call AutoLoad,40,pppol2tp)
+endef
+
+define KernelPackage/pppol2tp/description
+ Kernel modules for PPPoL2TP (PPP over L2TP) support
+endef
+
+$(eval $(call KernelPackage,pppol2tp))
+
+
define KernelPackage/pppoa
SUBMENU:=$(NETWORK_SUPPORT_MENU)
TITLE:=PPPoA support
Index: package/ppp/patches/101-debian_ip-up_option.patch
===
--- package/ppp/patches/101-debian_ip-up_option.patch (revision 16973)
+++ package/ppp/patches/101-debian_ip-up_option.patch (working copy)
@@ -2,37 +2,37 @@
===
--- ppp-2.4.3.orig/pppd/ipcp.c 2007-06-04 13:22:08.478566344 +0200
+++ ppp-2.4.3/pppd/ipcp.c 2007-06-04 13:22:09.003486544 +0200
-@@ -1846,7 +1846,7 @@
+@@ -1850,7 +1850,7 @@
*/
if (ipcp_script_state == s_down ipcp_script_pid == 0) {
ipcp_script_state = s_up;
-- ipcp_script(_PATH_IPUP);
-+ ipcp_script(path_ipup);
+- ipcp_script(_PATH_IPUP, 0);
++ ipcp_script(path_ipup, 0);
}
}
-@@ -1896,7 +1896,7 @@
+@@ -1900,7 +1900,7 @@
/* Execute the ip-down script */
if (ipcp_script_state == s_up ipcp_script_pid == 0) {
ipcp_script_state = s_down;
-- ipcp_script(_PATH_IPDOWN);
-+ ipcp_script(path_ipdown);
+- ipcp_script(_PATH_IPDOWN, 0);
++ ipcp_script(path_ipdown, 0);
}
}
-@@ -1950,13 +1950,13 @@
+@@ -1954,13 +1954,13 @@
case s_up:
if (ipcp_fsm[0].state != OPENED) {
ipcp_script_state = s_down;
-- ipcp_script(_PATH_IPDOWN);
-+ ipcp_script(path_ipdown);
+- ipcp_script(_PATH_IPDOWN, 0);
++ ipcp_script(path_ipdown, 0);
}
break;
case s_down:
if (ipcp_fsm[0].state == OPENED) {
ipcp_script_state = s_up;
-- ipcp_script(_PATH_IPUP);
-+ ipcp_script(path_ipup);
+- ipcp_script(_PATH_IPUP, 0);
++ ipcp_script(path_ipup, 0);
}
break;
}
@@ -40,7 +40,7 @@
===
--- ppp-2.4.3.orig/pppd/main.c 2007-06-04 13:22:08.487564976 +0200
+++ ppp-2.4.3/pppd/main.c 2007-06-04 13:22:09.004486392 +0200
-@@ -314,6 +314,9 @@
+@@ -315,6 +315,9 @@
struct protent *protp;
char numbuf[16];
@@ -54,7 +54,7 @@
===
--- ppp-2.4.3.orig/pppd/options.c 2007-06-04 13:22:08.495563760 +0200
+++ ppp-2.4.3/pppd/options.c 2007-06-04 13:22:09.005486240 +0200
-@@ -108,6 +108,8 @@
+@@ -113,6 +113,8 @@
bool tune_kernel;/* may alter kernel settings */
int connect_delay = 1000; /* wait this many ms after connect script */
int req_unit = -1; /* requested interface unit */
@@ -63,7 +63,7 @@
bool multilink = 0; /* Enable multilink operation */
char *bundle_name = NULL;/* bundle name for multilink */
bool dump_options; /* print out option values */
-@@ -276,6 +278,13 @@
+@@ -281,6 +283,13 @@
Number of seconds to wait for child processes at exit,
OPT_PRIO },
Index: package/ppp/patches/202-atm_fix.patch (deleted)
===
Index: package/ppp/patches/209-compensate_time_change.patch
===
--- package/ppp/patches/209-compensate_time_change.patch(revision 16973)
+++ package/ppp/patches/209-compensate_time_change.patch(working copy)
@@ -18,7 +18,7 @@
static void setup_signals __P((void));
static void create_pidfile __P((int pid));
static void create_linkpidfile __P((int pid));
-@@ -531,6 +533,7 @@
+@@ -532,6 +534,7
[OpenWrt-Devel] [PATCH] openl2tp-1.6 package support
This patch is for packages branch adds integration of openl2tp-1.6 support.
Startup script openl2tp.init has to be changed for common use.
I included it as an example of openl2tp module usage.
Signed-off-by: Vladimir Voronkov voronkovv at mail.ru
---
Index: net/openl2tp/files/openl2tpd.init
===
--- net/openl2tp/files/openl2tpd.init (revision 0)
+++ net/openl2tp/files/openl2tpd.init (revision 0)
@@ -0,0 +1,351 @@
+#!/bin/sh /etc/rc.common
+
+START=47
+
+USER='username'
+
+IP='85.21.0.251'
+
+L2TP='openl2tpd'
+OPTS='-u 1701'
+CONF='l2tpconfig'
+RPC='portmap'
+MOD='pppol2tp'
+L2TPRT='/var/run/openl2tpd.route'
+LED='/proc/diag/led/dmz'
+
+replace_default_route() {
+ if [ -r $L2TPRT ]; then
+GW=`cat $L2TPRT | awk '{if ($1 == GW) print $2}'`
+ else
+GW=`route -n 2 /dev/null | awk '{if ($1 == 0.0.0.0 $2 !=
0.0.0.0 $8 ~ eth) print $2}'`
+ fi
+
+ if [ -z $GW ]; then
+echo failed, no default gateway
+return 1
+ fi
+
+ TUNIP=`route -n | awk '{if ($2 == 0.0.0.0 $4 ~ H $8 ~
ppp) print $1}'`
+
+ if [ -z $TUNIP ]; then
+echo failed, no tunnel
+return 1
+ fi
+
+ if ! (route del default gw $GW 2 /dev/null) || ! (route add default
gw $TUNIP 2 /dev/null); then
+echo failed
+return 1
+ fi
+
+ echo done
+}
+
+restore_default_route() {
+ if [ -r $L2TPRT ]; then
+GW=`cat $L2TPRT | awk '{if ($1 == GW) print $2}'`
+ else
+IP=`nslookup tp.corbina.net 2 /dev/null | awk '{if ($1 ~ Address
$4 ~ corbina.net) print $3}'`
+if [ -z $IP ]; then
+ echo failed
+ return 1
+fi
+GW=`route -n 2 /dev/null | awk -v IP=$IP '{if ($1 == IP $2 !=
0.0.0.0 $8 ~ eth) print $2}'`
+ fi
+
+ TUNIP=`route -n 2 /dev/null | awk '{if ($1 == 0.0.0.0 $2 !=
0.0.0.0 $4 ~ G $8 ~ ppp) print $2}'`
+ if [ -n $TUNIP ]; then
+route del default gw $TUNIP 2 /dev/null
+ fi
+
+ if [ -z $GW ] || ! route add default gw $GW 2 /dev/null; then
+echo failed
+return 1
+ fi
+
+ echo done
+}
+
+#IPTABLES=echo iptables
+IPTABLES=iptables
+zone='wan'
+ifname='ppp+'
+
+add_iptables_rules() {
+ $IPTABLES -A input -i $ifname -j zone_${zone}
+ $IPTABLES -I zone_${zone}_MSSFIX 1 -o $ifname -p tcp --tcp-flags
SYN,RST SYN -j TCPMSS --clamp-mss-to-pmtu
+ $IPTABLES -I zone_${zone}_ACCEPT 1 -o $ifname -j ACCEPT
+ $IPTABLES -I zone_${zone}_DROP 1 -o $ifname -j DROP
+ $IPTABLES -I zone_${zone}_REJECT 1 -o $ifname -j reject
+ $IPTABLES -I zone_${zone}_ACCEPT 1 -i $ifname -j ACCEPT
+ $IPTABLES -I zone_${zone}_DROP 1 -i $ifname -j DROP
+ $IPTABLES -I zone_${zone}_REJECT 1 -i $ifname -j reject
+ $IPTABLES -I zone_${zone}_nat 1 -t nat -o $ifname -j MASQUERADE
+ $IPTABLES -I PREROUTING 1 -t nat -i $ifname -j zone_
${zone}_prerouting
+ $IPTABLES -A forward -i $ifname -j zone_${zone}_forward
+ #iptables -A INPUT -p udp -j ACCEPT --dport 1701 -m state --state NEW
+
+ echo done
+}
+
+del_iptables_rules() {
+ $IPTABLES -D input -i $ifname -j zone_${zone}
+ $IPTABLES -D zone_${zone}_MSSFIX -o $ifname -p tcp --tcp-flags
SYN,RST SYN -j TCPMSS --clamp-mss-to-pmtu
+ $IPTABLES -D zone_${zone}_ACCEPT -o $ifname -j ACCEPT
+ $IPTABLES -D zone_${zone}_DROP -o $ifname -j DROP
+ $IPTABLES -D zone_${zone}_REJECT -o $ifname -j reject
+ $IPTABLES -D zone_${zone}_ACCEPT -i $ifname -j ACCEPT
+ $IPTABLES -D zone_${zone}_DROP -i $ifname -j DROP
+ $IPTABLES -D zone_${zone}_REJECT -i $ifname -j reject
+ $IPTABLES -D zone_${zone}_nat -t nat -o $ifname -j MASQUERADE
+ $IPTABLES -D PREROUTING -t nat -i $ifname -j zone_
${zone}_prerouting
+ $IPTABLES -D forward -i $ifname -j zone_${zone}_forward
+
+ echo done
+}
+
+add_l2tp_route() {
+ if [ -r $L2TPRT ]; then
+rm -f $L2TPRT
+ fi
+ if [ -z $IP ]; then
+IP=`nslookup tp.corbina.net 2 /dev/null | awk '{if ($1 ~ Address
$4 ~ corbina.net) print $3}'`
+if [ -z $IP ]; then
+ echo failed, no IP for L2TP server.
+ return 1
+fi
+ fi
+
+ RT=`route -n 2 /dev/null | awk -v IP=$IP '{if ($1 == IP $2 !=
0.0.0.0 $8 ~ eth) print $2}'`
+ if [ -n $RT ]; then
+echo IP $IP $L2TPRT
+echo GW $RT $L2TPRT
+echo ok, route is already created.
+return
+ fi
+
+ GW=`route -n 2 /dev/null | awk '{if ($1 == 0.0.0.0 $2 !=
0.0.0.0 $8 ~ eth) print $2}'`
+ if [ -z $GW ]; then
+echo failed, no default gateway.
+return 1
+ fi
+
+ route add $IP gw $GW
+ RT=`route -n 2 /dev/null | awk -v IP=$IP '{if ($1 == IP $2 !=
0.0.0.0 $8 ~ eth) print $2}'`
+ if [ -z $RT ]; then
+echo failed
+return 1
+ fi
+
+ echo IP $IP $L2TPRT
+ echo GW $GW $L2TPRT
+ echo done
+}
+
+del_l2tp_route() {
+ if [ -r $L2TPRT ]; then
+IP=`cat $L2TPRT | awk '{if ($1 == IP) print $2}'`
+GW=`cat $L2TPRT | awk '{if ($1 == GW) print $2}'`
+rm -f $L2TPRT
+ else
+echo -n using hostname...
+if [ -z $IP ]; then
+ IP=`nslookup tp.corbina.net 2 /dev/null | awk '{if ($1 ~
Address $4 ~ corbina.net) print $3}'`
+ if [ -z $IP ]; then
+echo
Re: [OpenWrt-Devel] [PATCH] ppp switch to versi on 2.4.4
Hi, Florian,
I am new to submitting patches for openWRT, I am sorry for some mistakes in the
emails. Should I re-send
them again or you have applied the patches? How can I see the revision number
with my changes?
About configuration file for OpenL2TP - I was unable to build it with
L2TP_FEATURE_LOCAL_CONF_FILE because
of some dependencies that I couldn't resolve. For now OpenL2TP can only be
configured via rpc tool
l2tpconfig, see how it is used in my script. I understand that it is not
acceptable for generic purposes,
I just included in for you guys to see how it can be used in openwrt
configuration. Unfortunately I am not
aware of how UCI works. If you give me advice on how I can create startup
scrips or maybe some link where
I can read more info about it I will definitely improve that. I have in plans
to integrate it also in
luci-admin tool but I still investigating the code how you do this.
About kmod-pppol2tp for kernel version 2.6.28 and newer - what I can say is -
it works on my system:
device is Linksys WRT54GL v. 1.1
KAMIKAZE (8.09.1, r16973)
r...@openwrt:~# cat /proc/version
Linux version 2.6.25.20 (v...@vvv-vm-ubuntu) (gcc version 4.1.2) #6 Sat Jul 25
22:44:13 MSD 2009
and loaded
r...@openwrt:~# lsmod
Module Size Used byNot tainted
...
pppol2tp 29648 4
OpenL2TP doesn't work without it.
I also have quiestion about WiFi for my device. I built the firmware from
revision r16973, choosing
Broadcom BCM947xx/953xx [2.6] as a target and Broadcom BCM43xx WiFi as a
profile but I don't see that
kmod-b43 module is built and installed in my system. Revision is 8.09.1,
r16973. That is why WiFi isn't
working. Could you please explain what I did wrong or maybe what packages I
should include into my build.
Thanks for your support!
-Original Message-
From: Florian Fainelli flor...@openwrt.org
To: openwrt-devel@lists.openwrt.org
Date: Sun, 26 Jul 2009 12:27:22 +0200
Subject: Re: [OpenWrt-Devel] [PATCH] ppp switch to version 2.4.4
Hi Validimir,
Le Sunday 26 July 2009 10:45:38 Vladimir Voronkov, vous avez Иcrit :
This patch changes version of ppp to 2.4.4, which is required for
openl2tp-1.6 to work. Patch with integration of openl2tp will be sent in my
next email.
All current patches to ppp-2.4.3 are changed according to a new version of
ppp, some of them are removed (namely 102, 202, 205, 207) because they
already exist in ppp-2.4.4.
ppp-2.4.4 has been updated a while already, so I have only applied the
kmod-pppol2tp part of this patch. Also PPP over L2TP only appeared in 2.6.28
therefore the module is restricted to the kernel versions it can be built on.
Also kmod-pppol2tp kernel module has been added in configuration.
Signed-off-by: Vladimir Voronkov voronkovv at mail.ru
---
Index: package/kernel/modules/network.mk
===
--- package/kernel/modules/network.mk (revision 16973)
+++ package/kernel/modules/network.mk (working copy)
@@ -367,6 +367,7 @@
FILES:= \
$(LINUX_DIR)/drivers/net/pppoe.$(LINUX_KMOD_SUFFIX) \
$(LINUX_DIR)/drivers/net/pppox.$(LINUX_KMOD_SUFFIX)
+ AUTOLOAD:=$(call AutoLoad,40,pppox pppoe)
endef
define KernelPackage/pppoe/description
@@ -376,6 +377,22 @@
$(eval $(call KernelPackage,pppoe))
+define KernelPackage/pppol2tp
+ SUBMENU:=$(NETWORK_SUPPORT_MENU)
+ TITLE:=PPPoL2TP support
+ DEPENDS:=kmod-ppp +kmod-pppoe
+ KCONFIG:=CONFIG_PPPOL2TP
+ FILES:=$(LINUX_DIR)/drivers/net/pppol2tp.$(LINUX_KMOD_SUFFIX)
+ AUTOLOAD:=$(call AutoLoad,40,pppol2tp)
+endef
+
+define KernelPackage/pppol2tp/description
+ Kernel modules for PPPoL2TP (PPP over L2TP) support
+endef
+
+$(eval $(call KernelPackage,pppol2tp))
+
+
define KernelPackage/pppoa
SUBMENU:=$(NETWORK_SUPPORT_MENU)
TITLE:=PPPoA support
Index: package/ppp/patches/101-debian_ip-up_option.patch
===
--- package/ppp/patches/101-debian_ip-up_option.patch (revision 16973)
+++ package/ppp/patches/101-debian_ip-up_option.patch (working copy)
@@ -2,37 +2,37 @@
===
--- ppp-2.4.3.orig/pppd/ipcp.c 2007-06-04 13:22:08.478566344 +0200
+++ ppp-2.4.3/pppd/ipcp.c 2007-06-04 13:22:09.003486544 +0200
-@@ -1846,7 +1846,7 @@
+@@ -1850,7 +1850,7 @@
*/
if (ipcp_script_state == s_down ipcp_script_pid == 0) {
ipcp_script_state = s_up;
-- ipcp_script(_PATH_IPUP);
-+ ipcp_script(path_ipup);
+- ipcp_script(_PATH_IPUP, 0);
++ ipcp_script(path_ipup, 0);
}
}
-@@ -1896,7 +1896,7 @@
+@@ -1900,7 +1900,7 @@
/* Execute the ip-down script */
if (ipcp_script_state == s_up ipcp_script_pid == 0) {
ipcp_script_state = s_down
