Puzzled by modem IP address

[dave_tracey]

Thanks for the response! It just seemed odd that it didn't resolve the name. Shall I just ignore the Firewall log on the router?

[Jez]

Originally Posted by dave_tracey

Jez, your first post mentions 2 ip addresses: 10.147.xxx.xxx & 10.47.xxx.xxx. Is this correct, or a typo?

Er yes, typo I fear!

I appreciate that a router's firewall isn't all that smart, but I guess what I'm asking is whether there may be a problem in that the modem is presumably legitimately trying to talk to the router, but is being rebuffed by the firewall. I assume the answer is "no" but if that's the case, why is it trying it in the first place? (I'm thinking of an earlier thread to do with a particular brand of router being blocked for not playing ball with NTL's way of doing things, for instance?). Sorry if this is self-evident but it's all a bit of a black art to me as a broadband virgin

[BBKing]

It just seemed odd that it didn't resolve the name

Not really, it's just that it's a private address, which isn't unique on the internet so can't have a unique name. I could quite happily have 10.116.32.1 as my gateway IP here and call it BBs-Gateway, but this would mean nothing to anyone outside my private LAN.

Jez - I suggest a quick course of Robin Walker's cable broadband guide, which specifically states that you should allow your local UBR private IP and your DHCP servers through your firewall to prevent spurious attack indications.

Because your firewall is *behind* your router, the modem-to-ubr communication is unaffected. It's only router-to-ubr communication (DHCP in particular) that could be affected. Still best to allow the IP through.

[Jez]

Originally Posted by BBKing

Jez - I suggest a quick course of Robin Walker's cable broadband guide, which specifically states that you should allow your local UBR private IP and your DHCP servers through your firewall to prevent spurious attack indications. Because your firewall is *behind* your router, the modem-to-ubr communication is unaffected. It's only router-to-ubr communication (DHCP in particular) that could be affected. Still best to allow the IP through.

Thanks! I checked the relevant bit of the guide as you suggested - think I only understood one word in five but enough to see that my router's firewall is locked down too tightly ... I can turn back on the response to ICMP pings OK, but otherwise the firewall is either on or off (and Belkin's support have just confirmed this). I'm kind of reluctant to turn it off and use a software firewall on each of the PCs instead unless there's a compelling reason to do so - I take it that if things are basically working OK, then there probably isn't?

[BBKing]

If it's working, fine, but you'll have to ignore any spurious warnings that come off it. Or get a better firewall/router - mine certainly allows me to allow/deny specific ports and machines, and I think most do these days. Don't turn it off though, it's protecting you against a lot of malicious rubbish.

[dave_tracey]

Any suggestions for a better router/firewall (Needs to be 54g Wireless)?

Was thinking about getting another AP anyway, so could use my existing Belkin one as an AP only...