| Re: Not understanding networking (beware - tons of questions!) [message #30057 is a reply to message #30025] |
Wed, 07 May 2008 11:50   |
maratrus
Messages: 1495
Registered: August 2007
Location: Moscow
|
Senior Member |
|
|
Hello,
1.
| Quote: |
It is 100% impossible to change the MAC address inside the container for a veth device?
|
I have to admit that you've confused me with this question. So I've started to investigate this issue and found the following facts:
a) This feature was added here "http://git.openvz.org/?p=linux-2.6.18-openvz;a=commit;h=9b04401d0719c5a7f45d0816d3633a68ef79f10c"
b) But if you want to change MAC address from inside the VPS you have to set appropriate permission for this VE from inside the HN
c) The common methods of vzctl utility cannot do this.
http://bugzilla.openvz.org/show_bug.cgi?id=687
But you can write simple program for this purpose and give your VE such permission. If you want I can give you the simple example of such program.
2.
| Quote: |
So inside a VE with venet devices, the gateway is irrelevant - it can be anything?
|
yes
3.
| Quote: |
So the host listens for its own ip plus the ip of the VEs too?
|
a) vzctl put appropriate record to the route table when VE starts(something like VE_IP dev venet0 scope link)
b) When you try to reach your VE arp-request comes to HN.
The node will arp reply for VE_IP if and only if "ip r g VE_IP from HN_IP" ( HN_IP form [incoming dev])
will return a route other than one to [incoming dev]
c) vzctl aso put appropriate record to arp table to allow HN only reply for VE_IP addresses.
d) HN reply for the apr_request
c) Then HN receives other packets
HN works like a common router I'd say.
[Updated on: Wed, 07 May 2008 11:51] Report message to a moderator |
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
