search for: netmask0

...-eth0:192 and in accordance with the instructions obtained at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/sec-networkscripts-static-routes-network-netmask-directives.html I added these directives to the route-eth0:192 file: ADDRESS0=192.168.6.9 NETMASK0=255.255.255.0 GATEWAY0=192.168.6.1 However, when I restart the network service I see this: service network restart Shutting down interface eth0: [ OK ] Shutting down loopback interface: [ OK ] Bringing up loopback interface:...

...gt;> >> http://www.cyberciti.biz/tips/configuring-static-routes-in-debian-or-red-hat-linux-systems.html >> >> where it says to add to ifcfg-eth0: >> >> 192.168.128.0/17 via 40.53.24.3 That?s only for RHEL 7: http://goo.gl/AtjIyI > ADDRESS0=192.168.128.0 > NETMASK0=255.255.128.0 > GATEWAY0=40.53.24.3 This is the scheme used in prior versions of RHEL.

On Thu, February 19, 2015 12:33, Les Mikesell wrote: > On Thu, Feb 19, 2015 at 9:48 AM, James B. Byrne > <byrnejb at harte-lyne.ca> wrote: >> >>> I added these directives to the route-eth0:192 file: >>> >>> ADDRESS0=192.168.6.9 >>> NETMASK0=255.255.255.0 >>> GATEWAY0=192.168.6.1 >>> >> >> Which should have been: >> >> ADDRESS0=192.168.6.0 >> >> NETMASK0=255.255.255.0 >> GATEWAY0=192.168.6.1 >> > > But it still doesn't matter. Your netmask in the ifcfg- file a...

...expected rather than "19/27"..2.0 Bringing up interface xenbr1: Error: either "to" is duplicate, or "192.168.2.3" is a garbage. "ringing up interface xenbr1: Cannot find device "xenbr1 route-xenbr1: #192.168.2.0/27 via 192.168.2.3 #GATEWAY0=192.168.2.3 #NETMASK0=255.255.255.224 #ADDRESS0=192.168.2.10 #default 192.168.2.3 dev xenbr1 192.168.2.0/27 via 192.168.2.3 dev xenbr1 (the commented out are from various tries, corresponding to the errors above) This is on a xen kernel. 2.6.18-128.1.6.el5xen Kai -- Kai Sch?tzl, Berlin, Germany Get your web at C...

On Thu, February 19, 2015 10:19, James B. Byrne wrote: > > I added these directives to the route-eth0:192 file: > > ADDRESS0=192.168.6.9 > NETMASK0=255.255.255.0 > GATEWAY0=192.168.6.1 > Which should have been: ADDRESS0=192.168.6.0 NETMASK0=255.255.255.0 GATEWAY0=192.168.6.1 Sigh. -- *** E-Mail is NOT a SECURE channel *** James B. Byrne mailto:ByrneJB at Harte-Lyne.ca Harte & Lyne Limited...

Hi, I'd want to configure persistent static routes, ie in config files, but I can't configure static routes, I tested: [root at centos7 ~]# cat /etc/sysconfig/network-scripts/routes-enp0s3 ADDRESS0=10.10.10.0 NETMASK0=255.255.255.0 GATEWAY0=192.168.1.1 logs says nothing: ago 27 15:38:29 centos7.vhgroup.corp NetworkManager[2299]: <info> Activation (enp0s3) Stage 5 of 5 (IPv4 Commit) complete. ago 27 15:38:29 centos7.vhgroup.corp NetworkManager[2299]: <info> (enp0s3): device state change: ip-check -&...

...th1 # Please read /usr/share/doc/initscripts-*/sysconfig.txt # for the documentation of these parameters. IPV6INIT=no ONBOOT=yes USERCTL=no PEERDNS=yes TYPE=Ethernet DEVICE=eth1 HWADDR=00:60:08:3e:0a:d1 BOOTPROTO=none NETMASK=255.255.255.0 IPADDR=192.168.1.1 and route-eth1 GATEWAY0=192.168.1.1 NETMASK0=255.255.255.0 ADDRESS0=192.168.1.0 When I run ifup eth1 , follow messages show me. ifup eth1 RTNETLINK answers: File exists When I run command route -n , follow messages show me. # route -n 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 169.254.0.0 0.0.0.0...

