Developer Forum

My (Windows) subnet can ping the router and vv but can't see the Internet.
The router sees the Internet just fine.

Does Comcast require being able to broadcast messages to the usersusing UDP
before allowing connection?

I've got the account up and running on a Linux box connected to the cable
modem to Comcast. I have a Windows box connected to the Linux box, using a
192.168.1.0 subnet. I can ping my Window box from Linux and vice versa, I
can ping the Linux outgoing ethernet card (24.131.186.252)o from Windows,
but cannot connect from Windows to the Internet.

My firewall is not blocking the subnet - at least there are no log entries.
But it does block incoming and outgoing broadcast messages
(255.255.255.255). In particular it is blocking broadcasts from
10.222.160.1 and TCP messages from Comcast's 24.131.186.253 to my Comcast
interface card 24.131.186.252.

Would that explain why I can't connect from the Windows box? Any clues on
how to fix it? My firewall GUI doesn't address either of these...

TIA, Andy

Get a DSL/Cable router. You have overly convoluted your SOHO LAN. As always, I suggest the
Linksys BEFSR41.

Dave



| My (Windows) subnet can ping the router and vv but can't see the Internet.
| The router sees the Internet just fine.
|
| Does Comcast require being able to broadcast messages to the usersusing UDP
| before allowing connection?
|
| I've got the account up and running on a Linux box connected to the cable
| modem to Comcast. I have a Windows box connected to the Linux box, using a
| 192.168.1.0 subnet. I can ping my Window box from Linux and vice versa, I
| can ping the Linux outgoing ethernet card (24.131.186.252)o from Windows,
| but cannot connect from Windows to the Internet.
|
| My firewall is not blocking the subnet - at least there are no log entries.
| But it does block incoming and outgoing broadcast messages
| (255.255.255.255). In particular it is blocking broadcasts from
| 10.222.160.1 and TCP messages from Comcast's 24.131.186.253 to my Comcast
| interface card 24.131.186.252.
|
| Would that explain why I can't connect from the Windows box? Any clues on
| how to fix it? My firewall GUI doesn't address either of these...
|
| TIA, Andy

Thanks I'd love to.

Problem is, the "Windows box" is a virtual machine running on top of Linux.
So the Linux *has to be the router.

It's Win4Lin.

So, do they need to be able to broadcast for me to connect?

Cheers, Andy

> Problem is, the "Windows box" is a virtual machine running on top of
Linux.

No Wonder!

using win4Lin or something like that? If so, you may need to use a
virtual interface [mapped to ETHx].



yea, another windows goof-up. lol




--



"Windows: In a world without fences, who needs gates?"

Thanks. Win4Lin sent me a beta IP masquerading routine. It creates a dummy
ethx which responds to dhcp or static IP, although apparently the
masquerading part doesn't work.

But I solved the problem; got a router and put it between the cable modem
and Linux, set the Linux NIC to dhcp. So we can all ping and dance
together... :-)

Actually, it is rather a cool little box: Netgear 802.11g combination
router, hub, and WiFi access point for about $150... :-)

So we are CONNECTED...

Cheers, Andy