Well I found one way to get around it for now =)
route del -net 192.168.0.0 netmask 255.255.255.0 dev eth0
In that case what's the point of defining eth0:1 on the 192.168 network at all?
Well I found one way to get around it for now =)
route del -net 192.168.0.0 netmask 255.255.255.0 dev eth0