Help with new install for new user - Vero V

Help and Support
1

Hello,
I have a few issue with my install of Vero V.

  1. It all seems to have gone correctly. I can ssh into the Vero. I can access the Vero with a web browser, except that it gets me to the Kodi portal and not to the OSMC first page.

  2. Although I can ssh into the Vero, the DHCP assigned address does not show in my DHCP server active ip leases. That means that I cannot assign it a static ip address rather than using the temporary assigned one (and that is correct also, as it is the next number in the pool for temporary addresses for that DHCP server).

Any idea about how to fix either of these issues would be thankfully received. :slight_smile:

2

The Web Interface and the Skin (what is displayed on screen) are two different parts of OSMC so they are not expected to be identical. So have the same display as the TV you would need to use VNC.
Can you describe what is your problem/expectation.

3

No idea how we can help here as that is not influenced by the Vero.

4

Thanks fzinken,

As I said, brand new user, received my Vero V, late yesterday and I think I got myself into a knot. Unfortunately, I have not found anywhere on the net anything that may look like a user manual or complete documentation. I think that is what I need.

Regarding your answer to my question. I need a keyboard to deal with this, the remote is far too clumsy for my fingers.

What I want to do is add some addons, I guess. I am only interested in having it as a set-top box for free-to-air catch up from the internet. I think I need slyguy repo for that.

Thanks again for trying to help.

5

Strange, because if I connect a pi on the same cable, it works as expected.

It may be that in my fumbling along I have set the ip address on the Vero to the ip address that was initially given to it. But that may mess up the DHCP server because it is in the range of adhoc ip for unknown devices.

Anyway again the docs as to where to change that would be something wonderful. :slight_smile:

And again I would like to do that via SSH or web access on my workstation. The remote makes anything an near impossible task for me.

6

If the Vero Remote and/or your TV remote are not good enough for you and you don’t not have a wireless or USB Keyboard to connect to the Vero I suggest using VNC to remotely connect to it.
I believe in the meantime VNC Server is in the OSMC App Store (Settings → MyOSMC → App Store). Then you can use any vncviewer on your PC to remote navigate your Vero.
In terms of manual you can look at the any Kodi Manual (https://kodi.tv/) if you are confused by the different look (functionality is the same) just switch to Estuary Skin (Settings → Interface → Skin).

The Vero may or may not be the best solution for that.

7

Settings → MyOSMC → Network

8

Found that, after a bit of searching, but that is correct afaik as it says “Configure Network using DHCP”.
But still, the lease does not show on my gateway router for that net or any of the others I have.

9

That’s odd. FWIW I can see all my veros in the list of connected devices and get the router to assign IP by MAC. I don’t think this is a problem you can solve on the vero itself. Asus router here.

10

What is the make and model of the router? As others have said, we can’t influence the router settings.

It might be easier to install the VNC Server and configure a static IP on the device that way

Sam

11

I don’t think the router model should no be relevant since other Pi’s on exactly the same hardware wire connect properly. Anyway the router software is pfSense running on freeBSD on a protectli hardware.

In any case, it seems to be working and has received an ip from the DHCP server which in this instance only does not show it on the DHCP server list of leases.

12

usually, if an IP is not showing up in a lease-filke, it means it has been set as static IP in the dhcp-server configuration. This also means Mac and IP are in the configuration.

13

In my case it does not show either in the adhoc leases list or the static leases list.

14

Well, you can tell the connman dhcp module to be a bit more verbose adding the lines

CONNMAN_DHCP_DEBUG=yes
CONNMAN_DHCPV6_DEBUG=yes

to the file /etc/osmc/prefs.d/connman (Hint: These lines are case-sensitive!!!)

You get something like

Oct 05 07:15:34 osmc-vero4k connmand[2587]: DHCP index 2: switch listening mode (0 ==> 1)
Oct 05 07:15:34 osmc-vero4k connmand[2587]: DHCP index 2: DHCP client start with state init_reboot
Oct 05 07:15:34 osmc-vero4k connmand[2587]: DHCP index 2: sending DHCP request (state 1)
Oct 05 07:15:34 osmc-vero4k connmand[2587]: DHCP index 2: received DHCP packet xid 0x57ff359d (current state 1)
Oct 05 07:15:34 osmc-vero4k connmand[2587]: DHCP index 2: ip 10.10.10.183 -> not adding broadcast flag
Oct 05 07:15:34 osmc-vero4k connmand[2587]: DHCP index 2: switch listening mode (1 ==> 0)
Oct 05 07:15:34 osmc-vero4k connmand[2587]: DHCP index 2: start bound
Oct 05 07:15:34 osmc-vero4k connmand[2587]: DHCP index 2: processed DHCP packet (new state 3)
Oct 05 07:15:36 osmc-vero4k connmand[2587]: DHCPv6: DUID(14) 000100012e9387f8900eb3350d6f
Oct 05 07:15:36 osmc-vero4k connmand[2587]: DHCPv6: setting option 6 to 0xab9d5b48 len 6
Oct 05 07:15:36 osmc-vero4k connmand[2587]: DHCPv6: setting option 3 to 0xff823e78 len 12
Oct 05 07:15:36 osmc-vero4k connmand[2587]: DHCPv6: switch listening mode (0 ==> 2)
Oct 05 07:15:36 osmc-vero4k connmand[2587]: DHCPv6: sending DHCPv6 solicit message xid 0xd3f452
Oct 05 07:15:36 osmc-vero4k connmand[2587]: DHCPv6: option 8 len 6 added
Oct 05 07:15:36 osmc-vero4k connmand[2587]: DHCPv6: option 14 len 4 added
Oct 05 07:15:36 osmc-vero4k connmand[2587]: DHCPv6: option 1 len 18 added
Oct 05 07:15:36 osmc-vero4k connmand[2587]: DHCPv6: sent 58 pkt 0xff82388c len 58
Oct 05 07:15:36 osmc-vero4k connmand[2587]: DHCPv6: received DHCP packet xid 0x52f4d300 (current state 13)
Oct 05 07:15:36 osmc-vero4k connmand[2587]: DHCPv6: switch listening mode (2 ==> 0)
Oct 05 07:15:36 osmc-vero4k connmand[2587]: DHCPv6: header 12 sub-option max len 28
Oct 05 07:15:36 osmc-vero4k connmand[2587]: DHCPv6: pos 12 option 0xff823945 code 5 len 24
Oct 05 07:15:36 osmc-vero4k connmand[2587]: DHCPv6: address count 1 addr 2001:XXXX:YYYY:... T1 1800 T2 2880
Oct 05 07:15:36 osmc-vero4k connmand[2587]: DHCPv6: code 3 0xff823935 len 40 list 0xab9fd720
Oct 05 07:15:36 osmc-vero4k connmand[2587]: DHCPv6: code 23 0xff82390d len 16 list 0xab9fd740
Oct 05 07:15:36 osmc-vero4k connmand[2587]: DHCPv6: code 14 0xff8238e4 len 0 list (nil)
Oct 05 07:15:36 osmc-vero4k connmand[2587]: DHCPv6: code 1 0xff8238e8 len 14 list (nil)

using journalctl |grep -i dhcp.

But as others already told: Once you are sure having got a DHCP answer (seeing received DHCP packet), then it depends on your dhcp server/firewall/router environment how the dhcp lease is managed and displayed there. AVM Fritzbox router here.

1 Like