HR20 network question (technical)

[n-spring]

My HR20 gets a DHCP assigned IP address from my router. That address is always on the 192.168.1.0 network. However, my router log is showing that the HR20 is sending out a HTTP request to 192.168.0.1. What is it trying to do, and why would it be sending a request to port 80 and IP address on a network it's not even attached to?

[Clemsole]

Here is a link that might help in setting up the HD20 and your network.

http://www.dbstalk.com/showthread.php?t=99327

[gcisko]

My HR20 gets a DHCP assigned IP address from my router. That address is always on the 192.168.1.0 network. However, my router log is showing that the HR20 is sending out a HTTP request to 192.168.0.1. What is it trying to do, and why would it be sending a request to port 80 and IP address on a network it's not even attached to?

Not sure. But can we assume that other than this question, everything else is working as expected? And that you just see this unexplained conneciton attempt?

[Redlinetire]

My HR20 gets a DHCP assigned IP address from my router. That address is always on the 192.168.1.0 network. However, my router log is showing that the HR20 is sending out a HTTP request to 192.168.0.1. What is it trying to do, and why would it be sending a request to port 80 and IP address on a network it's not even attached to?

I'm far beyond a network guru but I do understand that those numbers aren't separate networks, they're different addresses on the same network. Like addresses on a street. They're all on the same street.

I think 192.168.0.1 is a common address for DSL modems. So it may be attempting to determine if you have a modem and what speed it can handle.

[HouseBowlrz]

My HR20 gets a DHCP assigned IP address from my router. That address is always on the 192.168.1.0 network. However, my router log is showing that the HR20 is sending out a HTTP request to 192.168.0.1. What is it trying to do, and why would it be sending a request to port 80 and IP address on a network it's not even attached to?

That's odd ... mine is also DHCP assigned inside my network, albeit my firewall which is managing the DHCP pool. The HR20 got assigned an address within the range of my private net.

I believe you can manually assign an address to the HR20 so give that a try if DHCP continues to be a RPITA.


cheers

[gcisko]

I'm far beyond a network guru but I do understand that those numbers aren't separate networks, they're different addresses on the same network. Like addresses on a street. They're all on the same street.

I think 192.168.0.1 is a common address for DSL modems. So it may be attempting to determine if you have a modem and what speed it can handle.

But the question would be "why ?". Depending on the subnet mask that is used it is not even the same network address space.

[Redlinetire]

But the question would be "why ?". Depending on the subnet mask that is used it is not even the same network address space.

But we're talking about a home network presumably. 99.99% of people with home networks don't even touch subnet masks 'cause you're only using one router.

[gcisko]

But we're talking about a home network presumably. 99.99% of people with home networks don't even touch subnet masks 'cause you're only using one router.

Doesn't matter. It still has to be the correct value. That is why i would like to see all of the network settings involved.

[Redlinetire]

Doesn't matter. It still has to be the correct value. That is why i would like to see all of the network settings involved.

Because if the subnet mask values were different that would explain the log entry for the router? :confused:

[cpanic]

This is just a wild guess, but maybe Directv has a local server at 192.168.0.1 that they use internally when testing the software releases.

It would be interesting to capture the packets that are attempting to go to that address.

[n-spring]

1. 192.168.0.1 and 192.168.1.1 ARE on separate networks because the netmask is 255.255.255.0.

2. Yes, everything is OK, other than this connection attempt to 192.168.0.1:80

3. I don't have a packet sniffer to see what the HR20 is trying to do.

Perhaps someone with an inside connection to DirecTV engineering can find out what it's trying to do.

[Spanky_Partain]

1. 192.168.0.1 and 192.168.1.1 ARE on separate networks because the netmask is 255.255.255.0.

2. Yes, everything is OK, other than this connection attempt to 192.168.0.1:80

3. I don't have a packet sniffer to see what the HR20 is trying to do.

Perhaps someone with an inside connection to DirecTV engineering can find out what it's trying to do.

Here is a free packet sniffer.

http://ethereal.com/

[cartrivision]

My HR20 gets a DHCP assigned IP address from my router. That address is always on the 192.168.1.0 network. However, my router log is showing that the HR20 is sending out a HTTP request to 192.168.0.1. What is it trying to do, and why would it be sending a request to port 80 and IP address on a network it's not even attached to?

192.168.0.1 is probably the address that the DHCP server (your router) told the HR20 to use for DNS lookups... i.e. the DNS server address to use. The router will route DNS lookups sent to that address to the DNS server address that your ISP's DHCP server gave to your router.

The HR20 network setup screen has a line that tells you what address it is using for the DNS server. Look and see if it says 192.168.0.1.

[n-spring]

192.168.0.1 is probably the address that the DHCP server (your router) told the HR20 to use for DNS lookups... i.e. the DNS server address to use. The router will route DNS lookups sent to that address to the DNS server address that your ISP's DHCP server gave to your router.

The HR20 network setup screen has a line that tells you what address it is using for the DNS server. Look and see if it says 192.168.0.1.

Nope. The DNS server(s) is/are different. It wouldn't be using port 80 to do DNS lookups anyway. I would be seeing port 53 if they were DNS requests.

[n-spring]

Mystery solved (I think)...

Thanks to Spanky for pointing me to Ethereal (now called Wireshark).

My router is reporting a bogus destination IP address because the HR20 is sending out a multicast discovery, looking for media servers. 192.168.0.1 happens to be the fist network/host on the list. Makes sense.

[gcisko]

Because if the subnet mask values were different that would explain the log entry for the router? :confused:

It could yes.

[gcisko]

Mystery solved (I think)...

Thanks to Spanky for pointing me to Ethereal (now called Wireshark).

My router is reporting a bogus destination IP address because the HR20 is sending out a multicast discovery, looking for media servers. 192.168.0.1 happens to be the fist network/host on the list. Makes sense.

Awesome!