On Feb 8, 2013, at 11:55 AM, Peter Fales wrote: > Apparently there are (at least?) two ways to do it. Andrew suggested > using recv_port=OFPP_NONE and buffer=BUFFER_ID_NONE which is what I was > doing. Murphy's sample capture did it by settting the Recv_port=1 > and output_port=OFPP_IN_PORT.
Ah, true -- in my case, the pong application was responding to a packet, so it set the in_port and output_port appropriately. > Here's a wireshark dump of the message being sent to the controller. It > has a buffer_id=none, recv_port=none, and an output action going to > port 2. As far as I can tell it's OK (and the switch does not return > an error), but a wireshark connected to port 2 does not see anything. One thing to check is... is port 2 the port 2 that you're thinking of? There's no well-defined mapping to OpenFlow port numbers and, say, interface numbers (or, for that matter, interface numbers to the labels on physical ports). > Any suggestions are welcome! I'd suggest that you try running POX's openflow.discovery component and see if it works, since it would seem to do pretty much what you're trying to do here (generate LLDP messages from scratch). If it works, check out the messages it's generating and compare them with your own (you can use openflow.debug to save it all as PCAP traces). -- Murphy _______________________________________________ openflow-discuss mailing list openflow-discuss@lists.stanford.edu https://mailman.stanford.edu/mailman/listinfo/openflow-discuss