I suggest you switch to mininet or OpenFlowVMS which means this easier. The former being more newer. (Disclaimer: I maintain the latter).
Regards KK On 16 November 2010 11:11, Macapuna, Carlos A. B. <carlosmacap...@gmail.com> wrote: > Do you don't need of s4: > > SWITCHES="s1 s2 s3 s4 s5" > s2_SLIRP=yes > - s4_SLIRP=yes (remove) > > VMS="end1 openflow1 openflow2 end2" > end1_NETS=s1 > end2_NETS=s5 > openflow1_NETS="s1 s2 s3" > openflow2_NETS="s3 s2 s5" > > end1_KERNEL=kernel.bin > end2_KERNEL=kernel.bin > openflow1_KERNEL=kernel.bin > openflow2_KERNEL=kernel.bin > > ---- > Carlos Macapuna > www.macapuna.com.br > > > > > On Tue, Nov 16, 2010 at 4:46 PM, Rohit Manohar <rdman...@ncsu.edu> wrote: >> >> I am trying to build the following network topology in NOX >> >> >> |----------| |------------------| >> |-----------------| |----------| >> | End1 |-----------| Openflow1 |----------------------------| Openflow2 >> |---------| End 2 | >> |----------| |------------------| >> |-----------------| |----------| >> >> Both of the Openflow switches are connected to the Nox-Controller >> >> My .conf file is: >> >> SWITCHES="s1 s2 s3 s4 s5" >> s2_SLIRP=yes >> s4_SLIRP=yes >> >> VMS="end1 openflow1 openflow2 end2" >> end1_NETS=s1 >> end2_NETS=s5 >> openflow1_NETS="s1 s2 s3" >> openflow2_NETS="s3 s4 s5" >> >> end1_KERNEL=kernel.bin >> end2_KERNEL=kernel.bin >> openflow1_KERNEL=kernel.bin >> openflow2_KERNEL=kernel.bin >> >> >> Now, I have a few doubts >> >> 1. When I do dhclient on Openflow1 and Openflow2, both of them get the >> same ip 10.0.2.15 on eth1. Is this right? Since they are different >> interfaces, how can they use same IP? >> >> 2. How do I connect the two switches? >> I am doing >> ./dpctl addif nl:0 eth0 to connect Openflow1 to End1 >> ./dpctl addif nl:1 eth0 to connect Openflow2 to End2 >> >> 3. Can pyswitch allow me to send packets from End1 to End2? >> >> Regards, >> >> -- >> Rohit Manohar >> Graduate Student >> North Carolina State University >> Raleigh, US. >> >> >> _______________________________________________ >> nox-dev mailing list >> nox-dev@noxrepo.org >> http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org >> > > > _______________________________________________ > nox-dev mailing list > nox-dev@noxrepo.org > http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org > > _______________________________________________ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
