On 12/22/05, martin <[EMAIL PROTECTED]> wrote: > > > --- Jason Crawford <[EMAIL PROTECTED]> wrote: > > > > > IP - 209.216.76.1 > > > Netmask - 255.255.255.252 > > > GW - 209.216.77.6 > > > > > Either a typo in your netmask, or a typo in your gateway, since your > > gateway IP does not belong to the current netmask you assigned to > > your > > external IP. I have a feeling it's a typo in the netmask as that's a > > very very small one. > > > > Jason > > > Jason. > > The figures are correct (I wondered about the unusual GW when I first > rx'd it but they said it was correct). The thing is, I've had this > connection for a couple of years and have run a number of firewalls > with no issue with these ie. Linux Router Project, Freesco and others I > have tested. It is running now with a commercial firewall with no > problems. > > Can I force it to accept the gateway IP ? > > Regards...Martin > Unless they don't follow IPv4 specs properly, with those exact numbers, none of them should work. 209.216.76.1 is nowhere near 209.216.77.6 so the netmask of 255.255.255.252 will not let you talk to 209.216.77.6 without another route. My guess, 255.255.252.0 is the netmask you want, as that would include both IPs. Or maybe you mistyped the 3rd set, and they should both be 76 or 77, although you'll still have to change the netmask to something like 255.255.255.240. Whether other OS's worked or not is irrelevant, the current WILL NOT WORK with an OS that follows the IPv4 spec PROPERLY. If your ISP is indeed handing this info to you, then they are complete morons, as it WILL NOT WORK.
Jason
