Ticket #152 (closed defect: fixed)
Opened 18 months ago
Last modified 16 months ago
ipv6 "default" routes not added when using routes_iface="default"
Reported by: | NightNord@gmail.com | Owned by: | roy |
---|---|---|---|
Priority: | major | Milestone: | |
Component: | rc | Version: | 0.4 |
Keywords: | Cc: |
Description
Very simple - if you are using ipv6 and defaulting all packages through one interface, without gateway (just like OpenVZ does), you will specify i.e. routes_venet0="default" (and latest openvz scripts do just such thing), but when you'll try to ping6 your new host, you'll be dissapointed by results (due to ipv6 routing features packages still will be returning, but with lags uncounted by ping6).
Tested with iproute2
Attachments
Change History
comment:1 Changed 18 months ago by roy
- Status changed from new to accepted
The above attachment should allow this
routes_venet0="default
-f inet6 default"
As your command would just forward ipv4 packets.
Does this fix your issue?
comment:2 Changed 18 months ago by NightNord@gmail.com
Yes, it will help in most cases, when you config your system manually, but that particular situation about openvz scripts, which overwrites venet0 config every time CT started. So, I suggest this small improvement, which make 'default' route really default - for both ipv4 and ipv6. Only thing - it violates standart scheme - 1 execute = 1 'ip' call. As side effect it allows to specify multiply families per route (don't really know if it's usefull).
comment:3 Changed 18 months ago by roy
Could you clarify what you mean by "overwrites venet0 config every time CT started".
Is the configuration file changed or just the routing table?
comment:4 Changed 18 months ago by NightNord@gmail.com
It overwrites /etc/conf.d/net and (re)starts /etc/init.d/net.venet0, that a problem =). Of course, it's possible to change it's scripts, but, imho, that's more logical, that default is default for all.
(Actually it uses sed for this work, so any variables exept {config,routes}_venet0 are saved)