Hi, anybody know why my Humax PC interface keeps disconnecting after a couple of minutes. It does this every day and then you can't get back into it until the next day, then two min's and it's gone again. I use 192.168.148 and when I check on the Humax it's the same numbers but it just won't stay connected.
Custom firmware works for a couple of minutes then disconnects
- Thread starter fatbloke
- Start date
grahamlthompson
Well-Known Member
Have you reserved the IP address on your router ? Is the package servermon installed ?
Hi thanks for your reply. Sorry to sound a bit thick but I haven't reserved the IP address and I haven't got servermon installed. Changed my router a few weeks ago so maybe it's that. I've never had a problem before then. How do you reserve the IP address?
Hello again, updated package list from internet and servermon appeared. Just downloaded it, interface still working after 5 mins.
Black Hole
May contain traces of nut
Is there a dot missing from the IP address you quoted?
The issue of "reserving" the address is to make sure you can always access the Humax on your network at the same address. I don't know the Foxsat, but I presume it has options to request an address from the router at boot time (DHCP) or to set an address manually. A DHCP address can be different each session, although typically the router will assign the same address each time, particularly if the connection is used frequently. The router can be configured to reserve the address for the Foxsat (identified by the unique MAC address), but detailed instructions depend on which router you have (usually via a control panel web page).
Manual address setting at the Foxsat carries a small risk of address conflicts unless you are careful not to set any address that is (or could be) in use by another device, but ensures the Foxsat is always at a predefined IP address. The perfect configuration is to either manually set an address which is not in the router's DHCP pool (the range of addresses the router can hand out to devices requesting an address), or manually freeze the address previously configured by DHCP and then reserved at the router. Again, the DHCP pool is router-specific.
DHCP is useful for devices to connect to your network on a casual basis, without the user being terribly aware of what's going on. The device needs an address; to get access to the Internet the particular address doesn't matter much and the user doesn't need to know it. Specific addresses only become important when you have local resources on your network - eg a NAS, or in this case the Foxsat. Local resources should have fixed addresses so another device knows where to find them (although Windows etc will attempt to locate resources by name rather than address).
By assigning an address outside the DHCP pool, the administrator can impose a logical scheme to fixed resources. For example, on my network I have three HDR-FOXes and three HD-FOXes. To share content, I want all the HD-FOXes to locate all the HDR-FOXes, and each HDR-FOX to locate the other HDR-FOXes... and I need PC web browser access to all of them. Thus they are fixed resources, and I have manually assigned their addresses 192.168.1.11, .12, .13, .21, .22, .23 respectively (my DHCP pool is .64 to .253). I will have to ensure that any other devices I might assign addresses to do not conflict with these assignments, and the router should not hand out any addresses which conflict because they are outside the DHCP pool.
Manual addresses are also useful for overcoming problems with networks which only "wake up" slowly, eg networks based on HomePlugs with sleep mode. In these cases the network connection is not established immediately the device boots, so cannot respond to the DHCP request and may leave the device unavailable on the network (even for outward communications). If the IP address is assigned manually, the device will be able to communicate once the network has stabilised.
I hope that helps. For explanation of terms see my Glossary (click).
The issue of "reserving" the address is to make sure you can always access the Humax on your network at the same address. I don't know the Foxsat, but I presume it has options to request an address from the router at boot time (DHCP) or to set an address manually. A DHCP address can be different each session, although typically the router will assign the same address each time, particularly if the connection is used frequently. The router can be configured to reserve the address for the Foxsat (identified by the unique MAC address), but detailed instructions depend on which router you have (usually via a control panel web page).
Manual address setting at the Foxsat carries a small risk of address conflicts unless you are careful not to set any address that is (or could be) in use by another device, but ensures the Foxsat is always at a predefined IP address. The perfect configuration is to either manually set an address which is not in the router's DHCP pool (the range of addresses the router can hand out to devices requesting an address), or manually freeze the address previously configured by DHCP and then reserved at the router. Again, the DHCP pool is router-specific.
DHCP is useful for devices to connect to your network on a casual basis, without the user being terribly aware of what's going on. The device needs an address; to get access to the Internet the particular address doesn't matter much and the user doesn't need to know it. Specific addresses only become important when you have local resources on your network - eg a NAS, or in this case the Foxsat. Local resources should have fixed addresses so another device knows where to find them (although Windows etc will attempt to locate resources by name rather than address).
By assigning an address outside the DHCP pool, the administrator can impose a logical scheme to fixed resources. For example, on my network I have three HDR-FOXes and three HD-FOXes. To share content, I want all the HD-FOXes to locate all the HDR-FOXes, and each HDR-FOX to locate the other HDR-FOXes... and I need PC web browser access to all of them. Thus they are fixed resources, and I have manually assigned their addresses 192.168.1.11, .12, .13, .21, .22, .23 respectively (my DHCP pool is .64 to .253). I will have to ensure that any other devices I might assign addresses to do not conflict with these assignments, and the router should not hand out any addresses which conflict because they are outside the DHCP pool.
Manual addresses are also useful for overcoming problems with networks which only "wake up" slowly, eg networks based on HomePlugs with sleep mode. In these cases the network connection is not established immediately the device boots, so cannot respond to the DHCP request and may leave the device unavailable on the network (even for outward communications). If the IP address is assigned manually, the device will be able to communicate once the network has stabilised.
I hope that helps. For explanation of terms see my Glossary (click).
Cheers thanks for that I'll have a go.
The web server in the Foxsat custom firmware is known to crash regularly. I don't think anyone has looked at it to see why (since it's basically the same one that is used in the Freeview custom firmware I'm guessing it's a bug triggered by the different endianess) but the servermon package adds a watchdog that kicks it when it crashes.