| Re: SIOCGIFADDR fails in container [message #48677 is a reply to message #48608] |
Mon, 29 October 2012 22:02  |
mose
Messages: 6
Registered: February 2012
Location: Nebraska
|
Junior Member |
|
|
Just to provide some closure to this post, there are other ways to determine the MAC address of an interface. I am now using Net::Frame and its siblings, including Net::Frame::Device. Net::Frame::Device is built on the dumb networking library (libdumbnet on Debian where libdnet conflicts with the DECNet library and libdumb conflicts with the dynamic universal music bibliotheque). Of course, now that I have found a successful way to do this, it is no longer needed for the direction this project is going. 
Net::Frame::Device uses Net::Libdnet and Net::Libdent6. Unfortunately, several installation tests in the Net::Libdnet and Net::Libdnet6 perl modules fail, because libdumbnet cannot figure out the default path out of the container, at least in this configuration. So, the installation has to be forced. The container has eth0 and eth1. There is only one default gateway, which is for eth0.
I haven't looked at the source code for libdumbnet to see what it is trying to do. All of the other calls seem to work OK. At this point, at least, it is not an issue for what I'm trying to do. I'm happy, and I'm moving on.
|
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
