• State Resolved
  • Locked Locked
  • Replies 16 replies
  • Subscribers 40 subscribers
  • Views 2988 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Enabling WiLink8 support on i.MX6SL, kernel:3.10.17

Iju
Expert 1985 points

Hi,

 I am getting the following error while applying patch in yocto environment. Please explain what is this error about.

############################################################################################
patching file imx/meta-fsl-arm/recipes-kernel/linux/linux-imx-3.10.17/0001-Add-DT-support-for-wilink-8.patch
patching file imx/meta-fsl-arm/recipes-kernel/linux/linux-imx-3.10.17/0002-Patching-the-imx_v7_defconfig-for-Wilink-8-support.patch
can't find file to patch at input line 209
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/imx/meta-fsl-arm/recipes-kernel/linux/linux-imx_3.10.17.bb b/imx/meta-fsl-arm/recipes-kernel/linux/linux-imx_3.10.17.bb
|index 422a54b..ac5e3ff 100644
|--- a/imx/meta-fsl-arm/recipes-kernel/linux/linux-imx_3.10.17.bb
|+++ b/imx/meta-fsl-arm/recipes-kernel/linux/linux-imx_3.10.17.bb
--------------------------
File to patch:
#####################################################################################################

Thanks,
Ijaz Fazily
  • 0
    TI__Guru* 85400 points
    Hi Ijaz,

    I have responded by e-mail - please confirm.

    Regards,
    Gigi Joseph.
  • 0 in reply to Joseph Gigi
    Expert 1985 points

    Hi Gigi,

    I have added the following config options while compiling Kernel.

    ########################################################################################

    CONFIG_WLAN=y
    CONFIG_WIRELESS=y
    CONFIG_WIRELESS_EXT=y
    CONFIG_WL12XX_PLATFORM_DATA=y
    CONFIG_KEYS=y
    CONFIG_SECURITY=y
    CONFIG_CRYPTO=y
    CONFIG_WIRELESS_EXT=y
    CONFIG_CRYPTO_ARC4=y
    CONFIG_CRYPTO_ECB=y
    CONFIG_CRYPTO_AES=y
    CONFIG_CRYPTO_MICHAEL_MIC=y
    CONFIG_RFKILL=y
    CONFIG_REGULATOR_FIXED_VOLTAGE=y
    CONFIG_CRC7=y
    CONFIG_NETFILTER=y
    CONFIG_NETFILTER_ADVANCED=y
    CONFIG_NF_CONNTRACK=y
    CONFIG_NETFILTER_XTABLES=y
    CONFIG_NF_DEFRAG_IPV4=y
    CONFIG_NF_CONNTRACK_IPV4=y
    CONFIG_NF_CONNTRACK_PROC_COMPAT=y
    CONFIG_IP_NF_IPTABLES=y
    CONFIG_IP_NF_FILTER=y
    CONFIG_IP_NF_TARGET_LOG=y
    CONFIG_NF_NAT=y
    CONFIG_NF_NAT_NEEDED=y
    CONFIG_IP_NF_TARGET_MASQUERADE=y
    CONFIG_INPUT_UINPUT=y
    CONFIG_NET_SCHED=y
    CONFIG_NET_SCH_FIFO=y
    CONFIG_TI_ST=y
    CONFIG_BRIDGE_NETFILTER=y

    ############################################################################################

    But I am getting following error:

    root@imx6slevk:~# echo 1 > /proc/sys/net/ipv4/ip_forward
    root@imx6slevk:~# udhcpd /etc/udhcpd.conf
    root@imx6slevk:~# iptables -t nat -A POSTROUTING -o wlan0 -j MASQUERADE
    -sh: iptables: not found

    Any suggestions?.

    ---------------------------------------------------------------------------------------------------------------------------------------------------------------

    In reference to http://processors.wiki.ti.com/index.php/WiLink8_WLAN_Demo:_Linux#MultiRole_.28STA.2BAP.29 [ configuring WiFIi modules as STA+AP] :
    Since our WLAN device is connected to Home Router through Ethernet, if I use eth0 instead of wlan0 with the same configuration steps will it work?.

    Is there anything else I should take care?.

    Regards,
    Ijaz Fazily

  • 0 in reply to Iju
    TI__Guru* 85400 points
    Hi Ijaz,

    The error means that the "iptables" binary does not exist in your filesystem. You would want to build it. It doesn't come from TI.
    Regarding your question, I don't think it will. The interface in the hostapd.conf tells the hostapd to use the 'wlan1' interface. Why do you want to run hostapd over eth0 ?

    Regards,
    Gigi Joseph
  • 0 in reply to Joseph Gigi
    Expert 1985 points
    Hi Gigi,

    Sorry for the confusion. We are actually looking for Bridging mode . The WLAN device is connected to Home Router through Ethernet and simultaneously support wireless clients. Do you have any use case based on bridging?

    Thanks.
    Ijaz Fazily
  • 0 in reply to Iju
    TI__Guru* 85400 points
    Hi Ijaz,

    Please take a look at: http://processors.wiki.ti.com/index.php/OMAP_Wireless_Connectivity_Ethernet_WLAN_Bridge

    Regards,
    Gigi Joseph.
  • 0 in reply to Joseph Gigi
    Expert 1985 points

    Hi Gigi,

           I have followed reference link for bridge mode configuration. I was not able to ping the modem from the terminal and also not able to connect any device to my SOFT_AP. 

    Am I missing something. Following is the log.

    ######################################################################################################################

    root@imx6slevk:~# ifconfig eth0 0.0.0.0 down
    fec 2188000.ethernet eth0: Freescale FEC PHY driver [Generic PHY] (mii_bus:phy_addr=2188000.ethernet:00, irq=-1)
    root@imx6slevk:~#
    root@imx6slevk:~# ifconfig wlan0 0.0.0.0 down
    wlcore: PHY firmware version: Rev 8.2.0.0.195
    wlcore: firmware booted (Rev 8.8.0.0.13)
    IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
    wlcore: down
    root@imx6slevk:~#
    root@imx6slevk:~#
    root@imx6slevk:~# brctl addbr br0
    root@imx6slevk:~#
    root@imx6slevk:~# brctl addif br0 eth0
    device eth0 entered promiscuous mode
    root@imx6slevk:~#
    root@imx6slevk:~#
    root@imx6slevk:~# hostapd -B /etc/hostapd.conf -P /var/run/hostapd.pid
    Configuration file: /etc/hostapd.conf
    wlcore: PHY firmware version: Rev 8.2.0.0.195
    wlcore: firmware booted (Rev 8.8.0.0.13)
    IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
    Using interface wlan0 with hwaddr 84:dd:20:92:a5:e1 and ssid "SoftAP_LBXU_ZBHA"
    IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
    root@imx6slevk:~#
    root@imx6slevk:~#
    root@imx6slevk:~#
    root@imx6slevk:~# brctl addif br0 wlan0
    device wlan0 entered promiscuous mode
    root@imx6slevk:~#
    root@imx6slevk:~#
    root@imx6slevk:~# ifconfig eth0 up
    fec 2188000.ethernet eth0: Freescale FEC PHY driver [Generic PHY] (mii_bus:phy_addr=2188000.ethernet:00, irq=-1)
    root@imx6slevk:~#
    root@imx6slevk:~# libphy: 2188000.ethernet:00 - Link is Up - 100/Full

    root@imx6slevk:~#
    root@imx6slevk:~# ifconfig wlan0 up
    root@imx6slevk:~#
    root@imx6slevk:~#
    root@imx6slevk:~# ifconfig br0 192.168.2.40 up
    br0: port 2(wlan0) entered forwarding state
    br0: port 2(wlan0) entered forwarding state
    br0: port 1(eth0) entered forwarding state
    br0: port 1(eth0) entered forwarding state
    root@imx6slevk:~#
    root@imx6slevk:~#
    root@imx6slevk:~#
    root@imx6slevk:~# udhcpd /etc/udhcpd.confbr0: port 2(wlan0) entered forwarding state
    br0: port 1(eth0) entered forwarding state

    root@imx6slevk:~#
    root@imx6slevk:~#
    root@imx6slevk:~# ifconfig
    br0 Link encap:Ethernet HWaddr 44:55:66:44:55:66
    inet addr:192.168.2.40 Bcast:192.168.2.255 Mask:255.255.255.0
    inet6 addr: fe80::4655:66ff:fe44:5566/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:0 (0.0 B) TX bytes:468 (468.0 B)

    eth0 Link encap:Ethernet HWaddr 44:55:66:44:55:66
    inet6 addr: fe80::4655:66ff:fe44:5566/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:7 errors:8 dropped:5 overruns:0 frame:9
    TX packets:17 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:4589 (4.4 KiB) TX bytes:1850 (1.8 KiB)

    lo Link encap:Local Loopback
    inet addr:127.0.0.1 Mask:255.0.0.0
    inet6 addr: ::1/128 Scope:Host
    UP LOOPBACK RUNNING MTU:65536 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

    wlan0 Link encap:Ethernet HWaddr 84:DD:20:92:A5:E1
    inet6 addr: fe80::86dd:20ff:fe92:a5e1/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:0 (0.0 B) TX bytes:1152 (1.1 KiB)

    root@imx6slevk:~# ping 192.168.2.1
    PING 192.168.2.1 (192.168.2.1): 56 data bytes


    --- 192.168.2.1 ping statistics ---
    30 packets transmitted, 0 packets received, 100% packet loss

    #########################################################################################################################

    Regards,

    Ijaz Fazily

  • 0 in reply to Iju
    TI__Guru* 85400 points
    Hi Ijaz,

    It looks like you don't have an IP address assigned. I believe you need to run the DHCP client.

    Regards,
    Gigi Joseph.
  • 0 in reply to Joseph Gigi
    Expert 1985 points

    Hi Gigi,

       That is correct. Its working fine now. But I have a couple of doubts.

    Following was the configuration steps I have done:

    ######################################################################

    BRIDGE_MODE

    ifconfig eth0 0.0.0.0 down

    ifconfig wlan0 0.0.0.0 down

    brctl addbr br0

    brctl addif br0 eth0

    hostapd -B /etc/hostapd.conf -P /var/run/hostapd.pid

    brctl addif br0 wlan0

    ifconfig eth0 up

    ifconfig wlan0 up

    ifconfig br0 up

    udhcpc -i br0

    Note: At this point br0 gets ip from the router. If I try to connect any device to the SOFT_AP(board) its not getting connected. But if I again

    run ' udhcpc & ' , I am successfully able to connect any device to the SOFT_AP and gets internet access. 

    I also noticed that, even if I do not execute  ' udhcpc -i br0 '  and just run ' udhcpc & '  its working fine.

    why is it like that. We do not need to configure br0 interface or what?. could you please explain?

    ######################################################################

    Regards,

    Ijaz Fazily

  • 0 in reply to Iju
    TI__Guru* 85400 points
    Hi Ijaz,

    I believe running the udhcpc without any parameters will default to the wlan0 interface.
    Can you try "udhcpc -i wlan0" to confirm?

    Regards,
    Gigi Joseph.
  • 0 in reply to Joseph Gigi
    Expert 1985 points

    Hi Gigi,

    I checked that. It is eth0 interface, not wlan0. when I tried udhcpc -i eth0 only its working.
    Does it mean that my br0 interface is not working?. Is this how bridge mode works? Am I missing something?.

    Following is my setup.

    LAPTOP<---------->BOARD<-----------------> ROUTER

                  (Wi-Fi)                    (Ethernet)

    LOG

    #################################################################################################################

    root@imx6slevk:~#
    root@imx6slevk:~#
    root@imx6slevk:~# ifconfig eth0 0.0.0.0 down
    root@imx6slevk:~# ifconfig wlan0 0.0.0.0 down
    wlcore: PHY firmware version: Rev 8.2.0.0.195
    wlcore: firmware booted (Rev 8.8.0.0.13)
    IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
    wlcore: down
    root@imx6slevk:~#
    root@imx6slevk:~#
    root@imx6slevk:~# brctl addbr br0
    root@imx6slevk:~# brctl addif br0 eth0
    device eth0 entered promiscuous mode
    root@imx6slevk:~#
    root@imx6slevk:~#
    root@imx6slevk:~# hostapd -B /etc/hostapd.conf -P /var/run/hostapd.pid
    Configuration file: /etc/hostapd.conf
    wlcore: PHY firmware version: Rev 8.2.0.0.195
    wlcore: firmware booted (Rev 8.8.0.0.13)
    IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
    Using interface wlan0 with hwaddr 84:dd:20:92:a5:e1 and ssid "SoftAP_LBXU_ZBHA"
    IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
    root@imx6slevk:~#
    root@imx6slevk:~#
    root@imx6slevk:~# brctl addif br0 wlan0
    device wlan0 entered promiscuous mode
    root@imx6slevk:~#
    root@imx6slevk:~#
    root@imx6slevk:~# ifconfig eth0 up
    fec 2188000.ethernet eth0: Freescale FEC PHY driver [Generic PHY] (mii_bus:phy_addr=2188000.ethernet:00, irq=-1)
    root@imx6slevk:~#
    root@imx6slevk:~#
    root@imx6slevk:~#
    root@imx6slevk:~# libphy: 2188000.ethernet:00 - Link is Up - 100/Full
    ifconfig wlan0 up
    root@imx6slevk:~#
    root@imx6slevk:~# ifconfig wlan0 up
    root@imx6slevk:~#
    root@imx6slevk:~#
    root@imx6slevk:~# ifconfig br0 up
    br0: port 2(wlan0) entered forwarding state
    br0: port 2(wlan0) entered forwarding state
    br0: port 1(eth0) entered forwarding state
    br0: port 1(eth0) entered forwarding state
    root@imx6slevk:~#
    root@imx6slevk:~#
    root@imx6slevk:~# br0: port 2(wlan0) entered forwarding state
    br0: port 1(eth0) entered forwarding state

    root@imx6slevk:~#
    root@imx6slevk:~#
    root@imx6slevk:~# ifconfig br0 192.168.239.78 netmask 255.255.255.0 up
    root@imx6slevk:~#
    root@imx6slevk:~#
    root@imx6slevk:~# route add default gw 192.168.239.3
    root@imx6slevk:~#
    root@imx6slevk:~#                                           
    root@imx6slevk:~# route
    Kernel IP routing table
    Destination Gateway Genmask Flags Metric Ref Use Iface
    default 192.168.239.3 0.0.0.0 UG 0 0 0 br0
    192.168.239.0 * 255.255.255.0 U 0 0 0 br0
    root@imx6slevk:~# ping 8.8.8.8
    PING 8.8.8.8 (8.8.8.8): 56 data bytes
    64 bytes from 8.8.8.8: seq=0 ttl=55 time=319.369 ms
    64 bytes from 8.8.8.8: seq=1 ttl=55 time=275.050 ms
    64 bytes from 8.8.8.8: seq=2 ttl=55 time=223.097 ms
    64 bytes from 8.8.8.8: seq=3 ttl=55 time=163.548 ms
    64 bytes from 8.8.8.8: seq=4 ttl=55 time=310.108 ms
                                                                                            Note: Internet access only at board. At this point, I was also not able to connect any device to the board through Wi-Fi. That is my laptop is getting associated with wlan0 interface but not getting any IP. 
    --- 8.8.8.8 ping statistics ---
    6 packets transmitted, 5 packets received, 16% packet loss
    round-trip min/avg/max = 163.548/258.234/319.369 ms
    root@imx6slevk:~#
    root@imx6slevk:~#
    root@imx6slevk:~#
    root@imx6slevk:~#
    root@imx6slevk:~# ifconfig
    br0 Link encap:Ethernet HWaddr 00:50:C2:BC:C0:F1
    inet addr:192.168.239.78 Bcast:192.168.239.255 Mask:255.255.255.0
    inet6 addr: fe80::250:c2ff:febc:c0f1/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:2364 errors:0 dropped:0 overruns:0 frame:0
    TX packets:20 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:145213 (141.8 KiB) TX bytes:1457 (1.4 KiB)

    eth0 Link encap:Ethernet HWaddr 00:50:C2:BC:C0:F1
    inet6 addr: fe80::250:c2ff:febc:c0f1/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:2453 errors:1 dropped:1 overruns:0 frame:1
    TX packets:63 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:191940 (187.4 KiB) TX bytes:9014 (8.8 KiB)

    lo Link encap:Local Loopback
    inet addr:127.0.0.1 Mask:255.0.0.0
    inet6 addr: ::1/128 Scope:Host
    UP LOOPBACK RUNNING MTU:65536 Metric:1
    RX packets:4 errors:0 dropped:0 overruns:0 frame:0
    TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:344 (344.0 B) TX bytes:344 (344.0 B)

    wlan0 Link encap:Ethernet HWaddr 84:DD:20:92:A5:E1
    inet6 addr: fe80::86dd:20ff:fe92:a5e1/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:31 errors:0 dropped:0 overruns:0 frame:0
    TX packets:2363 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:6155 (6.0 KiB) TX bytes:220740 (215.5 KiB)
    root@imx6slevk:~#
    root@imx6slevk:~#
    root@imx6slevk:~#
    root@imx6slevk:~#
    root@imx6slevk:~#
    root@imx6slevk:~#
    root@imx6slevk:~#
    root@imx6slevk:~# udhcpc -i eth0 &
    root@imx6slevk:~# udhcpc (v1.22.1) started
    Sending discover...
    Sending discover...
    Sending discover...                                             Note: At this point, I was able to connect my laptop with the board and use Internet. Irrespective of the bridge configuration, if I run DHCP client for eth0 interface I was able to connect devices with the board and use internet.

    root@imx6slevk:~#
    root@imx6slevk:~# route
    Kernel IP routing table
    Destination Gateway Genmask Flags Metric Ref Use Iface
    default 192.168.239.3 0.0.0.0 UG 0 0 0 br0
    192.168.239.0 * 255.255.255.0 U 0 0 0 br0
    root@imx6slevk:~#
    root@imx6slevk:~#
    root@imx6slevk:~#
    root@imx6slevk:~#
    root@imx6slevk:~# ifconfig
    br0 Link encap:Ethernet HWaddr 00:50:C2:BC:C0:F1
    inet addr:192.168.239.78 Bcast:192.168.239.255 Mask:255.255.255.0
    inet6 addr: fe80::250:c2ff:febc:c0f1/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:4220 errors:0 dropped:0 overruns:0 frame:0
    TX packets:24 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:283547 (276.9 KiB) TX bytes:2945 (2.8 KiB)

    eth0 Link encap:Ethernet HWaddr 00:50:C2:BC:C0:F1
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:4321 errors:1 dropped:1 overruns:0 frame:1
    TX packets:404 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:354476 (346.1 KiB) TX bytes:66166 (64.6 KiB)

    lo Link encap:Local Loopback
    inet addr:127.0.0.1 Mask:255.0.0.0
    inet6 addr: ::1/128 Scope:Host
    UP LOOPBACK RUNNING MTU:65536 Metric:1
    RX packets:12 errors:0 dropped:0 overruns:0 frame:0
    TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:1032 (1.0 KiB) TX bytes:1032 (1.0 KiB)

    wlan0 Link encap:Ethernet HWaddr 84:DD:20:92:A5:E1
    inet6 addr: fe80::86dd:20ff:fe92:a5e1/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:360 errors:0 dropped:0 overruns:0 frame:0
    TX packets:4378 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:60371 (58.9 KiB) TX bytes:435633 (425.4 KiB)

    root@imx6slevk:~#

    #################################################################################################################

    Thank you.


    Regards,
    Ijaz Fazily

  • 0 in reply to Joseph Gigi
    Expert 1985 points
    Hi Gigi,

    I have one doubt in this. I configured br0 interface with an IP in the same domain with the router. What do you meant by I don't have an IP address assigned?. I suppose wlan0 and eth0 does not require IP address in bridge.


    Regards,
    Ijaz Fazily
  • 0 in reply to Joseph Gigi
    Expert 1985 points
    Hi Gigi,

    Could you please have a look at the log?. I really appreciate your suggestion on that.
    Thank you.

    Regards,
    Ijaz Fazily
  • 0 in reply to Iju
    TI__Guru* 85400 points
    Hi Ijaz,

    I am sorry, I am a bit confused now... I thought you mentioned that things are working for you now . What is the issue you are facing now?

    Regards,
    Gigi Joseph.
  • 0 in reply to Joseph Gigi
    Expert 1985 points
    Hi Gigi,

    I am very sorry to have confused you. It's working if I run DHCP client for eth0 interface. I suppose it should work if I configure bridge interface and run DHCP client for the same. Why do we need to run DHCP client for Ethernet interface in bridge to have internet access?.

    LOG:
    #################################################################################################################


    root@imx6slevk:~#
    root@imx6slevk:~#
    root@imx6slevk:~# ifconfig eth0 0.0.0.0 down
    root@imx6slevk:~# ifconfig wlan0 0.0.0.0 down
    wlcore: PHY firmware version: Rev 8.2.0.0.195
    wlcore: firmware booted (Rev 8.8.0.0.13)
    IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
    wlcore: down
    root@imx6slevk:~#
    root@imx6slevk:~#
    root@imx6slevk:~# brctl addbr br0
    root@imx6slevk:~# brctl addif br0 eth0
    device eth0 entered promiscuous mode
    root@imx6slevk:~#
    root@imx6slevk:~#
    root@imx6slevk:~# hostapd -B /etc/hostapd.conf -P /var/run/hostapd.pid
    Configuration file: /etc/hostapd.conf
    wlcore: PHY firmware version: Rev 8.2.0.0.195
    wlcore: firmware booted (Rev 8.8.0.0.13)
    IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
    Using interface wlan0 with hwaddr 84:dd:20:92:a5:e1 and ssid "SoftAP_LBXU_ZBHA"
    IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
    root@imx6slevk:~#
    root@imx6slevk:~#
    root@imx6slevk:~# brctl addif br0 wlan0
    device wlan0 entered promiscuous mode
    root@imx6slevk:~#
    root@imx6slevk:~#
    root@imx6slevk:~# ifconfig eth0 up
    fec 2188000.ethernet eth0: Freescale FEC PHY driver [Generic PHY] (mii_bus:phy_addr=2188000.ethernet:00, irq=-1)
    root@imx6slevk:~#
    root@imx6slevk:~#
    root@imx6slevk:~#
    root@imx6slevk:~# libphy: 2188000.ethernet:00 - Link is Up - 100/Full
    ifconfig wlan0 up
    root@imx6slevk:~#
    root@imx6slevk:~# ifconfig wlan0 up
    root@imx6slevk:~#
    root@imx6slevk:~#
    root@imx6slevk:~# ifconfig br0 up
    br0: port 2(wlan0) entered forwarding state
    br0: port 2(wlan0) entered forwarding state
    br0: port 1(eth0) entered forwarding state
    br0: port 1(eth0) entered forwarding state
    root@imx6slevk:~#
    root@imx6slevk:~#
    root@imx6slevk:~# br0: port 2(wlan0) entered forwarding state
    br0: port 1(eth0) entered forwarding state


    root@imx6slevk:~#
    root@imx6slevk:~#
    root@imx6slevk:~# ifconfig br0 192.168.239.78 netmask 255.255.255.0 up
    root@imx6slevk:~#
    root@imx6slevk:~#
    root@imx6slevk:~# route add default gw 192.168.239.3
    root@imx6slevk:~#
    root@imx6slevk:~#
    root@imx6slevk:~# route
    Kernel IP routing table
    Destination Gateway Genmask Flags Metric Ref Use Iface
    default 192.168.239.3 0.0.0.0 UG 0 0 0 br0
    192.168.239.0 * 255.255.255.0 U 0 0 0 br0
    root@imx6slevk:~# ping 8.8.8.8
    PING 8.8.8.8 (8.8.8.8): 56 data bytes
    64 bytes from 8.8.8.8: seq=0 ttl=55 time=319.369 ms
    64 bytes from 8.8.8.8: seq=1 ttl=55 time=275.050 ms
    64 bytes from 8.8.8.8: seq=2 ttl=55 time=223.097 ms
    64 bytes from 8.8.8.8: seq=3 ttl=55 time=163.548 ms
    64 bytes from 8.8.8.8: seq=4 ttl=55 time=310.108 ms
    Note: Internet access only at board. At this point, I was also not able to connect any device to the board through Wi-Fi. That is my laptop is getting associated with wlan0 interface but not getting any IP.

    --- 8.8.8.8 ping statistics ---
    6 packets transmitted, 5 packets received, 16% packet loss
    round-trip min/avg/max = 163.548/258.234/319.369 ms
    root@imx6slevk:~#
    root@imx6slevk:~#
    root@imx6slevk:~#
    root@imx6slevk:~#
    root@imx6slevk:~# ifconfig
    br0 Link encap:Ethernet HWaddr 00:50:C2:BC:C0:F1
    inet addr:192.168.239.78 Bcast:192.168.239.255 Mask:255.255.255.0
    inet6 addr: fe80::250:c2ff:febc:c0f1/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:2364 errors:0 dropped:0 overruns:0 frame:0
    TX packets:20 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:145213 (141.8 KiB) TX bytes:1457 (1.4 KiB)


    eth0 Link encap:Ethernet HWaddr 00:50:C2:BC:C0:F1
    inet6 addr: fe80::250:c2ff:febc:c0f1/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:2453 errors:1 dropped:1 overruns:0 frame:1
    TX packets:63 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:191940 (187.4 KiB) TX bytes:9014 (8.8 KiB)


    lo Link encap:Local Loopback
    inet addr:127.0.0.1 Mask:255.0.0.0
    inet6 addr: ::1/128 Scope:Host
    UP LOOPBACK RUNNING MTU:65536 Metric:1
    RX packets:4 errors:0 dropped:0 overruns:0 frame:0
    TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:344 (344.0 B) TX bytes:344 (344.0 B)


    wlan0 Link encap:Ethernet HWaddr 84:DD:20:92:A5:E1
    inet6 addr: fe80::86dd:20ff:fe92:a5e1/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:31 errors:0 dropped:0 overruns:0 frame:0
    TX packets:2363 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:6155 (6.0 KiB) TX bytes:220740 (215.5 KiB)
    root@imx6slevk:~#
    root@imx6slevk:~#
    root@imx6slevk:~#
    root@imx6slevk:~#
    root@imx6slevk:~#
    root@imx6slevk:~#
    root@imx6slevk:~#
    root@imx6slevk:~# udhcpc -i eth0 &
    root@imx6slevk:~# udhcpc (v1.22.1) started
    Sending discover...
    Sending discover...
    Sending discover... Note: At this point, I was able to connect my laptop with the board and use Internet. Irrespective of the bridge configuration, if I run DHCP client for eth0 interface I was able to connect devices with the board and use internet.


    root@imx6slevk:~#
    root@imx6slevk:~# route
    Kernel IP routing table
    Destination Gateway Genmask Flags Metric Ref Use Iface
    default 192.168.239.3 0.0.0.0 UG 0 0 0 br0
    192.168.239.0 * 255.255.255.0 U 0 0 0 br0
    root@imx6slevk:~#
    root@imx6slevk:~#
    root@imx6slevk:~#
    root@imx6slevk:~#
    root@imx6slevk:~# ifconfig
    br0 Link encap:Ethernet HWaddr 00:50:C2:BC:C0:F1
    inet addr:192.168.239.78 Bcast:192.168.239.255 Mask:255.255.255.0
    inet6 addr: fe80::250:c2ff:febc:c0f1/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:4220 errors:0 dropped:0 overruns:0 frame:0
    TX packets:24 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:283547 (276.9 KiB) TX bytes:2945 (2.8 KiB)


    eth0 Link encap:Ethernet HWaddr 00:50:C2:BC:C0:F1
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:4321 errors:1 dropped:1 overruns:0 frame:1
    TX packets:404 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:354476 (346.1 KiB) TX bytes:66166 (64.6 KiB)


    lo Link encap:Local Loopback
    inet addr:127.0.0.1 Mask:255.0.0.0
    inet6 addr: ::1/128 Scope:Host
    UP LOOPBACK RUNNING MTU:65536 Metric:1
    RX packets:12 errors:0 dropped:0 overruns:0 frame:0
    TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:1032 (1.0 KiB) TX bytes:1032 (1.0 KiB)


    wlan0 Link encap:Ethernet HWaddr 84:DD:20:92:A5:E1
    inet6 addr: fe80::86dd:20ff:fe92:a5e1/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:360 errors:0 dropped:0 overruns:0 frame:0
    TX packets:4378 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:60371 (58.9 KiB) TX bytes:435633 (425.4 KiB)


    root@imx6slevk:~#

    #########################################################################################


    Regards,
    Ijaz Fazily
  • 0 in reply to Iju
    TI__Guru* 85400 points
    Hi Ijaz,

    My understanding is that you need to run the DHCP Client for the eth0 interface as well.

    The bridge would bridge the eth0 <-> wlan0 interfaces, but the eth0 itself should have an IP address. Without that, I don't think you can have internet access.

    Regards,
    Gigi Joseph.
  • 0 in reply to Joseph Gigi
    Expert 1985 points
    Okay Gigi. Thank you.


    Regards,
    Ijaz Fazily