From: Serge L. <ser...@gm...> - 2010-08-29 06:51:56
|
Heiko, Yes, thank to my current job I have a LOT of enthusiasm to make something useful :) What do you think about the following solution? every ifcfg-XXXX can contain routes in form of the lines ROUTE="default via xxx.xxx.xxx.xxx" ROUTE="blackhole 10.0.0.0/8" ROUTE="10.1.0.0/16 dev ppp0" ROUTE="192.168.1.0/24 via xxx.xxx.xxx.xxx dev $DEVICE" etc. actually, any "ip route" command is allowed, because the statement is the command itself, but without prefix "ip route add". We will add prefix "ip route add" for each ROUTE statement on 'start' and "ip route del" for each statement on 'stop'. $DEVICE is already defined at the moment of execution (it will be the name of this interface) , so we can use it as well. It seems to be simple and flexible enough. PS. Sorry for the broken thread - I copied the message from web, because ISP ( where my email account was) doesn't accept my credential anymore :( Serge > I hate to delay the release of 1.4 further, but I think you are right. > Would you have time to add it? > > Heiko > >> -----Original Message----- >> From: Serge Leschinsky [mailto:fi...@in...] >> Sent: Friday, August 27, 2010 7:49 PM >> To: dev...@li... >> Subject: [Devil-linux-develop] network configuration script - add >> routes >> >> Hi, >> >> there is a new bug: >> > >> ======================================================= >> =============== >> > Summary: Cannot add blackhole route >> > Description: >> > There is no way to add blackhole, unreachable etc. type of routes >> > using configuration scripts. >> > >> ======================================================= >> =============== >> >> I have taken a look at ROUTE section in network script and have to >> admit >> that old 'route' command doesn't allow us to add new sophisticated >> routes. The main idea is to replace 'route' by 'ip route', but it >> obviously >> causes the config format modification ('ip route' has much more >> options). On the other hand, release 1.4 is a good time to change >> things, >> because 1.2 -> 1.4 migration is a big deal anyway. >> >> So, please advise :) >> >> Serge >> >> >> |
From: Serge L. <ser...@gm...> - 2010-08-30 02:43:46
Attachments:
network.patch
|
Hi, OK, the patch for network script is in the attachment. If this approach is OK, I'll add 'RULE' keyword to work with additional routing tables. The suggest modification of the documentation is below: ######################################################## # ROUTE=" ...... " # where ROUTE is a key word and the line with ROUTE # should not have spaces between the beginning of # the line and the keyword # and route statement is a any valid "ip route" # command, without "ip route add" prefix - it will # be added automatically # # IPV6ROUTE="...." # IPV6ROUTE keyword can be used for ipv6 routes. # # $DEVICE can be used to directly specify the interface # ###### samples for several possible scenarios # # route to network 192.168.254.0/255.255.255.0 via gateway 10.90.1.252 #ROUTE="192.168.254.0/255.255.255.0 via 10.90.1.252" # or #ROUTE="192.168.254.0/24 via 10.90.1.252" # # # route to host 192.168.3.1 via 10.90.1.252 #ROUTE="192.168.3.0/32 via 10.90.1.252" # # route to network that is also reachable via this interface #ROUTE="192.168.3.0/24 dev $DEVICE" # # special routes #ROUTE="unreachable 10.0.0.0/8" #ROUTE="blackhole 192.168.1.0/24" # # add as many ROUTE="...." lines as you need routes # # the next line shows how to set the default gateway #ROUTE="$default via 10.90.1.1". # Sincerely, Serge On 08/28/2010 11:38 PM, Serge Leschinsky wrote: > Heiko, > > Yes, thank to my current job I have a LOT of enthusiasm to make something useful :) > > What do you think about the following solution?: > > every ifcfg-XXXX can contain routes in form of lines > > ROUTE="default via xxx.xxx.xxx.xxx" > ROUTE="blackhole 10.0.0.0/8" > ROUTE="10.1.0.0/16 dev ppp0" > ROUTE="192.168.1.0/24 via xxx.xxx.xxx.xxx dev $DEVICE" > > etc. actually, any "ip route" command is allowed, because the statement is the > command itself, but without prefix "ip route add". > > We will add prefix "ip route add" for each ROUTE statement on 'start' and "ip > route del" for each statement on 'stop'. > > $DEVICE is already defined at the moment of execution (it will be the name of > this interface) , so we can use it as well. > > It seems to be simple and flexible enough. > > PS. Sorry for the broken thread - I copied the message from web, because ISP ( > where my email account was) doesn't accept my credential anymore :( > > > Serge > > > >> I hate to delay the release of 1.4 further, but I think you are right. >> Would you have time to add it? >> >> Heiko >> >>> -----Original Message----- >>> From: Serge Leschinsky [mailto:fi...@in...] >>> Sent: Friday, August 27, 2010 7:49 PM >>> To: dev...@li... >>> Subject: [Devil-linux-develop] network configuration script - add >>> routes >>> >>> Hi, >>> >>> there is a new bug: >>>> >>> ======================================================= >>> =============== >>>> Summary: Cannot add blackhole route >>>> Description: >>>> There is no way to add blackhole, unreachable etc. type of routes >>>> using configuration scripts. >>>> >>> ======================================================= >>> =============== >>> >>> I have taken a look at ROUTE section in network script and have to >>> admit >>> that old 'route' command doesn't allow us to add new sophisticated >>> routes. The main idea is to replace 'route' by 'ip route', but it >>> obviously >>> causes the config format modification ('ip route' has much more >>> options). On the other hand, release 1.4 is a good time to change >>> things, >>> because 1.2 -> 1.4 migration is a big deal anyway. >>> >>> So, please advise :) >>> >>> Serge >>> >>> >>> > |
From: Serge L. <ser...@gm...> - 2010-08-30 04:59:21
Attachments:
network.patch
|
Extended version: ######################################################## # ROUTE=" ......" # where ROUTE is a key word and the line with ROUTE # should not have spaces between the beginning of # the line and the keyword # Route statement is any valid "ip route" command, # without "ip route add" prefix - it will be added # automatically # # IPV6ROUTE="...." # IPV6ROUTE keyword can be used for ipv6 routes. # # RULE=" ...... " # where RULE is a keyword and the line with RULE # should not have spaces between the beginning of # the line and the keyword # Rule statement is any valid "ip rule" command, # without "ip rule add" prefix - it will be added # automatically # # $DEVICE can be used to directly specify the interface # ###### samples for several possible scenarios # # route to network 192.168.254.0/255.255.255.0 via gateway 10.90.1.252 #ROUTE="192.168.254.0/255.255.255.0 via 10.90.1.252" # or #ROUTE="192.168.254.0/24 via 10.90.1.252" # # # route to host 192.168.3.1 via 10.90.1.252 #ROUTE="192.168.3.0/32 via 10.90.1.252" # # route to network that is also reachable via this interface #ROUTE="192.168.3.0/24 dev $DEVICE" # # special routes #ROUTE="unreachable 10.0.0.0/8" #ROUTE="blackhole 192.168.1.0/24" # # add as many ROUTE="...." lines as you need routes # # the next line shows how to set the default gateway #ROUTE="default via 10.90.1.1". # ###### advanced routing # make sure additional routing table is created # # echo "500 bypass" >> /etc/iproute2/rt_tables # #ROUTE="default via 1.234.123.1 table bypass" #RULE="from 10.0.0.0/24 table bypass prio 500" #RULE="from 10.0.1.0/24 table bypass prio 600" #RULE="from 10.0.2.123/32 to 10.8.0.0/16 table main prio 400" # Serge On 08/29/2010 07:43 PM, Serge Leschinsky wrote: > Hi, > > OK, the patch for network script is in the attachment. > > If this approach is OK, I'll add 'RULE' keyword to work with additional routing > tables. > > The suggest modification of the documentation is below: > > ######################################################## > # ROUTE=" ...... " > # where ROUTE is a key word and the line with ROUTE > # should not have spaces between the beginning of > # the line and the keyword > # and route statement is a any valid "ip route" > # command, without "ip route add" prefix - it will > # be added automatically > # > # IPV6ROUTE="...." > # IPV6ROUTE keyword can be used for ipv6 routes. > # > # $DEVICE can be used to directly specify the interface > # > ###### samples for several possible scenarios > # > # route to network 192.168.254.0/255.255.255.0 via gateway 10.90.1.252 > #ROUTE="192.168.254.0/255.255.255.0 via 10.90.1.252" > # or > #ROUTE="192.168.254.0/24 via 10.90.1.252" > # > # > # route to host 192.168.3.1 via 10.90.1.252 > #ROUTE="192.168.3.0/32 via 10.90.1.252" > # > # route to network that is also reachable via this interface > #ROUTE="192.168.3.0/24 dev $DEVICE" > # > # special routes > #ROUTE="unreachable 10.0.0.0/8" > #ROUTE="blackhole 192.168.1.0/24" > # > # add as many ROUTE="...." lines as you need routes > # > # the next line shows how to set the default gateway > #ROUTE="$default via 10.90.1.1". > # > > > > Sincerely, > Serge > > On 08/28/2010 11:38 PM, Serge Leschinsky wrote: >> Heiko, >> >> Yes, thank to my current job I have a LOT of enthusiasm to make something useful :) >> >> What do you think about the following solution?: >> >> every ifcfg-XXXX can contain routes in form of lines >> >> ROUTE="default via xxx.xxx.xxx.xxx" >> ROUTE="blackhole 10.0.0.0/8" >> ROUTE="10.1.0.0/16 dev ppp0" >> ROUTE="192.168.1.0/24 via xxx.xxx.xxx.xxx dev $DEVICE" >> >> etc. actually, any "ip route" command is allowed, because the statement is the >> command itself, but without prefix "ip route add". >> >> We will add prefix "ip route add" for each ROUTE statement on 'start' and "ip >> route del" for each statement on 'stop'. >> >> $DEVICE is already defined at the moment of execution (it will be the name of >> this interface) , so we can use it as well. >> >> It seems to be simple and flexible enough. >> >> PS. Sorry for the broken thread - I copied the message from web, because ISP ( >> where my email account was) doesn't accept my credential anymore :( >> >> >> Serge >> >> >> >>> I hate to delay the release of 1.4 further, but I think you are right. >>> Would you have time to add it? >>> >>> Heiko >>> >>>> -----Original Message----- >>>> From: Serge Leschinsky [mailto:fi...@in...] >>>> Sent: Friday, August 27, 2010 7:49 PM >>>> To: dev...@li... >>>> Subject: [Devil-linux-develop] network configuration script - add >>>> routes >>>> >>>> Hi, >>>> >>>> there is a new bug: >>>>> >>>> ======================================================= >>>> =============== >>>>> Summary: Cannot add blackhole route >>>>> Description: >>>>> There is no way to add blackhole, unreachable etc. type of routes >>>>> using configuration scripts. >>>>> >>>> ======================================================= >>>> =============== >>>> >>>> I have taken a look at ROUTE section in network script and have to >>>> admit >>>> that old 'route' command doesn't allow us to add new sophisticated >>>> routes. The main idea is to replace 'route' by 'ip route', but it >>>> obviously >>>> causes the config format modification ('ip route' has much more >>>> options). On the other hand, release 1.4 is a good time to change >>>> things, >>>> because 1.2 -> 1.4 migration is a big deal anyway. >>>> >>>> So, please advise :) >>>> >>>> Serge >>>> >>>> >>>> >> > |
From: Serge L. <ser...@gm...> - 2010-08-30 07:52:44
Attachments:
network.patch
|
the final final version: Summary: - added all types of route - added rules - added tunnel interface configuration Serge ------------------------------------------------------------------------- cat ifcfg-eth0.sample: # # example for a "normal" INTERFACE with no VLANs and no BRIDGING # DHCP=no #DHCP=yes #DHCP=server # options passed directly to dhcpcd on startup #DHCP_OPTIONS="" ONBOOT=yes DEVICE=eth0 IP=10.90.1.200 NETMASK=255.255.255.0 #BROADCAST=10.90.1.255 #MAC= MODULE=pcnet32 #MODULE_OPTS= # ######################################################## # ROUTE=" ...... " # where ROUTE is a key word and the line with ROUTE # should not have spaces between the beginning of # the line and the keyword # Route statement is a any valid "ip route"# command, # without "ip route add" prefix - it will be added # automatically # # IPV6ROUTE="...." # IPV6ROUTE keyword can be used for ipv6 routes. # # RULE=" ...... " # where RULE is a key word and the line with RULE # should not have spaces between the beginning of # the line and the keyword # Rule statement is a any valid "ip rule" command, # without "ip rule add" prefix - it will be added # automatically # # $DEVICE can be used to directly specify the interface # ###### samples for several possible scenarios # # route to network 192.168.254.0/255.255.255.0 via gateway 10.90.1.252 #ROUTE="192.168.254.0/255.255.255.0 via 10.90.1.252" # or #ROUTE="192.168.254.0/24 via 10.90.1.252" # # # route to host 192.168.3.1 via 10.90.1.252 #ROUTE="192.168.3.0/32 via 10.90.1.252" # # route to network that is also reachable via this interface #ROUTE="192.168.3.0/24 dev $DEVICE" # # special routes #ROUTE="unreachable 10.0.0.0/8" #ROUTE="blackhole 192.168.1.0/24" # # add as many ROUTE="...." lines as you need routes # # the next line shows how to set the default gateway #ROUTE="default via 10.90.1.1". # ###### advanced routing # make sure additional routing table is created # # echo "500 bypass" >> /etc/iproute2/rt_tables # #ROUTE="default via 1.234.123.1 table bypass" #RULE="from 10.0.0.0/24 table bypass prio 500" #RULE="from 10.0.1.0/24 table bypass prio 600" #RULE="from 10.0.2.123/32 to 10.8.0.0/16 table main prio 400" # ------------------------------------------------------------------------- cat ifcfg-tun0.sample: # # example for a tunnel INTERFACE # ONBOOT=yes TUNNEL=yes # bind the tunnel to the device DEVICE so that tunneled packets # will only be routed via this device and will not be able to escape # to another device when the route to endpoint changes. #DEVICE=eth4 # set the fixed local address for tunneled packets. LOCAL=10.90.1.200 # set the remote endpoint of the tunnel. REMOTE=1.2.3.204 # Available modes depend on the encapsulating address family. # Modes for IPv4 encapsulation available: ipip, sit, isatap and gre. # Modes for IPv6 encapsulation available: ip6ip6, ipip6 and any. MODE=ipip # addtional tunnel options if any TUN_OPTS="" |
From: Heiko Z. <he...@zu...> - 2010-08-30 15:32:34
|
Seems good to me. Let's get it in CVS so we can have more testers. I'm still working on updating all the software packages Alby mentioned, including a couple of fixes to the script he provided. Heiko Quoting Serge Leschinsky <ser...@gm...>: > the final final version: > > Summary: > > - added all types of route > - added rules > - added tunnel interface configuration > > Serge > > > ------------------------------------------------------------------------- > cat ifcfg-eth0.sample: > # > # example for a "normal" INTERFACE with no VLANs and no BRIDGING > # > DHCP=no > #DHCP=yes > #DHCP=server > # options passed directly to dhcpcd on startup > #DHCP_OPTIONS="" > ONBOOT=yes > DEVICE=eth0 > IP=10.90.1.200 > NETMASK=255.255.255.0 > #BROADCAST=10.90.1.255 > #MAC= > MODULE=pcnet32 > #MODULE_OPTS= > # > > ######################################################## > # ROUTE=" ...... " > # where ROUTE is a key word and the line with ROUTE > # should not have spaces between the beginning of > # the line and the keyword > # Route statement is a any valid "ip route"# command, > # without "ip route add" prefix - it will be added > # automatically > # > # IPV6ROUTE="...." > # IPV6ROUTE keyword can be used for ipv6 routes. > # > # RULE=" ...... " > # where RULE is a key word and the line with RULE > # should not have spaces between the beginning of > # the line and the keyword > # Rule statement is a any valid "ip rule" command, > # without "ip rule add" prefix - it will be added > # automatically > # > # $DEVICE can be used to directly specify the interface > # > ###### samples for several possible scenarios > # > # route to network 192.168.254.0/255.255.255.0 via gateway 10.90.1.252 > #ROUTE="192.168.254.0/255.255.255.0 via 10.90.1.252" > # or > #ROUTE="192.168.254.0/24 via 10.90.1.252" > # > # > # route to host 192.168.3.1 via 10.90.1.252 > #ROUTE="192.168.3.0/32 via 10.90.1.252" > # > # route to network that is also reachable via this interface > #ROUTE="192.168.3.0/24 dev $DEVICE" > # > > # special routes > #ROUTE="unreachable 10.0.0.0/8" > #ROUTE="blackhole 192.168.1.0/24" > # > # add as many ROUTE="...." lines as you need routes > # > # the next line shows how to set the default gateway > #ROUTE="default via 10.90.1.1". > # > ###### advanced routing > # make sure additional routing table is created > # > # echo "500 bypass" >> /etc/iproute2/rt_tables > # > #ROUTE="default via 1.234.123.1 table bypass" > #RULE="from 10.0.0.0/24 table bypass prio 500" > #RULE="from 10.0.1.0/24 table bypass prio 600" > #RULE="from 10.0.2.123/32 to 10.8.0.0/16 table main prio 400" > # > > ------------------------------------------------------------------------- > cat ifcfg-tun0.sample: > # > # example for a tunnel INTERFACE > # > ONBOOT=yes > TUNNEL=yes > > # bind the tunnel to the device DEVICE so that tunneled packets > # will only be routed via this device and will not be able to escape > # to another device when the route to endpoint changes. > #DEVICE=eth4 > > # set the fixed local address for tunneled packets. > LOCAL=10.90.1.200 > > # set the remote endpoint of the tunnel. > REMOTE=1.2.3.204 > > # Available modes depend on the encapsulating address family. > # Modes for IPv4 encapsulation available: ipip, sit, isatap and gre. > # Modes for IPv6 encapsulation available: ip6ip6, ipip6 and any. > MODE=ipip > > # addtional tunnel options if any > TUN_OPTS="" > > > -- Regards Heiko Zuerker http://www.devil-linux.org ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. |
From: Serge L. <ser...@gm...> - 2010-08-30 20:08:38
|
Done. Serge On 08/30/2010 08:32 AM, Heiko Zuerker wrote: > Seems good to me. > Let's get it in CVS so we can have more testers. > I'm still working on updating all the software packages Alby > mentioned, including a couple of fixes to the script he provided. > > Heiko > > Quoting Serge Leschinsky <ser...@gm...>: > >> the final final version: >> >> Summary: >> >> - added all types of route >> - added rules >> - added tunnel interface configuration >> >> Serge >> >> >> ------------------------------------------------------------------------- >> cat ifcfg-eth0.sample: >> # >> # example for a "normal" INTERFACE with no VLANs and no BRIDGING >> # >> DHCP=no >> #DHCP=yes >> #DHCP=server >> # options passed directly to dhcpcd on startup >> #DHCP_OPTIONS="" >> ONBOOT=yes >> DEVICE=eth0 >> IP=10.90.1.200 >> NETMASK=255.255.255.0 >> #BROADCAST=10.90.1.255 >> #MAC= >> MODULE=pcnet32 >> #MODULE_OPTS= >> # >> >> ######################################################## >> # ROUTE=" ...... " >> # where ROUTE is a key word and the line with ROUTE >> # should not have spaces between the beginning of >> # the line and the keyword >> # Route statement is a any valid "ip route"# command, >> # without "ip route add" prefix - it will be added >> # automatically >> # >> # IPV6ROUTE="...." >> # IPV6ROUTE keyword can be used for ipv6 routes. >> # >> # RULE=" ...... " >> # where RULE is a key word and the line with RULE >> # should not have spaces between the beginning of >> # the line and the keyword >> # Rule statement is a any valid "ip rule" command, >> # without "ip rule add" prefix - it will be added >> # automatically >> # >> # $DEVICE can be used to directly specify the interface >> # >> ###### samples for several possible scenarios >> # >> # route to network 192.168.254.0/255.255.255.0 via gateway 10.90.1.252 >> #ROUTE="192.168.254.0/255.255.255.0 via 10.90.1.252" >> # or >> #ROUTE="192.168.254.0/24 via 10.90.1.252" >> # >> # >> # route to host 192.168.3.1 via 10.90.1.252 >> #ROUTE="192.168.3.0/32 via 10.90.1.252" >> # >> # route to network that is also reachable via this interface >> #ROUTE="192.168.3.0/24 dev $DEVICE" >> # >> >> # special routes >> #ROUTE="unreachable 10.0.0.0/8" >> #ROUTE="blackhole 192.168.1.0/24" >> # >> # add as many ROUTE="...." lines as you need routes >> # >> # the next line shows how to set the default gateway >> #ROUTE="default via 10.90.1.1". >> # >> ###### advanced routing >> # make sure additional routing table is created >> # >> # echo "500 bypass" >> /etc/iproute2/rt_tables >> # >> #ROUTE="default via 1.234.123.1 table bypass" >> #RULE="from 10.0.0.0/24 table bypass prio 500" >> #RULE="from 10.0.1.0/24 table bypass prio 600" >> #RULE="from 10.0.2.123/32 to 10.8.0.0/16 table main prio 400" >> # >> >> ------------------------------------------------------------------------- >> cat ifcfg-tun0.sample: >> # >> # example for a tunnel INTERFACE >> # >> ONBOOT=yes >> TUNNEL=yes >> >> # bind the tunnel to the device DEVICE so that tunneled packets >> # will only be routed via this device and will not be able to escape >> # to another device when the route to endpoint changes. >> #DEVICE=eth4 >> >> # set the fixed local address for tunneled packets. >> LOCAL=10.90.1.200 >> >> # set the remote endpoint of the tunnel. >> REMOTE=1.2.3.204 >> >> # Available modes depend on the encapsulating address family. >> # Modes for IPv4 encapsulation available: ipip, sit, isatap and gre. >> # Modes for IPv6 encapsulation available: ip6ip6, ipip6 and any. >> MODE=ipip >> >> # addtional tunnel options if any >> TUN_OPTS="" >> >> >> > > > |
From: Heiko Z. <he...@zu...> - 2010-09-05 15:59:26
|
Hey, Seems like we need to update the upgrade script, to set the routes correctly. I just updated all my VMs and I had to fix the default route everywhere. Heiko > -----Original Message----- > From: Serge Leschinsky [mailto:ser...@gm...] > Sent: Monday, August 30, 2010 3:08 PM > To: dev...@li... > Subject: Re: [Devil-linux-develop] network configuration script - add > routes > > Done. > > Serge > > On 08/30/2010 08:32 AM, Heiko Zuerker wrote: > > Seems good to me. > > Let's get it in CVS so we can have more testers. > > I'm still working on updating all the software packages Alby > > mentioned, including a couple of fixes to the script he provided. > > > > Heiko > > > > Quoting Serge Leschinsky <ser...@gm...>: > > > >> the final final version: > >> > >> Summary: > >> > >> - added all types of route > >> - added rules > >> - added tunnel interface configuration > >> > >> Serge > >> > >> > >> --------------------------------------------------------------------- > >> ---- > >> cat ifcfg-eth0.sample: > >> # > >> # example for a "normal" INTERFACE with no VLANs and no BRIDGING > # > >> DHCP=no #DHCP=yes #DHCP=server # options passed directly to > dhcpcd on > >> startup #DHCP_OPTIONS="" > >> ONBOOT=yes > >> DEVICE=eth0 > >> IP=10.90.1.200 > >> NETMASK=255.255.255.0 > >> #BROADCAST=10.90.1.255 > >> #MAC= > >> MODULE=pcnet32 > >> #MODULE_OPTS= > >> # > >> > >> > ####################################################### > # > >> # ROUTE=" ...... " > >> # where ROUTE is a key word and the line with ROUTE # should not > have > >> spaces between the beginning of # the line and the keyword # Route > >> statement is a any valid "ip route"# command, # without "ip route > >> add" prefix - it will be added # automatically # # IPV6ROUTE="...." > >> # IPV6ROUTE keyword can be used for ipv6 routes. > >> # > >> # RULE=" ...... " > >> # where RULE is a key word and the line with RULE # should not have > >> spaces between the beginning of # the line and the keyword # Rule > >> statement is a any valid "ip rule" command, # without "ip rule add" > >> prefix - it will be added # automatically # # $DEVICE can be used to > >> directly specify the interface # ###### samples for several possible > >> scenarios # # route to network 192.168.254.0/255.255.255.0 via > >> gateway 10.90.1.252 > >> #ROUTE="192.168.254.0/255.255.255.0 via 10.90.1.252" > >> # or > >> #ROUTE="192.168.254.0/24 via 10.90.1.252" > >> # > >> # > >> # route to host 192.168.3.1 via 10.90.1.252 > >> #ROUTE="192.168.3.0/32 via 10.90.1.252" > >> # > >> # route to network that is also reachable via this interface > >> #ROUTE="192.168.3.0/24 dev $DEVICE" > >> # > >> > >> # special routes > >> #ROUTE="unreachable 10.0.0.0/8" > >> #ROUTE="blackhole 192.168.1.0/24" > >> # > >> # add as many ROUTE="...." lines as you need routes # # the next line > >> shows how to set the default gateway #ROUTE="default via > 10.90.1.1". > >> # > >> ###### advanced routing > >> # make sure additional routing table is created # # echo "500 > >> bypass" >> /etc/iproute2/rt_tables # #ROUTE="default via > 1.234.123.1 > >> table bypass" > >> #RULE="from 10.0.0.0/24 table bypass prio 500" > >> #RULE="from 10.0.1.0/24 table bypass prio 600" > >> #RULE="from 10.0.2.123/32 to 10.8.0.0/16 table main prio 400" > >> # > >> > >> --------------------------------------------------------------------- > >> ---- > >> cat ifcfg-tun0.sample: > >> # > >> # example for a tunnel INTERFACE > >> # > >> ONBOOT=yes > >> TUNNEL=yes > >> > >> # bind the tunnel to the device DEVICE so that tunneled packets # > >> will only be routed via this device and will not be able to escape # > >> to another device when the route to endpoint changes. > >> #DEVICE=eth4 > >> > >> # set the fixed local address for tunneled packets. > >> LOCAL=10.90.1.200 > >> > >> # set the remote endpoint of the tunnel. > >> REMOTE=1.2.3.204 > >> > >> # Available modes depend on the encapsulating address family. > >> # Modes for IPv4 encapsulation available: ipip, sit, isatap and gre. > >> # Modes for IPv6 encapsulation available: ip6ip6, ipip6 and any. > >> MODE=ipip > >> > >> # addtional tunnel options if any > >> TUN_OPTS="" > >> > >> > >> > > > > > > > > > ------------------------------------------------------------------------ ------ > This SF.net Dev2Dev email is sponsored by: > > Show off your parallel programming skills. > Enter the Intel(R) Threading Challenge 2010. > http://p.sf.net/sfu/intel-thread-sfd > _______________________________________________ > Devil-linux-develop mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/devil-linux-develop |
From: Serge L. <ser...@gm...> - 2010-09-05 18:28:50
|
Hi Heiko, you are right. The code below converts "old style" routes to "new style" and prints new ROUTE without modification. Can we use it as a template for upgrade script? # cat ./test ######### Possible route configuration ######### # OLD ROUTES ROUTE="$ROUTE 192.168.254.0/255.255.255.0:10.90.1.252" ROUTE="$ROUTE 192.168.3.0:10.90.1.252" ROUTE="$ROUTE default/0:10.90.1.1" ROUTE="$ROUTE 192.168.3.0/255.255.255.0" ROUTE="$ROUTE 192.168.5.7" # NEW ROUTES ROUTE="192.168.254.X/255.255.255.0 via 10.90.1.252 " ROUTE="192.168.3.X via 10.90.1.252 " ROUTE="default via 10.90.1.X " ROUTE="192.168.3.X/255.255.255.0 dev $DEVICE" ROUTE="192.168.5.X dev $DEVICE" ############################################### grep "^ROUTE=" ./$0 | while read line; do unset ROUTE net gw eval $line if echo $ROUTE | grep "via\|dev" > /dev/null 2>&1; then echo $line; continue ; fi if echo $ROUTE | grep ":" > /dev/null 2>&1; then net=$(echo $ROUTE | cut -d':' -f1) gw=$(echo $ROUTE | cut -d':' -f2) else net=$(echo $ROUTE) # to remove spaces fi #echo $net $gw $dev # fixes if echo $net | grep default > /dev/null 2>&1; then net="default"; fi if [ x"$gw" == "x" ]; then dev="dev \$DEVICE"; else gw="via $gw"; fi echo "ROUTE=\"$net $gw $dev\"" done On 09/05/2010 08:59 AM, Heiko Zuerker wrote: > Hey, > > Seems like we need to update the upgrade script, to set the routes > correctly. > I just updated all my VMs and I had to fix the default route everywhere. > > Heiko > >> -----Original Message----- >> From: Serge Leschinsky [mailto:ser...@gm...] >> Sent: Monday, August 30, 2010 3:08 PM >> To: dev...@li... >> Subject: Re: [Devil-linux-develop] network configuration script - add >> routes >> >> Done. >> >> Serge >> >> On 08/30/2010 08:32 AM, Heiko Zuerker wrote: >>> Seems good to me. >>> Let's get it in CVS so we can have more testers. >>> I'm still working on updating all the software packages Alby >>> mentioned, including a couple of fixes to the script he provided. >>> >>> Heiko >>> >>> Quoting Serge Leschinsky <ser...@gm...>: >>> >>>> the final final version: >>>> >>>> Summary: >>>> >>>> - added all types of route >>>> - added rules >>>> - added tunnel interface configuration >>>> >>>> Serge >>>> >>>> >>>> > --------------------------------------------------------------------- >>>> ---- >>>> cat ifcfg-eth0.sample: >>>> # >>>> # example for a "normal" INTERFACE with no VLANs and no BRIDGING >> # >>>> DHCP=no #DHCP=yes #DHCP=server # options passed directly to >> dhcpcd on >>>> startup #DHCP_OPTIONS="" >>>> ONBOOT=yes >>>> DEVICE=eth0 >>>> IP=10.90.1.200 >>>> NETMASK=255.255.255.0 >>>> #BROADCAST=10.90.1.255 >>>> #MAC= >>>> MODULE=pcnet32 >>>> #MODULE_OPTS= >>>> # >>>> >>>> >> ####################################################### >> # >>>> # ROUTE=" ...... " >>>> # where ROUTE is a key word and the line with ROUTE # should not >> have >>>> spaces between the beginning of # the line and the keyword # Route >>>> statement is a any valid "ip route"# command, # without "ip route >>>> add" prefix - it will be added # automatically # # IPV6ROUTE="...." >>>> # IPV6ROUTE keyword can be used for ipv6 routes. >>>> # >>>> # RULE=" ...... " >>>> # where RULE is a key word and the line with RULE # should not have >>>> spaces between the beginning of # the line and the keyword # Rule >>>> statement is a any valid "ip rule" command, # without "ip rule add" >>>> prefix - it will be added # automatically # # $DEVICE can be used > to >>>> directly specify the interface # ###### samples for several > possible >>>> scenarios # # route to network 192.168.254.0/255.255.255.0 via >>>> gateway 10.90.1.252 >>>> #ROUTE="192.168.254.0/255.255.255.0 via 10.90.1.252" >>>> # or >>>> #ROUTE="192.168.254.0/24 via 10.90.1.252" >>>> # >>>> # >>>> # route to host 192.168.3.1 via 10.90.1.252 >>>> #ROUTE="192.168.3.0/32 via 10.90.1.252" >>>> # >>>> # route to network that is also reachable via this interface >>>> #ROUTE="192.168.3.0/24 dev $DEVICE" >>>> # >>>> >>>> # special routes >>>> #ROUTE="unreachable 10.0.0.0/8" >>>> #ROUTE="blackhole 192.168.1.0/24" >>>> # >>>> # add as many ROUTE="...." lines as you need routes # # the next > line >>>> shows how to set the default gateway #ROUTE="default via >> 10.90.1.1". >>>> # >>>> ###### advanced routing >>>> # make sure additional routing table is created # # echo "500 >>>> bypass" >> /etc/iproute2/rt_tables # #ROUTE="default via >> 1.234.123.1 >>>> table bypass" >>>> #RULE="from 10.0.0.0/24 table bypass prio 500" >>>> #RULE="from 10.0.1.0/24 table bypass prio 600" >>>> #RULE="from 10.0.2.123/32 to 10.8.0.0/16 table main prio 400" >>>> # >>>> >>>> > --------------------------------------------------------------------- >>>> ---- >>>> cat ifcfg-tun0.sample: >>>> # >>>> # example for a tunnel INTERFACE >>>> # >>>> ONBOOT=yes >>>> TUNNEL=yes >>>> >>>> # bind the tunnel to the device DEVICE so that tunneled packets # >>>> will only be routed via this device and will not be able to escape > # >>>> to another device when the route to endpoint changes. >>>> #DEVICE=eth4 >>>> >>>> # set the fixed local address for tunneled packets. >>>> LOCAL=10.90.1.200 >>>> >>>> # set the remote endpoint of the tunnel. >>>> REMOTE=1.2.3.204 >>>> >>>> # Available modes depend on the encapsulating address family. >>>> # Modes for IPv4 encapsulation available: ipip, sit, isatap and > gre. >>>> # Modes for IPv6 encapsulation available: ip6ip6, ipip6 and any. >>>> MODE=ipip >>>> >>>> # addtional tunnel options if any >>>> TUN_OPTS="" >>>> >>>> >>>> >>> >>> >>> >> >> >> > ------------------------------------------------------------------------ > ------ >> This SF.net Dev2Dev email is sponsored by: >> >> Show off your parallel programming skills. >> Enter the Intel(R) Threading Challenge 2010. >> http://p.sf.net/sfu/intel-thread-sfd >> _______________________________________________ >> Devil-linux-develop mailing list >> Dev...@li... >> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop > > > ------------------------------------------------------------------------------ > This SF.net Dev2Dev email is sponsored by: > > Show off your parallel programming skills. > Enter the Intel(R) Threading Challenge 2010. > http://p.sf.net/sfu/intel-thread-sfd > _______________________________________________ > Devil-linux-develop mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/devil-linux-develop > |
From: Heiko Z. <he...@zu...> - 2010-09-05 19:08:56
|
Yes that would make sense. H. > -----Original Message----- > From: Serge Leschinsky [mailto:ser...@gm...] > Sent: Sunday, September 05, 2010 1:29 PM > To: dev...@li... > Subject: Re: [Devil-linux-develop] network configuration script - add > routes > > Hi Heiko, > > you are right. The code below converts "old style" routes to "new style" > and prints new ROUTE without modification. Can we use it as a template > for upgrade script? > > > # cat ./test > ######### Possible route configuration ######### # OLD ROUTES > > ROUTE="$ROUTE 192.168.254.0/255.255.255.0:10.90.1.252" > ROUTE="$ROUTE 192.168.3.0:10.90.1.252" > ROUTE="$ROUTE default/0:10.90.1.1" > > ROUTE="$ROUTE 192.168.3.0/255.255.255.0" > ROUTE="$ROUTE 192.168.5.7" > > # NEW ROUTES > > ROUTE="192.168.254.X/255.255.255.0 via 10.90.1.252 " > ROUTE="192.168.3.X via 10.90.1.252 " > ROUTE="default via 10.90.1.X " > ROUTE="192.168.3.X/255.255.255.0 dev $DEVICE" > ROUTE="192.168.5.X dev $DEVICE" > > ############################################### > grep "^ROUTE=" ./$0 | while read line; > do > unset ROUTE net gw > eval $line > > if echo $ROUTE | grep "via\|dev" > /dev/null 2>&1; then echo $line; > continue ; fi > > if echo $ROUTE | grep ":" > /dev/null 2>&1; then > net=$(echo $ROUTE | cut -d':' -f1) > gw=$(echo $ROUTE | cut -d':' -f2) > else > net=$(echo $ROUTE) # to remove spaces > fi > > #echo $net $gw $dev > > # fixes > if echo $net | grep default > /dev/null 2>&1; then > net="default"; > fi > > if [ x"$gw" == "x" ]; then > dev="dev \$DEVICE"; > else > gw="via $gw"; > fi > > echo "ROUTE=\"$net $gw $dev\"" > > done > > > On 09/05/2010 08:59 AM, Heiko Zuerker wrote: > > Hey, > > > > Seems like we need to update the upgrade script, to set the routes > > correctly. > > I just updated all my VMs and I had to fix the default route > everywhere. > > > > Heiko > > > >> -----Original Message----- > >> From: Serge Leschinsky [mailto:ser...@gm...] > >> Sent: Monday, August 30, 2010 3:08 PM > >> To: dev...@li... > >> Subject: Re: [Devil-linux-develop] network configuration script - add > >> routes > >> > >> Done. > >> > >> Serge > >> > >> On 08/30/2010 08:32 AM, Heiko Zuerker wrote: > >>> Seems good to me. > >>> Let's get it in CVS so we can have more testers. > >>> I'm still working on updating all the software packages Alby > >>> mentioned, including a couple of fixes to the script he provided. > >>> > >>> Heiko > >>> > >>> Quoting Serge Leschinsky <ser...@gm...>: > >>> > >>>> the final final version: > >>>> > >>>> Summary: > >>>> > >>>> - added all types of route > >>>> - added rules > >>>> - added tunnel interface configuration > >>>> > >>>> Serge > >>>> > >>>> > >>>> > > --------------------------------------------------------------------- > >>>> ---- > >>>> cat ifcfg-eth0.sample: > >>>> # > >>>> # example for a "normal" INTERFACE with no VLANs and no > BRIDGING > >> # > >>>> DHCP=no #DHCP=yes #DHCP=server # options passed directly to > >> dhcpcd on > >>>> startup #DHCP_OPTIONS="" > >>>> ONBOOT=yes > >>>> DEVICE=eth0 > >>>> IP=10.90.1.200 > >>>> NETMASK=255.255.255.0 > >>>> #BROADCAST=10.90.1.255 > >>>> #MAC= > >>>> MODULE=pcnet32 > >>>> #MODULE_OPTS= > >>>> # > >>>> > >>>> > >> > ####################################################### > >> # > >>>> # ROUTE=" ...... " > >>>> # where ROUTE is a key word and the line with ROUTE # should not > >> have > >>>> spaces between the beginning of # the line and the keyword # > Route > >>>> statement is a any valid "ip route"# command, # without "ip route > >>>> add" prefix - it will be added # automatically # # IPV6ROUTE="...." > >>>> # IPV6ROUTE keyword can be used for ipv6 routes. > >>>> # > >>>> # RULE=" ...... " > >>>> # where RULE is a key word and the line with RULE # should not > have > >>>> spaces between the beginning of # the line and the keyword # > Rule > >>>> statement is a any valid "ip rule" command, # without "ip rule add" > >>>> prefix - it will be added # automatically # # $DEVICE can be used > > to > >>>> directly specify the interface # ###### samples for several > > possible > >>>> scenarios # # route to network 192.168.254.0/255.255.255.0 via > >>>> gateway 10.90.1.252 > >>>> #ROUTE="192.168.254.0/255.255.255.0 via 10.90.1.252" > >>>> # or > >>>> #ROUTE="192.168.254.0/24 via 10.90.1.252" > >>>> # > >>>> # > >>>> # route to host 192.168.3.1 via 10.90.1.252 > >>>> #ROUTE="192.168.3.0/32 via 10.90.1.252" > >>>> # > >>>> # route to network that is also reachable via this interface > >>>> #ROUTE="192.168.3.0/24 dev $DEVICE" > >>>> # > >>>> > >>>> # special routes > >>>> #ROUTE="unreachable 10.0.0.0/8" > >>>> #ROUTE="blackhole 192.168.1.0/24" > >>>> # > >>>> # add as many ROUTE="...." lines as you need routes # # the next > > line > >>>> shows how to set the default gateway #ROUTE="default via > >> 10.90.1.1". > >>>> # > >>>> ###### advanced routing > >>>> # make sure additional routing table is created # # echo "500 > >>>> bypass" >> /etc/iproute2/rt_tables # #ROUTE="default via > >> 1.234.123.1 > >>>> table bypass" > >>>> #RULE="from 10.0.0.0/24 table bypass prio 500" > >>>> #RULE="from 10.0.1.0/24 table bypass prio 600" > >>>> #RULE="from 10.0.2.123/32 to 10.8.0.0/16 table main prio 400" > >>>> # > >>>> > >>>> > > --------------------------------------------------------------------- > >>>> ---- > >>>> cat ifcfg-tun0.sample: > >>>> # > >>>> # example for a tunnel INTERFACE > >>>> # > >>>> ONBOOT=yes > >>>> TUNNEL=yes > >>>> > >>>> # bind the tunnel to the device DEVICE so that tunneled packets # > >>>> will only be routed via this device and will not be able to escape > > # > >>>> to another device when the route to endpoint changes. > >>>> #DEVICE=eth4 > >>>> > >>>> # set the fixed local address for tunneled packets. > >>>> LOCAL=10.90.1.200 > >>>> > >>>> # set the remote endpoint of the tunnel. > >>>> REMOTE=1.2.3.204 > >>>> > >>>> # Available modes depend on the encapsulating address family. > >>>> # Modes for IPv4 encapsulation available: ipip, sit, isatap and > > gre. > >>>> # Modes for IPv6 encapsulation available: ip6ip6, ipip6 and any. > >>>> MODE=ipip > >>>> > >>>> # addtional tunnel options if any > >>>> TUN_OPTS="" > >>>> > >>>> > >>>> > >>> > >>> > >>> > >> > >> > >> > > ---------------------------------------------------------------------- > > -- > > ------ > >> This SF.net Dev2Dev email is sponsored by: > >> > >> Show off your parallel programming skills. > >> Enter the Intel(R) Threading Challenge 2010. > >> http://p.sf.net/sfu/intel-thread-sfd > >> _______________________________________________ > >> Devil-linux-develop mailing list > >> Dev...@li... > >> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop > > > > > > ---------------------------------------------------------------------- > > -------- This SF.net Dev2Dev email is sponsored by: > > > > Show off your parallel programming skills. > > Enter the Intel(R) Threading Challenge 2010. > > http://p.sf.net/sfu/intel-thread-sfd > > _______________________________________________ > > Devil-linux-develop mailing list > > Dev...@li... > > https://lists.sourceforge.net/lists/listinfo/devil-linux-develop > > > > > ------------------------------------------------------------------------ ------ > This SF.net Dev2Dev email is sponsored by: > > Show off your parallel programming skills. > Enter the Intel(R) Threading Challenge 2010. > http://p.sf.net/sfu/intel-thread-sfd > _______________________________________________ > Devil-linux-develop mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/devil-linux-develop |
From: Serge L. <ser...@gm...> - 2010-09-05 20:56:48
|
Heiko, how to identify that the network configuration has "new" format to avoid unnecessary processing? What about version in the file? The similar to syslog-ng config file. Something like that: #@version 1 I'll try to do that. Serge On 09/05/2010 12:08 PM, Heiko Zuerker wrote: > Yes that would make sense. > > H. > |
From: Serge L. <ser...@gm...> - 2010-09-05 22:37:23
|
Please test this code: # cat upgrade convert_routes () { local file=$1 grep "^ROUTE=" $file | while read line; do unset ROUTE net gw eval $line if echo $ROUTE | grep "via\|dev" > /dev/null 2>&1; then echo $line; continue ; fi if echo $ROUTE | grep ":" > /dev/null 2>&1; then net=$(echo $ROUTE | cut -d':' -f1) gw=$(echo $ROUTE | cut -d':' -f2) else net=$(echo $ROUTE) # to remove spaces fi #echo $net $gw $dev # fixes if echo $net | grep default > /dev/null 2>&1; then net="default"; fi if [ x"$gw" == "x" ]; then dev="dev \$DEVICE"; else gw="via $gw"; fi echo "ROUTE=\"$net $gw $dev\"" done } # convert network interface configuration to new format for iface in /etc/sysconfig/nic/*; do version=$(awk -F "@version:" ' /^#@version:/ { print $2}' $iface) if [ -n "$version" ]; then # conversion from version "x" # Versions other then '1' was not released yet" continue else cp $iface $iface.conversion echo "#@version: 1" > $iface sed -e 's/^ROUTE/#ROUTE/g' $iface.conversion >> $iface convert_routes $iface.conversion >> $iface rm -f $iface.conversion fi done On 09/05/2010 12:08 PM, Heiko Zuerker wrote: > Yes that would make sense. > > H. > |
From: Heiko Z. <he...@zu...> - 2010-09-06 14:04:46
|
Hey, I blame this question on my hangover... How do you want to me to test, this seems like just a code fragment. Heiko > -----Original Message----- > From: Serge Leschinsky [mailto:ser...@gm...] > Sent: Sunday, September 05, 2010 5:37 PM > To: dev...@li... > Subject: Re: [Devil-linux-develop] network configuration script - add > routes > > Please test this code: > > # cat upgrade > > convert_routes () > { > local file=$1 > grep "^ROUTE=" $file | while read line; > do > unset ROUTE net gw > eval $line > > if echo $ROUTE | grep "via\|dev" > /dev/null 2>&1; then > echo $line; continue ; > fi > > if echo $ROUTE | grep ":" > /dev/null 2>&1; then > net=$(echo $ROUTE | cut -d':' -f1) > gw=$(echo $ROUTE | cut -d':' -f2) > else > net=$(echo $ROUTE) # to remove spaces > fi > > #echo $net $gw $dev > > # fixes > if echo $net | grep default > /dev/null 2>&1; then > net="default"; > fi > > if [ x"$gw" == "x" ]; then > dev="dev \$DEVICE"; > else > gw="via $gw"; > fi > > echo "ROUTE=\"$net $gw $dev\"" > done > > } > > # convert network interface configuration to new format for iface in > /etc/sysconfig/nic/*; do > > version=$(awk -F "@version:" ' /^#@version:/ { print $2}' $iface) > > if [ -n "$version" ]; then > # conversion from version "x" > # Versions other then '1' was not released yet" > continue > else > cp $iface $iface.conversion > echo "#@version: 1" > $iface > sed -e 's/^ROUTE/#ROUTE/g' $iface.conversion >> $iface > convert_routes $iface.conversion >> $iface > rm -f $iface.conversion > fi > > done > > > > On 09/05/2010 12:08 PM, Heiko Zuerker wrote: > > Yes that would make sense. > > > > H. > > > > ------------------------------------------------------------------------ ------ > This SF.net Dev2Dev email is sponsored by: > > Show off your parallel programming skills. > Enter the Intel(R) Threading Challenge 2010. > http://p.sf.net/sfu/intel-thread-sfd > _______________________________________________ > Devil-linux-develop mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/devil-linux-develop |
From: Serge L. <ser...@gm...> - 2010-09-06 18:13:37
|
Heiko, actually, I have tested the code before posting, but it will be great to get feedback before I merge this fragment (which converts network interface files only) into upgrade-config. I'm asking because the price of my mistake in this case is quite big - after upgrade the network might be inaccessible. Any volunteers are welcome :) Serge On 09/06/2010 07:04 AM, Heiko Zuerker wrote: > Hey, > > I blame this question on my hangover... > How do you want to me to test, this seems like just a code fragment. > > Heiko > >> -----Original Message----- >> From: Serge Leschinsky [mailto:ser...@gm...] >> Sent: Sunday, September 05, 2010 5:37 PM >> To: dev...@li... >> Subject: Re: [Devil-linux-develop] network configuration script - add >> routes >> >> Please test this code: >> >> # cat upgrade >> >> convert_routes () >> { >> local file=$1 >> grep "^ROUTE=" $file | while read line; >> do >> unset ROUTE net gw >> eval $line >> >> if echo $ROUTE | grep "via\|dev" > /dev/null 2>&1; then >> echo $line; continue ; >> fi >> >> if echo $ROUTE | grep ":" > /dev/null 2>&1; then >> net=$(echo $ROUTE | cut -d':' -f1) >> gw=$(echo $ROUTE | cut -d':' -f2) >> else >> net=$(echo $ROUTE) # to remove spaces >> fi >> >> #echo $net $gw $dev >> >> # fixes >> if echo $net | grep default > /dev/null 2>&1; then >> net="default"; >> fi >> >> if [ x"$gw" == "x" ]; then >> dev="dev \$DEVICE"; >> else >> gw="via $gw"; >> fi >> >> echo "ROUTE=\"$net $gw $dev\"" >> done >> >> } >> >> # convert network interface configuration to new format for iface in >> /etc/sysconfig/nic/*; do >> >> version=$(awk -F "@version:" ' /^#@version:/ { print $2}' $iface) >> >> if [ -n "$version" ]; then >> # conversion from version "x" >> # Versions other then '1' was not released yet" >> continue >> else >> cp $iface $iface.conversion >> echo "#@version: 1" > $iface >> sed -e 's/^ROUTE/#ROUTE/g' $iface.conversion >> $iface >> convert_routes $iface.conversion >> $iface >> rm -f $iface.conversion >> fi >> >> done >> >> >> >> On 09/05/2010 12:08 PM, Heiko Zuerker wrote: >>> Yes that would make sense. >>> >>> H. >>> >> >> > ------------------------------------------------------------------------ > ------ >> This SF.net Dev2Dev email is sponsored by: >> >> Show off your parallel programming skills. >> Enter the Intel(R) Threading Challenge 2010. >> http://p.sf.net/sfu/intel-thread-sfd >> _______________________________________________ >> Devil-linux-develop mailing list >> Dev...@li... >> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop > > > ------------------------------------------------------------------------------ > This SF.net Dev2Dev email is sponsored by: > > Show off your parallel programming skills. > Enter the Intel(R) Threading Challenge 2010. > http://p.sf.net/sfu/intel-thread-sfd > _______________________________________________ > Devil-linux-develop mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/devil-linux-develop > |
From: Serge L. <ser...@gm...> - 2010-09-06 19:17:37
Attachments:
convert.sh
|
Sorry, I forgot to add that the code is a complete program. As formatting may be broken, I include the code as an attachment. Serge On 09/06/2010 11:13 AM, Serge Leschinsky wrote: > Heiko, > > actually, I have tested the code before posting, but it will be great to get > feedback before I merge this fragment (which converts network interface files > only) into upgrade-config. I'm asking because the price of my mistake in this > case is quite big - after upgrade the network might be inaccessible. > Any volunteers are welcome :) > > Serge > > On 09/06/2010 07:04 AM, Heiko Zuerker wrote: >> Hey, >> >> I blame this question on my hangover... >> How do you want to me to test, this seems like just a code fragment. >> >> Heiko >> >>> -----Original Message----- >>> From: Serge Leschinsky [mailto:ser...@gm...] >>> Sent: Sunday, September 05, 2010 5:37 PM >>> To: dev...@li... >>> Subject: Re: [Devil-linux-develop] network configuration script - add >>> routes >>> >>> Please test this code: >>> >>> # cat upgrade >>> >>> convert_routes () >>> { >>> local file=$1 >>> grep "^ROUTE=" $file | while read line; >>> do >>> unset ROUTE net gw >>> eval $line >>> >>> if echo $ROUTE | grep "via\|dev" > /dev/null 2>&1; then >>> echo $line; continue ; >>> fi >>> >>> if echo $ROUTE | grep ":" > /dev/null 2>&1; then >>> net=$(echo $ROUTE | cut -d':' -f1) >>> gw=$(echo $ROUTE | cut -d':' -f2) >>> else >>> net=$(echo $ROUTE) # to remove spaces >>> fi >>> >>> #echo $net $gw $dev >>> >>> # fixes >>> if echo $net | grep default > /dev/null 2>&1; then >>> net="default"; >>> fi >>> >>> if [ x"$gw" == "x" ]; then >>> dev="dev \$DEVICE"; >>> else >>> gw="via $gw"; >>> fi >>> >>> echo "ROUTE=\"$net $gw $dev\"" >>> done >>> >>> } >>> >>> # convert network interface configuration to new format for iface in >>> /etc/sysconfig/nic/*; do >>> >>> version=$(awk -F "@version:" ' /^#@version:/ { print $2}' $iface) >>> >>> if [ -n "$version" ]; then >>> # conversion from version "x" >>> # Versions other then '1' was not released yet" >>> continue >>> else >>> cp $iface $iface.conversion >>> echo "#@version: 1" > $iface >>> sed -e 's/^ROUTE/#ROUTE/g' $iface.conversion >> $iface >>> convert_routes $iface.conversion >> $iface >>> rm -f $iface.conversion >>> fi >>> >>> done >>> >>> >>> >>> On 09/05/2010 12:08 PM, Heiko Zuerker wrote: >>>> Yes that would make sense. >>>> >>>> H. >>>> >>> >>> >> ------------------------------------------------------------------------ >> ------ >>> This SF.net Dev2Dev email is sponsored by: >>> >>> Show off your parallel programming skills. >>> Enter the Intel(R) Threading Challenge 2010. >>> http://p.sf.net/sfu/intel-thread-sfd >>> _______________________________________________ >>> Devil-linux-develop mailing list >>> Dev...@li... >>> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop >> >> >> ------------------------------------------------------------------------------ >> This SF.net Dev2Dev email is sponsored by: >> >> Show off your parallel programming skills. >> Enter the Intel(R) Threading Challenge 2010. >> http://p.sf.net/sfu/intel-thread-sfd >> _______________________________________________ >> Devil-linux-develop mailing list >> Dev...@li... >> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop >> > |
From: Heiko Z. <he...@zu...> - 2010-09-06 19:48:08
|
It worked on my test machine, but it adds an additional space after the default gateways IP (right before the closing " ) Of course the next step is to correct the code in the "setup" program (which by the way doesn't like the new ifcfg files). Heiko > -----Original Message----- > From: Serge Leschinsky [mailto:ser...@gm...] > Sent: Monday, September 06, 2010 2:17 PM > To: dev...@li... > Subject: Re: [Devil-linux-develop] network configuration script - add > routes > > Sorry, I forgot to add that the code is a complete program. > As formatting may be broken, I include the code as an attachment. > > Serge > > > On 09/06/2010 11:13 AM, Serge Leschinsky wrote: > > Heiko, > > > > actually, I have tested the code before posting, but it will be great > > to get feedback before I merge this fragment (which converts network > > interface files > > only) into upgrade-config. I'm asking because the price of my mistake > > in this case is quite big - after upgrade the network might be > inaccessible. > > Any volunteers are welcome :) > > > > Serge > > > > On 09/06/2010 07:04 AM, Heiko Zuerker wrote: > >> Hey, > >> > >> I blame this question on my hangover... > >> How do you want to me to test, this seems like just a code fragment. > >> > >> Heiko > >> > >>> -----Original Message----- > >>> From: Serge Leschinsky [mailto:ser...@gm...] > >>> Sent: Sunday, September 05, 2010 5:37 PM > >>> To: dev...@li... > >>> Subject: Re: [Devil-linux-develop] network configuration script - > >>> add routes > >>> > >>> Please test this code: > >>> > >>> # cat upgrade > >>> > >>> convert_routes () > >>> { > >>> local file=$1 > >>> grep "^ROUTE=" $file | while read line; > >>> do > >>> unset ROUTE net gw > >>> eval $line > >>> > >>> if echo $ROUTE | grep "via\|dev" > /dev/null 2>&1; then > >>> echo $line; continue ; > >>> fi > >>> > >>> if echo $ROUTE | grep ":" > /dev/null 2>&1; then > >>> net=$(echo $ROUTE | cut -d':' -f1) > >>> gw=$(echo $ROUTE | cut -d':' -f2) > >>> else > >>> net=$(echo $ROUTE) # to remove spaces > >>> fi > >>> > >>> #echo $net $gw $dev > >>> > >>> # fixes > >>> if echo $net | grep default > /dev/null 2>&1; then > >>> net="default"; > >>> fi > >>> > >>> if [ x"$gw" == "x" ]; then > >>> dev="dev \$DEVICE"; > >>> else > >>> gw="via $gw"; > >>> fi > >>> > >>> echo "ROUTE=\"$net $gw $dev\"" > >>> done > >>> > >>> } > >>> > >>> # convert network interface configuration to new format for iface in > >>> /etc/sysconfig/nic/*; do > >>> > >>> version=$(awk -F "@version:" ' /^#@version:/ { print $2}' $iface) > >>> > >>> if [ -n "$version" ]; then > >>> # conversion from version "x" > >>> # Versions other then '1' was not released yet" > >>> continue > >>> else > >>> cp $iface $iface.conversion > >>> echo "#@version: 1" > $iface > >>> sed -e 's/^ROUTE/#ROUTE/g' $iface.conversion >> $iface > >>> convert_routes $iface.conversion >> $iface > >>> rm -f $iface.conversion > >>> fi > >>> > >>> done > >>> > >>> > >>> > >>> On 09/05/2010 12:08 PM, Heiko Zuerker wrote: > >>>> Yes that would make sense. > >>>> > >>>> H. > >>>> > >>> > >>> > >> --------------------------------------------------------------------- > >> --- > >> ------ > >>> This SF.net Dev2Dev email is sponsored by: > >>> > >>> Show off your parallel programming skills. > >>> Enter the Intel(R) Threading Challenge 2010. > >>> http://p.sf.net/sfu/intel-thread-sfd > >>> _______________________________________________ > >>> Devil-linux-develop mailing list > >>> Dev...@li... > >>> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop > >> > >> > >> --------------------------------------------------------------------- > >> --------- This SF.net Dev2Dev email is sponsored by: > >> > >> Show off your parallel programming skills. > >> Enter the Intel(R) Threading Challenge 2010. > >> http://p.sf.net/sfu/intel-thread-sfd > >> _______________________________________________ > >> Devil-linux-develop mailing list > >> Dev...@li... > >> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop > >> > > |
From: Serge L. <ser...@gm...> - 2010-09-06 21:22:13
Attachments:
upgrade-config.patch
setup.patch
|
Done. The patches for setup (with "no additional space for DG") and for upgrade-config are enclosed. Serge On 09/06/2010 12:47 PM, Heiko Zuerker wrote: > It worked on my test machine, but it adds an additional space after the > default gateways IP (right before the closing " ) > > Of course the next step is to correct the code in the "setup" program > (which by the way doesn't like the new ifcfg files). |
From: Heiko Z. <he...@zu...> - 2010-09-07 15:13:27
|
I'd say check it in, this way we get more testers right away. It'll probably be a few days before I get a chance to look at it. Heiko Quoting Serge Leschinsky <ser...@gm...>: > Done. > The patches for setup (with "no additional space for DG") and for > upgrade-config are enclosed. > > Serge > > On 09/06/2010 12:47 PM, Heiko Zuerker wrote: >> It worked on my test machine, but it adds an additional space after the >> default gateways IP (right before the closing " ) >> >> Of course the next step is to correct the code in the "setup" program >> (which by the way doesn't like the new ifcfg files). > > -- Regards Heiko Zuerker http://www.devil-linux.org ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. |
From: Dominic R. <dl...@ed...> - 2010-11-03 18:24:12
|
At last I got round to trying again with 1.4RC6 which seemed broken when I first tried it. I think I traced the problem I experienced back to a ROUTE line added at setup/upgrade time to ifcfg-eth0: ROUTE=" dev $DEVICE" This looks like a bug? Removing the line and doing /etc/init.d/network restart restored full functionality. Dominic On 07/09/2010 16:13, Heiko Zuerker wrote: > I'd say check it in, this way we get more testers right away. > It'll probably be a few days before I get a chance to look at it. > > Heiko > > Quoting Serge Leschinsky<ser...@gm...>: > >> Done. >> The patches for setup (with "no additional space for DG") and for >> upgrade-config are enclosed. >> >> Serge >> >> On 09/06/2010 12:47 PM, Heiko Zuerker wrote: >>> It worked on my test machine, but it adds an additional space after the >>> default gateways IP (right before the closing " ) >>> >>> Of course the next step is to correct the code in the "setup" program >>> (which by the way doesn't like the new ifcfg files). >> > > |
From: Serge L. <ser...@gm...> - 2010-11-04 07:13:24
|
Dominic, Hopefully it has been fixed. Thank you for cooperation! Serge On 11/03/2010 11:24 AM, Dominic Raferd wrote: > At last I got round to trying again with 1.4RC6 which seemed broken when > I first tried it. > > I think I traced the problem I experienced back to a ROUTE line added at > setup/upgrade time to ifcfg-eth0: > ROUTE=" dev $DEVICE" > > This looks like a bug? Removing the line and doing /etc/init.d/network > restart restored full functionality. > > Dominic > > > On 07/09/2010 16:13, Heiko Zuerker wrote: >> I'd say check it in, this way we get more testers right away. >> It'll probably be a few days before I get a chance to look at it. >> >> Heiko >> >> Quoting Serge Leschinsky<ser...@gm...>: >> >>> Done. >>> The patches for setup (with "no additional space for DG") and for >>> upgrade-config are enclosed. >>> >>> Serge >>> >>> On 09/06/2010 12:47 PM, Heiko Zuerker wrote: >>>> It worked on my test machine, but it adds an additional space after the >>>> default gateways IP (right before the closing " ) >>>> >>>> Of course the next step is to correct the code in the "setup" program >>>> (which by the way doesn't like the new ifcfg files). >>> >> >> > > ------------------------------------------------------------------------------ > Achieve Improved Network Security with IP and DNS Reputation. > Defend against bad network traffic, including botnets, malware, > phishing sites, and compromised hosts - saving your company time, > money, and embarrassment. Learn More! > http://p.sf.net/sfu/hpdev2dev-nov > _______________________________________________ > Devil-linux-develop mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/devil-linux-develop > |
From: Heiko Z. <he...@zu...> - 2010-08-29 13:06:17
|
Hey, I'm wondering if it wouldn't make sense to automatically add the "dev $DEVICE". Heiko > -----Original Message----- > From: Serge Leschinsky [mailto:ser...@gm...] > Sent: Sunday, August 29, 2010 1:52 AM > To: dev...@li... > Subject: Re: [Devil-linux-develop] network configuration script - add > routes > > Heiko, > > Yes, thank to my current job I have a LOT of enthusiasm to make > something useful :) > > What do you think about the following solution? > > every ifcfg-XXXX can contain routes in form of the lines > > ROUTE="default via xxx.xxx.xxx.xxx" > ROUTE="blackhole 10.0.0.0/8" > ROUTE="10.1.0.0/16 dev ppp0" > ROUTE="192.168.1.0/24 via xxx.xxx.xxx.xxx dev $DEVICE" > > etc. actually, any "ip route" command is allowed, because the statement > is the command itself, but without prefix "ip route add". > > We will add prefix "ip route add" for each ROUTE statement on 'start' and > "ip route del" for each statement on 'stop'. > > $DEVICE is already defined at the moment of execution (it will be the > name of this interface) , so we can use it as well. > > It seems to be simple and flexible enough. > > PS. Sorry for the broken thread - I copied the message from web, > because ISP ( where my email account was) doesn't accept my credential > anymore :( > > > Serge > > > > > I hate to delay the release of 1.4 further, but I think you are right. > > Would you have time to add it? > > > > Heiko > > > >> -----Original Message----- > >> From: Serge Leschinsky [mailto:fi...@in...] > >> Sent: Friday, August 27, 2010 7:49 PM > >> To: dev...@li... > >> Subject: [Devil-linux-develop] network configuration script - add > >> routes > >> > >> Hi, > >> > >> there is a new bug: > >> > > >> > ======================================================= > >> =============== > >> > Summary: Cannot add blackhole route > >> > Description: > >> > There is no way to add blackhole, unreachable etc. type of routes > >> > using configuration scripts. > >> > > >> > ======================================================= > >> =============== > >> > >> I have taken a look at ROUTE section in network script and have to > >> admit that old 'route' command doesn't allow us to add new > >> sophisticated routes. The main idea is to replace 'route' by 'ip > >> route', but it obviously causes the config format modification ('ip > >> route' has much more options). On the other hand, release 1.4 is a > >> good time to change things, because 1.2 -> 1.4 migration is a big > >> deal anyway. > >> > >> So, please advise :) > >> > >> Serge > >> > >> > >> > > > ------------------------------------------------------------------------ ------ > Sell apps to millions through the Intel(R) Atom(Tm) Developer Program > Be part of this innovative community and reach millions of netbook users > worldwide. Take advantage of special opportunities to increase revenue > and speed time-to-market. Join now, and jumpstart your future. > http://p.sf.net/sfu/intel-atom-d2d > _______________________________________________ > Devil-linux-develop mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/devil-linux-develop |
From: Serge L. <ser...@gm...> - 2010-08-29 20:54:26
|
Hi Heiko, In general, yes, we can. I've looked at my networks schemas and I see that sometimes I use routes statement for tunnels - they are actually handled by Quagga but may be static. So, it might be a good addition if we implement ifcfg-* format to handle tunnel interfaces. Serge On 08/29/2010 06:06 AM, Heiko Zuerker wrote: > Hey, > > I'm wondering if it wouldn't make sense to automatically add the "dev > $DEVICE". > > Heiko > >> -----Original Message----- >> From: Serge Leschinsky [mailto:ser...@gm...] >> Sent: Sunday, August 29, 2010 1:52 AM >> To: dev...@li... >> Subject: Re: [Devil-linux-develop] network configuration script - add >> routes >> >> Heiko, >> >> Yes, thank to my current job I have a LOT of enthusiasm to make >> something useful :) >> >> What do you think about the following solution? >> >> every ifcfg-XXXX can contain routes in form of the lines >> >> ROUTE="default via xxx.xxx.xxx.xxx" >> ROUTE="blackhole 10.0.0.0/8" >> ROUTE="10.1.0.0/16 dev ppp0" >> ROUTE="192.168.1.0/24 via xxx.xxx.xxx.xxx dev $DEVICE" >> >> etc. actually, any "ip route" command is allowed, because the > statement >> is the command itself, but without prefix "ip route add". >> >> We will add prefix "ip route add" for each ROUTE statement on 'start' > and >> "ip route del" for each statement on 'stop'. >> >> $DEVICE is already defined at the moment of execution (it will be the >> name of this interface) , so we can use it as well. >> >> It seems to be simple and flexible enough. >> >> PS. Sorry for the broken thread - I copied the message from web, >> because ISP ( where my email account was) doesn't accept my credential >> anymore :( >> >> >> Serge >> >> >> >>> I hate to delay the release of 1.4 further, but I think you are > right. >>> Would you have time to add it? >>> >>> Heiko >>> >>>> -----Original Message----- >>>> From: Serge Leschinsky [mailto:fi...@in...] >>>> Sent: Friday, August 27, 2010 7:49 PM >>>> To: dev...@li... >>>> Subject: [Devil-linux-develop] network configuration script - add >>>> routes >>>> >>>> Hi, >>>> >>>> there is a new bug: >>>>> >>>> >> ======================================================= >>>> =============== >>>>> Summary: Cannot add blackhole route >>>>> Description: >>>>> There is no way to add blackhole, unreachable etc. type of routes >>>>> using configuration scripts. >>>>> >>>> >> ======================================================= >>>> =============== >>>> >>>> I have taken a look at ROUTE section in network script and have to >>>> admit that old 'route' command doesn't allow us to add new >>>> sophisticated routes. The main idea is to replace 'route' by 'ip >>>> route', but it obviously causes the config format modification ('ip >>>> route' has much more options). On the other hand, release 1.4 is a >>>> good time to change things, because 1.2 -> 1.4 migration is a big >>>> deal anyway. >>>> >>>> So, please advise :) >>>> >>>> Serge >>>> >>>> >>>> >> >> >> > ------------------------------------------------------------------------ > ------ >> Sell apps to millions through the Intel(R) Atom(Tm) Developer Program >> Be part of this innovative community and reach millions of netbook > users >> worldwide. Take advantage of special opportunities to increase revenue >> and speed time-to-market. Join now, and jumpstart your future. >> http://p.sf.net/sfu/intel-atom-d2d >> _______________________________________________ >> Devil-linux-develop mailing list >> Dev...@li... >> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop > > > ------------------------------------------------------------------------------ > Sell apps to millions through the Intel(R) Atom(Tm) Developer Program > Be part of this innovative community and reach millions of netbook users > worldwide. Take advantage of special opportunities to increase revenue and > speed time-to-market. Join now, and jumpstart your future. > http://p.sf.net/sfu/intel-atom-d2d > _______________________________________________ > Devil-linux-develop mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/devil-linux-develop > |