I want to add a permanent route.
Reading some past articles here, I am told YaST is the best way to do this.
However, after going to
NetWork Devices->Network Settings->Edit <network card>
I don’t see a menu to add a route.
How can I add a permanent route?
I have a tab Routing in .NetWork Devices->Network Settings->. Do you have set “traditional method with ifup” in the Global tab?
I have openSUSE 10.3, so it may look different in 11.n (you forgot to mention your version).
I am using OpenSuse 11. I am using the line command version of yast, running it with yast2.
This is what the Network Settings http://you-saw-it-here-first.com/d/365-1/Networksettings.JPG screen looks like:
This is what the Network Card http://you-saw-it-here-first.com/d/370-1/networkcardsetup.JPG Setup screen looks like.
I do not see a tab or entry for Route.
Hmm, strange, you seem to be missing stuff on the first screen. On my screen, there is a set of links just under the title Network Settings. They read:
Global Options => Overview Hostname/DNS Routing
As ken_yap says, I (on10.3) have this:
http://www.xs4all.nl/~hcvv/yast-network.jpg
and when I choose Routing:
http://www.xs4all.nl/~hcvv/yast-network-routing.jpg
I suppose you have a text install only or is there another reason for not using the GUI?
I’m managing my server remotely…I set it to boot into init 3.
I set up vnc but they haven’t open the ports for me yet so I use the “yast” line command.
Are you starting yast with any special parameters? I find it odd that your yast interface is so different (again I’m using Suse 11).
Hi
If your currently using ssh for remote access, install freeNX or NX
from nomachine.com (my preference) no need to worry about other ports
and it will be more secure.
–
Cheers Malcolm °¿° (Linux Counter #276890)
openSUSE 11.0 x86 Kernel 2.6.25.18-0.2-default
up 15:05, 2 users, load average: 0.23, 0.13, 0.18
GPU GeForce 6600 TE/6200 TE - Driver Version: 177.80
It looks like FreeNX and NX are part of the Suse 11 distro.
Looks cool.
I’ll install FreeNX and then download the client for Windows.
Ack! That was a disaster. Either my server is too small or my network to constricted, but after connecting with the NX client all I saw was the Suse splash screen – then it went black for 5 minutes until I killed it.
Even, worse, it became almost non responsive to a regular ssh login! And now it’s running at a 3-5 load average where as before it was almost zero! I can’t use it this way.
Any idea how to stop NX?
I set it up using these instructions:
Ok, I removed it.
Looks great though, just not right for my environment.
Hi
Try the one from nomachine .com (it’s free) I have never tried freenx
as some people (like yourself) have had issues.
–
Cheers Malcolm °¿° (Linux Counter #276890)
openSUSE 11.0 x86 Kernel 2.6.25.18-0.2-default
up 16:32, 2 users, load average: 0.13, 0.04, 0.05
GPU GeForce 6600 TE/6200 TE - Driver Version: 177.80
Ok, will do. I have a dev suse machine I can try it out on!
Back to your original problem.
First we could try to find out why YaST is presenting itself to you in quite a different way then to us. A suggestion: could you, in your terminal, type
echo $TERM
and post what the answer is? Maybe the type of character terminal influences YaST.
A second thought that came to my mind: what is the version of YaST on that system?
Second (or maybe first) we could try to circumvent YaST. After all it is only a wrapper around utilities and configuration files. There is a file /etc/sysconfig/network/routes. It should already have your default route. In my system the contents is:
default 10.0.0.138 - -
You could try to add the parameters for your other route to this and see what happens after a reboot. This file seems to be used by the script /etc/sysconfig/network/scripts/ifup-route and in that script I find hat the parameters in the file are DEST GWAY MASK IFACE TYPE IPOPTS. When this is enough information for yoou to add your route info to the file, fine. When not, pleas post back.
Hope this helps.
ivnwmail:/etc/sysconfig/network # echo $TERM
xterm
In my routes file:
ivnwmail:/etc/sysconfig/network # cat routes
default 192.168.26.1 - -
These are (some of) the routes I want, which I added but realize they will not persist until I add them to the routes file:
ivnwmail:/etc/sysconfig/network # route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.26.0 * 255.255.255.0 U 0 0 0 eth0
10.40.1.0 192.168.26.254 255.255.255.0 UG 0 0 0 eth0
loopback * 255.0.0.0 U 0 0 0 lo
default 192.168.26.1 0.0.0.0 UG 0 0 0 eth0
There is only one of them that must be added by you:
10.40.1.0 192.168.26.254 255.255.255.0 UG 0 0 0 eth0
The other ones are generated automaticaly or by what is already in the file.
So edit /etc/sysconfig/network/routes and add:
10.40.1.0 192.168.26.254 255.255.255.0 -
Reboot and see if it is there.
BTW xterm is not strange and I have no idea why YaST works different in your case.
I am installing the nomachine NX from here:
NoMachine NX - Download: NX Free Edition for Linux
But I got this error on installing the NX node. “lsof is needed”…
http://you-saw-it-here-first.com/d/373-1/nx-nomachine-error.JPG
Hi
I thought lsof was installed by default? Oh well, just zypper in lsof
sudo zypper in lsof
sudo rpm -Uhv nxclient....
sudo rpm -Uhv nxnode....
sudo rpm -Uhv nxserver....
–
Cheers Malcolm °¿° (Linux Counter #276890)
openSUSE 11.0 x86 Kernel 2.6.25.18-0.2-default
up 17:10, 2 users, load average: 0.25, 0.13, 0.06
GPU GeForce 6600 TE/6200 TE - Driver Version: 177.80
No, it is not there (! surprised !). I checked the routes file and the entry is still there, but it did not take affect after a reboot!
ivnwmail:~ # route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.26.0 * 255.255.255.0 U 0 0 0 eth0
loopback * 255.0.0.0 U 0 0 0 lo
default 192.168.26.1 0.0.0.0 UG 0 0 0 eth0
ivnwmail:~ # cat /etc/sysconfig/network/routes
default 192.168.26.1 - -
10.40.1.0 192.168.26.254 255.255.255.0 -
Hm, and no errors during boot (use dmesg)?
NX/nomachine
I got it installed on my dev Suse system and works great. Much more responsive than vnc and I can use the ssh port!
I will try this on my main system after I try it out of a while!
One thing that doesn’t seem to work is the Ctrl-Alt-F for shifting from full to windowed screen. Ctrl-Alt-M works for minimizing, but not Ctrl-Alt-F, no response. They say it’s functional in NX 3.x and not in 2.x – but I’m using the 3.x client.