Hi
I have a Raspberry Pi running Kodi - quite successfully on the network.
I've recently bought a Sony Android TV 49X8309C, it comes with Google Play Store, so I installed Kodi - SUCCESS!!!
BUT - when I go to System -> System Info ---> Network, the IP address is unusual and different, i.e.
Sony TV IP address: 192.168.10.40
Default Gateway: 192.168.10.1
Kodi IP address: 192.168.49.1 <---- issue here!
(no gateway defined)
Primary DNS: 192.168.10.1 (same as original gateway)
SO.... The above occurs when connecting the TV via ethernet cable to the unmanaged netgear network switch.
If I connect the TV to the network via WiFi - the IP address issue is not there (but then there is an issue with connection and download speed).
I also noticed whilst typing this message - if I leave it on the system info ---> Network screen long enough, the IP address changes to the TV's ip address (192.168.10.40) for a split second before reverting back to 192.168.49.1
Please help!
I am attempting to install plugins - but I have no idea how to download the repo zip files onto the the TV storage - so I thought if I can map Kodi to one of the NAS drives, I can point it there?
Help much appreciated in advance!
I'm having the same issue; got my FTV2 and installed Kodi 15.2.... this is happening. deleted, installed SMPC 15.0... same thing. This problem is happening with Kodi 15 looks like a bug. In the FTV it's showing the correct IP, in Kodi it's showing 192.168.49.1
Seriously, I find it hard to believe that no one else beside us has this problem...
HI, am trying to see what i can do to help.
My IP address within Kodi, as reported by Kodi, is the same as the IP address as reported by the TV's OS Settings / Network status.
I've always assumed that Kodi simply displayed the TV's IP address anyway rather than securing its own - i cant imagine how or why it does that.
Even if you had some reserved DHCP space in your router, surely the MAC address is the same since it's the same hardware?
Odd, its beyond my knowledge, sorry! Good luck though
(2015-11-08, 07:13)MSIC Wrote: [ -> ]I've always assumed that Kodi simply displayed the TV's IP address
That.
Is there an actual issue or is it only cosmetic (=wrong info displayed)?
(2015-11-08, 10:00)Koying Wrote: [ -> ][Is there an actual issue or is it only cosmetic (=wrong info displayed)?
How would one know? I can't ping the 49.1 address, yet from Kodi I can access all my shares as before, no changes in "network behaviour".
It looks like a problem showing the correct info - cosmetic as you put it.
After installing KODI on Amazon Fire TV (2015 edition) I found it is not using the same IP of the fire TV. My home network is on 10.x.x.x series IP and when I install Kodi from Google play on my phone/tab, it showed the same IP of my phone/tab. But when I install Kodi on Fire TV, it got some 192.168.x.x IP. I don't know why. But the gateway and DNS are the same as my network's gateway and DNS but IP is not.
I do not have any problem with the IP as long as it works, but the problem is I cannot use Android based Remote (Yest or Kodi native remote) the web service is running on a separate IP series.
Can anyone help me to understand what is going on and how I may make it right?
If you look at the client device list on your router, does the TV show up, and if so on what IP address?
Can you make a connection to that IP address, by ping, SSH and/or SMB (depending on which services you have enabled in Kodi)?
If you're proficient enough, use "adb shell", then "ip addr show" to know where this "49" address comes from, i.e.:
Code:
koying@mint-VirtualBox:/src/kodi-jarvis$ adb shell
shell@SVP-DTV15:/ $ ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN qlen 1000
link/ether ac:9b:0a:50:18:2b brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether 34:68:95:5f:d0:ad brd ff:ff:ff:ff:ff:ff
inet 192.168.3.117/24 brd 192.168.3.255 scope global wlan0
valid_lft forever preferred_lft forever
4: p2p0: <NO-CARRIER,BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state DORMANT qlen 1000
link/ether 36:68:95:5f:d0:ad brd ff:ff:ff:ff:ff:ff
shell@SVP-DTV15:/ $
This comes from my Sony X8509. I now notice this "p2p0" interface that I don't know where it comes from, btw...
Merged a 2nd thread from @
omiazad about the same subject
(2015-11-08, 10:00)Koying Wrote: [ -> ] (2015-11-08, 07:13)MSIC Wrote: [ -> ]I've always assumed that Kodi simply displayed the TV's IP address
That.
Is there an actual issue or is it only cosmetic (=wrong info displayed)?
No, my Fire's IP is 10.11.10.55, so when I try to control KODI from my Android app remote no service gets resolved on that IP.
(2015-11-09, 11:04)DarrenHill Wrote: [ -> ]If you look at the client device list on your router, does the TV show up, and if so on what IP address?
Can you make a connection to that IP address, by ping, SSH and/or SMB (depending on which services you have enabled in Kodi)?
I checked with my router, the host IP 10.11.10.55 is fine and nothing with 192.168.1.5 (KODI's IP)
Kodi works fine with any issues just cannot control Kodi using web services from other devices. That is a bit painful.
(2015-11-09, 13:19)omiazad Wrote: [ -> ] (2015-11-08, 10:00)Koying Wrote: [ -> ] (2015-11-08, 07:13)MSIC Wrote: [ -> ]I've always assumed that Kodi simply displayed the TV's IP address
That.
Is there an actual issue or is it only cosmetic (=wrong info displayed)?
No, my Fire's IP is 10.11.10.55, so when I try to control KODI from my Android app remote no service gets resolved on that IP.
(2015-11-09, 11:04)DarrenHill Wrote: [ -> ]If you look at the client device list on your router, does the TV show up, and if so on what IP address?
Can you make a connection to that IP address, by ping, SSH and/or SMB (depending on which services you have enabled in Kodi)?
I checked with my router, the host IP 10.11.10.55 is fine and nothing with 192.168.1.5 (KODI's IP). Cannot resolve the IP using SSH/Ping etc.
Kodi works fine with any issues just cannot control Kodi using web services from other devices. That is a bit painful.
(2015-11-09, 11:04)DarrenHill Wrote: [ -> ]If you look at the client device list on your router, does the TV show up, and if so on what IP address?
Can you make a connection to that IP address, by ping, SSH and/or SMB (depending on which services you have enabled in Kodi)?
My fTV2 IP is at 192.168.5.169 (over the wireless if), 192.168.5.112 (if connected wired). Right now it's on wifi - I can ping the IP, and I can control Kodi with my phone app. However, in the "info" on Kodi it shows 192.168.49.1 (in Kodi 15.2, SPMC 15, SPMC 14.2).
I don't think I'm able to get SSH or SMB in the Android version of KODI - at least I can't find these settings any more - when I ran OE I had both of these enabled..
Code:
shell@sloane:/ $ ip addr show
ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: ifb0: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN qlen 32
link/ether fa:94:d4:79:61:6a brd ff:ff:ff:ff:ff:ff
3: ifb1: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN qlen 32
link/ether ae:b2:e8:14:4b:53 brd ff:ff:ff:ff:ff:ff
4: tunl0: <NOARP> mtu 0 qdisc noop state DOWN
link/ipip 0.0.0.0 brd 0.0.0.0
5: sit0: <NOARP> mtu 1480 qdisc noop state DOWN
link/sit 0.0.0.0 brd 0.0.0.0
6: ip6tnl0@NONE: <NOARP> mtu 1452 qdisc noop state DOWN
link/tunnel6 :: brd ::
7: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP q
len 1000
link/ether a0:02:dc:82:18:94 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.189/24 brd 192.168.1.255 scope global wlan0
valid_lft forever preferred_lft forever
inet6 fe80::a202:dcff:fe82:1894/64 scope link
valid_lft forever preferred_lft forever
9: p2p0: <NO-CARRIER,BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
state DORMANT qlen 1000
link/ether a2:02:dc:82:18:94 brd ff:ff:ff:ff:ff:ff
inet6 fe80::a002:dcff:fe82:1894/64 scope link
valid_lft forever preferred_lft forever
10: p2p-p2p0-0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast stat
e UP qlen 1000
link/ether a6:02:dc:82:18:94 brd ff:ff:ff:ff:ff:ff
inet 192.168.49.1/24 brd 192.168.49.255 scope global p2p-p2p0-0
valid_lft forever preferred_lft forever
inet6 fe80::a402:dcff:fe82:1894/64 scope link
valid_lft forever preferred_lft forever
shell@sloane:/ $
The FTV2 uses wi-fi for its remote, I surmise this is the remote's IP?
Ah, right, p2p might be wifi-direct.
Thanks, will look into it.