vgough> Now, I'm at 192.168.1.3, and the router is 192.168.1.30. It's actually
vgough> a subnet of 192.168.1.224 (with .31 as the broadcast and .0 as the net),
vgough> but I can't talk to anyone else in that net without going through the
vgough> router.
vgough>
vgough> So, the new kernel automatically adds a route for 192.168.1.31 as
vgough> direct, and doesn't seem to allow me to delete it! What is up with
vgough> that? Are we now at the point where we think the computer knows better
vgough> then the operator?
The way you have set up your subnets is not the usual way of going about
it, which is why the computer gets it "wrong"
The reason the kernel won't allow you to delete the route, is because you
need to specify the netmask with all route invocations under 2.1.XXX
Try changing your boot scripts so it runs:
ifconfig eth0 192.168.1.3 netmask 255.255.255.224 broadcast 192.168.1.31
route del -net 192.168.1.0 netmask 255.255.255.224 dev eth0
route add default netmask 0 gw 192.168.1.30 dev eth0
Of course a much better way would be to do:
ifconfig eth0 192.168.2.1 netmask 255.255.255.252 broadcast 192.168.2.3
route add default gw 192.168.2.2
and change the interface on the router you're connected to,
to 192.168.2.2/255.255.255.252
But I'm sure you have a valid reason for needing the network the way it
is.
- Matt Kemner
System Administrator
Networx Internet
Western Australia
++61 8 9345 3377
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/