On 10/13/06, <b class="gmail_sendername">Kirill Korotaev</b> <<a href="mailto:dev@sw.ru">dev@sw.ru</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
AFAICS,<br><br>vznetcfg is to configure host end of veth device.<br>you can put it into the bridge or setup the routing - whatever you want.<br>Just add routing with something like:<br># ip r a <ve ip> dev <out-device>
</blockquote><div><br>How to add routing isn't so much of the problem, but where to add it, and where to get the ip used to add it. The above ip command should work fine, and I'm fine with putting it in the vznetcfg script, but the question is "where do I get the veip from?" Like I said, it seems the IP_ADDRESS in the .conf would be the place for it. However, with the ip there, it tries to add to venet, and the vps _does not start_ without the venet interface setup. I could create another variable for the IP, or get it in another roundabout fashion, but it seems that there should be an elegant way for vznetcfg to get the ip. Even a way to disable IP_ADDRESS from being added to venet would work. (or a way that causes it to just fail at venet network setup instead of preventing the vps from starting at all).
<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">However, the second veth device in VE should be configured as well.<br>And this can be done with srd distribution scripts.
<br>for example, in Redhat based distributions you can<br>create appropriate ifcfg-vethX file with settings.</blockquote><div><br>I have no problems setting up the interface on the VE side.<br><br></div></div>