>Are you using the correct address for your cable modem. Most of the
>modems I have seen use 192.168.100.1 not 192.168.0.1.
I would have a look at the arp Table...
What kind of Cable Modem is in use (Samsung, Terayon, Motorola..?)
Some Modems *must* be disconnected from the CATV to be contacted.
The cable modem IP address 192.168.100.1 is not in the same sub-net
as the user's PC. So, when trying to send to 192.168.100.1, the user
PC's IP stack will normally route the packet to the Default Gateway
address at the UBR. Since no routes exist to the private address
192.168.100.1 (and there are multiple instances of this IP address
on any one CATV segment), the UBR drops the packet.
You Could add a static Route.
From: Jonathan Karras [mailto:jkarras at karras dot net]
Sent: Sunday, March 05, 2006 2:34 AM
To: Jeppe Oland
Cc: m0n0wall at lists dot m0n0 dot ch
Subject: Re: [m0n0wall] RE: 2nd (public) IP on the WAN interface?
Your problem is interesting because I can access my Cable Modem IP
address of 192.168.100.1 from inside the LAN on my M0n0wall. I currently
have the "Block private networks" rule turned on and it works fine. I
did nothing special to get this to work.
Are you using the correct address for your cable modem. Most of the
modems I have seen use 192.168.100.1 not 192.168.0.1.
Jeppe Oland wrote:
>> I have a pretty standard network setup:
>> DSL modem/bridge <-> M0n0 <-> PC.
>> DSL modem provides a public IP address via DHCP to the M0n0
>> WAN interface.
>> On the LAN interface I used the standard 192.168.1.x range.
>> Now the issue I have is that the modem has a webserver
>> running on 192.168.0.1 where I can get connection stats....
>> But I can't get a connection to it.
>> How would I configure m0n0 to make this work?
> Also, I have tried removing the "Block private networks" checkbox in the
> configuration, but this doesn't work.
> I assume m0n0 will forward the request for 192.168.0.1 to its GW since
> not on the same subnet.
> The problem is that the IP that the modem gives out does not route back.
> I have tried adding static routes, proxy arp, and outbound NAT - all to no
> effect... What I really need is a 2nd IP on the WAN interface - but that
> isn't supported :(
> Any way to get this working?