From: Max W. <dav...@fa...> - 2007-03-29 02:46:24
|
Max Waterman wrote: >> route network mask >> route 192.168.1.0 255.255.255.0 >> > So, that is identical to what I was trying, but which was failing. Of > course, now I try it, it works fine. > > "What was I doing wrong before?", I wonder, banging my head against a > wall. Curious.... Having looked at this a bit, I think I was just using a regular IP address, thinking it would ignore the bits that are masked off. For example, I was using : route 212.58.240.142 255.255.255.0 which doesn't work; but : route 212.58.240.0 255.255.255.0 does work. ..and this is fine because 'whois 212.58.240.0' says : inetnum: 212.58.240.0 - 212.58.240.255 However, when I tried that with 66.218.64.0 it worked, but 'whois 66.218.64.0' says : NetRange: 66.218.64.0 - 66.218.95.255 CIDR: 66.218.64.0/19 So, the netmask of 255.255.255.0 isn't good enough, and it should be 255.255.224.0 (19 bits from the left) The network address is thus as specified in the CIDR line. Is there a trick to converting /19 into hex/dec? It'd be nice if OpenVPN would a) allow use of /19 style netmasks, and b) mask off the irrelevant bits in the specified network (though I suspect this is due to the underlying route command). Oh well. All solved now :) Thanks all. Max. |