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

#76
General Discussions / Re: Icebox2 Setup Problems
July 26, 2006, 09:33:26 PM
If your router has an address of 192.168.2.1, then your default gateway and your DNS server are almost certainly 192.168.2.1 as well.
#77
General Discussions / Re: XBOX and ICE WIFI
July 05, 2006, 12:00:55 AM
Yes, IceBox2 and XBMC are great friends.
#78
You must not connect the wired LAN ports and the wireless network to the same Ethernet segment. If you do, you will create a loop and cause a network congestion that will kill the performance.

If you want to use the device in a wired configuration, disable the wireless radio in the Wireless Settings section.

If you absolutely must have wired and wireless at the same time, you should configure a separate wired network with a DHCP server and plug the IceBox2 WAN port into this new wired network. The WAN port will then acquire it's address from the DHCP server and the IceBox2 will then be visible on both networks. Please make sure that the wired and wireless networks end up being on different subnets, otherwise you have a 50% chance of having a routing problem. This is not a standard/supported configuration and requires some level of networking expertise.
#79
Topfield / Re: system log query
July 04, 2006, 10:53:37 PM
The WAN port always runs a DHCP client so that it is possible to recover a box, even if a user does something to screw up the box. This is somewhat mittigated by the fact that the reset button can be used to restore to factory defaults, however I chose to reserve the WAN port as a recovery vehicle.

If nothing else, those message are a good heartbeat indicator. You get two messages every minute or so. The fact that they keep on appearing means that everything is working normally.  :P
#80
General Discussions / Re: icebox2 as wireless bridge
April 15, 2006, 12:41:47 AM
That should work.

Connecting the Xbox Ethernet cable to the IceBox2 is equivalent to plugging the Xbox Ethernet cable into your accesspoint/router Ethernet switch.

As long as your wireless network can sustain the required data rates, everything should work as well as if it was connected with a cable.
#81
If you grab Ooba from XBMCscripts, you can easily watch video streamed directly off the Internet on your Xbox. The Xbox / Toppy / IceBox2 setup I have here is easily fast enough even with WPA-PSK/TKIP to stream movie trailers.
#83
XMLTV (General) / Re: Minor error in SBS program E=MC2
December 13, 2005, 02:11:13 PM
I guess I should have been a little bit less obtuse in my reply.

If you set the character encoding to UTF-8 (instead of ISO-8859-1) on the text editor you use to view the XML on the PC, everything will look just fine. Same applies to this web page, it looks fine with UTF-8, however there are funny characters if I view with other character encodings.

As far as the Toppy is concerned, that may be an issue that only Topfield can resolve. There is no documentation available from Topfield that would explain how to handle various text encodings. Perhaps the Toppy can not handle extended character sets at all?
#84
XMLTV (General) / Re: Minor error in SBS program E=MC2
December 07, 2005, 08:19:31 PM
Looks fine here. Are you sure you are using something that can handle Unicode UTF-8 properly?
#85
You should check out http://icebox.sf.net/ if you are interested in hacking the Netgear or contributing additional functionality.
#86
Topfield / Re: Wireless
October 31, 2005, 07:32:44 PM
QuoteAny idea whether the bridge works with mac osx
Yes, it does.

Quoteso can the Toppy's firmware be updated from a mac?
No, it can not. Topfield provide only Windows software. Topfield will not provide enough information to third parties to allow creation of firmware upgrade solutions for alternative platforms.
#87
Topfield / Re: Netgear WGT634U
October 11, 2005, 01:52:49 PM
There is at least one issue I can see already, both your laptop and access point are using 192.168.1.1 as their IP. That means the entire network is unstable.

Here's my recommendation for a reasonable network layout that should work rather well:

  • configure access point as 192.168.1.1 netmask 255.255.255.0
  • set access point to serve DHCP in the range 192.168.1.100 - 192.168.1.200
  • set laptop to use DHCP to obtain IP and network configuration
  • set desktop to use DHCP to obtain IP and network configuration
  • set WGT634U to use DHCP to obtain IP and network configuration
  • reboot access point
  • reboot laptop
  • reboot desktop
  • reboot WGT634U
  • use laptop or desktop to connect to access point and see what MAC addresses have been assigned what IP
  • if your access point supports it, configure DHCP server to always assign the same IP to a MAC address, I recommend something in the range 192.168.1.5-192.168.1.10. You can do this to the WGT634U and your other devices.
Making use of DHCP is fairly important, it tends to work much better than manual configuration and the entire network ends up with consistent configuration. What's perhaps even more important, is that if you need to change things, it can be done from one place and with little scope for typos.

I still think that allowing non-DHCP configuration is more trouble than it's worth. Just about any decent access point or router out there has a DHCP server. Giving manual IP configuration access is like handing a saw over to someone sitting on a branch. You'll always find someone who will cut the wrong side.  ;)

I'm pretty confident that your configuration can be sorted out without having to send the device away.

You should ensure that your firewall is not interfering with your web browser. Software firewalls tend to be a common cause of troubles for many people. It may not be a bad idea to temporarily disable your firewall until things work.

BTW: If you think you are having trouble with this, you should see how things break when you try to get WPA working between equipment from various vendors. Trust me, you are better off with WEP for now, until WPA2 is more common.
#88
Topfield / Re: Netgear WGT634U
October 11, 2005, 12:39:11 AM
Procedure for accessing a WGT634U that you think you misconfigured:
  • disconnect all cables from WGT634U, including power, network and USB
  • disconnect network cable from PC and configure network interface on PC for 192.168.1.1, netmask 255.255.255.0
  • connect power cable to WGT634U
  • wait 60 seconds
  • connect Ethernet cable between PC and WGT634U WAN port (the one next to the USB connector)
  • switch off the use of web proxies for your web browser (often called direct connection to the Internet)
  • use browser on PC to connect to http://192.168.1.17/
The above should work in most instances. If the above does not work, it almost certainly means that your wireless connection is working and the WGT634U is connecting to your access point. If that is the case, repeat the steps above, but ensure the access point is turned off before you start.
#89
Topfield / Re: Netgear WGT634U
October 11, 2005, 12:21:06 AM
You are probably violating a simple network topology rule and creating a routing blackhole. It sounds like you have made the same configuration error multiple times. Let's see if we can figure out where the problem is and how to get around it.

We'll need to start with a description of your existing network and how you expect to connect the Netgear to it. Please describe your existing networked equipment, how it is connected and what IP addresses and netmasks you use. Please also provide details of any network services that may be available, such as DHCP servers on access points or DNS proxies on firewalls / routers. The more information we have, the easier it is to see the whole picture.

In the case of the Netgear router, you should configure it with the least amount of information required. You should prefer DHCP over static configuration. Unless you fully understand the routing implications of a multi-homed network, I would not recommend entering any details for the static IP, default gateway or DNS servers.
#90
Topfield / Re: Netgear WGT634U
October 05, 2005, 04:58:13 PM
All the major components have been published either as part of the GPL release available from the IceTv GPL page or as part of the icebox project.

There are no plans to provide plaintext versions of any passwords to the public for obvious security reasons.

If you are planning on doing icebox development, I would suggest that you join the icebox-devel mailing list, hosted by the icebox project and start a conversation there.