Home
[RDK Central Wiki]
CMF
[Code Releases]
Hi I'm building a RDK-B_2020Q4 image for a raspbarryPi.
Image building works fine but when I flash the image to a raspbarryPi, only erouter0 IP V6 address is attached
No IPV4 address is attached .
dibbler-client service is also not working properly.
How can I attach IPV4 address from start to erouter0?
7 Comments
Priyankaa K V B
Hi Z-Vitor Lopes dos Santos ,
Can you please share the below details
Regards,
Priyankaa KVB
Z-Vitor Lopes dos Santos
Hi Priyankaa K V B
Any news on this topic.
Regards,
Vitor Santos
Z-Vitor Lopes dos Santos
Hi Priyankaa K V B ,
Thank you for your help.
RasbarryPi requested details are :
root@RaspberryPi-Gateway:~# ifconfig erouter0
erouter0 Link encap:Ethernet HWaddr B8:27:EB:C0:4A:41
inet addr:96.56.127.18 Bcast:0.0.0.0 Mask:255.255.255.248
inet6 addr: 2600:4808:88b0:30:1086:22d:bc41:b240/128 Scope:Global
inet6 addr: fe80::ba27:ebff:fec0:4a41/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:252 errors:0 dropped:41 overruns:0 frame:0
TX packets:157 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:43998 (42.9 KiB) TX bytes:17606 (17.1 KiB)
root@RaspberryPi-Gateway:~# ps | grep dhcp
3598 root 0:00 /sbin/udhcpc -i erouter0 -p /tmp/udhcpc.erouter0.pid -V eRouter1.0 -O ntpsrv -O timezone -O 125 -x 43 020745524f55544552031045434d3a454456413a45524f55544552 -s /etc/udhcpc.script
6272 root 0:00 grep dhcp
root@RaspberryPi-Gateway:~# ps | grep drop
2735 root 0:00 dropbear -R -E -a -r /tmp/.dropbear/dropcfg12476 -r /tmp/dropcfg 22476 -p [2600:4808:88b0:30:1086:22d:bc41:b240]:22 -P /var/run/dropbear.id -B
12625 root 0:00 dropbear -R -E -a -r /tmp/.dropbear/dropcfg12476 -r /tmp/dropcfg 22476 -p [2600:4808:88b0:30:1086:22d:bc41:b240]:22 -P /var/run/dropbear.id -B
13349 root 0:00 grep drop
root@RaspberryPi-Gateway:~# dmcli eRT getv Device.X_CISCO_COM_DeviceControl.LanManagementEntry.
CR component name is: eRT.com.cisco.spvtg.ccsp.CR
subsystem_prefix eRT.
getv from/to component(eRT.com.cisco.spvtg.ccsp.pam): Device.X_CISCO_COM_DeviceControl.LanManagementEntry.
Execution succeed.
Parameter 1 name: Device.X_CISCO_COM_DeviceControl.LanManagementEntry.1.LanMode
type: string, value: router
Parameter 2 name: Device.X_CISCO_COM_DeviceControl.LanManagementEntry.1.LanNetwork
type: string, value: 10.0.0.0
Parameter 3 name: Device.X_CISCO_COM_DeviceControl.LanManagementEntry.1.LanNetworksAllow
type: string, value: default
Parameter 4 name: Device.X_CISCO_COM_DeviceControl.LanManagementEntry.1.LanSubnetMask
type: string, value: 255.255.255.0
Parameter 5 name: Device.X_CISCO_COM_DeviceControl.LanManagementEntry.1.LanIPAddress
type: string, value: 10.0.0.1
Parameter 6 name: Device.X_CISCO_COM_DeviceControl.LanManagementEntry.1.LanDhcpServer
type: bool, value: false
Parameter 7 name: Device.X_CISCO_COM_DeviceControl.LanManagementEntry.1.LanNaptEnable
type: bool, value: true
Parameter 8 name: Device.X_CISCO_COM_DeviceControl.LanManagementEntry.1.LanNaptOnDhcp
type: bool, value: true
Parameter 9 name: Device.X_CISCO_COM_DeviceControl.LanManagementEntry.1.LanTos
type: uint, value: 0
Parameter 10 name: Device.X_CISCO_COM_DeviceControl.LanManagementEntry.1.LanDhcp125
type: bool, value: false
Parameter 11 name: Device.X_CISCO_COM_DeviceControl.LanManagementEntry.1.LanHnap
type: bool, value: false
Parameter 12 name: Device.X_CISCO_COM_DeviceControl.LanManagementEntry.1.LanUpnp
type: bool, value: true
root@RaspberryPi-Gateway:~# dmcli eRT getv Device.X_CISCO_COM_DeviceControl.
CR component name is: eRT.com.cisco.spvtg.ccsp.CR
subsystem_prefix eRT.
getv from/to component(eRT.com.cisco.spvtg.ccsp.pam): Device.X_CISCO_COM_DeviceControl.
Execution succeed.
Parameter 1 name: Device.X_CISCO_COM_DeviceControl.IGMPProxyEnable
type: bool, value: false
Parameter 2 name: Device.X_CISCO_COM_DeviceControl.DNSProxyEnable
type: bool, value: false
Parameter 3 name: Device.X_CISCO_COM_DeviceControl.TelnetEnable
type: bool, value: false
Parameter 4 name: Device.X_CISCO_COM_DeviceControl.SSHEnable
type: bool, value: true
Parameter 5 name: Device.X_CISCO_COM_DeviceControl.ReinitCmMac
type: bool, value: false
Parameter 6 name: Device.X_CISCO_COM_DeviceControl.HNAPEnable
type: bool, value: true
Parameter 7 name: Device.X_CISCO_COM_DeviceControl.MultiHomedHSDFlag
type: string, value: None
Parameter 8 name: Device.X_CISCO_COM_DeviceControl.PowerSavingModeStatus
type: string, value:
Parameter 9 name: Device.X_CISCO_COM_DeviceControl.MultiHomedUIPageControl
type: string, value: User
Parameter 10 name: Device.X_CISCO_COM_DeviceControl.DeviceMode
type: string, value: Dualstack
Parameter 11 name: Device.X_CISCO_COM_DeviceControl.ResetDefaultEnable
type: bool, value: false
Parameter 12 name: Device.X_CISCO_COM_DeviceControl.RebootDevice
type: string, value:
Parameter 13 name: Device.X_CISCO_COM_DeviceControl.FactoryReset
type: string, value:
Parameter 14 name: Device.X_CISCO_COM_DeviceControl.UserChangedFlags
type: string, value: 0
Parameter 15 name: Device.X_CISCO_COM_DeviceControl.DeviceConfigStatus
type: string, value: Complete
Parameter 16 name: Device.X_CISCO_COM_DeviceControl.DeviceConfigIgnore
type: string, value: notRequire
Parameter 17 name: Device.X_CISCO_COM_DeviceControl.SNMPEnable
type: string, value:
Parameter 18 name: Device.X_CISCO_COM_DeviceControl.HTTPEnable
type: bool, value: true
Parameter 19 name: Device.X_CISCO_COM_DeviceControl.HTTPPort
type: uint, value: 8080
Parameter 20 name: Device.X_CISCO_COM_DeviceControl.HTTPSEnable
type: bool, value: true
Parameter 21 name: Device.X_CISCO_COM_DeviceControl.HTTPSPort
type: uint, value: 8181
Parameter 22 name: Device.X_CISCO_COM_DeviceControl.ReinitMacThreshold
type: uint, value: 3165
Parameter 23 name: Device.X_CISCO_COM_DeviceControl.WanAddressMode
type: string, value: DHCP
Parameter 24 name: Device.X_CISCO_COM_DeviceControl.WanStaticIPAddress
type: string, value: 0.0.0.0
Parameter 25 name: Device.X_CISCO_COM_DeviceControl.WanStaticSubnetMask
type: string, value: 0.0.0.0
Parameter 26 name: Device.X_CISCO_COM_DeviceControl.WanStaticGatewayIP
type: string, value: 0.0.0.0
Parameter 27 name: Device.X_CISCO_COM_DeviceControl.WanSecondIPAddress
type: string, value: 53.114.199.118
Parameter 28 name: Device.X_CISCO_COM_DeviceControl.WanSecondIPRipAdvertised
type: bool, value: false
Parameter 29 name: Device.X_CISCO_COM_DeviceControl.WanBackupDefaultGateway
type: string, value: 53.114.199.118
Parameter 30 name: Device.X_CISCO_COM_DeviceControl.EnableZeroConfig
type: bool, value: false
Parameter 31 name: Device.X_CISCO_COM_DeviceControl.IGMPSnoopingEnable
type: bool, value: false
Parameter 32 name: Device.X_CISCO_COM_DeviceControl.WebUITimeout
type: uint, value: 0
Parameter 33 name: Device.X_CISCO_COM_DeviceControl.EnableMonitorUserChangedParams
type: bool, value: false
Parameter 34 name: Device.X_CISCO_COM_DeviceControl.UserOpComponents
type: string, value:
Parameter 35 name: Device.X_CISCO_COM_DeviceControl.UserChangedParams
type: string, value:
Parameter 36 name: Device.X_CISCO_COM_DeviceControl.ErouterEnable
type: bool, value: false
Parameter 37 name: Device.X_CISCO_COM_DeviceControl.LanManagementEntryNumberOfEntries
type: uint, value: 0
root@RaspberryPi-Gateway:~# syscfg get last_erouter_mode
3
Regards,
Vitor Santos
Z-Vitor Lopes dos Santos
The IPV6 problem is on the WAN site.
thanks
Priyankaa K V B
Hi Z-Vitor Lopes dos Santos ,
Sorry for the delay in response.
In the above shared output of "ifconfig erouter0" , both ipv4 and ipv6 are available .
Could you please explain your issue in detail ?
Regards,
Priyankaa KVB
Z-Vitor Lopes dos Santos
Hi Priyankaa K V B ,
Thank you for your time.
The problem is that after image flash to raspberry Pi we are not able to access erouter0 via IPv4.
dibbler-client service is not working from start on.
Regards,
Vitor Santos
Priyankaa K V B
Hi Z-Vitor Lopes dos Santos ,
So you are not able to do ssh to rpi , when you have both ipv4 and ipv6 (global, link) on erouter0 ?
If so , can you please check whether the below check-in resolves your issue
https://code.rdkcentral.com/r/c/rdkb/components/opensource/ccsp/Utopia/+/50127
Regards,
Priyankaa KVB