On Tue, 17 Mar 2009, ts7300 wrote:
> Now Kernel is recompiled with enable Ethernet bridge support and zImage of
> kernel is replaced with old one.And using brctl utility below
> brctl addbr br0
> brctl addif bro eth0
> brctl addif br0 wlan0
> ifconfig eth0 10.64.21.34 netmask 255.255.0.0 broadcast 10.64.255.255 up
> ifconfig wlan0 10.64.21.49 netmask 255.255.0.0 broadcast10.64.255.255 up
> ifconfig bro 10.64.21.34 netmask 255.255.0.0 broadcast 10.64.255.255 up
How about doing some reading.
When using bridging you only assign an IP address to the bridge interface,
br0.
Try reading up the difference between a bridging device and a routing
device and some elementary IP networking texts - that way you can start to
do your own interpretation and analysis.
> ifconfig br0 up
> routing Table
> Destination Gateway Genmansk Flags Metric Ref Use Iface
> 10.64.0.0 * 255.255.0.0 u 0 0 0 wlan0
> 10.64.0.0 * 255.255.0.0 u 0 0 0 eth0
> 10.64.0.0 * 255.255.0.0 u 0 0 0 br0
> default * u 0 0 0 eth0
>
> When I am Trying to ping 10.64.1.1 its failed.While eth0 Interface is
> connected to TCP/IP.Can somebody help me out from this.
>
> brctl showbr br0
> br0
> bridge id 0000.0800062815f6
> designated root 0000.0800062815f6
> root port 0 path cost 0
> max age 4.00 bridge max age 4.00
> hello time 1.00 bridge hello time 1.00
> forward delay 4.00 bridge forward delay 4.00
> ageing time 300.00 gc interval 4.00
> hello timer 0.84 tcn timer 0.00
> topology change timer 0.00 gc timer 1.84
> flags
>
>
> eth0 (1)
> port id 8001 state forwarding
> designated root 0000.0800062815f6 path cost 100
> designated bridge 0000.0800062815f6 message age timer 0.00
> designated port 8001 forward delay timer 0.00
> designated cost 0 hold timer 0.84
> flags
>
> wlan0 (2)
> port id 8002 state
> forwarding
> designated root 0000.0800062815f6 path cost 100
> designated bridge 0000.0800062815f6 message age timer 0.00
> designated port 8002 forward delay timer 0.00
> designated cost 0 hold timer 0.84
> flags
>
>
> thanx,
> --------------------------------------------------------------
> --- In Jim Jackson <> wrote:
>>
>>
>> First of all please try and be accurate otherwise nobody can help you..
>>
>> On Fri, 6 Mar 2009, ts7300 wrote:
>>
>>> please suggest something upon below insmod bridge.o problem.
>>> --- In "ts7300" <ts7300@> wrote:
>>>>
>>>> Thanx for prompt reply.Now I am trying to use bridge mode.First of all
>>>> started with insmod/libmodules/2.4.26-ts11/kernel/net/bridge.o
>>
>> insmod /lib/modules/2.4.26-ts11/kernel/net/bridge.o
>>
>> and which version of the kernel are you running? does it match the module
>> set? These sort of errors are sometimes because you are using modules
>> compiled for a different version of kernel.
>>
>> this site
>>
>> https://www.freewrt.org/list-archives/freewrt-bugs/2007-June/001154.html
>>
>> says that support for bridging must be compiled into the kernel.
>> So I suspect your running kernel does not have bridging support built in,
>> and the modules are for a different version of the kernel.
>>
>> Boot the right kernel, i'm guessing 2.4.26-ts11, then load the module.
>>
>>
>>>> /lib/modules/2.4.26-ts11/kernel/net/bridge.o:
>>>> /lib/modules/2.4.26-ts11/kernel/net/bridge.o: unresolved symbol
>>>> br_ioctl_hook
>>>> /lib/modules/2.4.26-ts11/kernel/net/bridge.o:
>>>> /lib/modules/2.4.26-ts11/kernel/net/bridge.o: unresolved symbol
>>>> br_handle_frame_hook
>>>> Can any have any Idea on this.Or I have to install some additional package
>>>> for this.
>>>> waiting for eary response.
>>>> ----------------------------------------------
>>>> --- In Jason Stahls <jason@> wrote:
>>>>>
>>>>> ts7300 wrote:
>>>>>> below routing table
>>>>>> Destination Gateway Genmask Flags Metric Ref Use Iface
>>>>>> 10.64.0.0 * 255.255.0.0 U 0 0 0 wlan0
>>>>>> 10.64.0.0 * 255.255.0.0 U 0 0 0 eth0
>>>>>> default 10.64.1.1 0.0.0.0 UG 0 0 0 wlan0
>>>>>> default 10.64.1.1 0.0.0.0 UG 0 0 0 eth0
>>>>>> can you elborate bit more about how to use bridge mode.according to
>>>>>> routing table subnet mask is same but again doubt is on gateway when
>>>>>> wlan0 set 10.64.1.1 Gateway then its might replace eth0 interface with
>>>>>> wlan0 interface thats why fail to ping when wlan0 default gateway is
>>>>>> used.
>>>>>
>>>>> You shouldn't have IP's on the interfaces. I'm not sure if the TS
>>>>> kernel has the required code compiled in or as a module, or at all but
>>>>> you need Ethernet Bridging support in the kernel. You also need the
>>>>> program brctl to create a bridge. You can then assign the bridge
>>>>> interface a IP. The bridge interface can be called anything.
>>>>>
>>>>> --
>>>>> Jason Stahls
>>>>>
>>>>
>>>
>>>
>>>
>>
>
>
>
------------------------------------
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/ts-7000/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/ts-7000/join
(Yahoo! ID required)
<*> To change settings via email:
<*> To unsubscribe from this group, send an email to:
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
|