Hi,
please do not do dirty hacks like relying on an interface called wan
in your scripts. You should develop a hotplug handler which is invoked
for ifup events on any interface. As soon as one interface appears
which carries as 0/0 route, you have your wan.
See the 6in4 and 6to4 packages for
I'd suggest to use ip route list exact 0.0.0.0/0 to find the device
and then the find_config() shell function to map the device to an uci
interface name.
~ Jow
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
I have however a designed issue. At the moment a bash daemon periodically
checks if the wan interface is up. If the check is positive then the mesh
daemon
advertise this gateway, otherwise the mesh interface is set as default
route.
in the OLSR routing protocol implementation, we have a
These patches add support for 802.1Q VLANs on ADM6996M and ADM6996FC. It is
called version 3; version 2 wasn't explicitly called as such, but the version I
sent April 3 would be it.
I am submitting for inclusion in OpenWRT the driver for the M chip. Since I
don't have the FC chip, I cannot test
This patch adds 802.1Q VLAN support for the ADM6996M chip.
The driver is loaded for both the FC and M model. It will detect which of the
two chips is connected. The FC model is initialised, but no further
functionality is offered.
The PHY driver will always report 100 Mbit/s, link up, for both
This patch, when applied on top of [PATCH v3 1/2], will enable VLAN support for
the ADM6996FC. It updates the whole to be identical to the patch I sent in on
April 12, though that patch also includes a board fix for the Ubiquiti
RouterStation PHY masks that is not here. And it was against backfire
I think the current situation of enforcing ETSI limits on US machines
flies in the face of WIRELESS FREEDOM.
In the interest of collaboration Atheros specifically wants OpenWrt to
not publish unregulated binaries. One prerequisite for publishing a
fully open driver was the ability to enforce
On Thu, Apr 14, 2011 at 10:25 AM, Jo-Philipp Wich x...@subsignal.org wrote:
I think the current situation of enforcing ETSI limits on US machines
flies in the face of WIRELESS FREEDOM.
In the interest of collaboration Atheros specifically wants OpenWrt to
not publish unregulated binaries. One
On 2011-04-14 5:41 PM, Larry Vaden wrote:
On Thu, Apr 14, 2011 at 10:25 AM, Jo-Philipp Wichx...@subsignal.org wrote:
I think the current situation of enforcing ETSI limits on US machines
flies in the face of WIRELESS FREEDOM.
In the interest of collaboration Atheros specifically wants
On Thu, Apr 14, 2011 at 10:47 AM, Felix Fietkau n...@openwrt.org wrote:
On 2011-04-14 5:41 PM, Larry Vaden wrote:
On Thu, Apr 14, 2011 at 10:25 AM, Jo-Philipp Wichx...@subsignal.org
wrote:
I think the current situation of enforcing ETSI limits on US machines
flies in the face of WIRELESS
On 2011-04-14 5:59 PM, Larry Vaden wrote:
On Thu, Apr 14, 2011 at 10:47 AM, Felix Fietkaun...@openwrt.org wrote:
On 2011-04-14 5:41 PM, Larry Vaden wrote:
On Thu, Apr 14, 2011 at 10:25 AM, Jo-Philipp Wichx...@subsignal.org
wrote:
I think the current situation of enforcing ETSI
On Wed, Apr 13, 2011 at 04:38:16PM -0600, Philip Prindeville wrote:
I actually think the older description was a lot more informative.
I agree. But I thought that description supposed to be like on the tools
home page. I mean you should not learn how to use a tool from OpenWrt
description. Or am
I ask because this STA never came back. The STA is running AirOS
v3.6, which was forked so long ago that the completion of its bitrot
will be announced shortly :)
Said STAs are hit once every five minutes by smokeping.
jv-2400-ap1/2011-04-14.log:301 2011-04-14T19:25:35+00:00 jv-2400-ap1
hostapd
On Thu, Apr 14, 2011 at 7:08 PM, OpenWrt
openwrt-devel@lists.openwrt.org wrote:
#9207: txpower may be limited to 20 dBm on Ubiquiti M900 series with
regdomain=US
---+
Reporter: vaden@… | Owner:
On 2011-04-15 2:18 AM, Larry Vaden wrote:
On Thu, Apr 14, 2011 at 7:08 PM, OpenWrt
openwrt-devel@lists.openwrt.org wrote:
#9207: txpower may be limited to 20 dBm on Ubiquiti M900 series with
regdomain=US
---+
The AR9280 radio is pretty sensitive. I've seen it register a noise floor
below -100dBm in 20mhz-wide 11g channels. I don't know what it'd look like
in 900mhz mode.
Adrian
On 15 April 2011 08:18, Larry Vaden va...@texoma.net wrote:
On Thu, Apr 14, 2011 at 7:08 PM, OpenWrt
Add the PC speaker back to the Geos platform.
Signed-off-by: Philip Prindeville phil...@redfish-solutions.com
---
Index: target/linux/x86/geos/config-default
===
--- target/linux/x86/geos/config-default(revision 26677)
+++
Punch firewall holes for ISAKMP (udp port 500) and IPsec ESP.
Set system.foreground to 1 to force scripts to complete before starting console
shell.
Signed-off-by: Philip Prindeville phil...@redfish-solutions.com
---
Index: target/linux/x86/geos/base-files/etc/uci-defaults/firewall
On Thu, 14 Apr 2011 22:05:27 -0600
Philip Prindeville philipp_s...@redfish-solutions.com wrote:
Punch firewall holes for ISAKMP (udp port 500) and IPsec ESP.
Set system.foreground to 1 to force scripts to complete before
starting console shell.
Signed-off-by: Philip Prindeville
On Thu, 14 Apr 2011 20:31:14 -0600
Philip Prindeville philipp_s...@redfish-solutions.com wrote:
Add the PC speaker back to the Geos platform.
Signed-off-by: Philip Prindeville phil...@redfish-solutions.com
---
Index: target/linux/x86/geos/config-default
20 matches
Mail list logo
