similar to: Network configuration: desktop vs. laptop

Hi Niki, On CentOS it's normal for both wireless and wired to be connected at the same time, maybe what you are seeing is just the icon's being confusing or not being replaced with the right thing? This is easy to check, just issue an "ip route". On My system I can see something like this: default via 192.168.0.1 dev eth0 proto static 192.168.0.0/24 dev eth0 proto kernel

Hi, I'm running CentOS 7 on all my servers, in three different contexts : 1. simple local server 2. public facing server 3. router/gateway/firewall I'm currently in the process of moving my KISS-style network-scripts-style configurations to something more orthodox based on NetworkManager. Scenarios (1) and (2) caused no problems, but (3) is giving me some headache. Let me

On 09/08/2016 20:01, Gordon Messmer wrote: > On 08/08/2016 04:05 AM, Levente Birta wrote: >> Can I add this in any config files (ex: route-enp2s0)? > > > Yes. Add a route file for each interface, and set up rules to send > packets out the corresponding physical interface: > > https://blogs.oracle.com/networking/entry/advance_routing_for_multi_homed > Yes, but no

Hello All, I'm installing some DIY routers, composed of Intel nuc's ,Linksys usb-ethernet adapters and Centos7 On most machines I just plug in the usb device, install Centos7 and everything works. But on this one machine the network interface doesn't work. After installing ip addr shows: [root at clgmol ~]# ip addr 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue

Hi There is a Centos 7 up-to-date box with 2 interfaces, let's say 192.168.1.12 - enp2s0, 192.168.1.13 on enp3s0. Default gateway on enp2s0. The gateway is pfsense, IP is 192.168.1.1 with 2 WAN connections On the gateway the outgoing traffic is routed by source ip to different WAN, 192.168.1.12 to WAN1 and 192.168.1.13 to WAN2 On the centos box are set all the route and routing rules:

Hi, My local server is running CentOS 7. The machine has two NICs and is acting as a gateway. For DHCP and DNS, I'm using Dnsmasq. I have a strange little problem with local hostname resolution. Before going into more details, here's my configuration. [root at nestor:~] # ifconfig enp2s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.0.2 netmask

On Wed, Aug 10, 2016 at 09:29:15AM +0300, Levente Birta wrote: > I read the document again ... and this talk about accessing this multi-homed > host from the internet... > I have all this configured and working! You say this is working because of the output here? # ip route show default via 192.168.1.1 dev enp3s0 default via

On 09/08/2016 15:47, Jonathan Billings wrote: > On Tue, Aug 09, 2016 at 10:58:40AM +0300, Levente Birta wrote: >> What I don't understand why the route command allow to add a second default >> gateway with different interface, but the ip route command doesn't? > You can only have one default gateway. > > It sounds to me like you want to use both interfaces, which

Hi, In my office I have an HP Proliant server running CentOS 7. It's a minimal install without GUI. The machine has two network interface cards, and for now it's acting as gateway/firewall, and it's running ntpd, Dnsmasq and Rsnapshot. I'd like this machine to also be a KVM virtualization host, so I installed qemu-kvm and libvirt. The interface facing the LAN is enp3s0, so I

Hi, I would like to run a network firewall as a VM on a KVM host. There are ~ 25 VLANs delivered to the KVM host on three dedicated links, no LACP or other things. I have the VLANs 100-180 on the host's enp1s0, the VLANs 200-280 on the host's enp2s0 and the VLANs 300-380 on the host's enp3s0. To save myself from configuring all VLANs on the KVM host, I'd like to hand the entire

Hi, I'm running CentOS on all kinds of setups: servers, workstations, desktops and laptops. Up until now, I'm only using NetworkManager on laptops, since it makes sense to use it there. On servers and desktop clients, I usually remove it and configure the network "traditionally" by simply editing /etc/sysconfig/network-scripts/ifcfg-whatever, /etc/resolv.conf, /etc/hosts,

Hi, I just migrated my office's server from Slackware64 14.1 to CentOS 7. So far everything's running fine, I just have a few minor details to work out. I removed the firewalld package and replaced it by a simple Iptables script: --8<---------------------------------------------------- #!/bin/sh # # firewall-lan.sh IPT=$(which iptables) MOD=$(which modprobe) SYS=$(which sysctl)

Hi, I'm currently experimenting with CentOS 7 on a couple of installations. I'm reasonably proficient with CentOS 5.x and 6.x. I'd like to manage networking using a more traditional approach (Keep It Simple Stupid). Here's what I tried so far, starting from a minimal install: Install net-tools (to be able to use ifconfig). Get rid of NetworkManager: # yum remove

Hi Laine, thanks for your answer, I really appreciate that. On Wed, Jan 02, 2019 at 11:34:30AM -0500, Laine Stump wrote: > On 12/16/18 4:59 PM, Marc Haber wrote: > > I would like to run a network firewall as a VM on a KVM host. There are > > ~ 25 VLANs delivered to the KVM host on three dedicated links, no LACP > > or other things. I have the VLANs 100-180 on the host's

On 09/08/2016 06:56, Anthony K wrote: > On 08/08/16 21:05, Levente Birta wrote: >> >> But how can I add achieve this only with ip route command ... without >> route? >> Can I add this in any config files (ex: route-enp2s0)? >> > Hi Levente. > > The iproute2 man page for each command is rather well documented on > CentOS 7. For instance, to view the

> On Feb 21, 2019, at 12:00 PM, Warren Young <warren at etr-usa.com> wrote: >> >> remotely talking someone through changing ifcfg-noisenoise via nano is a >> minor nightmare, especially now that Confusing Network Device Naming is >> the default. > > A relevant war story might help here. > > We were upgrading an old CentOS 5 box in the field. They

On 08/09/2016 12:03 PM, John R Pierce wrote: > those are both the same network, and the default gateway is a global > thing. packets forwarded to 192.168.1.1 could use either 192.168.1.12 > or .13, as they are all the same. in reality, they will use the first > match they find. Generally, but not necessarily. What Birta is trying to accomplish is called

On Tue, Feb 11, 2020 at 8:12 AM Jonathan Billings <billings at negate.org> wrote: > > On Tue, Feb 11, 2020 at 06:11:04AM +0100, Simon Matter via CentOS wrote: > > Unfortunately, instead of fixing/refactoring the whole bash networking > > script mess, another new project was started instead, called > > systemd-networkd :-) > > Actually, I'm sad that

Hi, I've done my fair share of CentOS 7 installations, but this is the first time I have this kind of weird problem. Here goes. In my office I have a battered Dell Optiplex 320 PC with two NICs that I'm using as a bare metal sandbox server for testing purposes. The CentOS 7 installer sees the connected network card as eth0. But after the first reboot, the interface comes up as eth1.

Le 11/02/2020 ? 14:11, Jonathan Billings a ?crit?: > I've mentioned on this list countless times about how NetworkManager > is actually pretty good for a general server. Automatic link > detection and activation/deactivation, a dispatch service on link > activation/deactivation, support for bringing up secondary interfaces > after a primary goes up, a dbus interface for