Re: Dynamically add/change interfaces in Click config

rchertov <[email protected]>
Newsgroups gmane.network.routing.click
Message-ID <[email protected]>
Typically on Emulab-type testbeds, I do the following.  Make a generic 
click script.  Use perl or bash to determine which interfaces need to be 
used.  Then, use sed to create a click script for a particular node.

 FromDevice(NET_DEVICE) -> Discard;

sed -e 's/NET_DEVICE/eth12/' generic_script.click > custom_script.click

Roman


On Mon, 5 Dec 2011 13:42:22 -0500, Shrutarshi Basu wrote:
> Hi all,
> I'm trying to get Click running under the Mininet network
> virtualizer. Mininet creates veth interfaces when new switches/hosts
> are added to the network. However it seems that for Click
> configurations the interfaces have to be specified statically in the
> config file. Is there someway I can use a variable to represent the
> interfaces and then pass in the actual veth interfaces once Mininet
> has created them? I suppose one way would be to pass the config file
> through some sort of custom preprocessor that spits out a real config
> with the correct interfaces and then install that configuration. Is
> there some standard/alternative way of doing what I want?
> Thanks,
> Basu
>
> _______________________________________________
> click mailing list
> [email protected]
> https://amsterdam.lcs.mit.edu/mailman/listinfo/click
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.