-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> P.S.:
> Where can I find the definition (.config, documentation, etc.) what has
> to be enabled in a release build?
Take a look at http://downloads.openwrt.org/kamikaze/8.09.1/ .
The architecture folders contain the used .config .
The script used t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Signed-off-by: Matthias Bücher
-BEGIN PGP SIGNATURE-
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkqEPHUACgkQUXXT+9wZdbWEIgCgyAFyKQm4DWJ/2yeNSE9m0YkE
tv8An0bBR1MqEMPFwdYowNHI/uWKYIwY
=JLBZ
-END PGP SIGNATU
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 13.08.2009 16:53, Matthias Buecher / Germany wrote:
> On 13.08.2009 14:57, Jo-Philipp Wich wrote:
>> Hi.
>
>>> Maybe it's indeed best to enable it in the kernel konfig, and disable
>>> by sysctl, as Matthias suggests.
>> Enabling the bridge filteri
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 13.08.2009 14:57, Jo-Philipp Wich wrote:
> Hi.
>
>> Maybe it's indeed best to enable it in the kernel konfig, and disable
>> by sysctl, as Matthias suggests.
>
> Enabling the bridge filtering in the kernel could have severe
> performance impact si
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
> Maybe it's indeed best to enable it in the kernel konfig, and disable
> by sysctl, as Matthias suggests.
Enabling the bridge filtering in the kernel could have severe
performance impact since all packets will be routed through the bridge
layer
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
After several discussions and some more documentation reading I finished
my etherwake uci support.
The patch is splitted in two files, one for the new package files
(config, init.d) and the makefile.
The patches are meant to be applied to a clean versi
Matthias Buecher / Germany writes:
> On 13.08.2009 11:08, Ferenc Wagner wrote:
>> Matthias Buecher / Germany writes:
>>
>>> The bridge firewalling is caused by CONFIG_BRIDGE_NETFILTER=y (bool),
>>> which is enabled by kmod-ebtables. As it is bool it can not be
>>> outsourced into an installable
Le Thu, 13 Aug 2009 10:10:18 +0200,
Florian Fainelli a écrit :
> Supposing that you are using a 2.6 kernel, the IPv6 Neighbor
> Discovery mechanism is by far the best way to provide IPv6
> connectivity to devices behind your Free-connected router.
For 2.6, yes via the NDP sysctl (but 2.6 is not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 13.08.2009 01:39, Matthias Buecher / Germany wrote:
>
> Matthias "Maddes" Bücher
> http://www.maddes.net/
> Home: Earth / Germany / Ruhr-Area
>
> On 12.08.2009 21:13, Matthias Buecher / Germany wrote:
>> On 12.08.2009 14:56, Matthias Buecher / Ger
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 13.08.2009 11:08, Ferenc Wagner wrote:
> Matthias Buecher / Germany writes:
>
>> The bridge firewalling is caused by CONFIG_BRIDGE_NETFILTER=y (bool),
>> which is enabled by kmod-ebtables. As it is bool it can not be
>> outsourced into an installa
Matthias Buecher / Germany writes:
> The bridge firewalling is caused by CONFIG_BRIDGE_NETFILTER=y (bool),
> which is enabled by kmod-ebtables. As it is bool it can not be
> outsourced into an installable module.
I wonder why it isn't possible to avoid loading ebtables... But can't
check now, I
Le Wednesday 12 August 2009 22:37:41 Jerome Benoit, vous avez écrit :
> Le Wed, 12 Aug 2009 21:13:16 +0200,
>
> Matthias Buecher / Germany a écrit :
> > Another solution would be to compile it as a separate module
> > (BRIDGE=m). Then the user can decide if he want to install it or not.
>
> Yes pl
12 matches
Mail list logo
