util-vserver - Bugs: bug #27027, Unexpected network behaviour if...
You are not allowed to post comments on this tracker with your current authentication level.
bug #27027: Unexpected network behaviour if prefix not provided
Submitter: | Dave O'Neill <dave0> | ||
Submitted: | Tue 14 Jul 2009 07:46:02 PM UTC | ||
Category: | None | Severity: | 3 - Normal |
Item Group: | Feature Request | Status: | None |
Privacy: | Public | Assigned to: | None |
Open/Closed: | Open | Component Version: | alpha |
Release: | SVN |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
Carbon-Copy List
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follows 1 latest change.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2009-07-14 | dave0 | Carbon-Copy | - | Added -email is unavailable- |
Powered by Savane 3.13-02a9.
Corresponding source code
If /etc/vservers/<servername>/interfaces/0/prefix doesn't exist, the created vserver does not use a local 127.0.0.1 mapped to/from the generated 127.x.y.1 lback address. Instead, all 127.0.0.1 traffic is rewritten to the IP configured in interfaces/0/ip.
This may or may not be a bug, but it's certainly surprising.
Possible fixes/workarounds:
1) in the absence of a prefix or broadcast, default the prefix
to an explicit /32 instead of whatever is occurring now.
2) in the absence of a prefix or broadcast, warn loudly that a
prefix should be defined.
Given that 'ip address add' should default to a /32 if no prefix is added, I'm not sure how the lack of an explicit prefix is clobbering lback -- perhaps someone more familiar with the code can
determine this.
Tested on 2.6.29-vserver-1 from Debian Lenny and 2.6.30.1 with vs2.3.0.36.14-pre4, using util-vserver 0.30.216-pre2772 from Debian Lenny, and util-vserver from SVN trunk (r2842).