Hi
Following up on a previous email we have done some more deeper digging.
We have two servers, each of them configured with a network interface using
vlan #4.
Doing a ping on host 192.168.4.2, a tcpdump on that same machine shows:
12:28:45.703365 70:71:bc:46:9a:be> ff:ff:ff:ff:ff:ff, ethertype 802.1Q
(0x8100), length 46: vlan 4, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4),
Request who-has 192.168.4.5 tell 192.168.4.2, length 28
which is what we expect
On the controller side, using the wireshark plug-in we see.
OpenFlow Protocol
Header
Version: 0x01
Type: Packet In (AM) (10)
Length: 74
Transaction ID: 0
Packet In
Buffer ID: 747
Frame Total Length: 56
Frame Recv Port: 1
Reason Sent: No matching flow (0)
Frame Data: FFFFFFFFFFFF7071BC469ABE080600010800060400017071...
Ethernet II, Src: 70:71:bc:46:9a:be (70:71:bc:46:9a:be), Dst: Broadcast
(ff:ff:ff:ff:ff:ff)
Destination: Broadcast (ff:ff:ff:ff:ff:ff)
Source: 70:71:bc:46:9a:be (70:71:bc:46:9a:be)
Type: ARP (0x0806)
Trailer: 0000000000000000000000000000
Address Resolution Protocol (request)
Hardware type: Ethernet (0x0001)
Protocol type: IP (0x0800)
Hardware size: 6
Protocol size: 4
Opcode: request (0x0001)
Is gratuitous: False
Sender MAC address: 70:71:bc:46:9a:be (70:71:bc:46:9a:be)
Sender IP address: 192.168.4.2 (192.168.4.2)
Target MAC address: 00:00:00_00:00:00 (00:00:00:00:00:00)
Target IP address: 192.168.4.5 (192.168.4.5)
and a tcpdump on the other server shows:
12:28:45.493121 70:71:bc:46:9a:be> ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806),
length 68: Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.4.5 tell
192.168.4.2, length 54
Somewhere the vlan tag is being dropped. If we correctly understand the
wireshark trace on the controller, it appears that the Indigo firmware is not
fully forwarding the packet.
Any help would be greatly appreciated.
Cheers
Saeed
________________________________
The information in this e-mail may be confidential and subject to legal
professional privilege and/or copyright. National ICT Australia Limited accepts
no liability for any damage caused by this email or its attachments.
_______________________________________________
openflow-discuss mailing list
[email protected]
https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
