On 4 May 2017 at 12:44, James Hogarth wrote:
> On 8 March 2017 at 11:19, James Hogarth wrote:
>> On 8 March 2017 at 11:15, Alice Wonder wrote:
>>> On 03/08/2017 01:57 AM, Giles Coochey wrote:
> The recommended
On 8 March 2017 at 11:19, James Hogarth wrote:
> On 8 March 2017 at 11:15, Alice Wonder wrote:
>> On 03/08/2017 01:57 AM, Giles Coochey wrote:
>>>
>>>
The recommended configuration for EL7 is to use NetworkManager unless
you have a very
On 09/03/17 09:28, John Hodrien wrote:
I'll obviously argue I wasn't scaremongering. You can start with
CentOS, and
do anything you like with it, and as I've said, you're absolutely free
to do
that. But at some point, you have to accept that what you've got left
isn't
CentOS. If you
On Thu, 9 Mar 2017, isdtor wrote:
Did I see an implicit "do as Red Hat says or else" there somewhere? Not
appropriate. Linux is not Windows (yet). In the heat of the moment it may
easily be forgotton that Linux is all about choice. We choose to run CentOS,
and we choose to run it the way we see
On 9 March 2017 at 00:54, isdtor wrote:
> Did I see an implicit "do as Red Hat says or else" there somewhere? Not
> appropriate. Linux is not Windows (yet). In the heat of the moment it may
> easily be forgotton that Linux is all about choice. We choose to run CentOS,
> and
Did I see an implicit "do as Red Hat says or else" there somewhere? Not
appropriate. Linux is not Windows (yet). In the heat of the moment it may
easily be forgotton that Linux is all about choice. We choose to run CentOS,
and we choose to run it the way we see fit. We appreciate the efforts
On 8 March 2017 at 15:00, Giles Coochey wrote:
>
>
> On 08/03/17 14:54, Jonathan Billings wrote:
>>
>>
>> If you'd like a really simple solution that avoids NetworkManager, I
>> suggest using systemd-networkd (both systemd-networkd and
>> systemd-resolved packages required).
On 08/03/17 14:54, Jonathan Billings wrote:
If you'd like a really simple solution that avoids NetworkManager, I
suggest using systemd-networkd (both systemd-networkd and
systemd-resolved packages required). I've used it to set up a bridge
on my workstattion for use with libvirtd/kvm, and it
On Wed, Mar 08, 2017 at 10:43:57AM +, Giles Coochey wrote:
> https://en.wikipedia.org/wiki/KISS_principle
>
> I'm not flaming NetworkManager, I'm just stating that for many (perhaps
> most), it is over-engineered for a server orientated distribution. I can run
> with the script above on 30
On 08/03/17 13:16, Steve Clark wrote:
Let us have a vote - how many of us do teaming/bonding/vlans on our servers?
Our networking gear does that in our installation.
The majority of my servers are virtual, if I need multiple subnets
(VLANs) then I have multiple cards.
Their throughput does
On 8 March 2017 at 13:16, Steve Clark wrote:
> On 03/08/2017 07:39 AM, John Hodrien wrote:
>> On Wed, 8 Mar 2017, Steve Clark wrote:
>>
>>> Yes it is really hard!
>>>
>>> ip address add 192.168.0.1/24 dev enp0s25
>>> ip route add default via 192.168.0.254 dev enp0s25
Hello David,
It was not to flame something about NetworkManager. There some
application that "needs" to wheel the old way.
I would never have thought it would be such an enlightenment for such a
small, old thing.
1. There is a file that isn't always needed (/etc/sysconfig/network)
2. I wanne
On 03/08/2017 07:39 AM, John Hodrien wrote:
> On Wed, 8 Mar 2017, Steve Clark wrote:
>
>> Yes it is really hard!
>>
>> ip address add 192.168.0.1/24 dev enp0s25
>> ip route add default via 192.168.0.254 dev enp0s25
>> echo nameserver 8.8.8.8 > /etc/resolv.conf
>> echo nameserver 8.8.4.4 >>
On Wed, 8 Mar 2017, Steve Clark wrote:
Yes it is really hard!
ip address add 192.168.0.1/24 dev enp0s25
ip route add default via 192.168.0.254 dev enp0s25
echo nameserver 8.8.8.8 > /etc/resolv.conf
echo nameserver 8.8.4.4 >> /etc/resolv.conf
This is still a deliberately trivial case, as
On 03/08/2017 05:43 AM, Giles Coochey wrote:
On 08/03/17 10:38, John Hodrien wrote:
On Wed, 8 Mar 2017, Giles Coochey wrote:
ifconfig enp0s25 192.168.0.1 netmask 255.255.255.0
route add default gw 192.168.0.254 enp0s25
echo nameserver 8.8.8.8 > /etc/resolv.conf
echo nameserver 8.8.4.4 >>
On 03/08/2017 05:52 AM, John Hodrien wrote:
> On Wed, 8 Mar 2017, Giles Coochey wrote:
>
>> Not really, Redhat/Centos has a lot to offer, but for me, networking is a
>> one-time configuration, and the best way to configure it is using something
>> that falls within this principle:
>>
>>
Certain application doesn't like the NetworkManager
for example take a look here.
https://www.rdoproject.org/install/quickstart/
And on server stage it's better to run without
any complicate configuration tools.
Tools can make life harder in some cases.
Got many other distros run before
On 03/08/2017 05:43 AM, Giles Coochey wrote:
>
> On 08/03/17 10:38, John Hodrien wrote:
>> On Wed, 8 Mar 2017, Giles Coochey wrote:
>>
>>> ifconfig enp0s25 192.168.0.1 netmask 255.255.255.0
>>> route add default gw 192.168.0.254 enp0s25
>>> echo nameserver 8.8.8.8 > /etc/resolv.conf
>>> echo
Hello James,
your right in that position. I will correct it.
Sincerely
Andy
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
On 8 March 2017 at 11:15, Alice Wonder wrote:
> On 03/08/2017 01:57 AM, Giles Coochey wrote:
>>
>>
>>> The recommended configuration for EL7 is to use NetworkManager unless
>>> you have a very specific edge case preventing you from doing so:
>>>
>> The truth is a lot of us
On 03/08/2017 01:57 AM, Giles Coochey wrote:
The recommended configuration for EL7 is to use NetworkManager unless
you have a very specific edge case preventing you from doing so:
The truth is a lot of us run servers that don't need to have their
network "managed" by Networkmanager.
My
On 08/03/17 11:10, James Hogarth wrote:
On 8 March 2017 at 10:58, Giles Coochey wrote:
On 08/03/17 10:52, John Hodrien wrote:
It means you're stuck in your own hand crafted niche. Which is fine, but
it's
up to you to maintain the niche, or you find yourself using
On 8 March 2017 at 10:58, Giles Coochey wrote:
>
>
> On 08/03/17 10:52, John Hodrien wrote:
>>
>>
>> It means you're stuck in your own hand crafted niche. Which is fine, but
>> it's
>> up to you to maintain the niche, or you find yourself using obsolete tools
>> like ifconfig
On 08/03/17 10:52, John Hodrien wrote:
It means you're stuck in your own hand crafted niche. Which is fine,
but it's
up to you to maintain the niche, or you find yourself using obsolete
tools
like ifconfig and route.
I'd argue there's a gulf between keeping things simple and doing
On Wed, 8 Mar 2017, Giles Coochey wrote:
Not really, Redhat/Centos has a lot to offer, but for me, networking is a
one-time configuration, and the best way to configure it is using something
that falls within this principle:
https://en.wikipedia.org/wiki/KISS_principle
I'm not flaming
On 08/03/17 10:38, John Hodrien wrote:
On Wed, 8 Mar 2017, Giles Coochey wrote:
ifconfig enp0s25 192.168.0.1 netmask 255.255.255.0
route add default gw 192.168.0.254 enp0s25
echo nameserver 8.8.8.8 > /etc/resolv.conf
echo nameserver 8.8.4.4 >> /etc/resolv.conf
Oh okay, you really do want
On Wed, 8 Mar 2017, Giles Coochey wrote:
ifconfig enp0s25 192.168.0.1 netmask 255.255.255.0
route add default gw 192.168.0.254 enp0s25
echo nameserver 8.8.8.8 > /etc/resolv.conf
echo nameserver 8.8.4.4 >> /etc/resolv.conf
Oh okay, you really do want to back away from Redhat entirely. That's
On 08/03/17 10:15, John Hodrien wrote:
On Wed, 8 Mar 2017, Giles Coochey wrote:
The truth is a lot of us run servers that don't need to have their
network
"managed" by Networkmanager.
You're opting to have your network managed by a bunch of unloved legacy
scripts that you're advised to
On Wed, 8 Mar 2017, Giles Coochey wrote:
The truth is a lot of us run servers that don't need to have their network
"managed" by Networkmanager.
You're opting to have your network managed by a bunch of unloved legacy
scripts that you're advised to avoid using unless necessary, or you've
The recommended configuration for EL7 is to use NetworkManager unless
you have a very specific edge case preventing you from doing so:
The truth is a lot of us run servers that don't need to have their
network "managed" by Networkmanager.
We just need to set an IP address, subnet mask,
On 8 March 2017 at 06:56, Andreas Benzler wrote:
> Hello Guys,
>
> update my post, because of a route from ipv6 on same networkcard,
> with only ipv4 enabled
>
> Sincerely
>
> Andy
>
>
Please accept this as honest constructive criticism from someone who
also likes to blog.
Hello Guys,
update my post, because of a route from ipv6 on same networkcard,
with only ipv4 enabled
Sincerely
Andy
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
Sorry:
Can be a bug, because /etc/sysconfig/network isn't nessesery.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
I don't know who is intereseted in,
http://www.centos.cms4all.org/index.php/2017/03/07/centos-7-the-journey-form-networkmanager-to-self-managed-network-configuration-files/
Can be a bug, because the isn't nessesery.
Sincerely
AndyBe
___
CentOS
34 matches
Mail list logo