IceTV Forum

IceTV Guide for IceTV enabled PVRs => Topfield => Topic started by: brad_nt on May 23, 2006, 08:44:52 PM

Title: ASUS and Toppy filemanager problem
Post by: brad_nt on May 23, 2006, 08:44:52 PM
My TF5000PVRt Masterpiece ( black Version) has version 5.2.72 with a firmware date of 15 June 2005. I am having trouble with the file manager through the ASUS wireless interface. From all the docs Should I down grade to April 24 th version. I would like to be able to copy and delete files from the Toppy to my PC via the wireless network.

This is the Syslog

ay 23 11:09:45 (none) kern.warn kernel: eth1: received packet with  own address as source address
May 23 11:09:45 (none) kern.warn kernel: eth1: received packet with  own address as source address
May 23 11:10:47 (none) kern.debug udhcpc[830]: Sending discover...
May 23 11:10:49 (none) kern.debug udhcpc[830]: Sending discover...
May 23 11:10:51 (none) kern.debug udhcpc[830]: Sending discover...
May 23 11:10:54 (none) kern.warn kernel: eth1: received packet with  own address as source address
May 23 11:10:54 (none) kern.warn kernel: eth1: received packet with  own address as source address
May 23 11:10:54 (none) kern.warn kernel: eth1: received packet with  own address as source address
May 23 11:10:54 (none) kern.warn kernel: eth1: received packet with  own address as source address
May 23 11:10:54 (none) kern.warn kernel: eth1: received packet with  own address as source address
May 23 11:10:54 (none) kern.warn kernel: eth1: received packet with  own address as source address
May 23 11:10:54 (none) kern.warn kernel: eth1: received packet with  own address as source address
May 23 11:10:54 (none) kern.warn kernel: eth1: received packet with  own address as source address
May 23 11:11:03 (none) kern.warn kernel: eth1: received packet with  own address as source address
May 23 11:11:03 (none) kern.warn kernel: eth1: received packet with  own address as source address
May 23 11:11:03 (none) kern.warn kernel: eth1: received packet with  own address as source address
May 23 11:11:08 (none) kern.warn kernel: NET: 12 messages suppressed.
May 23 11:11:08 (none) kern.warn kernel: eth1: received packet with  own address as source address
May 23 11:11:09 (none) kern.warn kernel: NET: 10 messages suppressed.
May 23 11:11:09 (none) kern.warn kernel: eth1: received packet with  own address as source address
May 23 11:11:14 (none) kern.warn kernel: NET: 20 messages suppressed.
May 23 11:11:14 (none) kern.warn kernel: eth1: received packet with  own address as source address
May 23 11:11:20 (none) kern.warn kernel: NET: 15 messages suppressed.
May 23 11:11:20 (none) kern.warn kernel: eth1: received packet with  own address as source address
May 23 11:11:29 (none) kern.warn kernel: NET: 15 messages suppressed.
May 23 11:11:29 (none) kern.warn kernel: eth1: received packet with  own address as source address
May 23 11:11:29 (none) kern.warn kernel: eth1: received packet with  own address as source address
Title: Re: ASUS and Toppy filemanager problem
Post by: kidhazy on May 26, 2006, 01:39:15 PM
Brad,

I can't solve your specific problem, but I don't believe you should have to downgrade your Toppy firmware to get it working.

I'm successfully running on the May 2005 Firmware with the ICEBOX2.

You should contact ICETV support to confirm this.

As for your syslog errors, I had similar messages (ie. the "eth1: received packet with  own address as source address " ) even whilst my ICEBOX2 was working OK.

These only occurred when I was running wireless.  ICETV support suggested that they may be because I also had an ethernet cable plugged in, or a dodgy Access Point on my end.  But they appeared even though I had no ethernet cables plugged in.  

I've since turned off the wireless and gone to a wired ethernet configuration (to get faster throughput) and these warning messages no longer appear.

Goodluck,
kidhazy.

Title: Re: ASUS and Toppy filemanager problem
Post by: pvogel on May 27, 2006, 07:13:13 AM
Can you provide a little more information about the configuration, e.g. static/dynamic IP

And what exactly is the problem you are having with the file manager?

Also, confirm that this problem is happening with the router in WiFi mode only, no ethernet connected?

Thanks

Peter Vogel
CTO IceTV