On a home network, running DHCP is 100% normal when using a router. When people mention static or dynamic IPs, I think they're typically referring to what their ISP gives them and that doesn't apply "inside" the network where the receiver will be.
am I the only one that does not see anything about connecting to a home network under the install menu at scott's link?
I suspect they're probably going to have the box call home on a regular basis to see if there's any waiting requests, rather than leave a port open and listening. Dish does *not* want to get into the business of explaining to people how to punch holes into firewalls. Another option is doing the same thing they've done for quite some time, use the satellite for E* -> receiver communications. If they can send a hit to program the box fairly quickly, there's no reason they can't do the same for DVR programming requests, though that might start taxing bandwidth if everyone started doing it.Furthermore, I look forward to seeing if any security modifications will be required for those of us running firewalls. The receivers will be executing two-way communication, meaning that many hardware firewalls may block the connection by default. Opening up ports for the feature, also opens up additional holes in security.
I suspect they're probably going to have the box call home on a regular basis to see if there's any waiting requests, rather than leave a port open and listening. Dish does *not* want to get into the business of explaining to people how to punch holes into firewalls. Another option is doing the same thing they've done for quite some time, use the satellite for E* -> receiver communications. If they can send a hit to program the box fairly quickly, there's no reason they can't do the same for DVR programming requests, though that might start taxing bandwidth if everyone started doing it.
Last option I can think of... the box will keep a persistent connection open to the call-home server. Only issue with this is keeping lots of persistent connections open can tax the server.
Oh well, we shall wait and see. I got my 622 working with my Sipura 2000 and Sipphone, but it's still not 100% reliable, and I'd rather have one less piece of hardware sitting in my home theater.
they would be STUPID to require a static address. 99% of residential customers are on a dynamic address. (Including yours truly).
...I have a serious problem with over thinking things and in the process overlooking the obvious.
What about the 211 for external storage, I'm starting to lose my patience
Do you have DHCP disabled ?? All Dish means is there won't be a menu/screen that allows you to configure IP, gateway address, DNS, etc, etc.Some of us use Static DHCP; where the device requests an address via DHCP but the router hands them out a consistent address.
OR--- the fact that people can put a Access Point connected to an antenna outside their house, and their neighbors and use a client bridge to get internet in their house, and all the receivers would be "calling in" from the same IP. So receivers could be shared between neighbors.
Don't worry.Will we need to call to get the $5 charge removed once the receiver is connected, or does that happen automatically?
What does your computer have to do with any of this ?? I suspect you think the internet is "off" when you turn your PC off. It isn't, unless you also turn off your modem.
Yes, I remember those days myself. In a setup like that, it will be hard (for the average person) to "share" their internet connection between their PC and the 622.Some DSL customers (especially really old Verizon DSL (and maybe some other national DSL carriers?)) may be connected directly to the DSL modem and starting PPPoE at the computer side. Without PPPoE, they'd not be able to get their connection up. Odds are the 622 won't support PPPoE either (nor should it, really).
Do you have DHCP disabled ?? All Dish means is there won't be a menu/screen that allows you to configure IP, gateway address, DNS, etc, etc.
I'm positive I've seen a sticker, either on the receiver itself (the bottom, I think) or on the box it was shipped in.Once I know the MAC of my 622 and 211; I'll add them to the list
I've plugged mine into my router and it does NOT pull an IP address, telling me that networking is off or more likely, dhcpd is not running on the receiver (yet). When this update comes, they will turn those daemons on and it will then pull an IP if it finds a DHCP server.Should those of us who have had a ethernet cable in the reciever disconnect them until the enabling is announced, or will it matter once the port goes "live"?