Hello
In the old trinity 3.5 series (at least for Kubuntu 10.04) the config file for knetworkmanager was in ./trinity/share/conf
However I can't file that file or anything similar in the trinity 14.X series (on Kununtu 14.04).
Anybody has an idea?
thanks
Uwe Brauer
On Sunday 03 July 2016 09:25:49 Uwe Brauer wrote:
Hello
In the old trinity 3.5 series (at least for Kubuntu 10.04) the config file for knetworkmanager was in ./trinity/share/conf
However I can't file that file or anything similar in the trinity 14.X series (on Kununtu 14.04).
Anybody has an idea?
thanks
Uwe Brauer
Hello Uwe,
You will find everything you want in "/etc/NetworkManager/" There is the main file "NetworkManager.conf" and the connection folder "/etc/NetworkManager/system-connections/" that will contain a conf file for every network connection.
I hope it will help you.
Dobigeon.
On Sunday 03 July 2016 09:25:49 Uwe Brauer wrote:
Hello Uwe,
You will find everything you want in "/etc/NetworkManager/" There is the main file "NetworkManager.conf" and the connection folder "/etc/NetworkManager/system-connections/" that will contain a conf file for every network connection.
I hope it will help you.
Thanks, but no, this is not the file where all the passwords and configurations of wifi networks are saved. I was wondering that I should have write access to a file which dwells in /etc/NetworkManager
Uwe
Uwe Brauer wrote:
On Sunday 03 July 2016 09:25:49 Uwe Brauer wrote:
Hello Uwe,
You will find everything you want in "/etc/NetworkManager/" There is the main file "NetworkManager.conf" and the connection folder "/etc/NetworkManager/system-connections/" that will contain a conf file for every network connection.
I hope it will help you.
Thanks, but no, this is not the file where all the passwords and configurations of wifi networks are saved. I was wondering that I should have write access to a file which dwells in /etc/NetworkManager
Uwe
The passwords are stored in the k/tdewallet
regards
> Uwe Brauer wrote:
> The passwords are stored in the k/tdewallet
Sorry what is k/ that supposed to be, for me at least not in .trinity.
When you say password do you mean all the parameters which are needed for a wifi network (in kde 3.5.X this was as I said all in the file knetworkmanagerrc) now in trinity 14.X I am puzzled
Uwe Brauer wrote:
Sorry what is k/ that supposed to be, for me at least not in .trinity.
k for kdewallet
When you say password do you mean all the parameters which are needed for a wifi network (in kde 3.5.X this was as I said all in the file knetworkmanagerrc) now in trinity 14.X I am puzzled
When I say passwords I mean exactly what I say - passwords. I've had this stored in the wallet - perhaps there is an option somewhere to use the wallet - not sure. I prefer the wallet anyway.
regards
On Sunday 03 July 2016 15:04:34 deloptes wrote:
Uwe Brauer wrote:
Sorry what is k/ that supposed to be, for me at least not in .trinity.
k for kdewallet
When you say password do you mean all the parameters which are needed for a wifi network (in kde 3.5.X this was as I said all in the file knetworkmanagerrc) now in trinity 14.X I am puzzled
When I say passwords I mean exactly what I say - passwords. I've had this stored in the wallet - perhaps there is an option somewhere to use the wallet - not sure. I prefer the wallet anyway.
regards
I can argue both sides of this. If all pw's are stored in tde-wallet, it is handier than bottled beer or sliced bread. OTOH, anybody who can crack the tdewallet encoding would also own the whole machine, and thats scary, so if pw's are kept on the machine, I'd feel a heck of a lot more comfortable if a different storage method was used per pw stored so the attacker only gets one user per hack it may have taken days to get while staying lost in the other noise of the rejections you will see if you tail the iptables logs in your router. I used to watch that for entertainment, until I figured out that the entertainment was equivalent to watching enamel paint dry. dd-wrt was having none of that.
Cheers, Gene Heskett
On Sunday 03 July 2016 14:26:10 Uwe Brauer wrote:
> Uwe Brauer wrote: > > The passwords are stored in the k/tdewalletSorry what is k/ that supposed to be, for me at least not in .trinity.
That is meant to show that its the same as kde-, but is tde- instead if you have most of trinity installed. And lots of bugs in the kde version, have been fixed in the tde version. So the files aren't exactly the same if compared. The diffs are bug fixes for the most part. So thank a tde developer for that.
[...]
Cheers, Gene Heskett
On Sunday 03 July 2016 14:26:10 Uwe Brauer wrote: That is meant to show that its the same as kde-, but is tde- instead if you have most of trinity installed. And lots of bugs in the kde version, have been fixed in the tde version. So the files aren't exactly the same if compared. The diffs are bug fixes for the most part. So thank a tde developer for that.
Well may be, but I insist in my .trinity tree there is no file which contains the wifi configuration. I made a grep for example for the wifi network which I am connected to. Greping the name for example No result.
[...]
Cheers, Gene Heskett
On Sunday 03 July 2016 20:40:20 Uwe Brauer wrote:
On Sunday 03 July 2016 14:26:10 Uwe Brauer wrote: That is meant to show that its the same as kde-, but is tde- instead if you have most of trinity installed. And lots of bugs in the kde version, have been fixed in the tde version. So the files aren't exactly the same if compared. The diffs are bug fixes for the most part. So thank a tde developer for that.
Well may be, but I insist in my .trinity tree there is no file which contains the wifi configuration. I made a grep for example for the wifi network which I am connected to. Greping the name for example No result.
If it is connecting,it surely must be stored somewhere. I had difficulty finding some of my network stuff because I was grepping for the wrong thing. Grep is very fussy!!!
Lisi
On Sunday 03 July 2016 15:40:20 Uwe Brauer wrote:
On Sunday 03 July 2016 14:26:10 Uwe Brauer wrote: That is meant to show that its the same as kde-, but is tde- instead if you have most of trinity installed. And lots of bugs in the kde version, have been fixed in the tde version. So the files aren't exactly the same if compared. The diffs are bug fixes for the most part. So thank a tde developer for that.
Well may be, but I insist in my .trinity tree there is no file which contains the wifi configuration. I made a grep for example for the wifi network which I am connected to. Greping the name for example No result.
[...]
Cheers, Gene Heskett
I seem to be in a position of a lack of ammo. My local network is all fixed addressing via a common /etc/hosts file, with the individual machine being located in that file by its name.
So the bottom line is that the name of the machine, and its address are in the /etc/hosts file. And the rest of it, includeing the duplicated address, is in /etc/networking/interfaces. With an /etc/resolv.conf set to hosts,dns, any name that is not in the hosts file, that query is sent to the gateway device, which in this case is running a small cacheing nameserver, and it that doesn't hit, its sent on to my ISP's dns servers. All transparent to me.
But, anything that looks or acts like network manager has been removed from my system. So any comments I might make about NM should be taken as the best swag* I can make based on 18 years of running linux.
*swag, a Scientific Wild Ass Guess.
Cheers, Gene Heskett
Gene Heskett wrote:
But, anything that looks or acts like network manager has been removed from my system. So any comments I might make about NM should be taken as the best swag* I can make based on 18 years of running linux.
NM is useful on notebooks that change locations, interfaces etc. If one uses a home network with many computers I would advise setting up proper dhcp and perhaps name server. You don't have to take care of each machines own files. But this is usually an individual preference.
regards
On Monday 04 July 2016 03:46:38 deloptes wrote:
Gene Heskett wrote:
But, anything that looks or acts like network manager has been removed from my system. So any comments I might make about NM should be taken as the best swag* I can make based on 18 years of running linux.
NM is useful on notebooks that change locations, interfaces etc. If one uses a home network with many computers I would advise setting up proper dhcp and perhaps name server. You don't have to take care of each machines own files. But this is usually an individual preference.
regards
The last time, several years ago, that I tried using dhcp on my lappy, which is itself an antique, I had 3 problems.
1. NM insisted on using the bcm-4318 radio in the lappy even if it was powered down by the switch. It totally ignored a radio in a usb dongle that actually worked where the bcm-4318 never worked for more than 1 minute, even when useing the drivers from xp that came installed to run it. Rebooting to xp disclosed that this pos radio was junk from the gitgo.
2. Getting it setup via dhcp with a usb radio dongle, so I could sit down while out in the shop, and write gcode for one of the 2 machines out there worked flawlessly over an ssh -Y machinename connection, until I wanted to ssh -Y lappy, which is its own name from the house machine. So the dns lookup which NM should have set up, wasn't there, forcing me to string a 25' hunk of cat5 plugged into its ethernet port. Adding its ip address and name to all the hosts files, and fixing all the network related files to be immutable after edited correctly, and then its just one of the family.
Strangely, when NM found it couldn't rewrite those files, it made no complaint in any log. And it didn't spin its wheels, burning up the cpu either.
3. I've left it that way in all subsequent installs. Now I remove NM and other than making /etc/resolv.conf a real file, its a 10 minute job after a fresh install to have a working network regardless of which socket I plug its cat5 cable into. With 2, 8 port switches available, soon to be 3 as I'll need another in the garage as I bring a bigger Sheldon 11x36 lathe to life with LinuxCNC. So the end of the cat5 I strung thru the nether regions of the house to get to the garage, will eventually have an 8 port switch on the end of it. That cable was 4 days getting run, a right PITA.
I think by now in 2016, if the computer has a working radio, or an ethernet over cat5 port, that it may be able to be made to work by now by people willing to do whats needed, but my long term experience with it has caused me to shoot it on sight. Bug squawks were ignored, or told to buzz off, and fixed versions were way too long working their way thru the pipeline to the users install. Several times I pulled the src and built it here, and it was better but still kept tearing down a working link and trying to find another, so it would eventually go back to the working link, which took it a good 2 minutes to do, then 3 minutes later I'm typing in the dark to /dev/null again. And I still have at least half my hair by using my lambasted by everybody methods. All I can say is that I can carry that lappy to anyplace on my local network, plug it in and boot it up, and the network Just Works(TM). Call me an idiot, and quite a few have, but simpler is better when it just works 100% of the time here. I have no reason to take it to mcd's and use their radio because there I would not have dd-wrt in my router standing guard. Its very very good at that. Recommended as the network guard dog by Grandpa Gene.
Cheers, Gene Heskett
Gene Heskett wrote:
On Monday 04 July 2016 03:46:38 deloptes wrote:
Gene Heskett wrote:
But, anything that looks or acts like network manager has been removed from my system. So any comments I might make about NM should be taken as the best swag* I can make based on 18 years of running linux.
NM is useful on notebooks that change locations, interfaces etc. If one uses a home network with many computers I would advise setting up proper dhcp and perhaps name server. You don't have to take care of each machines own files. But this is usually an individual preference.
regards
The last time, several years ago, that I tried using dhcp on my lappy, which is itself an antique, I had 3 problems.
- NM insisted on using the bcm-4318 radio in the lappy even if it was
powered down by the switch. It totally ignored a radio in a usb dongle that actually worked where the bcm-4318 never worked for more than 1 minute, even when useing the drivers from xp that came installed to run it. Rebooting to xp disclosed that this pos radio was junk from the gitgo.
You have the strangest problems. Amazingly you solve them the "gene" way.
- Getting it setup via dhcp with a usb radio dongle, so I could sit down
while out in the shop, and write gcode for one of the 2 machines out there worked flawlessly over an ssh -Y machinename connection, until I wanted to ssh -Y lappy, which is its own name from the house machine. So the dns lookup which NM should have set up, wasn't there, forcing me to string a 25' hunk of cat5 plugged into its ethernet port. Adding its ip address and name to all the hosts files, and fixing all the network related files to be immutable after edited correctly, and then its just one of the family.
I never had a problem using dhcp. At home we have a server (many disks) that has dhcpd and dns server running. This serves the local network. It stays behind a firewall. The router has wireless access point and is infront of the firewall. The router has also a dhcpd and nameserver, but when connecting via wireless I use the vpn (running on the firewall).
Strangely, when NM found it couldn't rewrite those files, it made no complaint in any log. And it didn't spin its wheels, burning up the cpu either.
- I've left it that way in all subsequent installs. Now I remove NM and
other than making /etc/resolv.conf a real file, its a 10 minute job after a fresh install to have a working network regardless of which socket I plug its cat5 cable into. With 2, 8 port switches available, soon to be 3 as I'll need another in the garage as I bring a bigger Sheldon 11x36 lathe to life with LinuxCNC. So the end of the cat5 I strung thru the nether regions of the house to get to the garage, will eventually have an 8 port switch on the end of it. That cable was 4 days getting run, a right PITA.
I had the issue with the resolv.conf being not a symlink when experimenting, but I prefer the standard solution, which seems to be working fine.
I takes 1minute to set a new machine up. Just add mac/hostname to dhcp and hostname/ip to bind and restart both - done. Many physical and virtual machines reside there. I even use the conf files to remember what is setup where :)
I think by now in 2016, if the computer has a working radio, or an ethernet over cat5 port, that it may be able to be made to work by now by people willing to do whats needed, but my long term experience with it has caused me to shoot it on sight. Bug squawks were ignored, or told to buzz off, and fixed versions were way too long working their way thru the pipeline to the users install. Several times I pulled the src and built it here, and it was better but still kept tearing down a working link and trying to find another, so it would eventually go back to the working link, which took it a good 2 minutes to do, then 3 minutes later I'm typing in the dark to /dev/null again. And I still have at least half my hair by using my lambasted by everybody methods. All I can say is that I can carry that lappy to anyplace on my local network, plug it in and boot it up, and the network Just Works(TM). Call me an idiot, and quite a few have, but simpler is better when it just works 100% of the time here. I have no reason to take it to mcd's and use their radio because there I would not have dd-wrt in my router standing guard. Its very very good at that. Recommended as the network guard dog by Grandpa Gene.
Cheers, Gene Heskett
I also prefer cat5 because of nfs, but my wife uses heavily the wireless from here (smart) phone. I think she finds typing with one finger on the touch screen sexy :)
The great thing of FOSS software is you can fix and customize it the way you like it. Thumbs up, Gene!
regards
On Wednesday 06 July 2016 14:33:25 deloptes wrote:
Gene Heskett wrote:
On Monday 04 July 2016 03:46:38 deloptes wrote:
Gene Heskett wrote:
But, anything that looks or acts like network manager has been removed from my system. So any comments I might make about NM should be taken as the best swag* I can make based on 18 years of running linux.
NM is useful on notebooks that change locations, interfaces etc. If one uses a home network with many computers I would advise setting up proper dhcp and perhaps name server. You don't have to take care of each machines own files. But this is usually an individual preference.
regards
The last time, several years ago, that I tried using dhcp on my lappy, which is itself an antique, I had 3 problems.
- NM insisted on using the bcm-4318 radio in the lappy even if it
was powered down by the switch. It totally ignored a radio in a usb dongle that actually worked where the bcm-4318 never worked for more than 1 minute, even when useing the drivers from xp that came installed to run it. Rebooting to xp disclosed that this pos radio was junk from the gitgo.
You have the strangest problems. Amazingly you solve them the "gene" way.
- Getting it setup via dhcp with a usb radio dongle, so I could sit
down while out in the shop, and write gcode for one of the 2 machines out there worked flawlessly over an ssh -Y machinename connection, until I wanted to ssh -Y lappy, which is its own name from the house machine. So the dns lookup which NM should have set up, wasn't there, forcing me to string a 25' hunk of cat5 plugged into its ethernet port. Adding its ip address and name to all the hosts files, and fixing all the network related files to be immutable after edited correctly, and then its just one of the family.
I never had a problem using dhcp. At home we have a server (many disks) that has dhcpd and dns server running. This serves the local network. It stays behind a firewall. The router has wireless access point and is infront of the firewall. The router has also a dhcpd and nameserver, but when connecting via wireless I use the vpn (running on the firewall).
Strangely, when NM found it couldn't rewrite those files, it made no complaint in any log. And it didn't spin its wheels, burning up the cpu either.
- I've left it that way in all subsequent installs. Now I remove
NM and other than making /etc/resolv.conf a real file, its a 10 minute job after a fresh install to have a working network regardless of which socket I plug its cat5 cable into. With 2, 8 port switches available, soon to be 3 as I'll need another in the garage as I bring a bigger Sheldon 11x36 lathe to life with LinuxCNC. So the end of the cat5 I strung thru the nether regions of the house to get to the garage, will eventually have an 8 port switch on the end of it. That cable was 4 days getting run, a right PITA.
I had the issue with the resolv.conf being not a symlink when experimenting, but I prefer the standard solution, which seems to be working fine.
I takes 1minute to set a new machine up. Just add mac/hostname to dhcp and hostname/ip to bind and restart both - done. Many physical and virtual machines reside there. I even use the conf files to remember what is setup where :)
In what files, plz? I found the man pages quite opaque in that regard.
I also prefer cat5 because of nfs, but my wife uses heavily the wireless from here (smart) phone. I think she finds typing with one finger on the touch screen sexy :)
I replaced all use of nfs with its finickety file system setups about 6 months back with a key file acl in sshfs, so no login. It Just Works(TM). Dr Klepp on this list can probably advise you how.
Putting all three of the current cnc machines to full read/write accessability, once the keys have been traded, is as simple as:
========================= #!/bin/bash sshfs gene@shop:/ /sshnet/shop sshfs gene@lathe:/ /sshnet/lathe sshfs gene@GO704:/ /sshnet/GO704 ========================= And they are magically available to me as user 1000.
The great thing of FOSS software is you can fix and customize it the way you like it. Thumbs up, Gene!
Absolutely, and too few, particularly those coming in from a windows environment, can understand that. My mind was never poisoned by that, thank $DIETY.
My trail thru multiuser/multitasking operating systems starts in about 1985 when I discovered os9 for the trs-80 Color computers, very much like unix but could run on a 16 bit cpu.
From there to amigados because we used half a dozen of them for graphics generators at the tv station, Jim Hines and I wrote some PD and some commercial SW in that language, the PD was a EzCron that didn't burn cpu in a wait loop, and the commercial program was EzHome to run a housefull of X10 stuff. I still do that but with heyu.
And finally in '98 to a RedHat 5 system I built at work and took home to replace the aging A2k I had been using for a decade. And we still, to this day, do not have a programming language with the power of William (Bill) Hawes "ARexx" which was a huge, went right to the hardware superset of Regina for Linux. You could write assembly language powerfull SW in plain English. Bill should have collected at least half of what Commie sold it for, on a per copy basis. But he never got a damned dime. Commie stiffed a lot of people when the two top guys went to Bermuda, along with any money that was in the bank account at the time.
Cheers, Gene Heskett
On Sunday 03 July 2016 09:25:49 Uwe Brauer wrote:
Hello Uwe,
Hi again
You will find everything you want in "/etc/NetworkManager/" There is the main file "NetworkManager.conf" and the connection folder "/etc/NetworkManager/system-connections/" that will contain a conf file for every network connection.
I finally find out, that you were right, so I owe you an apology.
However I am confused that the tde networkmanager could write to /etc without having asked for the root passwd as far as I can remember.
On Sunday 03 July 2016 09:25:49 Uwe Brauer wrote:
Hello Uwe,
You will find everything you want in "/etc/NetworkManager/" There is the main file "NetworkManager.conf" and the connection folder "/etc/NetworkManager/system-connections/" that will contain a conf file for every network connection.
On a secound thought, maybe this is connected to the problem I reported connected to an wifi with enterprise WPA, tde-networkmanager could not connect and gave three reason one was not having the correct permission. So if indeed he has to write to /etc and somehow does not get root rights that would explain the problem. I would then call that a bug.
Uwe Brauer wrote:
On Sunday 03 July 2016 09:25:49 Uwe Brauer wrote:
Hello Uwe,
You will find everything you want in "/etc/NetworkManager/" There is the main file "NetworkManager.conf" and the connection folder "/etc/NetworkManager/system-connections/" that will contain a conf file for every network connection.
On a secound thought, maybe this is connected to the problem I reported connected to an wifi with enterprise WPA, tde-networkmanager could not connect and gave three reason one was not having the correct permission. So if indeed he has to write to /etc and somehow does not get root rights that would explain the problem. I would then call that a bug.
usually it's just a matter of group membership
On Sunday 03 July 2016 08:25:49 Uwe Brauer wrote:
Hello
In the old trinity 3.5 series (at least for Kubuntu 10.04) the config file for knetworkmanager was in ./trinity/share/conf
However I can't file that file or anything similar in the trinity 14.X series (on Kununtu 14.04).
Interesting. I have /home/$USER/.trinity/share/config here, TDE14 on Debian Jessie (8). I wonder why Kubuntu changed it? Or is it because mine is an upgrade not a fresh install?
Lisi
-
deloptes -
Dobigeon Nicolas -
Gene Heskett -
Lisi Reisz -
Uwe Brauer