You don't say what it is working *with* just that it isn't working
with m0n0wall. There are many systems out there which do IP
incorrectly. I've seen windows machines figure out the correct route
even when the gateway is wrong, causing them to "mostly" work. Some
sonicwall firewall products will permit gateways to work that are on
different physical interfaces than the clients.
How it works for you is a matter for speculation. However, I bet if
you set your WAN on m0n0wall to a /24 netmask, it would work for you.
My guess is that the ISP has a big /24 available for their customers
(perhaps more than one) with a real /24 netmask on the network, and
they hand out different slices of the /24 (in your case, a /27 slice)
without doing real routing to enable those netmasks to work.
Mind you, that is just a guess.
On Mon, 18 Oct 2004 19:16:18 +0200, Peter Parnican <peter at procad dot sk> wrote:
> OOoo my god, i found at http://www.batch.com/netmask.html how works subnet
> (nothing easy!!!!)... I asked small question but answer is veeeery long...
> Now I know why should be gateway address between 188.8.131.52 and
> 184.108.40.206 but why is it working without monowall ? ...gateway is
> Ok, now i start understand what can be wrong. The gateway which give me my
> ISP isnt propably correct. (but why is my conection working without
> monowall? is it normal?)
> And next question, how you know that:
> > With the address of 220.127.116.11/27, your upstream gateway device
> > needs to be an address between 18.104.22.168 and 22.214.171.124
> > excluding 126.96.36.199.
> ISP give me 188.8.131.52
> Which math are You using? :-) (sorry but Im very newbie)
> I want know it because if i ask my ISP and he will telling somethings else i
> can disagree... but now its difficult because i dont know the correct
> settings for gateway.