...xternal routing falls apart. /etc/sysconfig/network-scripts/rule-eth2 from 173.11.51.45 table Cable /etc/sysconfig/network-scripts/rule-eth3 from 67.152.166.2 table T1 /etc/sysconfig/network-scripts/route-eth0 GATEWAY1=192.168.4.3 NETMASK1=255.255.255.0 ADDRESS1=192.168.6.0 GATEWAY0=192.168.4.2 NETMASK0=255.255.255.0 ADDRESS0=192.168.5.0 /etc/sysconfig/network-scripts/route-eth1 GATEWAY0=192.168.4.1 NETMASK0=255.255.255.0 ADDRESS0=192.168.4.0 /etc/sysconfig/network-scripts/route-eth2 173.11.51.44/30 dev eth2 proto kernel scope link src 173.11.51.45 table Cable 173.11.51.44/30 dev eth2 src 173.1...

I know how to use 'ip' to set up a static route, e.g.: ip route add 192.168.128.0/17 via 40.53.24.3 dev eth0 But if you reboot or restart network, you loose this. Thus you have to make it persistant. I found: http://www.cyberciti.biz/tips/configuring-static-routes-in-debian-or-red-hat-linux-systems.html where it says to add to ifcfg-eth0: 192.168.128.0/17 via 40.53.24.3 But this

...routes-in-debian-or-red-hat-linux-systems.html > > where it says to add to ifcfg-eth0: > > 192.168.128.0/17 via 40.53.24.3 > Create the file /etc/sysconfig/network-scripts/route-eth0 Add the following for each static route, incrementing the numeric for each: ADDRESS0=192.168.128.0 NETMASK0=255.255.128.0 GATEWAY0=40.53.24.3 > But this did not work after the interface was restarted. So what is the > proper to set up persistant static routes? > > > _______________________________________________ > CentOS mailing list > CentOS at centos.org > http://lists.cent...

...t; >>> where it says to add to ifcfg-eth0: >>> >>> 192.168.128.0/17 via 40.53.24.3 > > That?s only for RHEL 7: http://goo.gl/AtjIyI Aside from being irritating, that's just wrong. I'm using that syntax on Centos5, >> ADDRESS0=192.168.128.0 >> NETMASK0=255.255.128.0 >> GATEWAY0=40.53.24.3 > > This is the scheme used in prior versions of RHEL. I think both types of syntax will work in all versions. The GUI tools do the latter form. -- Les Mikesell lesmikesell at gmail.com

Hello List, I have one network card and added two IP-Adresses to it: eth1 192.168.1.1/24 eth1:1 10.1.2.3/24 a want to use static routes on device eth1:1 and added one in /etc/sysconfig/network-scripts/route-eth1:1: GATEWAY0=10.1.2.4 ADDRESS0=10.2.2.0 NETMASK0=255.255.255.0 What the network-script should execute in background is: ip route add 10.2.2.0/24 via 10.1.2.4 dev eth1 but it executes ip route add 10.2.2.0/24 via 10.1.2.4 dev eth1:1 BUT: "eth1:1" is in the "ip" command not working, "ip" throws an error ("Cann...

Hi, I'm working with the iproute2/iptables toolset on my CentOS4 server to create custom routing rules. However, I'm a bit at a loss how to create these permanently so that they are automatically reloaded upon reboot of the server. I know that iptables has a config file in /etc/sysconfig/iptables that is loaded by /etc/init.d/iptables startup script. Is there anything that works

...t wrong. I'm using that > syntax on Centos5, AH, I think I see what I did wrong. I put that line in the ifcfg-eth0 when according to this page, it goes in the route-eth0 just like the old format. I will give that a try tomorrow... > >>> ADDRESS0=192.168.128.0 >>> NETMASK0=255.255.128.0 >>> GATEWAY0=40.53.24.3 >> This is the scheme used in prior versions of RHEL. > I think both types of syntax will work in all versions. The GUI tools > do the latter form. >

Is it possible to have a route stick in the kernel, even if device it points to goes to roller coaster up and down drive. For example. I have an ADSL modem and am doing VPN over it. There's a route needed for VPN added like this: ip route add 192.168.1.0/24 via 1.2.3.4 src 192.168.2.1 There are two problems with it: a) if ADSL link is down when above command is executed, the route