-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
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 / Germany wrote:
>> On 12.08.2009 10:50, Ferenc Wagner wrote:
>>> Matthia
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12.08.2009 22:37, Jerome Benoit wrote:
> 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
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 please do so. IPv6 connectivity can be bridged cleanly, it's what
most French openw
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12.08.2009 14:56, Matthias Buecher / Germany wrote:
> On 12.08.2009 10:50, Ferenc Wagner wrote:
>> Matthias Buecher / Germany writes:
>
>>> When compiling a kernel prepared for all packages, then bridge
>>> firewalling is enabled inside the kernel
On Tue, 11 Aug 2009 03:18:58 +0200
Felix Fietkau wrote:
> Are you really sure that in your case it substitutes the sizeof
> expression with a value of 1 or is this a guess?
With your reminder of sizeof on constant arrays, I was able to find the
true offender and now the patch affects exactly one
> From: Daniel Dickinson
> Subject: Re: [OpenWrt-Devel] [RFC] preinit/failsafe
> customization/modularization
> To: openwrt-devel@lists.openwrt.org
> Date: Tuesday, August 11, 2009, 6:14 PM
> So, do you feel better about it knowing that it is only the
> firmware
> builder who modifies the behavi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12.08.2009 10:50, Ferenc Wagner wrote:
> Matthias Buecher / Germany writes:
>
>> When compiling a kernel prepared for all packages, then bridge
>> firewalling is enabled inside the kernel.
>
> Rather, I think you get the "problem" when you start
i Understand. why~
carsh.
svn -r 16800
make V=66 ing.
2009/8/12 linux_pro :
> y,but i can telnet 192.168.1.1
> ifconfig ,free. is ok
> top. dmesg can't work.
> i know what's wrong.
>
>
> :"(
>
> 2009/8/12 :
>> seems like the route back is not properly set .. ede
>>
>> On 12
Matthias Buecher / Germany writes:
> When compiling a kernel prepared for all packages, then bridge
> firewalling is enabled inside the kernel.
Rather, I think you get the "problem" when you start the firewall.
> This leads to "unexpected" behaviour for newbies and normal users: they
> can not
y,but i can telnet 192.168.1.1
ifconfig ,free. is ok
top. dmesg can't work.
i know what's wrong.
:"(
2009/8/12 :
> seems like the route back is not properly set .. ede
>
> On 12.08.2009 10:31, linux_pro wrote:
>>
>> O!
>> i user ttyS0 on the mi424, ping my PC IP 192.168.1.26,
>> display t
seems like the route back is not properly set .. ede
On 12.08.2009 10:31, linux_pro wrote:
O!
i user ttyS0 on the mi424, ping my PC IP 192.168.1.26,
display time out
but on the my PC, ping MI424 192.168.1.1, is OK
i iptables -F
iptables -Z
not diff
2009/8/12 linux_pro:
thanks ede
i try
O!
i user ttyS0 on the mi424, ping my PC IP 192.168.1.26,
display time out
but on the my PC, ping MI424 192.168.1.1, is OK
i iptables -F
iptables -Z
not diff
2009/8/12 linux_pro :
> thanks ede
>
> i try to do.
>
>
> 2009/8/12 :
>> you can try to narrow down the changeset that causes the pro
thanks ede
i try to do.
2009/8/12 :
> you can try to narrow down the changeset that causes the problem by checking
> out revisions, buildroot them and flash them on the device .. ede
>
> On 12.08.2009 04:27, linux_pro wrote:
>>
>> I very sure , SVN 17220 LUCI can't work.
>> i backup SVN 15XXX,
you can try to narrow down the changeset that causes the problem by
checking out revisions, buildroot them and flash them on the device .. ede
On 12.08.2009 04:27, linux_pro wrote:
I very sure , SVN 17220 LUCI can't work.
i backup SVN 15XXX, is ok.
so,my mi424(ixp425) hardware is OK.
HI, Mark
14 matches
Mail list logo