|
||||||
| Forums FAQ | Members List | Search | Today's Posts | Mark Forums Read |
| Network/Internet Questions about internet applications, network configuration, usage (SAMBA, network printing, NFS) |
![]() |
|
|
LinkBack | Thread Tools | Display Modes |
|
|||
|
I replaced an old Red Hat bind/router box with suse 11.0 (easy way to upgrade the bind server) and now I'm wrestling with the routing. I miss being able to manipulate the routing tables from the cli. Anyhow, is there a limit on the # of routes? I have about 80 defined in the yast list, but some refuse to show up in the kernel routing table (route -n) and I simply can't see a reason why. The gateways are reachable, and they are routing internally.
|
|
|||
|
well, resolve.conf defines nameserver definitions. /etc/sysconfig/network contains a file called route-list and one called routes. route-list contains 84 lines, routes contains 72. I think yast builds the kernel route list (routes) from the yast route definitions (route-list) but doesn't squawk about any problems it encounters. unfortunately, I was forced into putting the suse box into the live network and have to be careful with modifications. Anybody know if there is another distro better suited for this type of work?
|
![]() |
| Bookmarks |
| Thread Tools | |
| Display Modes | |
|
|