[Users] Networking confusion and NIS client inside a CT

[Scott Dowdle]

Steve,

----- "Steve Scaffidi" <stephen at scaffidi.net> wrote:
> We've just started using OpenVZ on a test box here at work and I've
> come across some odd things I don't understand, and can't figure out
> from the wiki.
> 
> It began when I attempted to start an NIS client on a CT and it
> couldn't bind to the NIS server, which is on the host system.
> However, other networking functionality seemed to work properly: ping, wget,
> ssh, etc... (BTW, other physical hosts on the same LAN can bind to
> the NIS server on that host just fine)
> 
> I checked connectivity from the CT to the host, and it seemed fine.
> The host has the IP address 10.1.10.60 and the CT has the address
> 10.1.10.101. The CT's network interface is venet0:0 which is a PTP,
> and there is also a venet0 with no address. This seems to make sense
> given what I've read on the wiki. The part that has me scratching my
> head is this:
> 
> ct-101:/# route -n
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags Metric Ref   
> Use Iface
> 192.0.2.1       0.0.0.0         255.255.255.255 UH    0      0       
> 0 venet0
> 0.0.0.0         192.0.2.1       0.0.0.0         UG    0      0       
> 0 venet0
> 
> I have no idea where this address is coming from or why network
> functionality seems to work at all with this here! I'm really not
> sure what questions to ask or what to search for, hence this email to the
> list! :)
> 
> BTW, both host and CT are debian lenny systems. I started with a
> template that was already there, called "debian-5.0-x86". OpenVZ was
> installed and configured on this system by someone else, but I can't
> figure out what he may have done.
> 
> Any hints as to what's going on, and furthermore, how I might be able
> to get the NIS client working?

I just got ypbind going in a Fedora 11 container.  I had to jump through some config hoops to make sure everything needed was working:

1) Install ypbind
2) Turn on rpcbind (portmapper on some distros)
3) Configure the system to use NIS via authconfig-tui
4) Start rpcbind and ypbind

I wasn't sure if NIS used anything that requires a unique MAC address but it appears not because my container is using a venet device.

My guess would be that you don't have all of the pieces going or you have firewall / iptables issues.

TYL,
-- 
Scott Dowdle
704 Church Street
Belgrade, MT 59714
(406)388-0827 [home]
(406)994-3931 [work]