anastop / latte Goto Github PK

Hi,
I found Latte very promising and would like to use it my my own project. But I have now knowledge about Go. Im wondering to ask does it support Mininet & Pox controller?

Best Regards,

I think this is just the initial steps - and I never read go before, so...
In the final section:

    src := int32(tcp.SrcPort)
    dst := int32(tcp.DstPort)
    if dst == ofport {
        packets_in[src] = time.Now().UnixNano()
    }

    if src == ofport {
        latency := time.Now().UnixNano() - packets_in[dst]
        h.Add(float64(latency / 1000000.0))

you use the switch port as an index, and match the packet_in time
to the response packet and calculate latency. So, do you assume
only one packet from the switch is being served at a time?
Or, will the match find the first packet in the packet_in list?
And what if there is no response packet from the controller (lost packet_in)?

The idea is to replace the offset arithmetic used to walk through a packet and extract specific fields, with a more structured and comprehensive approach.

That is, it would be convenient if we could convert (i.e., "deserialize", "unmarshall", "unpack", ...) a byte slice corresponding to a certain OF packet region (e.g. ofp_match) to a well defined struct. Then accessing the desired packet fields would be as simple as accessing the corresponding struct fields.

This approach can potentially enhance code simplicity and readability, but may hurt performance, especially if the inspected packets contain many variable-sized fields that need many "jump-to-offset"-"read-length"-"jump-to-offset"-... operations.

while clone with github this type of error shows
gocode/src/github.com/google/gopacket/pcap/pcap_unix.go:486:8: error: incompatible types in assignment
p.cur = p.cur.next
gocode/src/github.com/google/gopacket/pcap/pcap_unix.go:486:8: error: incompatible types in assignment
p.cur = p.cur.next
^
gocode/src/github.com/google/gopacket/pcap/pcap_unix.go:507:33: error: incompatible type for field 1 in struct construction
return pcapAddresses{all: p.cur.addresses}
^

#4 pull request submitted.

Hi,

Wanted to know if this tool is compatible with windows platform. If yes could be please assist with steps for running it?

Specifically wanted to know what param should we pass to "-device" options as there is no such naming convention like 'eth0, lan0' in windows.

Any help would be appreciated.

Thanks,