• 1
  • 2(current)
  • 3
  • 4
  • 5
  • 7
Android KODI is not getting the same IP as the Host
#16
(2015-11-09, 14:39)Koying Wrote: Pointless to add the same report.
I need the info from http://forum.kodi.tv/showthread.php?tid=...pid2155369

Will this help:
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 66:8c:0d:29:43:58 brd ff:ff:ff:ff:ff:ff
3: ifb1: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN qlen 32
    link/ether 12:fb:a1:79:15:8a 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 qlen 1000
    link/ether f0:27:2d:9a:d9:fc brd ff:ff:ff:ff:ff:ff
    inet 10.11.10.35/24 brd 10.11.10.255 scope global wlan0
       valid_lft forever preferred_lft forever
    inet6 fe80::f227:2dff:fe9a:d9fc/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 f2:27:2d:9a:d9:fc brd ff:ff:ff:ff:ff:ff
    inet6 fe80::f027:2dff:fe9a:d9fc/64 scope link
       valid_lft forever preferred_lft forever
10: p2p-p2p0-0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether f6:27:2d:9a:d9:fc 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::f427:2dff:fe9a:d9fc/64 scope link
       valid_lft forever preferred_lft forever
shell@sloane:/ $

My point is, this is the host machine result, how that will show where I am getting what IP on Kodi?
Reply
#17
(2015-11-09, 17:58)Koying Wrote: Ah, right, p2p might be wifi-direct.

Thanks, will look into it.

*sigh*
Reply
#18
Any news on this? All of my media sources are ftp and I cannot connect to them with Kodi responding to the wrong ip.
Reply
#19
As said earlier, this is purely cosmetic. If you have a network issue, it's unrelated to this. Kodi does nothing to your device network setup.
Reply
#20
@ravibc

Same Issues

Hi,have got my Fire-tv box 3 days ago.When installing the last Kodi ver15.2 the same issue occurs with exactly the same IP adress:192.168.49.1.
After closing Kodi,a popup appears with the message (kind of) you must use the same network for WLAN as for LAN,with the options to configurate manually and a kind of policy.But no chance to activate the option buttons.
Solution:Exit!But the Popup appeared again several times and i couldn´t use the other apps anymore.

I did a factory reset of my Fire TV box twice:
1. Same issue
2.I only installed the "Fire starter"app ,not KODI with USB and checked the system information using this app:
Showing the"unknown address: xx:xx:xx:xx.xx%p2p-p2p0-0:192.168.49.1 and the static Fire-TV IP & Ethernet
I have to mention,that after the Factory resets the box did not boot.I had to remove and plugin the power cable.(Factory resetConfusedecond try only with LAN connection)

I still have the same problems....!Wondering if it is not a Fire TV Box- bug ?( Fire TV stick is working )
Reply
#21
See #19 above.
Reply
#22
I'm seeing the same IP address from within Kodi (192.168.49.1) on my Fire TV 2.
I cannot get external apps such as Yatse to connect using either the FTV box IP or the 192.168.49.1

Could it be something that Amazon have implemented within the Fire TV, maybe where side loaded / non official apps are isolated somehow from the FTV network. Could it be some kind of Network Address Translation perhaps ?
Reply
#23
Obviously that's not the IP that's given to your FTV by your router, go to your router and find the actual IP assigned to it.
Reply
#24
(2015-11-30, 23:37)cd2022 Wrote: Obviously that's not the IP that's given to your FTV by your router, go to your router and find the actual IP assigned to it.

I've removed and reinstalled Kodi. It still says 192.168.49.1, but appears to be available via it's LAN (DHCP) address now, so happy days Smile
Reply
#25
Having same problem as OP and it is impacting Kodi from using smb and nfs shares. Should be noted that I'm not using WIFI for Networking. I have a hard wired ETH0 interface on a 10.x.x.x network. I would prefer to simply disable the WIFI interface altogether on the FireTV. Why is Kodi defaulting to using P2P WIFI? This is a Media server, not a Hotspot or router.

There is a hard coded IP address from the Android P2P WIFI Manager found in:

Code:
package com.android.server.wifi.p2p;

public final class WifiP2pServiceImpl extends IWifiP2pManager.Stub {
    private static final String TAG = "WifiP2pService";
    private static final boolean DBG = false;
    private static final String NETWORKTYPE = "WIFI_P2P";

/* Is chosen as a unique address to avoid conflict with the ranges defined in Tethering.java */
private static final String SERVER_ADDRESS = "192.168.49.1";
Source: https://android.googlesource.com/platfor...eImpl.java

Any downsides to removing the WIFI P2P package from Kodi? I remember seeing some drill down on packages scrolling through the Kodi GUI. Not only do I not want a P2P WIFI network in my house, I don't want Kodi to use WIFI.

Thanks!
Reply
#26
The remote control communicates to the box via p2p wifi,

See post #19
Reply
#27
(2016-01-18, 22:34)cd2022 Wrote: The remote control communicates to the box via p2p wifi,

See post #19

That's not correct. The FireTV Voice Remote uses BlueTooth to communicate with both the FireTV and FireStick. BlueTooth is a short-range wireless protocol.

The Android P2P WiFi implementation I cited appears to be called by Kodi or is being picked up by Kodi. Androids WiFi-peer-to-peer (P2P), which is compatible with WiFi Direct, is designed to enable WIFI networking without a WiFi access point; similar yet different than mesh-WiFi.

If I spent the time to dig deeper into this problem, to include identifying the offending Android package name, then surely I have already read this entire thread, including post #19.

Now if I could post a dang screen shot of the Kodi Network Summary screen showing the P2P WiFi hijacked IP address of 192.168.49.1 in contrast to the rest of the 10.x.x.x DHCP scope address that should be there (DNS1, DNS2, Gateway, etc.), maybe we could move this ball forward a bit.
Reply
#28
Continued....

Image

This screen shot shows an example of the IP address found under System, System Info, Network Settings on an example Kodi. On my Kodi (Isengard 15.2), the IP address showing is 192.168.49.1, and the Gateway is completely wiped out. However, my DHCP server happily provides all of my network clients a 10.x.x.x address for both settings. The Android P2P WiFi manager within Kodi is trampling on the IP settings somehow on my Kodi/FireTV.
Reply
#29
Here is the Screen shot of my Kodi:
Image
Reply
#30
And here are the correct IP settings in the FireTV side.

Image
Reply
  • 1
  • 2(current)
  • 3
  • 4
  • 5
  • 7

Logout Mark Read Team Forum Stats Members Help
KODI is not getting the same IP as the Host0