Probably - I just think in perl. Seriously though - if you can do it smaller/nicer/better/whatever, then by all means post it up. I'm not attached to it - I just thought it might save certain people a bit of time On Tue, May 29, 2001 at 12:56:02PM +1200, Juha Saarinen wrote:

Can't you do it with awk instead?

:: -----Original Message----- :: From: owner-nznog(a)list.waikato.ac.nz :: [mailto:owner-nznog(a)list.waikato.ac.nz] On Behalf Of Dean Pemberton :: Sent: Tuesday, 29 May 2001 12:39 :: To: nznog(a)list.waikato.ac.nz :: Subject: Re: New improved prefix list :) :: :: :: Seeings as more people are getting them, I thought it might :: be helpful to write this. :: :: :: #!/usr/bin/perl :: $cli = 0; :: $header = 0; :: while (<>) { :: chomp; :: ($crap,$crap,$name,$crap,$crap,$crap,$prefix,$le,$limit) :: = split (/\ /,$_); :: if (!$header) { :: if ($cli){ :: print "edit policy-options policy-statement $name\n"; :: }else{ :: print "policy-statement ihug-networks {\n\tterm :: accept {\n\t\tfrom {\n"; :: } :: $header = 1; :: } :: if ($cli) { :: print "set term accept from "; :: }else{ :: print "\t\t\t"; :: } :: print "route-filter $prefix "; :: if ($le eq "le") {print "upto /$limit";}else{print "exact";} :: if ($cli) { :: print "\n"; :: }else{ :: print ";\n"; :: } :: } :: if ($cli) { :: print"set term accept then accept\nset term reject then :: reject\n"; :: } else { :: print "\t\t}\n\t\tthen accept;\n\t}\n\tterm reject :: {\n\t\t\tthen reject;\n\t}\n}\n"; :: } :: :: :: output looks like this :: :: edit policy-options policy-statement ihug-networks :: set term accept from route-filter 202.36.94.0/23 upto /24 :: set term accept from route-filter 202.37.129.0/24 exact :: set term accept from route-filter 202.37.136.0/24 exact :: set term accept from route-filter 202.37.182.0/24 exact :: set term accept from route-filter 202.37.194.0/24 exact :: set term accept from route-filter 202.49.59.0/24 exact :: set term accept from route-filter 202.49.88.0/23 upto /24 :: set term accept from route-filter 202.49.148.0/23 upto /24 :: set term accept from route-filter 202.49.176.0/23 upto /24 :: set term accept from route-filter 202.49.180.0/23 upto /24 :: set term accept from route-filter 202.49.186.0/24 exact :: set term accept from route-filter 202.49.240.0/22 upto /24 :: set term accept from route-filter 202.49.249.0/24 exact :: set term accept from route-filter 202.49.252.0/22 upto /24 :: set term accept from route-filter 202.50.84.0/24 exact :: set term accept from route-filter 202.50.103.0/24 exact :: set term accept from route-filter 202.50.255.0/24 exact :: set term accept from route-filter 203.109.128.0/17 upto /24 :: set term accept from route-filter 203.173.128.0/17 upto /24 :: set term accept from route-filter 210.55.184.0/24 exact :: set term accept from route-filter 210.55.203.0/24 exact :: set term accept from route-filter 210.55.248.0/21 upto /24 :: set term accept then accept :: set term reject then reject :: :: or this :: :: policy-statement ihug-networks { :: term accept { :: from { :: route-filter 202.36.94.0/23 upto /24; :: route-filter 202.37.129.0/24 exact; :: route-filter 202.37.136.0/24 exact; :: route-filter 202.37.182.0/24 exact; :: route-filter 202.37.194.0/24 exact; :: route-filter 202.49.59.0/24 exact; :: route-filter 202.49.88.0/23 upto /24; :: route-filter 202.49.148.0/23 upto /24; :: route-filter 202.49.176.0/23 upto /24; :: route-filter 202.49.180.0/23 upto /24; :: route-filter 202.49.186.0/24 exact; :: route-filter 202.49.240.0/22 upto /24; :: route-filter 202.49.249.0/24 exact; :: route-filter 202.49.252.0/22 upto /24; :: route-filter 202.50.84.0/24 exact; :: route-filter 202.50.103.0/24 exact; :: route-filter 202.50.255.0/24 exact; :: route-filter 203.109.128.0/17 upto /24; :: route-filter 203.173.128.0/17 upto /24; :: route-filter 210.55.184.0/24 exact; :: route-filter 210.55.203.0/24 exact; :: route-filter 210.55.248.0/21 upto /24; :: } :: then accept; :: } :: term reject { :: then reject; :: } :: } :: :: depending on the value of $cli :: :: Apologies for the ugly perl - just hacked it up - feel free :: to make it pretty and rerelease. :: Also check the output before you apply it - It's your :: responsibility remember =) :: :: :: :: :: On Tue, May 29, 2001 at 09:52:11AM +1200, David Robb wrote: :: > Now with free steak knives! [1] :: > :: > As you can see, these allow for variable masks. If anyone requires :: > specific prefixes, let me know and I'll see what I can do. :: We change them :: > from time to time, and its easier this way. :: > :: > [1] Ok, I was kidding about the steak knives. :: > :: > :: > :: > --------- :: > To unsubscribe from nznog, send email to :: majordomo(a)list.waikato.ac.nz :: > where the body of your message reads: :: > unsubscribe nznog :: --------- :: To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz :: where the body of your message reads: :: unsubscribe nznog :: ::

