I don't entirely follow your topology description.   It looks like you're 
testing this on a network with other hosts; you might try simplifying things 
(e.g., removing devices for the purposes of testing).

In the log you sent, are you trying to communicate between your two hosts?  Are 
their ethernet addresses in that log?

I also think it's worth testing l2_learning and forwarding.hub and seeing what 
they do...

-- Murphy

On Apr 9, 2013, at 5:58 AM, Mayumi Park Campos wrote:

> I think my problem is my configuration of the network, but, correct me if I'm 
> wrong, openflow should work it through I had undestood.
> 
> I have four ubuntu pc's: one is for the reference switch, one for the pox 
> controller and the other two are the hosts. The swith and the  controller are 
> connected through a cisco switch on a vlan without exit to the internet and 
> each host is connected to a hub so each host belongs to diferente LANs and 
> each hub is connected to the switch and for what I see here is were the 
> problem is, cause for the switch its ports are eth1 and eth2 were the hubs 
> are connnected and for the controller the ports are the MACs of the hosts.
> 
> Here is the log debug:
> controlador@controlador-OptiPlex-GX620:~/pox$ ./pox.py log.level --DEBUG 
> forwarding.l2_learning
> POX 0.1.0 (betta) / Copyright 2011-2013 James McCauley, et al.
> DEBUG:forwarding.l2_learning:Starts l2 learning
> DEBUG:core:POX 0.1.0 (betta) going up...
> DEBUG:core:Running on CPython (2.7.3/Aug 1 2012 05:16:07)
> DEBUG:core:Platform is 
> Linux-3.2.0-39-generic-pae-i686-with-Ubuntu-12.04-precise
> INFO:core:POX 0.1.0 (betta) is up.
> DEBUG:openflow.of_01:Listening on 0.0.0.0:6633
> INFO:openflow.of_01:[00-14-22-4b-5e-60 1] connected
> DEBUG:forwarding.l2_learning:Connection [00-14-22-4b-5e-60 1]
> DEBUG:forwarding.l2_learning:Initializing LearningSwitch, transparent=False
> DEBUG:forwarding.l2_learning:Port for 00:50:8b:5a:89:83 unknown -- flooding
> DEBUG:forwarding.l2_learning:86474710624: flood 00:14:22:4b:5e:72 -> 
> 00:50:8b:5a:89:83
> DEBUG:forwarding.l2_learning:Port for 00:50:04:9d:16:db unknown -- flooding
> DEBUG:forwarding.l2_learning:86474710624: flood 00:14:22:46:af:30 -> 
> 00:50:04:9d:16:db
> DEBUG:forwarding.l2_learning:Port for 00:50:8b:5a:89:83 unknown -- flooding
> DEBUG:forwarding.l2_learning:86474710624: flood 00:14:22:4b:5e:72 -> 
> 00:50:8b:5a:89:83
> DEBUG:forwarding.l2_learning:Port for 00:50:04:9d:16:db unknown -- flooding
> DEBUG:forwarding.l2_learning:86474710624: flood 00:14:22:46:af:30 -> 
> 00:50:04:9d:16:db
> DEBUG:forwarding.l2_learning:Port for 00:50:8b:5a:89:83 unknown -- flooding
> DEBUG:forwarding.l2_learning:86474710624: flood 00:14:22:4b:5e:72 -> 
> 00:50:8b:5a:89:83
> DEBUG:forwarding.l2_learning:Port for 00:50:04:9d:16:db unknown -- flooding
> DEBUG:forwarding.l2_learning:86474710624: flood 00:14:22:46:af:30 -> 
> 00:50:04:9d:16:db
> DEBUG:forwarding.l2_learning:Port for 00:50:8b:5a:89:83 unknown -- flooding
> DEBUG:forwarding.l2_learning:86474710624: flood 00:14:22:4b:5e:72 -> 
> 00:50:8b:5a:89:83
> DEBUG:forwarding.l2_learning:Port for 00:50:04:9d:16:db unknown -- flooding
> DEBUG:forwarding.l2_learning:86474710624: flood 00:14:22:46:af:30 -> 
> 00:50:04:9d:16:db
> DEBUG:forwarding.l2_learning:86474710624: flood 00:14:22:46:af:30 -> 
> 33:33:00:00:00:fb
> DEBUG:forwarding.l2_learning:86474710624: flood 00:14:22:46:af:30 -> 
> 01:00:5e:00:00:fb
> INFO:openflow.of_01:[00-14-22-4b-5e-60 1] closed
> 
> Subject: Re: [pox-dev] Problem with stanford's software reference design 
> openflow switch
> From: murphy.mccau...@gmail.com
> Date: Mon, 8 Apr 2013 15:26:42 -0700
> CC: pox-dev@lists.noxrepo.org
> To: rebek_...@hotmail.com
> 
> Add "log.level --DEBUG" to the commandline.  Even better, put it first on the 
> commandline.  (This is in the manual.)
> 
> Incidentally, you don't need to specify the port, since 6633 is the default.  
> For that matter, you probably don't need to specify the address either.  
> "./pox.py forwarding.l2_learning" is probably sufficient.
> 
> -- Murphy
> 
> On Apr 8, 2013, at 3:22 PM, Mayumi Park Campos wrote:
> 
> The reason I use the reference switch is cause I understood that it is 
> user-space and it will be easier to add new features. 
> I haven´t tried l2_pairs, i would do it. 
> I know its strange that l3_learning does make the flow modification and i 
> think the reason is that theres a problem with the switch implementation. I 
> would give a look to the openvswitch.
> And I just update pox to the beta branch and when I run the "./pox.py 
> openflow.of_01 --address=192.168.0.100 --port=6633 forwarding.l2_learning" it 
> doesn´t print the debug, could you tell me you can I print it? 
> 
> Thanks for the quick reply
> 
> Subject: Re: [pox-dev] Problem with stanford's software reference design 
> openflow switch
> From: murphy.mccau...@gmail.com
> Date: Mon, 8 Apr 2013 15:07:33 -0700
> CC: pox-dev@lists.noxrepo.org
> To: rebek_...@hotmail.com
> 
> On Apr 8, 2013, at 2:57 PM, Mayumi Park Campos wrote:
> I have implemented the pox controller with a openflow stanford's software 
> reference design openflow switch emulated on a pc and my problem is that when 
> a try to run pox as forwarding l2_learning behavior my “switch” do not work 
> as switch and do not install any flow but when I run pox as forwarding 
> l3_learning it works fine.
> 
> Could anyone tell me what should I do to make my emulated switch works as a 
> switch and not as a router?  I have not make any modification to the original 
> code.
> 
> Are you using the reference switch for any particular reason?  Open vSwitch 
> is considerably more maintained.
> 
> It seems strange that it's working for l3_learning (which, incidentally, is 
> more like an L3 switch than anything that anyone would call a router) and not 
> l2_learning.  Have you tried l2_pairs?  Can you post the entire POX log at 
> debug level for a test run?  See the manual for info on configuring the log 
> (there's a FAQ entry for troubleshooting).
> https://openflow.stanford.edu/display/ONL/POX+Wiki
> 
> -- Murphy

Reply via email to