Opened 6 years ago

Closed 6 years ago

#1016 closed (fixed)

SCS returns malformed VLAN range

Reported by: Aaron Helsinger Owned by: xyang@maxgigapop.net
Priority: major Milestone:
Component: MAXSCS Version: SPIRAL5
Keywords: Cc: lnevers@bbn.com, tlehman@maxgigapop.net
Dependencies:

Description

With certain hop exclusion list inputs, SCS returns a malformed VLAN Range for vlanRangeAvailability.

Sent options:

{'geni_routing_profile': {u'link': {'hop_exclusion_list': [u'urn:publicid:IDN+emulab.net+interface+procurveA:3.19=753,764,769,772,779,792,802,805,812,819,831,835,844,845,847,856,863,864,871,873,875,885,886,889,905,907,908,914,918,924,935,937,949,956,981-983,992,1000']}}}

Got back a range that was 865-999-999

Attachments (2)

stitch-pg-utah-ig-utah.rspec (1.2 KB) - added by Aaron Helsinger 6 years ago.
request rspec
stitching-scs-expanded-request.xml3 (3.0 KB) - added by Aaron Helsinger 6 years ago.
SCS expanded request rspec

Download all attachments as: .zip

Change History (4)

Changed 6 years ago by Aaron Helsinger

request rspec

Changed 6 years ago by Aaron Helsinger

SCS expanded request rspec

comment:1 Changed 6 years ago by Aaron Helsinger

Also note that that range allows VLANS that were in the list of VLANs to be excluded, specifically it includes these VLANs that should have been excluded:

871,873,875,885,886,889,905,907,908,914,918,924,935,937,949,956,981-983,992

comment:2 Changed 6 years ago by xyang@maxgigapop.net

Resolution: fixed
Status: newclosed

Unusual long vlan range string caused buffer overflow. Fix has been committed. Code updated for test server.

Note: See TracTickets for help on using tickets.