Ticket #291 (accepted defect)

Opened 22 months ago

Last modified 3 months ago

Losing an IP address causes port forwarding to fail.

Reported by: KevinLai Owned by: KevinLai
Priority: high Milestone: 0.5.4 Stability/Security/Performance
Component: Xen Version:
Severity: normal Keywords:
Cc:

Description

This is probably a routing table problem

Change History

Changed 22 months ago by KevinLai

  • summary changed from Loosing an IP address causes port forwarding to fail. to Losing an IP address causes port forwarding to fail.

Changed 18 months ago by KevinLai

  • milestone changed from 1.0.0 Unscheduled to 0.5.2 PlanetLab

Changed 18 months ago by KevinLai

  • priority changed from normal to highest

Changed 17 months ago by KevinLai

  • priority changed from highest to high
  • milestone changed from 0.5.2 PlanetLab/GUI release to 1.0.0 Unscheduled

This is occuring because the bridged interface has a lower routing metric. This allows it to be used automatically when the user allocates an IP address. However, when the address is lost, there is currently no way to notify the virtual machine. This causes the incoming TCP connection to be routed to oblivion.

I changed the DHCP lease time out to be 300 seconds to limit the extent of the problem. However, the full solution is to provide a way to explicitly notify the virtual machine when it has gained/lost an address.

Changed 3 months ago by KevinLai

  • status changed from new to accepted
  • milestone changed from 1.0.0 Unscheduled to 0.5.4 Stability/Security/Performance
Note: See TracTickets for help on using tickets.