WizOS connection issues

[Valo265]

Hi, I have recently installed tge WizOS application on my iPad. Up until a few days ago I could connect to my T4 and use the app for everything. The other day I went to watch a recording on my iPad and when I opened the app I got a error "Coonection Error: could not download movies from host". I can still watch live TV using the app, just cannot view any recorded shows.
Any help would be appreciated.
Thanks

[emmsee]

Have installed the WizOS (Android) and auto configured it, however it wont connect to my T2 - Connection Error ' cannot connect to Beyonwiz T2' .
My Gateway is 10.0.0.138 and the T2 was 10.0.0.22
Gateways at times set a high/low range for the wireless network so I turned off DHCP on the T2 and set 10.0.0.92 as the IP address (a laptop is 10.0.0.90 and yet another is 10.0.0.114. so I figure in between is safe.
Other settings are
Protocol HTTP.
HTTP Port 80
Streaming Port 8001
Enable Transcoder set to on.
Transcoder Type is Enigma2 Embedded
Enable Authentication is off
Zap b4 stream is off
Network name is the correct name for the Router..

The first time I configured the app it worked (4 days ago) but hasn't since.

Any clues or advice would be greatly appreciated.
cheers
Mike

[emmsee]

Further to the above post I ping 10.0.0.92 and the reply I got is weird:
Pinging 10.0.0.92 with 32 bytes of data:
Reply from 10.8.8.1: Destination port unreachable.
I didn't ping 10.8.8.1 and I don' t have any port forwards enabled.
I get the connection timed out error when I try 10.0.0.92 in my browser.
More grist for the mill.
cheers
Mike

[MrQuade]

Further to the above post I ping 10.0.0.92 and the reply I got is weird:
Pinging 10.0.0.92 with 32 bytes of data:
Reply from 10.8.8.1: Destination port unreachable.
I didn't ping 10.8.8.1 and I don' t have any port forwards enabled.

Your network appears to be configured very strangely.

Do you have multiple gateways and/or DHCP servers present?

What are the settings on your PC for IP, gateway, and subnet mask? And likewise in your gateway.

[prl]

Further to the above post I ping 10.0.0.92 and the reply I got is weird:
Pinging 10.0.0.92 with 32 bytes of data:
Reply from 10.8.8.1: Destination port unreachable.
I didn't ping 10.8.8.1 and I don' t have any port forwards enabled.

Your network appears to be configured very strangely. ...

I agree. I wonder if there may be a netmask mismatch somewhere, though I wouldn't expect that to cause the devices to start using a private IP address (10.8.8.1) that's way out of range of the probable correct range (10.0.0.1 - 10.0.0.254).

Gateways at times set a high/low range for the wireless network so I turned off DHCP on the T2 and set 10.0.0.92 as the IP address (a laptop is 10.0.0.90 and yet another is 10.0.0.114. so I figure in between is safe.

You figured incorrectly.

If you want to assign a non-DHCP managed IP address to a device it must be outside the host address range that your router uses for DHCP. You have almost certainly not done that. While it may not be causing the problems you are seeing now (but it might), it is likely at some time to turn around and bite you, when the DHCP system unknowingly assigns a second device to the same IP address that the manually-configured device is using.

On my router, the usable address range is 192.168.178.1 - 192.168.178.254 . Within that, the range 192.168.1782.20 - 192.168.178.200 is reserved for DHCP-allocated addresses. Addresses set manually in devices must be outside that range, i.e. 192.168.178.2 - 192.168.172.19 (192.168.178.1 is reserved for the router by default) or 192.168.178.201 - 192.168.178.254. The last number in the quad is the host address.

The correct host address ranges on your device are likely to be different from the choice on my router (as well as the network part of the address being different). You'll only be able to find out the reserved DHCP address range by looking in your router's admin interface (or less likely, in the router manual).

I'm also not sure what you mean by "Gateways at times set a high/low range for the wireless network".

[emmsee]

Only one modem router - in address 10.0.0.138
PC addresses are IP: 10.0.0.14
Mask: 255.255.255.0
Gateway: 10.0.0.138
DHCP?? This is weird
There is an ethernet lan from the router/modem to a Telstra TV box with the following :
IP address 10.8.8.58
Mask: 255.255.255.252
DHCP server address 10.8.8.57
Why would my browser redirect a URL of 10.0.0.92 redirect to the Lan address?
When I look at the T2 details on the router, no IP address is shown (unlike my other wireless linked devices) but instead under IP is: fe80::20e:4cff::fe81:7800 (yes 2 colons after the first digits)
Can you shed some light on the above?
Cheers
Mike

[prl]

...
fe80::20e:4cff::fe81:7800 (yes 2 colons after the first digits)
Can you shed some light on the above?
...

That looks like an IPv6 address, but the rest of your network seems to be using IPv4 addresses. Where you have '::' (in two places), that's equivalent to a series of 0000 groups. You're not supposed to have more than one "::" in a properly constructed IPv6 address, though, because it's ambiguous.

The address isn't a mapping of an IPv4 address into IPv6, though, they look like: ::ffff:0123:4567.

[MrQuade]

Only one modem router - in address 10.0.0.138
PC addresses are IP: 10.0.0.14
Mask: 255.255.255.0
Gateway: 10.0.0.138

That looks ok, though it is a bit strange to have the gateway configured to be in the middle of the subnet like that. Usually they live at x.x.x.1 or x.x.x.254.
It won't necessarily cause issues with the way you have it though.

DHCP?? This is weird
There is an ethernet lan from the router/modem to a Telstra TV box with the following :
IP address 10.8.8.58
Mask: 255.255.255.252
DHCP server address 10.8.8.57
Why would my browser redirect a URL of 10.0.0.92 redirect to the Lan address?

Now I am not sure what you are describing here. What device has a 10.8.8.x address? Is this configured into your gateway somewhere?

[prl]

Its also a slightly odd netmask: /30, where /24 is more usual.

[IanSav]

Hi MrQuade,

That looks ok, though it is a bit strange to have the gateway configured to be in the middle of the subnet like that. Usually they live at x.x.x.1 or x.x.x.254.
It won't necessarily cause issues with the way you have it though.

This is (was) common with Telstra configured equipment.

Regards,
Ian.

[emmsee]

DHCP?? This is weird
There is an ethernet lan from the router/modem to a Telstra TV box with the following :
IP address 10.8.8.58
Mask: 255.255.255.252
DHCP server address 10.8.8.57
Why would my browser redirect a URL of 10.0.0.92 redirect to the Lan address?

Now I am not sure what you are describing here. What device has a 10.8.8.x address? Is this configured into your gateway somewhere?[/quote]
The Telstra TV box that is connected to the Telstra Gateway Modem/Router via Ethernet cable

[MrQuade]

It sounds a bit like you have a couple of VLANs set up, or you have set up multiple WiFi access point SSIDs with WiFi isolation turned on. Is your PC on WiFi too?

If that's not it, then I'm not sure what the Telstra equipment is doing here. There must be some strange requirements to run their Telstra TV service that requires that odd little subnet to exist. I can't advise on that any further since I am unfamiliar with their services. None of what you have posted regarding the 10.8.8.x and 10.0.0.x subnets are making sense yet and I am not sure how the two ranges are coexisting.

What happens when you turn DHCP back on in the T2 settings? Is your T2 currently able to access the Internet?

It sounds like the T2 may not have joined your network at this time, and that is why the pings from your PC are failing. The reply from the 10.8.8.x address may be the main gateway address reporting that the T2 can't be found.

[emmsee]

It sounds a bit like you have a couple of VLANs set up, or you have set up multiple WiFi access point SSIDs with WiFi isolation turned on. Is your PC on WiFi too?

No Vlans, only one WiFi access point/gateway and the Laptop is on th Gateway network wirelessly.

If that's not it, then I'm not sure what the Telstra equipment is doing here. There must be some strange requirements to run their Telstra TV service that requires that odd little subnet to exist. I can't advise on that any further since I am unfamiliar with their services. None of what you have posted regarding the 10.8.8.x and 10.0.0.x subnets are making sense yet and I am not sure how the two ranges are coexisting.

What happens when you turn DHCP back on in the T2 settings? Is your T2 currently able to access the Internet?

Turning DHCP on on the T2 makes no difference (rebooted after resetting) and yes the T2 has no problem accessing the internet - updated the firmware today via internet (to the mid August firmware, as the latest update is not available via Internet update yet)

It sounds like the T2 may not have joined your network at this time, and that is why the pings from your PC are failing. The reply from the 10.8.8.x address may be the main gateway address reporting that the T2 can't be found.

After rebooting the T2 (not after re-enabling DHCP) I can now Ping the T2 at 10.0.0.92, but the Wizos still won't connect

I'll describe my network.
1 Modem/Router (Telstra Gateway) with 6 Wifi units showing up in the Router - 1 laptop, 1 tablet, 2 Android phones, 1 T2, 1 wireless printer.
As well the Router shows a LAN connection as Telstra TV (gives me access to all 5 network 'Iview' style apps); Netflix and Stan plus Youtube, internet browser ++.

All have normal IP addresses except the T2, but it is visible.
As well the Wizos shows that I have a T2 setup with a fixed IP address in the range. Fixed because the IP address was changing each time the T2 was updated and the Wizos couldn't then recognise it.
To proceed, I'll reset the modem and see what difference that makes to the network.
Any other suggestions?
cheers
Mike

[MrQuade]

After rebooting the T2 (not after re-enabling DHCP) I can now Ping the T2 at 10.0.0.92, but the Wizos still won't connect

Hmm, that's strange. Try editing the WizOS app settings and make sure the T2 connection's IP address is set correctly to 10.0.0.92.

I'll describe my network.
1 Modem/Router (Telstra Gateway) with 6 Wifi units showing up in the Router - 1 laptop, 1 tablet, 2 Android phones, 1 T2, 1 wireless printer.
As well the Router shows a LAN connection as Telstra TV (gives me access to all 5 network 'Iview' style apps); Netflix and Stan plus Youtube, internet browser ++.

Ok, it does sound like your gateway is using a different subnet on wireless than it is for wired. That's probably a bit excessive, but I'd say what has happened here is that there is an option switched on in your gateway that isolates wireless clients from the wired clients. It didn't affect you much since most of your devices are wireless.

All have normal IP addresses except the T2, but it is visible.
As well the Wizos shows that I have a T2 setup with a fixed IP address in the range. Fixed because the IP address was changing each time the T2 was updated and the Wizos couldn't then recognise it.
To proceed, I'll reset the modem and see what difference that makes to the network.

Normal addresses? As in dynamically assigned DHCP addresses? That should be fine.

Sounds like things are working as they should now.

Try accessing the T2's web interface from your PC. Go to http://10.0.0.92/ from your PC's web browser.

If that works, then WizOS should also work assuming the IP address is set correctly in the WizOS app as mentioned earlier.

[emmsee]

I deleted the T2 from the WizOS and started from scratch.
Also reset the modem.
The modem reset hasn't changed the differing IP ranges between WiFi and LAN but the web based access to the T2 now works fine and the WizOS is also working.
Looks like a glitch that resetting has fixed.
All good here.
Thanks Mr Quade for the tip in another thread to use Open Webif; it's great and much easier than using the remote /menu settings.
Many thanks for all your input guys - much appreciated!
Cheers
Mike