Main Menu
Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - peteru

#91
Topfield / Re: All EPG items 2 minutes late
October 02, 2005, 10:34:32 PM
It sounds like your Masterpiece PVR is set to "Manual", rather than "Automatic" time.
#92
Topfield / Re: Netgear WGT634U
September 19, 2005, 10:58:30 PM
Just thought of another few things.

1. Physical position with respect to the AP.

When I got my first lot of wireless equipment, I wasted about 40 minutes trying to get things going. As it turned out, my AP was almost directly above the client and the two devices were within each other's blind zone.

Ensure that both devices are at the same height and at least 1-2m from each other. Both antennae should be as vertical as you can get them - ideally parallel to each other.


2. Routing loops.

Once you configure your wireless network properly, you may end up with both the wired and wireless networks connected at the same time. Depending on the exact setup of your home network, this could present issues related to routing loops. The fix is simple. Wait about 30 seconds, power down the icebox, unplug the wired network and power on the icebox. Wait another 60 seconds, then check the web interface of your AP to see if the icebox is on the network.


3. Firewalls and proxies.

Always a good idea to check that there isn't something else in the way, like a firewall rule or a caching proxy.
#93
Topfield / Re: Netgear WGT634U
September 19, 2005, 10:43:37 PM
QuoteMy initial configuration was with MAC filtering enabled, I added the 2 MAC addresses on the bottom of the unit and then during setup I noticed a third MAC address in the status page in the icebox interface so added that too.
Ignore the MAC addresses printed on the box. Instead, go to the "Device Status" page, where you will find MAC addresses for both the wired and wireless interface. You only need the one for wireless.

QuoteMy normal network configuration is SSID hidden, MAC filtering on and WPA-PSK.
Paranoia mode. ;) Nothing wrong with that - if it works. When it doesn't, you can relax a few of these settings to troubleshoot the problems, without making your network insecure.

If you have hidden SSID, you will have to specify it exactly in the icebox web interface. Keep in mind that the SSID is case sensitive and that it should not have any leading or trailing whitespace. To be on the safe side, keep it to alphanumerics with no spaces or punctuation. Something like "My1stHiddenNetwork" is good, but "My #1 network!" is not the best choice.

WPA-PSK is not supported right now. Main reason is poor interoperability between various vendor implementations.

QuoteI had the initial conditions for this one as SSID Hidden, MAC Filtering on with the 3 Icebox associated MACs in there, and "WEP or WPA-PSK" security. WEP kep was the example WEP 128bit HEX just copied straight from my router management page into router and icebox setup page.
That sounds almost right. I find that various vendors have varying levels of compatibility with "WEP and WPA-PSK" mode. Most of the time it does not work properly, especially with mixed networks that have WEP only as well as WPA-PSK TKIP and WPA2 AES clients.

QuoteAfter initial failure I went to WEP only on the router.
I'd suggest the following approach:

Start with the AP configured for:
* MAC filtering - OFF
* WEP - 128-bit key in hex
* Broadcast SSID - ON
* DHCP server - ON

Icebox wireless settings:
* Enabled - ON
* ESSID - blank
* WEP key - 128 bit key in hex
* Address - blank (use DHCP)
* Default gateway - blank (obtained via DHCP)
* DNS server - blank (obtained via DHCP)

That should be the easiest to get working, without making your network insecure.

Assuming that this configuration works, you can further enhance your security by enabling the following features one at a time:

* Specify ESSID on the icebox and turn SSID broadcasts OFF on the AP.
* Enter icebox MAC address in AP access list and enable MAC filtering on the AP.

I'd expect things to work up to this point.

Other adventures you can try, however you are likely to encounter problems:

* Mixed WEP / WPA-PSK mode
* Afterburner / SuperG / Turbo modes
* WDS

This isn't really an issue with any particular product, it's just the current state of the wireless marketplace. Each chipset vendor has different ideas on how to get the most performance out of their product. As soon as you start using anything new, compatibility ends up going out the window. WEP is fairly well understood, WPA is a disaster zone, WPA2 / 802.1x is not mature enough to be properly supported by most vendors.

Good luck with it, I'm sure you'll get it working.
#94
Topfield / Re: Netgear WGT634U
September 19, 2005, 01:47:46 PM
Wireless networking can have many compatibility issues, both new and older equipment. The only way to resolve them in many situations is to keep things as simple as possible and use a systematic approach to eliminate one thing at a time. This can be very time consuming and frustrating and is one of the reasons why the ICE firmware is as simple as possible. Every network connection has at least two end points and unfortunately the AP end point is a big complicated unknown quantity in most cases.

In your case, the inability to connect to an open network sounds a lot like there may be MAC address filtering enabled on your AP. Of course, it could be any number of other things.

Either way, it's always a good idea to report problems to the manufacturer. Even if the manufacturer can not help you on the spot, they can become aware of any potential issues and improve the product in the future.

Half the effort of fixing a problem is reproducing it and identifying the cause. Yes, it is more effort to post the router to someone and have it examined, but at least there is a chance of having the problem fixed. I doubt that your rubbish bin will be much help.  ;)
#95
XMLTV (General) / expat parser
January 31, 2005, 11:29:38 PM
Is anyone working on an expat based parser for the guide data and willing to share source? I'd rather not re-invent the wheel if I don't have to  :)

I'm happy to collaborate, so it does not have to be a complete implementation.

I'm mainly looking for something with small memory footprint, which precludes DOM.