Hi Alexey, Your setup is a bit complicated , I am not clear whether you are doing inband, and why you set an action that forwards everything to the controller. What is the configuration of your openflow switch (inband or outband)? Can you copy /etc/config/openflow ?
t might be easier to debug with a simpler setup. A possible way to start is the following setup : Configure your switch of out-of-band. Attach laptop1 at port 1 of the switch, laptop2 at port2 and PC running the pyswitch at the control port. Configure laptops under the same subnet and try to ping between them. Thanks, Yiannis On Mon, Jun 13, 2011 at 2:03 PM, Alexey Bogaevskiy <[email protected]>wrote: > Yiannis, > > I have tried running pyswitch, pytutorial, and the reference controller > with the wireless setup. Now I am trying using an ethernet connection along > with wireless and I am using pyswitch, because I can see packet-in and > packet-out events on wireshark, however I cannot establish connection > between laptop and switch. > Current topology (laptop)<->(wrt54GL openflow switch)<->(PC running > pyswitch NOX controller) > I can also see notification come up on the nox controller: > 01175|openflow-event|DBG:openflow packet too short > 01176|openflow-event|DBG:received packet-in event from 002320c178eb (len:0) > 01177|pyswitch|ERR:'**warning** learned port = inport' > 01178|flow|ERR:Packet length 0 less than minimum Ethernet packet 14: > port0400:vlanffff:pcp:0 mac00:00:00:00:00:00->00:00:00:00:00:00 proto0000 > ip0.0.0.0->0.0.0.0 port0->0 > > I can also see activity on the switch: > root@OpenWrt:~# dpctl dump-flows tcp:10.5.10.1:6633 > stats_reply (xid=0xfb200b74): flags=none type=1(flow) > cookie=0, duration_sec=30s, duration_nsec=241000000s, table_id=1, > priority=32768, n_packets=3, n_bytes=1026, > idle_timeout=60,hard_timeout=0,dl_src=00:23:5a:d3:eb:f7,actions=CONTROLLER:all > > this is the flow rule that I am using: > dpctl add-flow tcp:10.5.10.1:6633 > dl_src=00:23:5a:d3:eb:f7,actions=CONTROLLER:all > > similar thing happens if I try to ping the switch from the laptop, can see > packet in and out events, but no ping replies... > > And exactly the same thing happens when I try to connect via the wireless > interface, i can see the first OFP+XID packet in, then one packet out, the > dump flow comand shows that I received a packet according to my rule, but > still cannot establish connection... > > Thank you for your help, > > -Alex > > On Mon, Jun 13, 2011 at 3:31 PM, Yiannis Yiakoumis > <[email protected]>wrote: > >> Hi Alexey, >> >> What application runs in your controller? Do you see any flow-mod or >> packet-out after the initial packet-in you receive? >> >> The wildcarded entry you sent is for FlowVisor : it says that the >> "wireless" slice CAN control all traffic coming from all APs, but it doesn't >> say anything about how this happens. This decision belongs to your >> 'wireless" controller. You can use dpctl to see what flows are installed in >> your switch. Alternatively you may run with the "switch" application that >> comes with nox and see whether this works at first. >> >> Thanks, >> Yiannis >> >> On Mon, Jun 13, 2011 at 7:15 AM, Alexey Bogaevskiy <[email protected]>wrote: >> >>> Hello, >>> >>> I am trying to set up a network with 3 openflow switches, flowvisor, a >>> couple of controllers, and a couple wireless clients. I followed the >>> tutorial to set up wireless on the switches (WRT54GL) >>> http://www.openflow.org/wk/index.php/OpenFlow_1.0_for_OpenWRT , but >>> can't seem to be able to connect my wireless client(laptop) to any of the >>> switches. >>> >>> I can see a "00037|openflow-event|DBG:received packet-in event from >>> 002320d6f041 (len:60)" when I try to establish connection from the laptop, >>> and can see a packet going into the main nox controller, but that is it. >>> Packet: >>> 21750 67557.062366 GemtekTe_e7:a1:9e Broadcast OFP+XID Packet In (AM) >>> (BufID=259) (78B) => Basic Format; Type 1 LLC (Class I LLC); Window Size 0 >>> it also mentions that there is no matching flow for this packet, although >>> I think I have the flow set up, with wildcard rules, so it should accept >>> anything. >>> Flow: >>> abogaevskiy@abogaevskiy-desktop:~/flowvisor$ fvctl listFlowSpaceEnter >>> fvadmin's passwd: >>> Got reply: >>> rule 0: >>> FlowEntry[dpid=[all_dpids],ruleMatch=[OFMatch[]],actionsList=[Slice:wireless=7],id=[170],priority=[1],] >>> >>> >>> Does anybody have any idea what might be going wrong? >>> >>> Thank you, >>> -Alex >>> >>> _______________________________________________ >>> openflow-discuss mailing list >>> [email protected] >>> https://mailman.stanford.edu/mailman/listinfo/openflow-discuss >>> >>> >> >
_______________________________________________ openflow-discuss mailing list [email protected] https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