--------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

On Tue, May 29, 2001 at 12:56:02PM +1200, Juha Saarinen wrote:

Can't you do it with awk instead?

#!/usr/bin/awk -f BEGIN { # insert more stuff here if you have a test box to play with, or can # be bothered to go look at the manuals when you've drunk just enough # Niagra region chardonnay to start to think that it tastes half-decent trans["le"] = "upto"; } /^ip prefix-list [A-Za-z0-9-]+ permit [0-9\.]+\/[0-9]+/ && \ trans[$6] != "" && $7 ~ /[0-9]+/ { phrase[$3 ":" clauses[$3]++] = "route-filter " $5 " " trans[$6] " /" $7; next; } /^ip prefix-list [A-Za-z0-9-]+ seq [0-9]+ permit [0-9\.]+\/[0-9]+/ && \ trans[$8] != "" && $9 ~ /[0-9]+/ { phrase[$3 ":" clauses[$3]++] = "route-filter " $7 " " trans[$8] " /" $9; next; } /^ip prefix-list [A-Za-z0-9-]+ permit [0-9\.]+\/[0-9]+/ { phrase[$3 ":" clauses[$3]++] = "route-filter " $5 " exact"; } /^ip prefix-list [A-Za-z0-9-]+ seq [0-9]+ permit [0-9\.]+\/[0-9]+/ { phrase[$3 ":" clauses[$3]++] = "route-filter " $7 " exact"; } END { for (c in clauses) { printf "policy-statement %s {\n\tterm accept {\n\t\tfrom {\n", c; for (i = 0; i < clauses[c]; i++) printf "\t\t\t%s;\n", phrase[c ":" i]; printf "\t\t}\n\t\tthen accept;\n\t}\n\tterm reject {\n"; printf "\t\t\tthen reject;\n\t}\n}\n"; } } --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

On Tue, May 29, 2001 at 03:37:50PM +1200, Matt Camp wrote:

Ok Mr SmartyPants.

Lets see you do it in Befunge.

Doing it in Befunge would require integration of the IOS source into the program, since the instruction pointer traverses both data and code. Clearly the job of formatting the source into a valid befunge-97 automaton is a task that best belongs in IOS, rather than some external script. I will leave it to you to write up the feature request. 0"): spleh taht epoH">v ,: ^_@ Joe --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

Thanks man - I don't actually have a use for any of this (for obvious reasons). But it's good to see this sort of thing becoming availible =) On Tue, May 29, 2001 at 03:32:32PM +1200, Dylan Hall wrote:

Attached is my version. It's considerably larger, but a litte more versitile. Give it the output of a 'write term' and it will convert all the prefix-lists into JUNOS policy-statements. There is a '-c' flag that will cause the output to be compatible with the CLI (as per $cli in your version).

Dean Pemberton wrote:

...

Seeings as more people are getting them, I thought it might be helpful to write this.

<snip>

...

Apologies for the ugly perl - just hacked it up - feel free to make it pretty and rerelease. Also check the output before you apply it - It's your responsibility remember =)

-- Dylan Hall IP Engineer TelstraSaturn Ltd Ph: +64 4 9228400 Fax: +64 4 9228401

--------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog