On Mon, 01 Mar 2010 07:19:02 +0100, Nico wrote:
Hi,
Any objections adding a firewall "feature" ? That would help preventing
netfilter related modules and utilities from being build on systems
where CONFIG_NETFILTER is not set ?
Systems should either drop that setting or migrate to the DEVICE
Hi devs,
Any objections adding a firewall "feature" ? That would help preventing
netfilter related modules and utilities from being build on systems
where CONFIG_NETFILTER is not set ?
Proposed patch attached
Regards,
--
-{Nico}
Index: include/target.mk
=
Hi,
On 02/20/2010 08:44 PM, Dennis Bartsch wrote:
> can anyone comfirm that on the TP-Link TL-WR741ND broadcasts are not
> received on LAN ports? I got aware of it when I had not gotten an IP
> adress through DHCP. Then I generated other broadcast. But a quick sniff
> with tcpdump didn't show thes
Ok, I decided I will start the Job offer at 100 dollars and the board. dont
worry about the chip sizes, I control that from the factory side.
On Mon, Mar 1, 2010 at 7:07 AM, jason duhamell wrote:
> Actually it is this.
> http://www.jcg.com.cn/en/display.asp?id=1312&idd=Wireless%20Products
> And
Actually it is this.
http://www.jcg.com.cn/en/display.asp?id=1312&idd=Wireless%20Products
And I can order it wit 4 mb flash or 8mb flash, but i need to fix the
software on it.
On Sun, Feb 28, 2010 at 7:46 PM, ulf kypke wrote:
> hi jason,
> this device looks like an accton oem device similar to t
> No, as his patch only modifies OpenWrt scripts and uci.
> The functionality of multiple ports with only one DropBear instance is
> already in DropBear.
Duh... sorry for being so dense,
Stefan
___
openwrt-devel mailing list
openwrt-devel@list
On Sun, February 28, 2010 21:58, Stefan Monnier wrote:
>> This patch allows multiple listen ports to be configured for dropbear in
>> /etc/config/dropbear. It renames the 'Port' option to 'Ports', so this
>> will break existing configs.
>
> Shouldn't this be sent to the dropbear upstream maintainer
> This patch allows multiple listen ports to be configured for dropbear in
> /etc/config/dropbear. It renames the 'Port' option to 'Ports', so this
> will break existing configs.
Shouldn't this be sent to the dropbear upstream maintainers? It doesn't
seem specific to OpenWRT at all.
Ste
This patch removes redundant code in the psk handling in wpa_supplicant.sh.
Regards,
Stijn
Index: package/hostapd/files/wpa_supplicant.sh
===
--- package/hostapd/files/wpa_supplicant.sh (revision 19917)
+++ package/hostapd/files/w
2010/2/28 ZioPRoTo (Saverio Proto)
> > And packets are sent by the laptop but not received by the nanostation
> > according to tcpdump (attached) but they do if I use eth0 instead of eth1
> to
> > connect the laptop and the nanostation m5. Also I attach olsrd output
> with
> > -d 3.
>
> is eth1 i
Hi,
a friend of mine made the usb driver for the board working but he has some
problems to integrade it into the openwrt buildsystem.
He had to adjust some things in the kernelconfig but the buildssytem ignores
the changes . So he build the kernel with his own scripts outside by his own.
Now i
This change adds CONFIG_HW_RANDOM to the HIFN 795x crypro accelerator which has
a hardware random number generator.
With out this one will get the following errors
hifn_795x: Unknown symbol hwrng_unregister
hifn_795x: Unknown symbol hwrng_register
which will cause the driver not to load.
This w
> And packets are sent by the laptop but not received by the nanostation
> according to tcpdump (attached) but they do if I use eth0 instead of eth1 to
> connect the laptop and the nanostation m5. Also I attach olsrd output with
> -d 3.
is eth1 inside the bridge ? Try without the bridge.
Saverio
On 28-02-10 11:58, Matthias Buecher / Germany wrote:
> Just my two cents:
> Maybe some OpenWrt team members can review if the option rename causes
> hassle to the normal end user.
Isn't that the point of sending patches to this list? ;-) IMO, since
this patch is for trunk, it shouldn't be too much
Don't missunderstand me please:
I say switch to ports but don't break old configs by means of keeping
port working in the background, maybe supported with a deprecation
message for users with old config ;)
.. ede
On 28.02.2010 13:40, Matthias Buecher / Germany wrote:
> To me that's even more co
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
To me that's even more confusing.
Either use "port" or "ports", not both.
Maddes
On 28.02.2010 12:21, edgar.sol...@web.de wrote:
> Let's keep it simple and backward compatible.
>
> Change new config to ports but also add old port setting to this lis
When you have an old working trunk version you can try to narrow down
the changeset that broke trunk. Check out revisions, compile, flash and
test.
Efficient is trying the circa middle between known broken and known
working revision. When broken then raise known broken revision. When
it's working l
hi jason,
this device looks like an accton oem device similar to the smc webt-g.
it has only 2 mb of flash and 8 mb or ram, this is too less for running openwrt.
an other thing is the dc power design, it does not have a dc/dc
converter, so it will "burn" the rest of power while dropping the
voltage
Let's keep it simple and backward compatible.
Change new config to ports but also add old port setting to this list.
Something like:
config_get ports "${section}" Ports
config_get port "${section}" Port
ports="$port $ports"
Perfect of course would be a log message telling deprecation of port
set
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Just my two cents:
Maybe some OpenWrt team members can review if the option rename causes
hassle to the normal end user.
Multiple ports will be rarely used by normal users (same as with multiple
instances), and advanced users should find out fast that
On 28-02-10 11:28, Stijn Tintel wrote:
> This patch allows multiple listen ports to be configured for dropbear in
> /etc/config/dropbear. It renames the 'Port' option to 'Ports', so this
> will break existing configs.
>
> Regards,
> Stijn
> ___
> openwrt-
This patch allows multiple listen ports to be configured for dropbear in
/etc/config/dropbear. It renames the 'Port' option to 'Ports', so this
will break existing configs.
Regards,
Stijn
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
htt
22 matches
Mail list logo
