I often hear friends tell me not to use PPPoE to connect to the Internet in openSUSE. Don’t be sneering. That this is true, because I do not know how to use the graphical interface to connect to the Internet. however, when i use of more graphics interface on openSUSE, this problem will no longer haunt me, so i want to summarize how to connect to internet using pppoe as below. I wish this information will help you to fix connecting problem of PPPoE.
===For KDE Environment===
1. Do you have below packages?
If the answer is no please download and install these packages.
kinternet-0.75-253.1.i586.rpm
smpppd-1.59_SVN16-10.1.i586.rpm
wvdial-1.60-31.1.i586.rpm
wvstreams-4.4.1-32.1.i586.rpm
2. Now, you can see the kinternet option from internet –> Dail-Up menu
3. You will receive an error message after click kinternet option.
Please don’t worry
4. Open your console and then follow below commands.
#service smppd start
#chkconfig smpppd on
#chkconfig –list smpppd —> the smpppd service will start on runlevel 2,3,5
5. Please click kinternet and then choice configure with YaST2 option.
6. Choice DSL Connection option when display Network Configuration window
7. It’s Initializing DSL Configuration.
8. Please click Add option in this window.
9. Please don’t modify any setting and click Next button if your PPP Mode is PPPoE.
10. Select your ISP in this window.
Please click New button if your ISP not in this list.
11. Fill your ISP information in Provider Parameters and then click Next button.
12. You only need to click Next button.
13. You will see dsl0 device in DSL Devices list.
14. You can also see your Provider information in Providers list.
Please click Finish button.
15. It’s saving DSL Configuration.
The pppoe setting have been finished, please reboot your machine.
16. You can see the Dial-in option show in kinternet tool after reboot.
Enjoy network now 
===For Gnome Environment===
1. Please open your gnome menu and then select YaST
2. Please search this keyword network.
You will see the Network Settings option and then click it.
3. You need to change the Network Setup Method if you prefer to use the gui rather than use command.
4. You can see the network icon in below panel after click Finish button.
Now, please click Edit Connections.
5. It will pop up a Network Connections window, please select DSL and then click Add button.
6. Fill the username and password which provided by your ISP in DSL option.
7. DSL Connection 1 can be shown in DSL option.
Please click Close button.
8. You shall click left button of mouse and then choice DSL connection 1.
9. It will pop up a DSL authentication window after step 8, please key in your password here.
10. You will see the connection status in network icon.
11. The ppp0 device can be shown after you type ifconfig command.
Attention:
1. If the SuSEfirewall2 has enabled, please note the following two diagrams.
2. Please also checks your username and password provided by ISP which recorded in pap-secrets and chap-secrets files.
July 7th, 2008 at 5:03 pm
Does this work with Gnome? I don’t really want to download all the dependencies for KDE. I am using openSUSE 11, and for the life of me can’t figure out how to set up pppoe for connection with my wireless to my work connection, which requires a username and password. Under Ubuntu I used to use pppoeconf which worked perfectly….. Any advice?
July 7th, 2008 at 6:29 pm
sorry, it’s for kde environment.
you can download gnome-ppp and then install it for gnome environment.
here is link address;
http://www.gnomefiles.org/download.php?soft_id=41&where=http%3A%2F%2Fftp.debian.org%2Fdebian%2Fpool%2Fmain%2Fg%2Fgnome-ppp%2Fgnome-ppp_0.3.23.orig.tar.gz
July 7th, 2008 at 8:24 pm
Cheers for that. Now just have to figure out how to install it. I did some research and it seems really hard to install. I wonder why the app. is not included in any of the depositories… But thanks for the file anyway!
July 7th, 2008 at 10:06 pm
I always use kde environment until now.
July 7th, 2008 at 11:38 pm
Hello. After this steps(in instructions) in kinternet’s log l see next:
Authorization CHAP secrets failed
Authorization failed.
But login and password correct!!! Maby i need set perrmisions on any config-files? Please help me! Thanks. Sory for my bad English.
July 7th, 2008 at 11:39 pm
@tora:
I have updated my post of PPPoE.
It maybe fulfill your requirement.
If you still have any question,please kindly leave message to me.
July 8th, 2008 at 12:02 am
@shurik:
Please make sure your username and password have been include /etc/ppp/chap-secrets first.
Below is example:
# INBOUND CONNECTIONS
#client hostname
866xxxx@hinet.net@hinet * aaaaaa *
July 8th, 2008 at 12:03 am
please read my first post at: Today at 11:38 pm
Thanks.
July 8th, 2008 at 12:31 am
Do you enter this information in /etc/ppp/chap-secrets or Gnome?
July 8th, 2008 at 12:48 am
@shurik:
/etc/ppp/chap-secrets and /etc/ppp/ppp-secrets both contain my username and password.
I don’t know which is the security of your ISP was chosen.
Please check these files and permissions because i login kde as root permission.
My ISP use ppp security as below detail message.
Jul 8 00:46:25 radius pppd[3959]: Plugin rp-pppoe.so loaded.
Jul 8 00:46:25 radius pppd[3959]: RP-PPPoE plugin version 3.3 compiled against pppd 2.4.4
Jul 8 00:46:25 radius pppd[3959]: Plugin passwordfd.so loaded.
Jul 8 00:46:25 radius pppd[3959]: pppd 2.4.4 started by root, uid 0
Jul 8 00:46:25 radius pppd[3959]: PPP session is 3709
Jul 8 00:46:25 radius kernel: ppp0 renamed to dsl0
Jul 8 00:46:25 radius pppd[3959]: Renamed interface ppp0 to dsl0
Jul 8 00:46:25 radius pppd[3959]: Using interface dsl0
Jul 8 00:46:25 radius pppd[3959]: Connect: dsl0 eth1
Jul 8 00:46:25 radius pppd[3959]: PAP authentication succeeded
Jul 8 00:46:25 radius pppd[3959]: peer from calling number 00:90:1A:40:10:8D authorized
Jul 8 00:46:29 radius pppd[3959]: replacing old default route to eth1 [192.168.1.254]
Jul 8 00:46:29 radius pppd[3959]: local IP address 61.231.24.232
Jul 8 00:46:29 radius pppd[3959]: remote IP address 61.231.24.254
Jul 8 00:46:29 radius pppd[3959]: primary DNS address 168.95.192.1
Jul 8 00:46:29 radius pppd[3959]: secondary DNS address 168.95.1.1
Jul 8 00:46:29 radius modify_resolvconf: Service pppd modified /etc/resolv.conf. See info block in this file
Jul 8 00:46:29 radius pppd[3959]: Script /etc/ppp/ip-up finished (pid 3965), status = 0×0
Jul 8 00:46:34 radius poll.tcpip: no server configured
July 8th, 2008 at 2:32 am
Please post your /etc/ppp/chap-secrets and /etc/ppp/ppp-secrets, because i don’t known stored format of login and password in this files. I use KDE not Gnome, I was mistaken in my last topic. Thanks!
July 8th, 2008 at 9:16 am
@shurik:
You only need to focus on “INBOUND CONNECTIONS” that will show your username and password of ISP.
/etc/ppp/chap-secrets
# Secrets for authentication using CHAP
# client server secret IP addresses
# OUTBOUND CONNECTIONS
# Here you should add your PPP Login and PPP password to connect to your
# provider via pap. The * means that the entry(login and passoword may be
# used for ANY host you connect to.
# Thus you do not have to worry about the foreign machine name. Just
# replace password with your password.
#hostname * password
# PREDIFINED CONNECTIONS
# These are user and password entries for publically accessible call-by-call
# Internet providers in Germany. If they confict with your config, remove them.
# READ_IN_CALLBYCALL_SECRETS
# INBOUND CONNECTIONS
#client hostname 192.168.1.1
866xxxx@hinet.net@hinet * aaaaaa *
/etc/pap-secrets
# Secrets for authentication using PAP
# client server secret IP addresses
# OUTBOUND CONNECTIONS
# Here you should add your PPP Login and PPP password to connect to your
# provider via pap. The * means that the entry(login and passoword may be
# used for ANY host you connect to.
# Thus you do not have to worry about the foreign machine name. Just
# replace password with your password.
#hostname * password
# PREDIFINED CONNECTIONS
# These are user and password entries for publically accessible call-by-call
# Internet providers in Germany. If they confict with your config, remove them.
# READ_IN_CALLBYCALL_SECRETS
# INBOUND CONNECTIONS
#client hostname 192.168.1.1
866xxxx@hinet.net@hinet * aaaaaa *
# If you add “auth login -chap +pap” to /etc/mgetty+sendfax/login.config,
# all users in /etc/passwd can use their password for pap-authentication.
#
# Every regular user can use PPP and has to use passwords from /etc/passwd
#* hostname “”
# UserIDs that cannot use PPP at all. Check your /etc/passwd and add any
# other accounts that should not be able to use pppd! Replace hostname
# with your local hostname.
#guest hostname “*” -
#master hostname “*” -
#root hostname “*” -
#support hostname “*” -
#stats hostname “*” -
July 8th, 2008 at 3:40 pm
@Bryan:
Hello Bryan! Thanks so much. It was confusing. of course, now it all makes sense. I will try this at work tomorrow and see if it will connect me through the wireless. It is funny how a wireless pppoe connection is called DSL in Gnome. No wonder I couldn’t think of those settings! Will let you know how it goes. Cheers for your help!
July 8th, 2008 at 4:02 pm
Hi again.. it seems this will only work with a wired DSL connection, via the Gnome settings as described in this guide. (The option of dialing the DSL is blanked out in Suse 11) Anybody know why? Oh for the simplicity of pppoeconf like in Ubuntu…..
July 8th, 2008 at 6:05 pm
@tora:
I don’t know you are connecting via wireless.
You can install rp-pppoe-3.8-107.1.i586.rpm that can be found from http://software.opensuse.org
You shall set your username and password via pppoe-setup command after install.
The configuration file can be found in here
/etc/ppp/pppoe.conf
pppoe-start –> dial up command
pppoe-stop –> hang up command
pppoe-status –> status command
PS: I have been tried it and working now.
Don’t forget to change Network Setup Method from NetworkManager to Traditional Method with ifup.
August 4th, 2008 at 5:39 pm
I did all the steps, but i still have problem…
it can’t connect!
what should i do now?
August 4th, 2008 at 6:16 pm
i also check /etc/ppp/chap-secrets and there is no username and password
the last line is
#client hostname an.ip.address.
August 4th, 2008 at 10:41 pm
@Omid:
It will help for analyze if you can provide more information.
#ifconfig
#dmesg
#cat /var/log/message
August 5th, 2008 at 11:52 am
@Omid:
Please also make sure your username and password can be found on /etc/ppp/pap-secrets and /etc/ppp/chap-secrets files.
September 16th, 2008 at 5:07 pm
Hi
you Can Help Me?
Im Will config corecess 3112 ug and openSUSE 11.0
but …
Yast cannot view My Connection (tap0)
September 17th, 2008 at 12:32 am
@Ahmad: Do yo mean DSL Device that didn’t show anything or ….?
Can you give me more detail information?
December 2nd, 2008 at 9:15 pm
Hi, I use Opensuse 11 with KDE. I have tried to follow the intructions above. I easyly get to this point: kinternet-> configure with Yast2. Then I click in DSL connection, then in add, and here as default I find PPP over ATM instead of PPPoE as in the tutorial. Ok, a change it to PPPoE and then click next. At this point a get this Error message: “UI Syntax Error. Invalid arguments for the SelectionBox widget.Check the log file!”
I would appreciate any help.
December 3rd, 2008 at 3:06 pm
@Toopho: Sorry, i don’t have PPPoA line for test.
Can you output log file for analyze?
December 4th, 2008 at 4:08 am
Sorry, I am a bit lost. I don’t know where I can find the log file. Please tell me how I can do that.
December 4th, 2008 at 5:26 am
SuSE Meta pppd (smpppd-ifcfg), Version 1.59_SVN16 on linux-4zpk.
Status is: disconnected
trying to connect to smpppd
connect to smpppd
Status is: disconnected
Status is: lurking
pppd[0]: Plugin passwordfd.so loaded.
pppd[0]: Renamed interface ppp0 to dsl0
pppd[0]: Using interface dsl0
Status is: lurking
pppd[0]: replacing old default route to eth0 [192.168.0.1]
pppd[0]: local IP address 10.64.64.64
pppd[0]: remote IP address 10.112.112.112
December 4th, 2008 at 9:26 am
@Toopho:
1. What’s dsl line you using?
PPPoE or PPPoA
You need to fill VCI/VPI value if you are using PPPoA.
2. You can see the following line of your log that mean connection has been connected.
Can you ping to 10.112.112.112?
pppd[0]: replacing old default route to eth0 [192.168.0.1]
pppd[0]: local IP address 10.64.64.64
pppd[0]: remote IP address 10.112.112.112
December 5th, 2008 at 5:32 am
I am so sorry bryan. I posted a log file of a interet provider I made up choosing PPP over ATM instead. If I ping to 10.112.112.112 it doesnt give an error message but seems stuck. In my internet provider manual, section Machintoch, it says I should select PPPoE mode. Following is the log for the internet provider made according to the instructions:
SuSE Meta pppd (smpppd-ifcfg), Version 1.59_SVN16 on linux-4zpk.
Status is: error
trying to connect to smpppd
connect to smpppd
Status is: error
Status is: connecting
pppd[0]: Plugin passwordfd.so loaded.
pppd[0]: Renamed interface ppp0 to dsl0
pppd[0]: Using interface dsl0
Status is: connecting
pppd[0]: Connect: dsl0 /dev/pts/1
December 5th, 2008 at 9:46 am
@toopho:
You should be PPPoA mode, please fill the VCI/VPI value in DSL Configuration.
December 7th, 2008 at 1:22 am
I cant post the log file.
December 7th, 2008 at 2:54 am
I don’t know what I am doing wrong but I can’t post in this blog what I want.
December 7th, 2008 at 3:07 am
Following is the log file from when tried to ping to 10.112.112.112
SuSE Meta pppd (smpppd-ifcfg), Version 1.59_SVN16 on linux-4zpk.
Status is: disconnected
trying to connect to smpppd
connect to smpppd
Status is: disconnected
Status is: lurking
pppd[0]: Plugin passwordfd.so loaded.
pppd[0]: Renamed interface ppp0 to dsl0
pppd[0]: Using interface dsl0
Status is: lurking
pppd[0]: replacing old default route to eth0 [192.168.0.1]
pppd[0]: local IP address 10.64.64.64
pppd[0]: remote IP address 10.112.112.112
pppd[0]: Starting link
Establishing connection due to activity.
Status is: connecting
pppd[0]: Serial connection established.
pppd[0]: Connect: dsl0 /dev/pts/3
pppd[0]: LCP: timeout sending Config-Requests
pppd[0]: Connection terminated.
pppd[0]: Starting link
Establishing connection due to activity.
Status is: connecting
pppd[0]: Serial connection established.
pppd[0]: Connect: dsl0 /dev/pts/4
pppd[0]: anon warn[open_inetsock:pptp_callmgr.c:326]: connect: Connection timed out
pppd[0]: anon fatal[callmgr_main:pptp_callmgr.c:124]: Could not open control connection to 10.0.0.138
pppd[0]: anon fatal[open_callmgr:pptp.c:439]: Call manager exited with error 256
pppd[0]: Script /usr/sbin/pptp 10.0.0.138 –nolaunchpppd finished (pid 3051), status = 0×1
pppd[0]: LCP: timeout sending Config-Requests
pppd[0]: Connection terminated.
I also would like to show you what it is said about OpenSuSE in my provider’s web page, but I can’t post the link here.
December 8th, 2008 at 5:47 pm
@toopho:
Can you let me know which mode are you using? PPPoA or PPPoE?
December 9th, 2008 at 2:04 am
Following is a we translation of what is said in my provider’s web page:
Dialling under Linux and Unix
At the moment we can offer to you no direct support by the installation of your Alice Anschlusses with Linux-or Unix-been based operating systems.
At the market there are many different, constantly changing Linux distributions which partly very deviating settings require.
Special Alice Software is not necessary for the use of your DSL connection. As a rule the distributions offer suitable easy configuration assistants DSL. Please, find out in addition in the operating instructions or on the on-line help sides of your operating system manufacturer.
Under Suse Linux from version 7.3, for example, you configure the ADSL access quite comfortably with the provided programme YaST.
To the equipment you need Login and password (access data) which you find in the welcome writing which you have received after your registration from Alice.
The following settings are possibly necessary:
1- A PPPoE driver must be installed
2- The MTU value of the operating system must be put on 1492.
3- DNA server:
name1: 213.191.74.18
name2: 213.191.74.19
name3: 213.191.92.87
name4: 213.191.92.86
name5: 213.191.74.11
name6: 213.191.92.84
name7: 213.191.74.12
name8: 213.191.92.82
Please, use always the pairs name1 / name3, name2 / name4, name5 / name7 and name6 / name8.
4- Authentication method: Chap
December 9th, 2008 at 2:30 am
I believe my DSL is of the PPPoE type. My provider only mentiones PPPoE.
December 9th, 2008 at 2:35 am
I believe my DSL is of the PPPoE type. Only PPPoE is mentioned by provider.
December 9th, 2008 at 9:17 am
@toopho:
Thank you for post provider message
1. Please modify /etc/resolv.conf as following DNS records.
name1: 213.191.74.18
name2: 213.191.74.19
name3: 213.191.92.87
2. Please also checks your username and password provided by ISP and then fill in /etc/ppp/chap-secrets files.
3. You should try to follow my steps to configure again.
December 10th, 2008 at 4:21 am
I am glad you said that.
Here is the file chap-secrets as found in OpenSuSE11:
# Secrets for authentication using CHAP
# client server secret IP addresses
# OUTBOUND CONNECTIONS
# Here you should add your PPP Login and PPP password to connect to your
# provider via pap. The * means that the entry(login and passoword may be
# used for ANY host you connect to.
# Thus you do not have to worry about the foreign machine name. Just
# replace password with your password.
#hostname * password
# PREDIFINED CONNECTIONS
# These are user and password entries for publically accessible call-by-call
# Internet providers in Germany. If they confict with your config, remove them.
# READ_IN_CALLBYCALL_SECRETS
# INBOUND CONNECTIONS
#client hostname 192.168.1.1
I don’t understand it wery well. Which line should I modify and how? I already tried changing the word password by “my own password” in lines 9 and 17 after uncommenting them by removing the #symbol.
December 10th, 2008 at 9:04 am
@toopho:
The chap-secrets file should look like last line of the following content:
# Secrets for authentication using CHAP
# client server secret IP addresses
# OUTBOUND CONNECTIONS
# Here you should add your PPP Login and PPP password to connect to your
# provider via pap. The * means that the entry(login and passoword may be
# used for ANY host you connect to.
# Thus you do not have to worry about the foreign machine name. Just
# replace password with your password.
#hostname * password
# PREDIFINED CONNECTIONS
# These are user and password entries for publically accessible call-by-call
# Internet providers in Germany. If they confict with your config, remove them.
# READ_IN_CALLBYCALL_SECRETS
# INBOUND CONNECTIONS
#client hostname
yourusername * yourpassword
December 10th, 2008 at 9:31 pm
After making this changes I went through your tutorial and still got the same error message I first posted. This is the log file now :
SuSE Meta pppd (smpppd-ifcfg), Version 1.59_SVN16 on linux-4zpk.
Status is: disconnected
trying to connect to smpppd
connect to smpppd
Status is: disconnected
Status is: connecting
pppd[0]: Plugin passwordfd.so loaded.
pppd[0]: Renamed interface ppp0 to dsl0
pppd[0]: Using interface dsl0
Status is: connecting
pppd[0]: Connect: dsl0 /dev/pts/1
pppd[0]: LCP: timeout sending Config-Requests
pppd[0]: Connection terminated.
pppd[0]: Modem hangup
Status is: disconnected
pppd[0] died: A modem hung up the phone (exit code 16)
December 11th, 2008 at 3:14 pm
@toopho:
Can you use the following command to check interface?
# ifconfig -a
PPPoA don’t need to choose interface, but PPPoE need to do it, so i want to know how many interface in your machine now.
December 11th, 2008 at 9:19 pm
numberone@linux-4zpk:~> ifconfig -a
bash: ifconfig: command not found
numberone@linux-4zpk:~> su
Password:
su: incorrect password
numberone@linux-4zpk:~> sudo ifconfig -a
root’s password:
sudo: ifconfig: command not found
numberone@linux-4zpk:~> #ifconfig -a
numberone@linux-4zpk:~> # ifconfig -a
numberone@linux-4zpk:~> ifconfig -a
bash: ifconfig: command not found
numberone@linux-4zpk:~> ifconfig -a
bash: ifconfig: command not found
I have OpenSuSE 11.
December 11th, 2008 at 10:42 pm
@toopho:
Please use another command as below:
$ su -
$ Password:
You will change environment to root.
# ifconfig -a
December 12th, 2008 at 3:38 am
File: *manpages*, Node: ifconfig, Up: (dir)
IFCONFIG(8) Linux Programmer’s Manual IFCONFIG(8)
NAME
ifconfig – configure a network interface
SYNOPSIS
ifconfig [interface]
ifconfig interface [aftype] options | address …
DESCRIPTION
Ifconfig is used to configure the kernel-resident network interfaces.
It is used at boot time to set up interfaces as necessary. After that,
it is usually only needed when debugging or when system tuning is
needed.
WARNING: Ifconfig is obsolete on system with Linux kernel newer than
2.0. On this system you should use ip. See the ip manual page for
details
If no arguments are given, ifconfig displays the status of the cur-
rently active interfaces. If a single interface argument is given, it
displays the status of the given interface only; if a single -a argu-
ment is given, it displays the status of all interfaces, even those
that are down. Otherwise, it configures an interface.
(…)
Welcome to Info version 4.11. Type ? for help, m for menu item.
I found this warning message and I am puzzled.
December 15th, 2008 at 11:10 am
@toopho:
You don’t need to man ifconfig command.
You can see the following message (password incorrect).
numberone@linux-4zpk:~> su
Password:
su: incorrect password
Please type the correct password for change to root permission, you will use ifconfig command.
December 16th, 2008 at 3:48 am
Sorry it took so long…
numberone@linux-4zpk:~> su
Password:
linux-4zpk:/home/numberone # ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:0B:CD:36:82:6A
inet addr:192.168.0.102 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::20b:cdff:fe36:826a/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:90 errors:0 dropped:0 overruns:0 frame:0
TX packets:134 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:12808 (12.5 Kb) TX bytes:13718 (13.3 Kb)
Interrupt:10 Base address:0×8000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:42 errors:0 dropped:0 overruns:0 frame:0
TX packets:42 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2708 (2.6 Kb) TX bytes:2708 (2.6 Kb)
linux-4zpk:/home/numberone #
December 16th, 2008 at 9:20 am
@toopho:
So, you are using eth0 to connect to Internet.
Can you check step 9 in my tutorial.
PPP Mode:
PPP Over Ethernet
Ethernet Card:
Network Card -192.168.0.102
Activate device:
Manually
X Enable Device Control ….
December 16th, 2008 at 8:02 pm
When I get to step 9 in the tutorial, I read “PPP Mode: PPP over ATM”, so I change it to PPPoE. In the Ethernet Card section I can read “Unknown device. Network card – DHCP address”. I have tried to change this but I get lost, I don’t know how to do it. “Activate device” is shown as “manually” by default.
December 16th, 2008 at 10:02 pm
@toopho:
It look like driver issue of Ethernet Card from your message.
“Unknown device. Network card – DHCP address”
Please download Ethernet card driver and then install it first.
January 21st, 2009 at 2:04 am
Where can i download these:
kinternet-0.75-253.1.i586.rpm
smpppd-1.59_SVN16-10.1.i586.rpm
wvdial-1.60-31.1.i586.rpm
wvstreams-4.4.1-32.1.i586.rpm
It doesn’t have a link.
tnx!!
January 21st, 2009 at 8:55 am
@megaera:
You can find out these packages from the following address.
http://software.opensuse.org/search
February 9th, 2009 at 11:34 pm
@tora:
I have the same problem with wireless and it is true that with Ubuntu and Mint it is quite easy.
Have you sucseeded to solwe this issue?
September 23rd, 2009 at 2:27 am
This works perfectly on SUSE 11.1 GNOME. Excellent clear cut solution.
Thanks a lot.