This configuration does not seem useful?! If you want to hook up switches you could either do it directly,
... -> a::EtherSwitch [0] -> [0] b::EtherSwitch -> ... Or use any of Click's other elements, such as Unqueue LinkUnqueue whatever, to hook up the switches E sendoa vaz wrote: > Hello! > > Thanks a lot for the answer. What I want to do is to communicate two > configuration files in which I have built two switches. The > configuration files are really easy but maybe what I'm trying to do is > impossible. I would like to have several switches connected with each > other and I thought I could it using the same tap device as a link > between two switches, like in the following "drawing". > > > > tap0 |----------------| > |----------------| > | SWITCH 1| -------tap1---------------| > SWITCH2| tap2 > |----------------| > |----------------| > > > The thing is that I don't know if I could do this using tap devices. The > configuration files are the following ones (I have created the tap > devices previously). The thing is that packets from switch1 aren't > forwarded via tap1 to the second switch. Do you know why could it be? > > Thanks in advance > > > Switch1.click > > Switch1::EtherSwitch() > > FromDevice(tap0)->[0]Switch1[0]->Queue->ToDevice(tap0) > FromDevice(tap1)->[1]Switch1[1]->Queue->ToDevice(tap1) > TimedSource(INTERVAL 1)->EtherEncap(/0800, 00:19:00:19:10:10,tap2) -> > [2]Switch1[2]->Discard > > Switch2.click > > > Switch2::EtherSwitch() > > FromDevice(tap1)->[0]Switch2[0]->Queue->ToDevice(tap1) > FromDevice(tap2)->[1]Switch2[1]->Queue->ToDevice(tap2) > > > > > > 2008/8/26 Eddie Kohler <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> > > RouterLink has no definition. It isn't supposed to. It is a > placeholder representing the fake connection between two routers. > If you want you can add a compound element definition such as > > elementclass RouterLink { __REST__ $rest | > input -> Unqueue -> output > } > > to the top of your file. > > I don't know what you expected running the combined configuration to do. > > Eddie > > > sendoa vaz wrote: > > Hello, > > I don't know if there is a bug in the tool click-combine but the > element > RouterLink is not find anywhere. The tools creates a > configuration file > which seems to be the interconexion of another two configuration > files but > when I run it it fails saying that the RouterLink element is > unknown. I > think there must be a file that have been lost... I enclose the > configuration file so you can check it. > > Thanks > > Sendoa > > > ------------------------------------------------------------------------------------------------- > !<arch> > config 1216774776 0 0 644 1684 ` > # 1 "/home/sendoa/PFC/sendoa/switch1.click" > switch1/switch1 :: EtherSwitch; > # 3 "/home/sendoa/PFC/sendoa/switch1.click" > switch1/tap1 :: KernelTap(1.0.0.1/8 <http://1.0.0.1/8>, ETHER > 1:1:1:1:1:1); > # 1 "/home/sendoa/PFC/sendoa/switch2.click" > switch2/switch2 :: EtherSwitch; > # 0 "<click-combine>" > link2 :: RouterLink(switch1 tap3 KernelTap, 3.0.0.1/8 > <http://3.0.0.1/8>, ETHER 3:3:3:3:3:3, > switch3 tap7 KernelTap, 7.0.0.1/8 <http://7.0.0.1/8>, ETHER > 7:7:7:7:7:7); > # 0 "<click-combine>" > link4 :: RouterLink(switch2 tap6 KernelTap, 6.0.0.1/8 > <http://6.0.0.1/8>, ETHER 6:6:6:6:6:6, > switch4 tap10 KernelTap, 10.0.0.1/8 <http://10.0.0.1/8>, ETHER > 10:10:10:10:10:10); > # 1 "/home/sendoa/PFC/sendoa/switch3.click" > switch3/switch3 :: EtherSwitch; > # 0 "<click-combine>" > link3 :: RouterLink(switch3 tap8 KernelTap, 8.0.0.1/8 > <http://8.0.0.1/8>, ETHER 8:8:8:8:8:8, > switch2 tap5 KernelTap, 5.0.0.1/8 <http://5.0.0.1/8>, ETHER > 5:5:5:5:5:5); > # 1 "/home/sendoa/PFC/sendoa/switch4.click" > switch4/switch4 :: EtherSwitch; > # 0 "<click-combine>" > link5 :: RouterLink(switch3 tap9 KernelTap, 9.0.0.1/8 > <http://9.0.0.1/8>, ETHER 9:9:9:9:9:9, > switch4 tap12 KernelTap, 12.0.0.1/8 <http://12.0.0.1/8>, ETHER > 12:12:12:12:12:12); > # 4 "/home/sendoa/PFC/sendoa/switch4.click" > switch4/tap11 :: KernelTap(11.0.0.1/8 <http://11.0.0.1/8>, ETHER > 11:11:11:11:11:11); > # 0 "<click-combine>" > link1 :: RouterLink(switch1 tap2 KernelTap, 2.0.0.1/8 > <http://2.0.0.1/8>, ETHER 2:2:2:2:2:2, > switch2 tap4 KernelTap, 4.0.0.1/8 <http://4.0.0.1/8>, ETHER > 4:4:4:4:4:4); > # 24 "" > switch1/switch1 [1] -> link1 > -> switch2/switch2; > switch1/switch1 [2] -> link2 > -> switch3/switch3; > switch2/switch2 [2] -> link4 > -> switch4/switch4; > switch3/switch3 [1] -> link3 > -> [1] switch2/switch2; > switch3/switch3 [2] -> link5 > -> [2] switch4/switch4; > switch4/switch4 [1] -> switch4/tap11 > -> [1] switch4/switch4; > switch1/tap1 -> switch1/switch1 > -> switch1/tap1; > elementmap.xml 1216774776 0 0 600 178 ` > <?xml version="1.0" standalone="yes"?> > <elementmap xmlns="http://www.lcdf.org/click/xml/";> > <entry name="RouterLink" processing="l/h" flowcode="x/x" > flags="S3" /> > </elementmap> > componentmap 1216774776 0 0 600 32 ` > switch1 > switch2 > switch3 > switch4 > ---------------------------------------------------------------- > _______________________________________________ > click mailing list > [email protected] <mailto:[email protected]> > https://amsterdam.lcs.mit.edu/mailman/listinfo/click > > _______________________________________________ click mailing list [email protected] https://amsterdam.lcs.mit.edu/mailman/listinfo/click
