similar to: Gateway question

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 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

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 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, You can define your default gateway in "/etc/sysconfig/network" file, GATEWAY="192.168.1.1" After that, restart network services. # systemctl restart network --Regards Ashishkumar S. Yadav On Mon, Aug 8, 2016 at 4:35 PM, Levente Birta <blevi.linux at gmail.com> wrote: > Hi > > There is a Centos 7 up-to-date box with 2 interfaces, let's say >

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 10/08/16 16:29, Levente Birta wrote: > And as I said this problem is resolved too ... I asked for another way > to achieve this When you add a default gateway with: route add default gw 192.168.1.1 dev enp3s0 you'll note that you now have 2 routes with the same metric of 0 (use route -n to see the metric field - couldn't get ip route to show me the metric). When using ip

On 8/9/2016 11:42 AM, Birta Levente wrote: > So, again: > Centos 7 > 2 NICs > enp2s0-192.168.1.12 > enp3s0-192.168.1.13 > default gateway on enp2s0 is 192.168.1.1, defined in > /etc/sysconfig/network > > Which other way (preferred with "ip route") can I add this, but: > #route add default gw 192.168.1.1 dev enp3s0 those are both the same network, and the

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

Hi, I'm just migrating some stuff from Slackware Linux to CentOS, and I have a question about the orthodox way of configuring a network connection. On a desktop or workstation, I usually get rid of NetworkManager: # systemctl stop NetworkManager # yum remove NetworkManager Then I edit the /etc/sysconfig/network-scripts/ifcfg-XXXXX file corresponding to my network interface. Here's

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 have a supermicro server, motherboard is with C612 chipset and beside that with LSI3108 raid controller integrated. Two Intel SSD DC S3710 200GB. OS: Centos 7.1 up to date. My problem is that the Intel SSD Data Center Tool (ISDCT) does not recognize the SSD drives when they connected to the standard S-ATA ports on the motherboard, but through the LSI raid controller is working. Does

> 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

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

Hi all Can someone explain me this: ifcfg-eth0-range1: ONBOOT="yes" IPADDR_START="192.168.1.48" IPADDR_END="192.168.1.55" CLONENUM_START="1" Why Bcast is 192.168.1.51 and why Mask is 255.255.255.252 ? OS: Centos 6.3/64bit Thanks Levi # ifconfig eth0:1 Link encap:Ethernet HWaddr 00:9C:02:99:FA:00 inet addr:192.168.1.48

Hi How can I convert all virtual mailboxes from maildir to mdbox? Manually, one by one, working, but I have a lot ... Virtual users and domains stored in sql database. Thats what I want: mail_location = maildir:/var/vmail/%d/%n/Maildir to mail_location = mdbox:/var/vmail/%d/%n/mdbox Thanks Levi -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s

On 11/19/2015 12:54 AM, Birta Levente wrote: > I tried today morning on RHEL too ... > The ISDCT tool does not work on supported OS neither I think everyone focused on your problem with the vendor, who didn't support your OS, and ignored the fact that the tool worked when the drives were connected to a secondary controller. The OS never caused a problem for the tool, only for the

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

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

On 18/11/2015 16:37, Eero Volotinen wrote: > What is Intel SSD Data Center Tool (ISDCT) ? " This tool provides a command line interface for interacting with and issuning commands to Intel SSD Data Center devices. It is intended to configure and check the state of Intel PCIe SSDs and SATA SSDs for a production environment. " > Does Linux kernel detect disk on sata ports? >