Opened 10 years ago

Closed 9 years ago

#610 closed defect (fixed)

Multi-homed SNMP picks the lowest IP address

Reported by: skylar Owned by: skylar
Priority: critical Milestone: 3.0.3
Component: Both Version:
Keywords: Cc:
Blocked By: Blocking: 599
Estimated Hours: 1 Total Hours: 1.00

Description

This means that if you have 10.0.2.5 (say) as a public address and 192.168.3.1 for your BCCD network, SNMP will choose 10.0.2.5 even if it's sending traffic on 192.168.3.1. ACLs on BCCD systems will silently drop these packets.

Change History (10)

comment:1 Changed 10 years ago by skylar

  • Status changed from new to assigned

seems like setting clientaddr ought to work, but this doesn't change the behavior

comment:2 Changed 10 years ago by skylar

In [3018]:

go one beyond number of cpus to show slowdown (#599)
work around linux routing limitations (#610)

comment:3 Changed 10 years ago by skylar

0.8 hours logged for skylar: think I have a workaround for this

comment:4 Changed 10 years ago by skylar

merged in [3050]

comment:5 Changed 10 years ago by fitz

  • Milestone set to 3.0.3

comment:6 Changed 10 years ago by fitz

In [3053]:

Merge #610 and #611 for milestone:3.0.3

comment:7 Changed 10 years ago by fitz

  • Status changed from assigned to qa

comment:8 Changed 10 years ago by skylar

0.3 hours logged for skylar: this seems to work fine in VB

comment:9 Changed 10 years ago by skylar

works fine in liberation

comment:10 Changed 9 years ago by fitz

  • Resolution set to fixed
  • Status changed from qa to closed
Note: See TracTickets for help on using tickets.