We use the branch rdkb-2022q1-dunfell.

After startup, eth1 is not up and only wlan0 in the bridge.

ifconfig
br0       Link encap:Ethernet  HWaddr 5A:96:10:C3:97:84
          inet addr:192.168.101.3  Bcast:192.168.101.255  Mask:255.255.255.0
          inet6 addr: fe80::5896:10ff:fec3:9784/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:18 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:1404 (1.3 KiB)

br106     Link encap:Ethernet  HWaddr 82:60:84:C9:39:2F
          inet addr:192.168.106.1  Bcast:192.168.106.255  Mask:255.255.255.0
          inet6 addr: fe80::8060:84ff:fec9:392f/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:18 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:1404 (1.3 KiB)

br403     Link encap:Ethernet  HWaddr 9A:C2:0E:69:66:AC
          inet addr:192.168.245.1  Bcast:192.168.245.255  Mask:255.255.255.0
          inet6 addr: fe80::98c2:eff:fe69:66ac/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:18 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:1404 (1.3 KiB)

brebhaul  Link encap:Ethernet  HWaddr 56:DD:05:21:B8:B3
          inet addr:169.254.85.1  Bcast:169.254.85.255  Mask:255.255.255.0
          inet6 addr: fe80::54dd:5ff:fe21:b8b3/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:18 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:1404 (1.3 KiB)

brlan0    Link encap:Ethernet  HWaddr E4:5F:01:A7:3A:9A
          inet addr:10.0.0.1  Bcast:10.0.0.255  Mask:255.255.255.0
          inet6 addr: fe80::dc42:97ff:fe2a:9f62/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:114 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:12300 (12.0 KiB)

erouter0  Link encap:Ethernet  HWaddr E4:5F:01:A7:3A:99
          inet addr:192.168.18.10  Bcast:192.0.0.168  Mask:255.255.255.0
          inet6 addr: fe80::e65f:1ff:fea7:3a99/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:12528 errors:0 dropped:5567 overruns:0 frame:0
          TX packets:4667 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:5559041 (5.3 MiB)  TX bytes:394748 (385.4 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:298932 errors:0 dropped:0 overruns:0 frame:0
          TX packets:298932 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:15029408 (14.3 MiB)  TX bytes:15029408 (14.3 MiB)

wlan0     Link encap:Ethernet  HWaddr E4:5F:01:A7:3A:9A
          inet6 addr: fe80::e65f:1ff:fea7:3a9a/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:168 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:19856 (19.3 KiB)

root@RaspberryPi-Gateway:/usr/sbin# brctl show
bridge name     bridge id               STP enabled     interfaces
br0             8000.000000000000       no
br106           8000.000000000000       no
br403           8000.000000000000       no
brebhaul                8000.000000000000       no
brlan0          8000.e45f01a73a9a       no              wlan0


But we can add eth1 to bridge manually.

The question is which module should be response to start the eth1 and add eth1 to brlan0?

What is the normal scenario?



  • No labels

6 Comments

  1. Priyankaa K V B

    Hi jianchun zhu ,

    With 2022q1-dunfell , there are some known issues(wifi coming up and ethernet interface creation) . It requires dongle to be connected . Please connect dongle and check eth1 behavior.

    You can also try with 2022q2-dunfell , where this issue is not observed .

    which module should be response to start the eth1 and add eth1 to brlan0? → Utopia

    Regards,
    Priyankaa KVB

  2. jianchun zhu

    Hi,

    Thanks.

    I checked 2022q2, it seems there is one bug in utopia.

    In source / scripts / init / c_registration / Makefile.am, only 02_lanHandler is complied.

    bin_PROGRAMS = \
        02_bridge \
        02_forwarding \
        02_ipv4 \
        02_lanHandler \

    And in source / scripts / init / c_registration / 02_lanHandler.c, the service name is defined with "lan".

    const char* SERVICE_NAME = "lan";

    const char* SERVICE_DEFAULT_HANDLER = "/etc/utopia/service.d/lan_handler.sh";

    But in source / scripts / init / service.d / lan_handler.sh, the service_name is "lan_handler".

    THIS=/etc/utopia/service.d/lan_handler.sh
    SERVICE_NAME="lan_handler"


    Is the lan_handler.sh or service_bridge.sh to add the eth1 to brlan0 during the startup with default route mode?

    1. Priyankaa K V B

      Hi jianchun zhu ,

      Please check lan_create() in service_lan.sh file. Inside that loop links all device lan interfaces to bridge

      Regards,
      Priyankaa KVB


  3. jianchun zhu

    Another question is event ipv4_4-status is not in the SERVICE_CUSTOM_EVENTS of 02_lanhandler.c.

    But this event is still processed by lanhandler.sh.

    Why?

    1. Priyankaa K V B

      Hi jianchun zhu ,

      If the service should receive events other than start, stop and restart, then those events should be declared under SERVICE_CUSTOM_EVENTS . If there are no custom events then we can set it to NULL

      Regards,
      Priyankaa KVB

  4. Raghu Venkataraju

    Hi Priyankaa K V B 


    In 2023_q1 rdk, during bootup "/etc/utopia/service.d/lan_handler.sh" is not getting triggered

    lan_handler service is getting registered with all the custom events correctly, under service name 'lan'

    cat /var/log/messages | grep lan_handler
    local7.notice UTOPIA: service.info Registered lan_handler for lan_handler-start using /etc/utopia/service.d/lan_handler.sh
    local7.notice UTOPIA: service.info Registered lan_handler for lan_handler-stop using /etc/utopia/service.d/lan_handler.sh
    local7.notice UTOPIA: service.info Registered lan_handler for lan_handler-restart using /etc/utopia/service.d/lan_handler.sh
    local7.notice UTOPIA: service.info Registered lan_handler for pnm-status using /etc/utopia/service.d/service.d/lan_handler.sh
    local7.notice UTOPIA: service.info Registered lan_handler for bring-lan using /etc/utopia/service.d/service.d/lan_handler.sh
    local7.notice UTOPIA: service.info Registered lan_handler for iot_status using /etc/utopia/service.d/service.d/lan_handler.sh
    local7.notice UTOPIA: service.info Registered lan_handler for ipv4-resync using /etc/utopia/service.d/service.d/lan_handler.sh
    local7.notice UTOPIA: service.info Registered lan_handler for erouter_mode-updated using /etc/utopia/service.d/lan_handler.sh

    Though registration is successful, these sysevents are not triggered. Due to which the script '/etc/utopia/service.d/lan_handler.sh' is not called with respective events. what could be the reason for this ? Anything needs to be taken care  ?
    same is the case with service_dhcp and service_bridge as well.

    syseventd is started successfully.

    Please provide your input and help on this regard.

    Regards,
    Raghu