[OpenWrt-Devel] hostapd WDS nl80211 mac80211 wds_bridge
Hi I'm tryin to understand wds so I'm trying to set one up using some Ar9103 cards , there are some questions regarding it's setup, in hostapd configuration file it's mentioned that it's only supported with driver=nl80211 and I'm guessing I may be using ath9k (mac80211) for these routers (wr1043nd,g300nh,wr941nd). so are there any other programs that is going to handle this since I find nothing regarding wds in hostapd.sh ? is it possible with using wds_bridge=wds-br0 force the wds to talk to other stations on wired network ? if they all operate on same channel I think that would be a good deal to make areas less crowded for each network with a better roaming. I'll appreciate if someone shed some light to this cave thanks ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH][BRCM63XX] Add CT6376-1 board support
Add CT6376-1 board support.
This board uses the same 74HC64 configuration of Neufbox 4
(adsl/line/fxs1/fxs2).
Signed-off-by: Álvaro Fernández Rojas nolt...@gmail.com
Index: target/linux/brcm63xx/patches-3.3/555-board-CT6376-1.patch
===
--- target/linux/brcm63xx/patches-3.3/555-board-CT6376-1.patch (revisión: 0)
+++ target/linux/brcm63xx/patches-3.3/555-board-CT6376-1.patch (revisión: 0)
@@ -0,0 +1,87 @@
+--- a/arch/mips/bcm63xx/boards/board_bcm963xx.c
b/arch/mips/bcm63xx/boards/board_bcm963xx.c
+@@ -2287,6 +2287,76 @@ static struct board_info __initdata boar
+ .num_spis = ARRAY_SIZE(nb4_spi_devices),
+ };
+
++static struct board_info __initdata board_ct6373_1 = {
++ .name = CT6373-1,
++ .expected_cpu_id= 0x6358,
++
++ .has_uart0 = 1,
++ .has_pci= 1,
++ .has_ohci0 = 1,
++ .has_ehci0 = 1,
++
++ .has_enet1 = 1,
++ .enet1 = {
++ .force_speed_100= 1,
++ .force_duplex_full = 1,
++ },
++
++ .leds = {
++ {
++ .name = CT6373-1:green:power,
++ .gpio = 0,
++ .default_trigger = default-on,
++ },
++ {
++ .name = CT6373-1:green:usb,
++ .gpio = 3,
++ .active_low = 1,
++ },
++ {
++ .name = CT6373-1:green:wlan,
++ .gpio = 9,
++ .active_low = 1,
++ },
++ {
++ .name = CT6373-1:green:adsl,
++ .gpio = NB4_74HC64_GPIO(0),
++ .active_low = 1,
++ },
++ {
++ .name = CT6373-1:green:line,
++ .gpio = NB4_74HC64_GPIO(1),
++ .active_low = 1,
++ },
++ {
++ .name = CT6373-1:green:fxs1,
++ .gpio = NB4_74HC64_GPIO(2),
++ .active_low = 1,
++ },
++ {
++ .name = CT6373-1:green:fxs2,
++ .gpio = NB4_74HC64_GPIO(3),
++ .active_low = 1,
++ },
++ },
++
++ .buttons = {
++ {
++ .desc = reset,
++ .gpio = 35,
++ .active_low = 1,
++ .type = EV_KEY,
++ .code = KEY_RESTART,
++ .debounce_interval = BCM963XX_KEYS_DEBOUNCE_INTERVAL,
++ },
++ },
++
++ .devs = nb4_devices,
++ .num_devs = ARRAY_SIZE(nb4_devices),
++ .spis = nb4_spi_devices,
++ .num_spis = ARRAY_SIZE(nb4_spi_devices),
++};
++
+ static struct board_info __initdata board_HW553 = {
+ .name = HW553,
+ .expected_cpu_id= 0x6358,
+@@ -2620,6 +2690,7 @@ static const struct board_info __initdat
+ board_nb4_ser_r2,
+ board_nb4_fxc_r1,
+ board_nb4_fxc_r2,
++ board_ct6373_1,
+ board_HW553,
+ board_spw303v,
+ #endif
Index: target/linux/brcm63xx/base-files/etc/uci-defaults/network
===
--- target/linux/brcm63xx/base-files/etc/uci-defaults/network (revisión:
32614)
+++ target/linux/brcm63xx/base-files/etc/uci-defaults/network (copia de
trabajo)
@@ -18,6 +18,7 @@
963281TAN |\
96348A-122 |\
96358-502V |\
+CT6373-1 |\
AW4339U |\
CPVA642 |\
CT536_CT5621 |\
Index: target/linux/brcm63xx/base-files/etc/uci-defaults/brcm63xx_fixcrc.sh
===
--- target/linux/brcm63xx/base-files/etc/uci-defaults/brcm63xx_fixcrc.sh
(revisión: 32614)
+++ target/linux/brcm63xx/base-files/etc/uci-defaults/brcm63xx_fixcrc.sh
(copia de trabajo)
@@ -18,6 +18,7 @@
CPVA502+ |\
AW4339U |\
CPVA642 |\
+ CT6373-1 |\
MAGIC |\
V2110 |\
V2500V_BB)
Index: target/linux/brcm63xx/image/Makefile
===
--- target/linux/brcm63xx/image/Makefile(revisión: 32614)
+++ target/linux/brcm63xx/image/Makefile(copia de trabajo)
@@ -191,6 +191,8 @@
$(call Image/Build/CFEFIXUP,$(1),96348GW,GW6200,6348,GW6200,$(shell
printf '\x99'))
# Neufbox4
$(call Image/Build/CFE,$(1),96358VW,6358,NEUFBOX4,OpenWRT-$(REVISION))
+ # Comtrend 6373
+ $(call
[OpenWrt-Devel] [PATCH] dropbear: set DEFAULT_PATH for non-interactive logins
Set PATH in non-interactive logins to include /sbin paths, so to be consistent with what is currently set in /etc/profile for interactive shells. Signed-off-by: Gui Iribarren g...@altermundi.net --- Index: package/dropbear/patches/500-set-default-path.patch === --- package/dropbear/patches/500-set-default-path.patch (revision 0) +++ package/dropbear/patches/500-set-default-path.patch (revision 0) @@ -0,0 +1,11 @@ +--- /a/options.h 2011-11-08 09:48:15.0 -0300 /b/options.h 2012-07-05 12:45:49.296635776 -0300 +@@ -292,7 +297,7 @@ + #define DEFAULT_IDLE_TIMEOUT 0 + + /* The default path. This will often get replaced by the shell */ +-#define DEFAULT_PATH /usr/bin:/bin ++#define DEFAULT_PATH /bin:/sbin:/usr/bin:/usr/sbin + + /* Some other defines (that mostly should be left alone) are defined + * in sysoptions.h */ ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATH] Adds support for libsocketcan
Please find a link to a patch for adding libsocketcan Signed-off-by: Gerhard Bertelsmann info at gerhard-bertelsmann http://lnxpps.de/can2udpe/libsocketcan_patch.txt ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] dnsmasq - bump version and add config option for ra_names
Hi,
(I just subscribed to the list, so sorry if my mail format isn't right
somehow. I quickly glanced at the archive and don't think what I offer
has been looked at, aside of a quick reference to the changelog when
the feature wasn't available in a stable release of dnsmasq yet)
ra_names is a feature introduced in dnsmasq 2.61, which is why I changed
the rules to build something newer (and figured I might as well take it
to 62)
Basically, it:
- does router-advertisment (not dhcpv6)
- when it gets a request for RA, it looks up if there is an active ipv4
lease for the same host via its MAC address, and if there is it adds
the to-be ipv6 to the local dns (assuming the host will take the dns)
- when it gets a dhcpv4 release it takes off the ipv6 dns record as
well
(since RA is stateless and doesn't give the host name, I couldn't figure
any better way without dhcpv6; I was about to hack something (with a
very large axe and radvd) when I found out they've done it already :D)
There are also modes for router-advertisment only which I haven't looked
at, and a dhcpv6 client implementation that I didn't try yet either.
The option I added is in the dhcp field, a ra_name option with the
prefix to announce in RAs, i.e.
config dhcp 'lan'
option interface 'lan'
option ra_names '2001:dead:beef::'
(Note: it doesn't seem to add the local dns with a fe80:: prefix)
Attached is the patch in svn format, feel free to ask if you prefer git's (I
personally do but didn't look hard enough for the git repository!)
Please give any comment and include something similar if you like it.
Rergards,
--
Dominique Martinet | Asmadeus
Index: package/dnsmasq/files/dnsmasq.init
===
--- package/dnsmasq/files/dnsmasq.init (revision 32579)
+++ package/dnsmasq/files/dnsmasq.init (working copy)
@@ -360,6 +360,12 @@
xappend --dhcp-range=$networkid,$START,$END,$NETMASK,$leasetime${options:+ $options}
dhcp_option_add $cfg $networkid
+
+ config_get ra_names $cfg ra_names
+
+ [ -n $ra_names ] {
+ xappend --dhcp-range=$networkid,$ra_names,ra-names,$leasetime
+ }
}
dhcp_option_add() {
Index: package/dnsmasq/patches/101-ipv6.patch
===
--- package/dnsmasq/patches/101-ipv6.patch (revision 32579)
+++ package/dnsmasq/patches/101-ipv6.patch (working copy)
@@ -1,13 +0,0 @@
a/src/config.h
-+++ b/src/config.h
-@@ -263,8 +263,9 @@ NOTES:
- /* We assume that systems which don't have IPv6
-headers don't have ntop and pton either */
-
--#if defined(INET6_ADDRSTRLEN) defined(IPV6_V6ONLY) !defined(NO_IPV6)
-+#if defined(INET6_ADDRSTRLEN) !defined(NO_IPV6)
- # define HAVE_IPV6
-+# define IPV6_V6ONLY 26
- # define ADDRSTRLEN INET6_ADDRSTRLEN
- # if defined(SOL_IPV6)
- #define IPV6_LEVEL SOL_IPV6
Index: package/dnsmasq/Makefile
===
--- package/dnsmasq/Makefile (revision 32579)
+++ package/dnsmasq/Makefile (working copy)
@@ -8,12 +8,12 @@
include $(TOPDIR)/rules.mk
PKG_NAME:=dnsmasq
-PKG_VERSION:=2.59
-PKG_RELEASE:=4
+PKG_VERSION:=2.62
+PKG_RELEASE:=1
PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.gz
PKG_SOURCE_URL:=http://thekelleys.org.uk/dnsmasq
-PKG_MD5SUM:=b5757ef2d7b651748eeebb88af29d7d6
+PKG_MD5SUM:=f47e5cb8f5bac6343f24b2dbe317ab40
PKG_INSTALL:=1
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] dnsmasq - bump version and add config option for ra_names
On Thu, Jul 5, 2012 at 3:38 PM, Dominique Martinet asmad...@codewreck.org wrote: Hi, (I just subscribed to the list, so sorry if my mail format isn't right somehow. I quickly glanced at the archive and don't think what I offer has been looked at, aside of a quick reference to the changelog when the feature wasn't available in a stable release of dnsmasq yet) ra_names is a feature introduced in dnsmasq 2.61, which is why I changed the rules to build something newer (and figured I might as well take it to 62) Basically, it: - does router-advertisment (not dhcpv6) - when it gets a request for RA, it looks up if there is an active ipv4 lease for the same host via its MAC address, and if there is it adds the to-be ipv6 to the local dns (assuming the host will take the dns) - when it gets a dhcpv4 release it takes off the ipv6 dns record as well (since RA is stateless and doesn't give the host name, I couldn't figure any better way without dhcpv6; I was about to hack something (with a very large axe and radvd) when I found out they've done it already :D) This is gorgeous Dominique, My planned hack involved ladvd and flooding the network with LLDP packets, then parse the info inside those packets and spew it in /tmp/dhcp.leases I was just waiting for ladvd dev to patch the source so that it can compile cleanly on OpenWrt. While that scheme doesn't depend on ipv4, ra_names is definitely more elegant and as long as double-stack is the standard, i'll buy it! There are also modes for router-advertisment only which I haven't looked at, and a dhcpv6 client implementation that I didn't try yet either. The option I added is in the dhcp field, a ra_name option with the prefix to announce in RAs, i.e. config dhcp 'lan' option interface 'lan' option ra_names '2001:dead:beef::' I understand this serves the double purpose of activating this feature, and at the same time making dnsmasq send RA, so no radvd is needed or does it depend on RA sent by radvd ? in the second case, wouldn't it make sense to get the prefix config directly from /etc/config/radvd instead of duplicating information? (Note: it doesn't seem to add the local dns with a fe80:: prefix) It shouldn't, AFAIU link-local addresses are not meant to be resolved, since they always need the interface scope suffix Attached is the patch in svn format, feel free to ask if you prefer git's (I personally do but didn't look hard enough for the git repository!) Please give any comment and include something similar if you like it. Rergards, -- Dominique Martinet | Asmadeus ___ 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] [PATCH] dnsmasq - bump version and add config option for ra_names
Hi, Gui Iribarren wrote on Thu, Jul 05, 2012 : On Thu, Jul 5, 2012 at 3:38 PM, Dominique Martinet asmad...@codewreck.org wrote: config dhcp 'lan' option interface 'lan' option ra_names '2001:dead:beef::' I understand this serves the double purpose of activating this feature, and at the same time making dnsmasq send RA, so no radvd is needed or does it depend on RA sent by radvd ? in the second case, wouldn't it make sense to get the prefix config directly from /etc/config/radvd instead of duplicating information? It effectively makes radvd unneeded (but harmless, I just tried with both running with my previous radvd configuration), so it seems better to give the prefix here. I'm pretty sure it would be possible to have the same feature with announces only from radvd and dnsmasq passively listening, but I didn't find a way to do so and for what I've been using radvd it doesn't seem to change much. Also I forgot to say it in the mail body, but I removed some ipv6 patch for dnsmasq as it no longer applied, I am not quite sure what or if it implies anything. -- Asmadeus | Dominique Martinet ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] dnsmasq - bump version and add config option for ra_names
On Thu, Jul 5, 2012 at 5:18 PM, Dominique Martinet asmad...@codewreck.org wrote: Hi, Gui Iribarren wrote on Thu, Jul 05, 2012 : On Thu, Jul 5, 2012 at 3:38 PM, Dominique Martinet asmad...@codewreck.org wrote: config dhcp 'lan' option interface 'lan' option ra_names '2001:dead:beef::' I understand this serves the double purpose of activating this feature, and at the same time making dnsmasq send RA, so no radvd is needed or does it depend on RA sent by radvd ? in the second case, wouldn't it make sense to get the prefix config directly from /etc/config/radvd instead of duplicating information? It effectively makes radvd unneeded (but harmless, I just tried with both running with my previous radvd configuration), so it seems better to give the prefix here. Agree, great to know. I'm pretty sure it would be possible to have the same feature with announces only from radvd and dnsmasq passively listening, but I didn't find a way to do so and for what I've been using radvd it doesn't seem to change much. I'm currently using the config rdnss feature of radvd so that SLAAC hosts also get a DNS server entry, again independent of dhcpv4. I assume that's also possible with this new scheme, right? i could search about it on dnsmasq documentation , but you seem to have immersed in the subject much more than i could achieve right now. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
