The only place I found so far to assign routes to specific interfaces is
in tcpcon, which does not 'stick' after reboot. Is there a better
place/file/submenu to set these things at?

This is why I ask:

I have a dual homed setup (internal and internet/external). I have a
router on the same segment/subnet as the internet interface, and that's
my default route.
ip/net: 192.192.192.67/24
gw: 192.192.192.1 on the external interface <--that's also my default
route

Inside I just have a private network, but i also have a lot of other
vlans in there, so to get to all of them, all i need to do is to point
at the .1 on its subnet.
internal ip: 172.17.241.12/24
static route: for 172.17.0.0/16 go to 172.17.241.1 on the internal
interface

So normally (I have a bunch of other computers, linux/bsd/windows set up
the same way and they work fine) all I need to say something like:
route add -net 172.17.0.0 netmask 255.255.0.0 gw 172.17.241.1 eth1

The real problem is that I start pinging around, end everything works
except one thing: I cannot ping things on other internal vlans, it
behaves like it completely ignores the 172.17/16 -> 172.17.241.1 route.
I used IPTRACE and I found out that when i try to get to anything on the
other internal vlans, the packets try to originate from the external
interface (follow the default route), completely ignoring my settings of
assgning routes to interfaces. I changed the interface number on the
route in question, just to see if that changes anything, and it doesn't.
Why is Novell ignoring such important settings, and how do I make them
permanent? Is there a commandline route command? Maybe this way I'd be
able to do it all and not be ignored.

Hope that's enough information, if you need anything else, ask me.
thanks,
Marcin Pohl