12 Sep
2016
12 Sep
'16
12:14 p.m.
Hi
This is the first time I have such an experience. I installed Kubuntu
14.04 and trinity via
deb http://mirror.xcer.cz/trinity-sb trusty deps-r14 main-r14
deb-src http://mirror.xcer.cz/trinity-sb trusty deps-r14 main-r14
Everything went smooth wireless net can be configured with
tdenetworkmanager, but when I try to set up the wired net, via the
networktool I run into a problem.
I use all the parameters I used in previous trinity + Kubuntu
installations (namely 10.04 and 12.04)
static IP number
DNS server
Gateway.
The connection works for a couple of seconds and then crashes the
problem see to be the Gateway, when I restart the configuration tool the
value has been deleted.
Anybody has an idea what do?
That is a very serious problem, right now use the Wifi connection, but
this has severe restriction in the network I am using.
Thanks
Uwe Brauer
12 Sep
12 Sep
7:49 p.m.
Hi Uwe,
Uwe Brauer wrote:
Everything went smooth wireless net can be configured
with
tdenetworkmanager, but when I try to set up the wired net, via the
networktool I run into a problem.
This network tool is tdenetworkmanager or something else? I assume yes.
I use all the parameters I used in previous trinity + Kubuntu
installations (namely 10.04 and 12.04)
static IP number
DNS server
Gateway.
The connection works for a couple of seconds and then crashes the
problem see to be the Gateway, when I restart the configuration tool the
value has been deleted.
Anybody has an idea what do?
That is a very serious problem, right now use the Wifi connection, but
this has severe restriction in the network I am usin
You could turn off network manager and try configuring the wired network
manually or via network/interfaces.
This way you prove if it is tdenetworkmanager causing the trouble.
If yes, you could start tdenetworkmanager in the console or from gdb and try
to get some more information on why it crashes.
Watch out using static ips - if you are not the admin, this could cause
collisions.
Let us know what you have found out.
regards
13 Sep
13 Sep
8:15 a.m.
New subject: SOLVED partially (was: [trinity-users] Re: Kubuntu 14.04 and trinity:problems with wired network)
Hi Uwe,
Uwe Brauer wrote:
Hi
Thanks for your answer
This network tool is tdenetworkmanager or something
else? I assume yes.
Yes it is.
You could turn off network manager and try configuring
the wired network
manually or via network/interfaces.
I tried this already, the problem is that in Kubuntu 14.04 things are
different, maybe caused my the switch to systemd.
In 10.4 and 12.04 I had in /etc a file resolv.conf which contained the
IP of the DNS server and in
/etc/network/interfaces
The static IP of the machine, the gateway etc.
Also the command
sudo /etc/init.d/networking restart
Restarted the network.
Now in 14.04
resolv.conf -> ../run/resolvconf/resolv.conf
Which seems ok, but
sudo /etc/init.d/networking restart
Seems not to do anything.
In any case one problem is caused by the IPv6 protocol.
So I added the following line to my grub configuration
(/etc/default/grub
GRUB_CMDLINE_LINUX_DEFAULT="ipv6.disable=1 quiet splash"
And rebooted, then tdenetworkmanager seemed to configure the network
correctly, but after rebooting the DNS server was deleted from
resolv.conf again, which is annoying.
Regards
Uwe
9:26 a.m.
New subject: [trinity-users] SOLVED partially (was: [trinity-users] Re: Kubuntu 14.04 and trinity:problems with wired network)
14.04 didn't use systemd it used upstart.
On 13 September 2016 at 18:15, Uwe Brauer <oub.oub.oub(a)gmail.com> wrote:
Hi Uwe,
Uwe Brauer wrote:
Hi
Thanks for your answer
This network tool is tdenetworkmanager or
something else? I assume
yes.
Yes it is.
You could turn off network manager and try
configuring the wired
network
manually or via network/interfaces.
I tried this already, the problem is that in Kubuntu 14.04 things are
different, maybe caused my the switch to systemd.
In 10.4 and 12.04 I had in /etc a file resolv.conf which contained the
IP of the DNS server and in
/etc/network/interfaces
The static IP of the machine, the gateway etc.
Also the command
sudo /etc/init.d/networking restart
Restarted the network.
Now in 14.04
resolv.conf -> ../run/resolvconf/resolv.conf
Which seems ok, but
sudo /etc/init.d/networking restart
Seems not to do anything.
In any case one problem is caused by the IPv6 protocol.
So I added the following line to my grub configuration
(/etc/default/grub
GRUB_CMDLINE_LINUX_DEFAULT="ipv6.disable=1 quiet splash"
And rebooted, then tdenetworkmanager seemed to configure the network
correctly, but after rebooting the DNS server was deleted from
resolv.conf again, which is annoying.
Regards
Uwe
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-users-unsubscribe@
lists.pearsoncomputing.net
For additional commands, e-mail: trinity-users-help@lists.
pearsoncomputing.net
Read list messages on the web archive: http://trinity-users.
pearsoncomputing.net/
Please remember not to top-post: http://trinity.
pearsoncomputing.net/mailing_lists/#top-posting
10 a.m.
New subject: SOLVED partially
>> "relosrl" == relosrl
<relosrl(a)tiscalinet.it> writes:
Il 13/09/2016 11:40, Uwe Brauer ha scritto:
> And now after every rebook my DNS server is deleted and I have re
> configure my wired net, very inconvient, not sure who is the culprit
> here.
I solve with:
chattr +i resolv.conf
Well
sudo chattr +i /run/resolv.conf
Gives
chattr: Inappropriate ioctl for device while reading flags on resolv.conf
Rodolfo
10:26 a.m.
New subject: [trinity-users] Re: SOLVED partially
Il 13/09/2016 12:00, Uwe Brauer ha scritto:
Well
sudo chattr +i /run/resolv.conf
Gives
chattr: Inappropriate ioctl for device while reading flags on resolv.conf
I had delete in etc the symlink resolv.conf and make a file resolv.conf,
than sudo chattr +i /run/resolv.conf.
Rodolfo
11:10 a.m.
New subject: [trinity-users] Re: SOLVED partially
On Tuesday 13 September 2016 06:00:11 Uwe Brauer wrote:
Well
sudo chattr +i /run/resolv.conf
Gives
chattr: Inappropriate ioctl for device while reading flags on
resolv.conf
Not /run/resolv.conf,
/etc/resolv.conf. On some systems, it may be a
link. I nuked the link and made a real file that contained 'hosts,dns'
as I use hosts files for local dns on my little network, only using dhcp
for transient connections. I also did the chattr +i on that,
and /etc/network/interfaces back when you couldn't remove NM, so that
was my way of disabling that monster.
Frowned on in strong language by TPTB here, but no stronger than NM
caused when it tears a perfectly good network connection down and then
fails to invent one that works. DNS is defined
in /etc/network/interfaces as the gateway, which is my router, so any
addresses not in my /etc/hosts file are forwarded to DD-WRT in the
router, which is the only place my ISP's supplied dns servers are used.
Now, watch the firestorm because I mentioned NM in less than glowing
terms.
> "relosrl" == relosrl
<relosrl(a)tiscalinet.it> writes:
Il 13/09/2016 11:40, Uwe Brauer ha scritto:
And now after every rebook my DNS server is
deleted and I have
re configure my wired net, very inconvient, not sure who is the
culprit here.
I solve with:
chattr +i resolv.conf Rodolfo
---------------------------------------------------------------------
To unsubscribe, e-mail:
trinity-users-unsubscribe(a)lists.pearsoncomputing.net For additional
commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net Read
list messages on the web archive:
http://trinity-users.pearsoncomputing.net/ Please remember not to
top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>
1:01 p.m.
New subject: [trinity-users] Re: SOLVED partially
On Tuesday 13 September 2016 12:10:31 Gene Heskett wrote:
Now, watch the firestorm because I mentioned NM in
less than glowing
terms.
I don't know where you get that from, Gene. It has long had the nick-name
Network Mangler (though I understand that it is less deserved now than
formerly). ;-/
Lisi
14 Sep
14 Sep
10:35 a.m.
New subject: SOLVED partially
On Tuesday 13 September 2016 06:00:11 Uwe Brauer
wrote:
Not /run/resolv.conf, /etc/resolv.conf. On some systems, it may be a
link. I nuked the link and made a real file that contained
'hosts,dns'
Ok, that solved this issue. That is I deleted the link copied the
resolv.conf file
which contained the lines.
# Generated by NetworkManager
nameserver 147.96.1.9
nameserver 147.96.2.4
from /run/resolvconf/resolv.conf to /etc and run
chattr +i resolv.conf
Rebooted and now everything is ok, when rebooting. However I noticed
that I did not quite describe what I did:
- I used /opt/trinity/bin/systemsettings for setting the wired net
- and tdenetworkmanager for the wireless net.
Maybe this is not smart and I had no problems, when passing from wired
--> wireless but problems when passing from wireless --> wired since the
wireless deleted the DNS server entries.
I will report this in a new mail with a new subject.
Uwe Brauer
13 Sep
13 Sep
9:36 a.m.
New subject: [trinity-users] SOLVED partially (was: [trinity-users] Re: Kubuntu 14.04 and trinity:problems with wired network)
On Tuesday 13 September 2016 09:15:43 Uwe Brauer wrote:
sudo /etc/init.d/networking restart
Seems not to do anything.
I understand it doesn't with systemd. I'm afraid that I can't remember what
one is supposed to use instead. When all else fails, restart the system
works!!
Lisi
9:42 a.m.
New subject: SOLVED partially
>> "Lisi" == Lisi Reisz
<lisi.reisz(a)gmail.com> writes:
On Tuesday 13 September 2016 09:15:43 Uwe Brauer
wrote:
> sudo /etc/init.d/networking restart
>
> Seems not to do anything.
I understand it doesn't with systemd. I'm
afraid that I can't
remember what one is supposed to use instead. When all else fails,
restart the system works!!
The problem is after every restart, my DNS server is deleted from the
configuration so I have to re configure via tdenetworkmanager the DNS
server and restart the net, very inconvient.
9:03 p.m.
New subject: SOLVED partially
Uwe Brauer wrote:
The problem is after every restart, my DNS server is
deleted from the
configuration so I have to re configure via tdenetworkmanager the DNS
server and restart the net, very inconvient.
I am a bit confused now. On both places (/etc/network/interfaces) and in
network manager you can specify the DNS.
See this - looks like similar:
http://askubuntu.com/questions/137037/networkmanager-not-populating-resolv-…
I think you should keep information only at one place. I now moved
completely to NM since perhaps 1-2 months for similar reasons and do not
experience any issues. However I am using dhcp and never tried fixed IPs.
About the resolv.conf I think it also depends on how you configure the
interface in /etc/network/interfaces. Do you have something like
auto eth0
or similar.
I recall vague that there was something ifup/down vs. ifconfig up/down
related.
So perhaps your problem is because of configuration mixing up both.
regards
PS:
In my case I have a custom script I hooked to /etc/network/if-up.d/
including restarting firewall after changing connection etc. This was
necessary, after moving to systemd. These directories and their files are
honored by NM. It is worth looking into it.
Everything works great! Just keep it simple and clean!
4:44 p.m.
New subject: [trinity-users] SOLVED partially (was: [trinity-users] Re: Kubuntu 14.04 and trinity:problems with wired network)
Uwe Brauer wrote:
I tried this already, the problem is that in Kubuntu
14.04 things are
different, maybe caused my the switch to systemd.
In 10.4 and 12.04 I had in /etc a file resolv.conf which contained
the IP of the DNS server and in
/etc/network/interfaces
The static IP of the machine, the gateway etc.
I missed the start of this thread so my answer may be clueless. In
Jessie (and other systemd OS's?), static IP and DNS have moved to
/etc/dhcpd.conf. All I did to setup this machine was to add the
following to the bottom of dhcpd.conf:
interface eth0
static ip_address=192.168.0.8/24
static routers=192.168.0.1
static domain_name_servers=208.67.222.222 8.8.8.8
...I hadn't tried "service networking restart", which generates a
warning. While networking was fine at this point, I ran the suggested
command which had no visible affect (networking still fine).
5:11 p.m.
New subject: [trinity-users] SOLVED partially (was: [trinity-users] Re: Kubuntu 14.04 and trinity:problems with wired network)
On Tuesday 13 September 2016 17:44:43 Dave Lers wrote:
Uwe Brauer wrote:
Thanks for that! This is the first time I have seen that clearly explained -
or even explained at all. :-)
Lisi
I tried this already, the problem is that in
Kubuntu 14.04 things are
different, maybe caused my the switch to systemd.
In 10.4 and 12.04 I had in /etc a file resolv.conf which contained
the IP of the DNS server and in
/etc/network/interfaces
The static IP of the machine, the gateway etc.
I missed the start of this thread so my answer may be clueless. In
Jessie (and other systemd OS's?), static IP and DNS have moved to
/etc/dhcpd.conf. All I did to setup this machine was to add the
following to the bottom of dhcpd.conf:
interface eth0
static ip_address=192.168.0.8/24
static routers=192.168.0.1
static domain_name_servers=208.67.222.222 8.8.8.8 ...I hadn't tried "service networking
restart", which generates a
warning. While networking was fine at this point, I ran the suggested
command which had no visible affect (networking still fine).
---------------------------------------------------------------------
To unsubscribe, e-mail:
trinity-users-unsubscribe(a)lists.pearsoncomputing.net For additional
commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net Read list
messages on the web archive: http://trinity-users.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
7:36 p.m.
New subject: [trinity-users] SOLVED partially (was: [trinity-users] Re: Kubuntu 14.04 and trinity:problems with wired network)
On Tuesday 13 September 2016 13:11:31 Lisi Reisz wrote:
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>
On Tuesday 13 September 2016 17:44:43 Dave Lers
wrote:
Yes, thats quite helpfull, so I'll toss some flowers myself. Thank you
Dave Lers. :)
Uwe Brauer wrote:
Thanks for that! This is the first time I have seen that clearly
explained - or even explained at all. :-)
Lisi I tried this already, the problem is that in
Kubuntu 14.04 things
are different, maybe caused my the switch to systemd.
In 10.4 and 12.04 I had in /etc a file resolv.conf which contained
the IP of the DNS server and in
/etc/network/interfaces
The static IP of the machine, the gateway etc.
I missed the start of this thread so my answer may be clueless. In
Jessie (and other systemd OS's?), static IP and DNS have moved to
/etc/dhcpd.conf. All I did to setup this machine was to add the
following to the bottom of dhcpd.conf:
interface eth0
static ip_address=192.168.0.8/24
static routers=192.168.0.1
static domain_name_servers=208.67.222.222 8.8.8.8 ...I hadn't tried "service networking
restart", which generates a
warning. While networking was fine at this point, I ran the
suggested command which had no visible affect (networking still
fine).
--------------------------------------------------------------------
- To unsubscribe, e-mail:
trinity-users-unsubscribe(a)lists.pearsoncomputing.net For additional
commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net Read
list messages on the web archive:
http://trinity-users.pearsoncomputing.net/ Please remember not to
top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
---------------------------------------------------------------------
To unsubscribe, e-mail:
trinity-users-unsubscribe(a)lists.pearsoncomputing.net For additional
commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net Read
list messages on the web archive:
http://trinity-users.pearsoncomputing.net/ Please remember not to
top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting 
5:28 p.m.
New subject: [trinity-users] SOLVED partially (was: [trinity-users] Re: Kubuntu 14.04 and trinity:problems with wired network)
Dne út 13. září 2016 Dave Lers napsal(a):
Uwe Brauer wrote:
Ha, I still use the file /etc/network/interfaces, same way as I'm used
from previous versions of Debian. This is for me an unknown novelty. It
has some advantage over the interfaces file?
However, I never use restart for networking service. I always apply only
ifdown / ifup on particular interface that I need to address.
--
Slávek
I tried this already, the problem is that in
Kubuntu 14.04 things are
different, maybe caused my the switch to systemd.
In 10.4 and 12.04 I had in /etc a file resolv.conf which contained
the IP of the DNS server and in
/etc/network/interfaces
The static IP of the machine, the gateway etc.
I missed the start of this thread so my answer may be clueless. In
Jessie (and other systemd OS's?), static IP and DNS have moved to
/etc/dhcpd.conf. All I did to setup this machine was to add the
following to the bottom of dhcpd.conf:
interface eth0
static ip_address=192.168.0.8/24
static routers=192.168.0.1
static domain_name_servers=208.67.222.222 8.8.8.8
...I hadn't tried "service networking restart", which generates a
warning. While networking was fine at this point, I ran the suggested
command which had no visible affect (networking still fine).
14 Sep
14 Sep
4:43 a.m.
New subject: [trinity-users] SOLVED partially (was: Kubuntu 14.04 and trinity:problems with wired network)
Slávek Banko composed on 2016-09-13 19:28 (UTC+0200):
Dave Lers composed:
> Uwe Brauer wrote:
> > I tried this already, the problem is that in
Kubuntu 14.04 things are
> > different, maybe caused my the switch to systemd.
> > In 10.4 and 12.04 I had in /etc a file
resolv.conf which contained
> > the IP of the DNS server and in
> > /etc/network/interfaces
> > The static IP of the machine, the gateway
etc.
> I missed the start of this thread so my answer may
be clueless. In
> Jessie (and other systemd OS's?), static IP and DNS have moved to
> /etc/dhcpd.conf. All I did to setup this machine was to add the
> following to the bottom of dhcpd.conf:
> interface eth0
> static ip_address=192.168.0.8/24
> static routers=192.168.0.1
> static domain_name_servers=208.67.222.222 8.8.8.8
I wonder what created this? I can't imagine why a system would be configured
for fixed IP and yet have an ostensible DHCP configuration file at all, much
less specifying static configuration parameters. Does that installation also
have /etc/sysconfig/interfaces, and if so, is it last written subsequent to
/etc/dhcpd.conf? Or before?
> ...I hadn't tried "service networking
restart", which generates a
> warning. While networking was fine at this point, I ran the suggested
> command which had no visible affect (networking still fine).
Ha, I still use the file /etc/network/interfaces, same
way as I'm used
from previous versions of Debian. This is for me an unknown novelty. It
has some advantage over the interfaces file?
For the first time since Hermine, I booted host g5eas, which has both 16.04
and Jessie. Both are configured with static IP. Both have
/etc/sysconfig/interfaces. Neither have /etc/dhcpd.conf.
--
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/
7:17 a.m.
New subject: [trinity-users] SOLVED partially (was: Kubuntu 14.04 and trinity:problems with wired network)
On Wednesday 14 September 2016 05:43:07 Felix Miata wrote:
Slávek Banko composed on 2016-09-13 19:28 (UTC+0200):
For the first time since Hermine, I booted host g5eas, which has both 16.04
and Jessie. Both are configured with static IP. Both have
/etc/sysconfig/interfaces. Neither have /etc/dhcpd.conf.
This makes more sense!
I hope that your life has gone somewhere back towards normal.
Lisi
Dave Lers composed:
> Uwe Brauer wrote:
> > I tried this already, the problem is that in Kubuntu 14.04 things are
> > different, maybe caused my the switch to systemd.
> >
> > In 10.4 and 12.04 I had in /etc a file resolv.conf which contained
> > the IP of the DNS server and in
> >
> > /etc/network/interfaces
> >
> > The static IP of the machine, the gateway etc.
>
> I missed the start of this thread so my answer may be clueless. In
> Jessie (and other systemd OS's?), static IP and DNS have moved to
> /etc/dhcpd.conf. All I did to setup this machine was to add the
> following to the bottom of dhcpd.conf:
>
> interface eth0
> static ip_address=192.168.0.8/24
> static routers=192.168.0.1
> static domain_name_servers=208.67.222.222 8.8.8.8
I wonder what created this? I can't imagine why a system would be
configured for fixed IP and yet have an ostensible DHCP configuration file
at all, much less specifying static configuration parameters. Does that
installation also have /etc/sysconfig/interfaces, and if so, is it last
written subsequent to /etc/dhcpd.conf? Or before?
...I
hadn't tried "service networking restart", which generates a
warning. While networking was fine at this point, I ran the suggested
command which had no visible affect (networking still fine).
Ha, I still use the file /etc/network/interfaces, same way as I'm used
from previous versions of Debian. This is for me an unknown novelty. It
has some advantage over the interfaces file?
8:36 p.m.
New subject: [trinity-users] SOLVED partially (was: Kubuntu 14.04 and trinity:problems with wired network)
Dave Lers
composed:
>> I missed the start of this thread so my answer may be clueless. In
>> Jessie (and other systemd OS's?), static IP and DNS have moved to
>> /etc/dhcpd.conf.
2792
days inactive
2794
days old
20 comments
10 participants
participants (10)
-
Dave Lers -
deloptes -
Felix Miata -
Gene Heskett -
Lisi Reisz -
Michael . -
relosrl -
Slávek Banko -
Uwe Brauer -
Uwe Brauer