Re: [nox-dev] [mininet-dev] Mininet/Nox randomMacs error
The Python parsing logic in zaku has a few corner cases that it does
not handle. I would suggest trying the destiny version of this
function.
def convert_to_eaddr(val):
if isinstance(val, ethernetaddr):
return val
if isinstance(val, array.array):
val = val.tostring()
if isinstance(val, str) and len(val) == ethernetaddr.LEN:
return create_bin_eaddr(val)
elif isinstance(val, str) or isinstance(val, int) or
isinstance(val, long):
return create_eaddr(val)
return None
Regards
KK
On 5 January 2011 15:51, Yiannis Yiakoumis wrote:
> In the pcap files there are some unexpected packet-ins :
>
> -> Multicast Listener Report Message v2
> -> Neighbour Solicitation.
>
> These are IPv6 packets, with src "::" and dest ff02::16.
>
> 1. Why my switch receives these packets. Should I disable IPv6 or any daemon
> at mininet hosts?
> 2. Could Nox be meshed-up while trying to decode these?
>
> Y.
>
>
> On Wed, Jan 5, 2011 at 3:37 PM, Bob Lantz wrote:
>>
>> As I recall the problem had to do with certain Nox routines trying to be
>> smart and accept either a binary MAC ('\1\2\3\4\5\6') or one in ASCII
>> ('01:02:03:04:05:06'). If it has ASCII 58, ':', it assumes that it's an
>> ASCII MAC and various errors occur. I thought the problem was fixed
>> however...
>> -Bob
>> On Jan 5, 2011, at 2:51 PM, Yiannis Yiakoumis wrote:
>>
>> it might be cause I remember another address that started with 58 as well.
>> What's this bug? I am using zaku..
>>
>> Y.
>>
>> On Wed, Jan 5, 2011 at 2:40 PM, Bob Lantz wrote:
>>>
>>> Is this because we're using an older version of NOX that still has the
>>> colon (i.e. chr(58)) bug?
>>>
>>> On Jan 5, 2011, at 2:06 PM, Yiannis Yiakoumis wrote:
>>>
>>> > Hi,
>>> >
>>> > I am writing a simple script using Mininet and Nox. When I don't set
>>> > the setAutoMacs=True in Mininet, randomly selected MACs seem to cause
>>> > problems to Nox. Nox just shows an "invalid ethernet addr" message and
>>> > skips
>>> > the packet. It comes from nox/lib/util.py, lines 278-285. Here is an
>>> > output
>>> > :
>>> >
>>> > array('B', [2, 129, 31, 58, 172, 59])
>>> > invalid ethernet addr
>>> > array('B', [2, 129, 31, 58, 172, 59])
>>> > invalid ethernet addr
>>> > array('B', [2, 129, 31, 58, 172, 59])
>>> > invalid ethernet addr
>>> > array('B', [2, 129, 31, 58, 172, 59])
>>> > invalid ethernet addr
>>> > array('B', [2, 129, 31, 58, 172, 59])
>>> > invalid ethernet addr
>>> > array('B', [2, 129, 31, 58, 172, 59])
>>> > invalid ethernet addr
>>> >
>>> > Setting setAutoMacs=True seems to solve the problem...
>>> >
>>> > Thanks,
>>> > Y.
>>> > ___
>>> > mininet-dev mailing list
>>> > mininet-...@lists.stanford.edu
>>> > https://mailman.stanford.edu/mailman/listinfo/mininet-dev
>>>
>>
>>
>
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
Re: [nox-dev] dl_vlan not correct?
Hi KK,
Sorry you are right. I'll email the openflow-discuess. This isn't a NOX
issue. BTW, sorry for all the failed attachments.
Aaron
On Wed, Jan 5, 2011 at 6:13 PM, kk yap wrote:
> Hi Aaron,
>
> Let me get this right. You see the 802.1Q tag for a switch and not
> another. What does this has to do with NOX? NOX will simply parse
> the packet it receives. Should this email to be openflow-discuss
> instead? Correct me if I am misinterpreting.
>
> Regards
> KK
>
> On 5 January 2011 15:11, Aaron Rosen wrote:
> > Gah wrong permissions on file here we go..
> >
> > Sorry,
> >
> > Aaron
> >
> > On Wed, Jan 5, 2011 at 6:08 PM, Aaron Rosen wrote:
> >>
> >> Opps, sorry for got to attach the laptop dump file.
> >>
> >> Aaron
> >>
> >> On Wed, Jan 5, 2011 at 6:08 PM, Aaron Rosen wrote:
> >>>
> >>> Hi KK,
> >>>
> >>> Attached are two wireshark dump files. One is a dump from my laptop
> >>> plugged into the trunk port (on the hp switch). If you look at it in
> >>> wireshark all of these packets have a 802.1Q virtual LAN frame with an
> ID of
> >>> either 845, 846, or 847.
> >>>
> >>> The other dump file 'dump_at_controller', is a wireshark capture at the
> >>> controller where an switch running indigo is pointing. If you look at
> all of
> >>> these packet_in events I don't see any of these 802.1Q frames.
> >>>
> >>> Thanks,
> >>>
> >>> Aaron
> >>>
> >>>
> >>>
> >>> On Wed, Jan 5, 2011 at 5:58 PM, kk yap wrote:
>
> Hi Aaron,
>
> Can you tell us if there is any difference in the tcpdump from the HP
> and Indigo?
>
> I skimmed through the NOX code and it seems to parse VLAN. So, there
> is something amiss here.
>
> Regards
> KK
>
> On 5 January 2011 14:50, Srini Seetharaman
> wrote:
> > I'm a bit confused by what you see with Indigo. Here's what I said:
> > - HP switch: Packet_ins seen at the controller will not have the
> VLAN
> > tag, but outgoing packets in the dataplane will have the appropriate
> > tag.
> > - Indigo switch: Packet_ins seen at the controller will have the
> VLAN
> > tag if tagged packets are sent to it. For outgoing packets to have
> the
> > tag, the controller has to add the tag (as an additional action).
> >
> > On Wed, Jan 5, 2011 at 2:37 PM, Aaron Rosen
> > wrote:
> >> Hi Srini,
> >>
> >> In my topology I have an HP switch which I have configured a port
> to
> >> tag
> >> several vlans. If I plug my laptop into this port I'm able to see
> the
> >> correct vlan values. Now If I plug a switch into this port that is
> >> running
> >> the indigo firmware when the controller gets the packets I'm seeing
> >> 0x
> >> as the value instead of the correct value I see with my laptop
> using
> >> wireshark.
> >>
> >> (According to your response this should be fine? )
> >>
> >> Aaron
> >>
> >> On Wed, Jan 5, 2011 at 5:31 PM, Srini Seetharaman
> >>
> >> wrote:
> >>>
> >>> Hi Aaron
> >>> Only pure-OF switches (like Pronto switch with Indigo firmware)
> will
> >>> send the VLAN tag to the controller. With others, the tag is
> usually
> >>> added / stripped by the VLAN configs on the switch. So, you'll not
> >>> get
> >>> to see them.
> >>>
> >>> Srini.
> >>>
> >>> On Wed, Jan 5, 2011 at 2:23 PM, Aaron Rosen
> >>> wrote:
> >>> > Hello,
> >>> >
> >>> > I'm trying to extract the dl_vlan value from packets on a trunk
> >>> > port.
> >>> > When I
> >>> > plug my computer into the trunk port and run tcpdump I see the
> >>> > correct
> >>> > 802.1Q values. Though when I attach this port to my openflow
> >>> > switch
> >>> > (running
> >>> > the pronto firmware) I can't get the correct values at my
> >>> > controller.
> >>> >
> >>> > In my controller I'm running these few lines of code to print
> out
> >>> > what's
> >>> > in
> >>> > the packet.
> >>> >
> >>> > test = extract_flow(packet)
> >>> > print test.keys()
> >>> > print test.values()
> >>> >
> >>> > From this: I'm getting the following output
> >>> >
> >>> > ['dl_type', 'nw_dst', 'dl_vlan_pcp', 'dl_src', 'nw_proto',
> >>> > 'nw_tos',
> >>> > 'tp_dst', 'tp_src', 'dl_dst', 'dl_vlan', 'nw_src']
> >>> > [2048, 4294967295, 0, array('B', [0, 27, 177, 2, 100, 167]), 17,
> >>> > 0, 698,
> >>> > 698, array('B', [255, 255, 255, 255, 255, 255]), 65535,
> >>> > 2189371010]
> >>> >
> >>> > I'm getting 65535 for every packet and that is not correct from
> >>> > what I'm
> >>> > seeing with tcpdump and not what I'm expecting.
> >>> >
> >>> > Can someone point out where I'm going wrong.
> >>> >
> >>> > Thanks,
> >>> >
> >>> > Aaron
> >>> >
> >>> > --
> >>> > Aaron O. Ro
Re: [nox-dev] dl_vlan not correct?
Hi Aaron,
Let me get this right. You see the 802.1Q tag for a switch and not
another. What does this has to do with NOX? NOX will simply parse
the packet it receives. Should this email to be openflow-discuss
instead? Correct me if I am misinterpreting.
Regards
KK
On 5 January 2011 15:11, Aaron Rosen wrote:
> Gah wrong permissions on file here we go..
>
> Sorry,
>
> Aaron
>
> On Wed, Jan 5, 2011 at 6:08 PM, Aaron Rosen wrote:
>>
>> Opps, sorry for got to attach the laptop dump file.
>>
>> Aaron
>>
>> On Wed, Jan 5, 2011 at 6:08 PM, Aaron Rosen wrote:
>>>
>>> Hi KK,
>>>
>>> Attached are two wireshark dump files. One is a dump from my laptop
>>> plugged into the trunk port (on the hp switch). If you look at it in
>>> wireshark all of these packets have a 802.1Q virtual LAN frame with an ID of
>>> either 845, 846, or 847.
>>>
>>> The other dump file 'dump_at_controller', is a wireshark capture at the
>>> controller where an switch running indigo is pointing. If you look at all of
>>> these packet_in events I don't see any of these 802.1Q frames.
>>>
>>> Thanks,
>>>
>>> Aaron
>>>
>>>
>>>
>>> On Wed, Jan 5, 2011 at 5:58 PM, kk yap wrote:
Hi Aaron,
Can you tell us if there is any difference in the tcpdump from the HP
and Indigo?
I skimmed through the NOX code and it seems to parse VLAN. So, there
is something amiss here.
Regards
KK
On 5 January 2011 14:50, Srini Seetharaman
wrote:
> I'm a bit confused by what you see with Indigo. Here's what I said:
> - HP switch: Packet_ins seen at the controller will not have the VLAN
> tag, but outgoing packets in the dataplane will have the appropriate
> tag.
> - Indigo switch: Packet_ins seen at the controller will have the VLAN
> tag if tagged packets are sent to it. For outgoing packets to have the
> tag, the controller has to add the tag (as an additional action).
>
> On Wed, Jan 5, 2011 at 2:37 PM, Aaron Rosen
> wrote:
>> Hi Srini,
>>
>> In my topology I have an HP switch which I have configured a port to
>> tag
>> several vlans. If I plug my laptop into this port I'm able to see the
>> correct vlan values. Now If I plug a switch into this port that is
>> running
>> the indigo firmware when the controller gets the packets I'm seeing
>> 0x
>> as the value instead of the correct value I see with my laptop using
>> wireshark.
>>
>> (According to your response this should be fine? )
>>
>> Aaron
>>
>> On Wed, Jan 5, 2011 at 5:31 PM, Srini Seetharaman
>>
>> wrote:
>>>
>>> Hi Aaron
>>> Only pure-OF switches (like Pronto switch with Indigo firmware) will
>>> send the VLAN tag to the controller. With others, the tag is usually
>>> added / stripped by the VLAN configs on the switch. So, you'll not
>>> get
>>> to see them.
>>>
>>> Srini.
>>>
>>> On Wed, Jan 5, 2011 at 2:23 PM, Aaron Rosen
>>> wrote:
>>> > Hello,
>>> >
>>> > I'm trying to extract the dl_vlan value from packets on a trunk
>>> > port.
>>> > When I
>>> > plug my computer into the trunk port and run tcpdump I see the
>>> > correct
>>> > 802.1Q values. Though when I attach this port to my openflow
>>> > switch
>>> > (running
>>> > the pronto firmware) I can't get the correct values at my
>>> > controller.
>>> >
>>> > In my controller I'm running these few lines of code to print out
>>> > what's
>>> > in
>>> > the packet.
>>> >
>>> > test = extract_flow(packet)
>>> > print test.keys()
>>> > print test.values()
>>> >
>>> > From this: I'm getting the following output
>>> >
>>> > ['dl_type', 'nw_dst', 'dl_vlan_pcp', 'dl_src', 'nw_proto',
>>> > 'nw_tos',
>>> > 'tp_dst', 'tp_src', 'dl_dst', 'dl_vlan', 'nw_src']
>>> > [2048, 4294967295, 0, array('B', [0, 27, 177, 2, 100, 167]), 17,
>>> > 0, 698,
>>> > 698, array('B', [255, 255, 255, 255, 255, 255]), 65535,
>>> > 2189371010]
>>> >
>>> > I'm getting 65535 for every packet and that is not correct from
>>> > what I'm
>>> > seeing with tcpdump and not what I'm expecting.
>>> >
>>> > Can someone point out where I'm going wrong.
>>> >
>>> > Thanks,
>>> >
>>> > Aaron
>>> >
>>> > --
>>> > Aaron O. Rosen
>>> > Masters Student - Network Communication
>>> > 306B Fluor Daniel
>>> > 843.425.9777
>>> >
>>> >
>>> > ___
>>> > nox-dev mailing list
>>> > nox-dev@noxrepo.org
>>> > http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
>>> >
>>> >
>>
>>
>>
>> --
>> Aaron O. Rosen
>> Masters Student - Network Communication
>> 306B Fluor Daniel
>> 843.425.
Re: [nox-dev] dl_vlan not correct?
Opps, sorry for got to attach the laptop dump file.
Aaron
On Wed, Jan 5, 2011 at 6:08 PM, Aaron Rosen wrote:
> Hi KK,
>
> Attached are two wireshark dump files. One is a dump from my laptop plugged
> into the trunk port (on the hp switch). If you look at it in wireshark all
> of these packets have a 802.1Q virtual LAN frame with an ID of either 845,
> 846, or 847.
>
> The other dump file 'dump_at_controller', is a wireshark capture at the
> controller where an switch running indigo is pointing. If you look at all of
> these packet_in events I don't see any of these 802.1Q frames.
>
> Thanks,
>
> Aaron
>
>
>
>
> On Wed, Jan 5, 2011 at 5:58 PM, kk yap wrote:
>
>> Hi Aaron,
>>
>> Can you tell us if there is any difference in the tcpdump from the HP
>> and Indigo?
>>
>> I skimmed through the NOX code and it seems to parse VLAN. So, there
>> is something amiss here.
>>
>> Regards
>> KK
>>
>> On 5 January 2011 14:50, Srini Seetharaman wrote:
>> > I'm a bit confused by what you see with Indigo. Here's what I said:
>> > - HP switch: Packet_ins seen at the controller will not have the VLAN
>> > tag, but outgoing packets in the dataplane will have the appropriate
>> > tag.
>> > - Indigo switch: Packet_ins seen at the controller will have the VLAN
>> > tag if tagged packets are sent to it. For outgoing packets to have the
>> > tag, the controller has to add the tag (as an additional action).
>> >
>> > On Wed, Jan 5, 2011 at 2:37 PM, Aaron Rosen wrote:
>> >> Hi Srini,
>> >>
>> >> In my topology I have an HP switch which I have configured a port to
>> tag
>> >> several vlans. If I plug my laptop into this port I'm able to see the
>> >> correct vlan values. Now If I plug a switch into this port that is
>> running
>> >> the indigo firmware when the controller gets the packets I'm seeing
>> 0x
>> >> as the value instead of the correct value I see with my laptop using
>> >> wireshark.
>> >>
>> >> (According to your response this should be fine? )
>> >>
>> >> Aaron
>> >>
>> >> On Wed, Jan 5, 2011 at 5:31 PM, Srini Seetharaman <
>> seeth...@stanford.edu>
>> >> wrote:
>> >>>
>> >>> Hi Aaron
>> >>> Only pure-OF switches (like Pronto switch with Indigo firmware) will
>> >>> send the VLAN tag to the controller. With others, the tag is usually
>> >>> added / stripped by the VLAN configs on the switch. So, you'll not get
>> >>> to see them.
>> >>>
>> >>> Srini.
>> >>>
>> >>> On Wed, Jan 5, 2011 at 2:23 PM, Aaron Rosen
>> wrote:
>> >>> > Hello,
>> >>> >
>> >>> > I'm trying to extract the dl_vlan value from packets on a trunk
>> port.
>> >>> > When I
>> >>> > plug my computer into the trunk port and run tcpdump I see the
>> correct
>> >>> > 802.1Q values. Though when I attach this port to my openflow switch
>> >>> > (running
>> >>> > the pronto firmware) I can't get the correct values at my
>> controller.
>> >>> >
>> >>> > In my controller I'm running these few lines of code to print out
>> what's
>> >>> > in
>> >>> > the packet.
>> >>> >
>> >>> > test = extract_flow(packet)
>> >>> > print test.keys()
>> >>> > print test.values()
>> >>> >
>> >>> > From this: I'm getting the following output
>> >>> >
>> >>> > ['dl_type', 'nw_dst', 'dl_vlan_pcp', 'dl_src', 'nw_proto', 'nw_tos',
>> >>> > 'tp_dst', 'tp_src', 'dl_dst', 'dl_vlan', 'nw_src']
>> >>> > [2048, 4294967295, 0, array('B', [0, 27, 177, 2, 100, 167]), 17, 0,
>> 698,
>> >>> > 698, array('B', [255, 255, 255, 255, 255, 255]), 65535, 2189371010]
>> >>> >
>> >>> > I'm getting 65535 for every packet and that is not correct from what
>> I'm
>> >>> > seeing with tcpdump and not what I'm expecting.
>> >>> >
>> >>> > Can someone point out where I'm going wrong.
>> >>> >
>> >>> > Thanks,
>> >>> >
>> >>> > Aaron
>> >>> >
>> >>> > --
>> >>> > Aaron O. Rosen
>> >>> > Masters Student - Network Communication
>> >>> > 306B Fluor Daniel
>> >>> > 843.425.9777
>> >>> >
>> >>> >
>> >>> > ___
>> >>> > nox-dev mailing list
>> >>> > nox-dev@noxrepo.org
>> >>> > http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
>> >>> >
>> >>> >
>> >>
>> >>
>> >>
>> >> --
>> >> Aaron O. Rosen
>> >> Masters Student - Network Communication
>> >> 306B Fluor Daniel
>> >> 843.425.9777
>> >>
>> >>
>> >
>> > ___
>> > nox-dev mailing list
>> > nox-dev@noxrepo.org
>> > http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
>> >
>>
>
>
>
> --
> Aaron O. Rosen
> Masters Student - Network Communication
> 306B Fluor Daniel
> 843.425.9777
>
>
--
Aaron O. Rosen
Masters Student - Network Communication
306B Fluor Daniel
843.425.9777
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
Re: [nox-dev] dl_vlan not correct?
Hi KK,
Attached are two wireshark dump files. One is a dump from my laptop plugged
into the trunk port (on the hp switch). If you look at it in wireshark all
of these packets have a 802.1Q virtual LAN frame with an ID of either 845,
846, or 847.
The other dump file 'dump_at_controller', is a wireshark capture at the
controller where an switch running indigo is pointing. If you look at all of
these packet_in events I don't see any of these 802.1Q frames.
Thanks,
Aaron
On Wed, Jan 5, 2011 at 5:58 PM, kk yap wrote:
> Hi Aaron,
>
> Can you tell us if there is any difference in the tcpdump from the HP
> and Indigo?
>
> I skimmed through the NOX code and it seems to parse VLAN. So, there
> is something amiss here.
>
> Regards
> KK
>
> On 5 January 2011 14:50, Srini Seetharaman wrote:
> > I'm a bit confused by what you see with Indigo. Here's what I said:
> > - HP switch: Packet_ins seen at the controller will not have the VLAN
> > tag, but outgoing packets in the dataplane will have the appropriate
> > tag.
> > - Indigo switch: Packet_ins seen at the controller will have the VLAN
> > tag if tagged packets are sent to it. For outgoing packets to have the
> > tag, the controller has to add the tag (as an additional action).
> >
> > On Wed, Jan 5, 2011 at 2:37 PM, Aaron Rosen wrote:
> >> Hi Srini,
> >>
> >> In my topology I have an HP switch which I have configured a port to tag
> >> several vlans. If I plug my laptop into this port I'm able to see the
> >> correct vlan values. Now If I plug a switch into this port that is
> running
> >> the indigo firmware when the controller gets the packets I'm seeing
> 0x
> >> as the value instead of the correct value I see with my laptop using
> >> wireshark.
> >>
> >> (According to your response this should be fine? )
> >>
> >> Aaron
> >>
> >> On Wed, Jan 5, 2011 at 5:31 PM, Srini Seetharaman <
> seeth...@stanford.edu>
> >> wrote:
> >>>
> >>> Hi Aaron
> >>> Only pure-OF switches (like Pronto switch with Indigo firmware) will
> >>> send the VLAN tag to the controller. With others, the tag is usually
> >>> added / stripped by the VLAN configs on the switch. So, you'll not get
> >>> to see them.
> >>>
> >>> Srini.
> >>>
> >>> On Wed, Jan 5, 2011 at 2:23 PM, Aaron Rosen
> wrote:
> >>> > Hello,
> >>> >
> >>> > I'm trying to extract the dl_vlan value from packets on a trunk port.
> >>> > When I
> >>> > plug my computer into the trunk port and run tcpdump I see the
> correct
> >>> > 802.1Q values. Though when I attach this port to my openflow switch
> >>> > (running
> >>> > the pronto firmware) I can't get the correct values at my controller.
> >>> >
> >>> > In my controller I'm running these few lines of code to print out
> what's
> >>> > in
> >>> > the packet.
> >>> >
> >>> > test = extract_flow(packet)
> >>> > print test.keys()
> >>> > print test.values()
> >>> >
> >>> > From this: I'm getting the following output
> >>> >
> >>> > ['dl_type', 'nw_dst', 'dl_vlan_pcp', 'dl_src', 'nw_proto', 'nw_tos',
> >>> > 'tp_dst', 'tp_src', 'dl_dst', 'dl_vlan', 'nw_src']
> >>> > [2048, 4294967295, 0, array('B', [0, 27, 177, 2, 100, 167]), 17, 0,
> 698,
> >>> > 698, array('B', [255, 255, 255, 255, 255, 255]), 65535, 2189371010]
> >>> >
> >>> > I'm getting 65535 for every packet and that is not correct from what
> I'm
> >>> > seeing with tcpdump and not what I'm expecting.
> >>> >
> >>> > Can someone point out where I'm going wrong.
> >>> >
> >>> > Thanks,
> >>> >
> >>> > Aaron
> >>> >
> >>> > --
> >>> > Aaron O. Rosen
> >>> > Masters Student - Network Communication
> >>> > 306B Fluor Daniel
> >>> > 843.425.9777
> >>> >
> >>> >
> >>> > ___
> >>> > nox-dev mailing list
> >>> > nox-dev@noxrepo.org
> >>> > http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
> >>> >
> >>> >
> >>
> >>
> >>
> >> --
> >> Aaron O. Rosen
> >> Masters Student - Network Communication
> >> 306B Fluor Daniel
> >> 843.425.9777
> >>
> >>
> >
> > ___
> > nox-dev mailing list
> > nox-dev@noxrepo.org
> > http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
> >
>
--
Aaron O. Rosen
Masters Student - Network Communication
306B Fluor Daniel
843.425.9777
dump_at_controller
Description: Binary data
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
Re: [nox-dev] dl_vlan not correct?
Hi Aaron,
Can you tell us if there is any difference in the tcpdump from the HP
and Indigo?
I skimmed through the NOX code and it seems to parse VLAN. So, there
is something amiss here.
Regards
KK
On 5 January 2011 14:50, Srini Seetharaman wrote:
> I'm a bit confused by what you see with Indigo. Here's what I said:
> - HP switch: Packet_ins seen at the controller will not have the VLAN
> tag, but outgoing packets in the dataplane will have the appropriate
> tag.
> - Indigo switch: Packet_ins seen at the controller will have the VLAN
> tag if tagged packets are sent to it. For outgoing packets to have the
> tag, the controller has to add the tag (as an additional action).
>
> On Wed, Jan 5, 2011 at 2:37 PM, Aaron Rosen wrote:
>> Hi Srini,
>>
>> In my topology I have an HP switch which I have configured a port to tag
>> several vlans. If I plug my laptop into this port I'm able to see the
>> correct vlan values. Now If I plug a switch into this port that is running
>> the indigo firmware when the controller gets the packets I'm seeing 0x
>> as the value instead of the correct value I see with my laptop using
>> wireshark.
>>
>> (According to your response this should be fine? )
>>
>> Aaron
>>
>> On Wed, Jan 5, 2011 at 5:31 PM, Srini Seetharaman
>> wrote:
>>>
>>> Hi Aaron
>>> Only pure-OF switches (like Pronto switch with Indigo firmware) will
>>> send the VLAN tag to the controller. With others, the tag is usually
>>> added / stripped by the VLAN configs on the switch. So, you'll not get
>>> to see them.
>>>
>>> Srini.
>>>
>>> On Wed, Jan 5, 2011 at 2:23 PM, Aaron Rosen wrote:
>>> > Hello,
>>> >
>>> > I'm trying to extract the dl_vlan value from packets on a trunk port.
>>> > When I
>>> > plug my computer into the trunk port and run tcpdump I see the correct
>>> > 802.1Q values. Though when I attach this port to my openflow switch
>>> > (running
>>> > the pronto firmware) I can't get the correct values at my controller.
>>> >
>>> > In my controller I'm running these few lines of code to print out what's
>>> > in
>>> > the packet.
>>> >
>>> > test = extract_flow(packet)
>>> > print test.keys()
>>> > print test.values()
>>> >
>>> > From this: I'm getting the following output
>>> >
>>> > ['dl_type', 'nw_dst', 'dl_vlan_pcp', 'dl_src', 'nw_proto', 'nw_tos',
>>> > 'tp_dst', 'tp_src', 'dl_dst', 'dl_vlan', 'nw_src']
>>> > [2048, 4294967295, 0, array('B', [0, 27, 177, 2, 100, 167]), 17, 0, 698,
>>> > 698, array('B', [255, 255, 255, 255, 255, 255]), 65535, 2189371010]
>>> >
>>> > I'm getting 65535 for every packet and that is not correct from what I'm
>>> > seeing with tcpdump and not what I'm expecting.
>>> >
>>> > Can someone point out where I'm going wrong.
>>> >
>>> > Thanks,
>>> >
>>> > Aaron
>>> >
>>> > --
>>> > Aaron O. Rosen
>>> > Masters Student - Network Communication
>>> > 306B Fluor Daniel
>>> > 843.425.9777
>>> >
>>> >
>>> > ___
>>> > nox-dev mailing list
>>> > nox-dev@noxrepo.org
>>> > http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
>>> >
>>> >
>>
>>
>>
>> --
>> Aaron O. Rosen
>> Masters Student - Network Communication
>> 306B Fluor Daniel
>> 843.425.9777
>>
>>
>
> ___
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
Re: [nox-dev] dl_vlan not correct?
I'm a bit confused by what you see with Indigo. Here's what I said:
- HP switch: Packet_ins seen at the controller will not have the VLAN
tag, but outgoing packets in the dataplane will have the appropriate
tag.
- Indigo switch: Packet_ins seen at the controller will have the VLAN
tag if tagged packets are sent to it. For outgoing packets to have the
tag, the controller has to add the tag (as an additional action).
On Wed, Jan 5, 2011 at 2:37 PM, Aaron Rosen wrote:
> Hi Srini,
>
> In my topology I have an HP switch which I have configured a port to tag
> several vlans. If I plug my laptop into this port I'm able to see the
> correct vlan values. Now If I plug a switch into this port that is running
> the indigo firmware when the controller gets the packets I'm seeing 0x
> as the value instead of the correct value I see with my laptop using
> wireshark.
>
> (According to your response this should be fine? )
>
> Aaron
>
> On Wed, Jan 5, 2011 at 5:31 PM, Srini Seetharaman
> wrote:
>>
>> Hi Aaron
>> Only pure-OF switches (like Pronto switch with Indigo firmware) will
>> send the VLAN tag to the controller. With others, the tag is usually
>> added / stripped by the VLAN configs on the switch. So, you'll not get
>> to see them.
>>
>> Srini.
>>
>> On Wed, Jan 5, 2011 at 2:23 PM, Aaron Rosen wrote:
>> > Hello,
>> >
>> > I'm trying to extract the dl_vlan value from packets on a trunk port.
>> > When I
>> > plug my computer into the trunk port and run tcpdump I see the correct
>> > 802.1Q values. Though when I attach this port to my openflow switch
>> > (running
>> > the pronto firmware) I can't get the correct values at my controller.
>> >
>> > In my controller I'm running these few lines of code to print out what's
>> > in
>> > the packet.
>> >
>> > test = extract_flow(packet)
>> > print test.keys()
>> > print test.values()
>> >
>> > From this: I'm getting the following output
>> >
>> > ['dl_type', 'nw_dst', 'dl_vlan_pcp', 'dl_src', 'nw_proto', 'nw_tos',
>> > 'tp_dst', 'tp_src', 'dl_dst', 'dl_vlan', 'nw_src']
>> > [2048, 4294967295, 0, array('B', [0, 27, 177, 2, 100, 167]), 17, 0, 698,
>> > 698, array('B', [255, 255, 255, 255, 255, 255]), 65535, 2189371010]
>> >
>> > I'm getting 65535 for every packet and that is not correct from what I'm
>> > seeing with tcpdump and not what I'm expecting.
>> >
>> > Can someone point out where I'm going wrong.
>> >
>> > Thanks,
>> >
>> > Aaron
>> >
>> > --
>> > Aaron O. Rosen
>> > Masters Student - Network Communication
>> > 306B Fluor Daniel
>> > 843.425.9777
>> >
>> >
>> > ___
>> > nox-dev mailing list
>> > nox-dev@noxrepo.org
>> > http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
>> >
>> >
>
>
>
> --
> Aaron O. Rosen
> Masters Student - Network Communication
> 306B Fluor Daniel
> 843.425.9777
>
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
Re: [nox-dev] dl_vlan not correct?
Hi Srini,
In my topology I have an HP switch which I have configured a port to tag
several vlans. If I plug my laptop into this port I'm able to see the
correct vlan values. Now If I plug a switch into this port that is running
the indigo firmware when the controller gets the packets I'm seeing 0x
as the value instead of the correct value I see with my laptop using
wireshark.
(According to your response this should be fine? )
Aaron
On Wed, Jan 5, 2011 at 5:31 PM, Srini Seetharaman wrote:
> Hi Aaron
> Only pure-OF switches (like Pronto switch with Indigo firmware) will
> send the VLAN tag to the controller. With others, the tag is usually
> added / stripped by the VLAN configs on the switch. So, you'll not get
> to see them.
>
> Srini.
>
> On Wed, Jan 5, 2011 at 2:23 PM, Aaron Rosen wrote:
> > Hello,
> >
> > I'm trying to extract the dl_vlan value from packets on a trunk port.
> When I
> > plug my computer into the trunk port and run tcpdump I see the correct
> > 802.1Q values. Though when I attach this port to my openflow switch
> (running
> > the pronto firmware) I can't get the correct values at my controller.
> >
> > In my controller I'm running these few lines of code to print out what's
> in
> > the packet.
> >
> > test = extract_flow(packet)
> > print test.keys()
> > print test.values()
> >
> > From this: I'm getting the following output
> >
> > ['dl_type', 'nw_dst', 'dl_vlan_pcp', 'dl_src', 'nw_proto', 'nw_tos',
> > 'tp_dst', 'tp_src', 'dl_dst', 'dl_vlan', 'nw_src']
> > [2048, 4294967295, 0, array('B', [0, 27, 177, 2, 100, 167]), 17, 0, 698,
> > 698, array('B', [255, 255, 255, 255, 255, 255]), 65535, 2189371010]
> >
> > I'm getting 65535 for every packet and that is not correct from what I'm
> > seeing with tcpdump and not what I'm expecting.
> >
> > Can someone point out where I'm going wrong.
> >
> > Thanks,
> >
> > Aaron
> >
> > --
> > Aaron O. Rosen
> > Masters Student - Network Communication
> > 306B Fluor Daniel
> > 843.425.9777
> >
> >
> > ___
> > nox-dev mailing list
> > nox-dev@noxrepo.org
> > http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
> >
> >
>
--
Aaron O. Rosen
Masters Student - Network Communication
306B Fluor Daniel
843.425.9777
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
Re: [nox-dev] dl_vlan not correct?
Hi Aaron
Only pure-OF switches (like Pronto switch with Indigo firmware) will
send the VLAN tag to the controller. With others, the tag is usually
added / stripped by the VLAN configs on the switch. So, you'll not get
to see them.
Srini.
On Wed, Jan 5, 2011 at 2:23 PM, Aaron Rosen wrote:
> Hello,
>
> I'm trying to extract the dl_vlan value from packets on a trunk port. When I
> plug my computer into the trunk port and run tcpdump I see the correct
> 802.1Q values. Though when I attach this port to my openflow switch (running
> the pronto firmware) I can't get the correct values at my controller.
>
> In my controller I'm running these few lines of code to print out what's in
> the packet.
>
> test = extract_flow(packet)
> print test.keys()
> print test.values()
>
> From this: I'm getting the following output
>
> ['dl_type', 'nw_dst', 'dl_vlan_pcp', 'dl_src', 'nw_proto', 'nw_tos',
> 'tp_dst', 'tp_src', 'dl_dst', 'dl_vlan', 'nw_src']
> [2048, 4294967295, 0, array('B', [0, 27, 177, 2, 100, 167]), 17, 0, 698,
> 698, array('B', [255, 255, 255, 255, 255, 255]), 65535, 2189371010]
>
> I'm getting 65535 for every packet and that is not correct from what I'm
> seeing with tcpdump and not what I'm expecting.
>
> Can someone point out where I'm going wrong.
>
> Thanks,
>
> Aaron
>
> --
> Aaron O. Rosen
> Masters Student - Network Communication
> 306B Fluor Daniel
> 843.425.9777
>
>
> ___
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
>
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
[nox-dev] dl_vlan not correct?
Hello,
I'm trying to extract the dl_vlan value from packets on a trunk port. When I
plug my computer into the trunk port and run tcpdump I see the correct
802.1Q values. Though when I attach this port to my openflow switch (running
the pronto firmware) I can't get the correct values at my controller.
In my controller I'm running these few lines of code to print out what's in
the packet.
test = extract_flow(packet)
print test.keys()
print test.values()
>From this: I'm getting the following output
['dl_type', 'nw_dst', 'dl_vlan_pcp', 'dl_src', 'nw_proto', 'nw_tos',
'tp_dst', 'tp_src', 'dl_dst', 'dl_vlan', 'nw_src']
[2048, 4294967295, 0, array('B', [0, 27, 177, 2, 100, 167]), 17, 0, 698,
698, array('B', [255, 255, 255, 255, 255, 255]), 65535, 2189371010]
I'm getting 65535 for every packet and that is not correct from what I'm
seeing with tcpdump and not what I'm expecting.
Can someone point out where I'm going wrong.
Thanks,
Aaron
--
Aaron O. Rosen
Masters Student - Network Communication
306B Fluor Daniel
843.425.9777
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
Re: [nox-dev] Quick Bugfix for pyglue.
Hi Derek, I pushed all the patches. I did not realize you are just exposing things to Python and not declaring new structs. Sorry. A quick glimpse has failed me. Regards KK On 3 January 2011 21:07, Derek Cormier wrote: > Here is a patch for destiny to fix a bug where pyglue.cc was using ntohl on > ofp_flow_stat's cookie field instead of ntohll, which is required for 64-bit > values. > > -Derek > > ___ > nox-dev mailing list > nox-dev@noxrepo.org > http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org > > ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
