Static Address Selection

[tinman]

Running with KRavEN-hacked prom and replaced init.rd img. NOT running the U5 software but running the version that shipped with box. Have bash and am trying to get telnet and tytools working but can't seem to connect to box thru FTP.

I have a NETGEAR FR 314 firewall router that uses DHCP and permits assignment of static addressess as well. (Anyone got DHCP working with the Series 2 DTIVOs?)

I plugged my Linksys USB200M into a PC box to see what addy it would get and also to locate its MAC address since I couldn't find it on the box or on the hardware. I then assigned one static addy to that MAC address and a second static addy to the same MAC address to represent the two addresses in the rc.sysinit.author file (one for the eth0 assignment and one for broadcast). When I check my router software, I only see one addy there (besides all my PCs), the one for the assigned broadcast address.

Should I assign two static addys or just one and if only one, then which one--the eth0 addy or the broadcast addy? BTW: I think this problem is keeping my from telneting into the box since all other hacks are working and the lights on my USB200M light up.

If I assign only the eth0 static addy, what's the purpose of the broadcast addy? Does the box do this on it's own? Does it need a broadcast addy? Frankly, I don't understand this part of the setup or why it's there. I think someone else asked this question before as an aside but there were no takers. Any takers now?

[mrblack51]

well, you don't have to do anything to your router to get the static ip to work in general. just pick an ip thats valid for your network and use it. if you have used your router to pick a static ip, then just use the one htat you picked. however, your tivo will not show up on your router most likely, because the router will probably only show the systems that it gave addresses to via DHCP.

[devnull]

eth0 is the Tivo's IP address. When Tivo sees this IP address on the wire, it picks up the packet. Note that "static IP" applies to the client. It's notion of it's address is defined ON THE CLIENT. Contrast this with DHCP where the client asks a DHCP server (your router is one) to tell the client it's address.

The "broadcast" address is what the Tivo uses when it doesn't know the MAC address of a machine on it's network. It is used BY Tivo to do things on the local network.

The gateway is where the tivo sends packet destined for IP addresses outside it's network (as defined by the netmask).

Finally, there's your router. What you're probably doing is a fixed DHCP mapping. This tells the router to assign THIS IP address when it gets a DHCP request from THAT MAC address.

You should delete the static IP for the broadcast address. My guess is that this is defined last (probably being .255) and since you only have one MAC address for the tivo, it is associated with the bcast. This definitely doesn't agree with what Tivo thinks it's IP address is.

But aside from knowing that you need to change this, I cannot think of why this setting on the router would cause you problems.
As mrblack says, your router doesn't need to be involved in a static address.

I checked mine and my tivos don't even show up. I do have fixed mapped clients so that my PCs always get the same IP addresses. I have made sure that the IP addresses for the Tivos are outside the range of addresses doled out for DHCP.

gary

[tinman]

Thanks for all the help MrB51 and devnull. I now have a better understanding of TIVO networking (and networking in general).

I followed devnull's suggestion and deleted the static addy I had used for broadcast and just assigned a single static addy against the MAC address. I used this same static addy in the eth0 networking line and voila, got it working with a LinksysUSB100TX but the lights don't come on which alldeadhomiez (ADH) alluded to in his great post on network drivers. However, I can now telnet in and also use Tivoweb.

I still can't get Tytools working--it connects but can't find nowshowing list--but I think I may have a problem with kmem and I shall tackle that this weekend. I'm also going to put the drivers in for the USB200M and see if I can get it working with that device.