Thanks Yiannis, Indeed, wrong firmware.
Now I have other question: in process list I see 1200 root 1320 S ofdatapath ptcp:6634 -i eth0.1 eth0.2 eth0.3 eth0.4 - 1240 root 1052 S ofprotocol tcp:127.0.0.1:6634 tcp:10.92.0.100:6633-- >From where is comming the port 6634? On other switches (Linksys) I was checking the flows using dpctl dump-flows unix:/var/run/dp0.sock, but on tp-link the dp0.sock dosen't exist. Is there a reason? Here dosen't work, so I use dpctl dump-flows tcp:127.0.0.1:6633 and I see the same content on the :6634. Thanks!!! On Fri, Jul 6, 2012 at 7:59 PM, Yiannis Yiakoumis <gyiakou...@gmail.com>wrote: > Hi Diana, > > Also make sure that you've installed the firmware which is > specifically for v1.8. The box runs its own VLAN-based learning switch > which we have to disable, and 1.8 had some changes that required a new > image. > > Thanks, > Y. > > On Fri, Jul 6, 2012 at 4:59 AM, Bill Owens <ow...@nysernet.org> wrote: > > On Fri, Jul 06, 2012 at 01:28:37PM +0200, Diana Marosin wrote: > >> Dear all, > >> I followed the tutorial on this > >> page > http://www.openflow.org/wk/index.php/Pantou_:_OpenFlow_1.0_for_OpenWRT > >> I have h1----sw----h2 and the POX controller running > >> forwarding.l2_learning > >> Now, if I try to ping from h1 to h2, the controller installs flows > on the > >> switch: > >> cookie=1, duration_sec=5s, duration_nsec=897000000s, table_id=1, > >> priority=32768, n_packets=6, n_bytes=360, > >> > > idle_timeout=300,hard_timeout=300,arp,dl_vlan=0xffff,dl_vlan_pcp=0x00,dl_src=f4:ec:38:b7:d8:64,dl_dst=00:0f:1f:a6:85:11,nw_src=10.92.0.1,nw_dst=10.92.0.101,nw_proto=2,tp_src=0,tp_dst=0,actions=output:4 > >> cookie=0, duration_sec=14s, duration_nsec=941000000s, table_id=1, > >> priority=32768, n_packets=12, n_bytes=1176, > >> > > idle_timeout=300,hard_timeout=300,icmp,dl_vlan=0xffff,dl_vlan_pcp=0x00,dl_src=00:0f:1f:a6:85:11,dl_dst=f4:ec:38:b7:d8:64,nw_src=10.92.0.101,nw_dst=10.92.0.1,nw_tos=0x00,icmp_type=8,icmp_code=0,actions=output:3 > >> But on the h1 the message is "destination host unreachable". > >> Do you have any idea, what could be the issue? > >> Best, > >> Diana > > > > If you manually install two flows to connect the ports, does the ping > work? For example: > > > > dpctl add-flow tcp:<your TP-LINK> in_port=3,actions=output:4 > > dpctl add-flow tcp:<your TP-LINK> in_port=4,actions=output:3 > > > > That would troubleshoot the two test hosts' ports and configurations, > and the connections to the TP-LINK. If that works, I'd suggest running > tshark on both hosts to see what packets they're receiving. It looks as > though traffic is only flowing in one direction, based on the flows above. > > > > Bill. > > _______________________________________________ > > openflow-discuss mailing list > > openflow-discuss@lists.stanford.edu > > https://mailman.stanford.edu/mailman/listinfo/openflow-discuss > > > > -- > Yiannis . >
_______________________________________________ openflow-discuss mailing list openflow-discuss@lists.stanford.edu https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
