search for: pubilc

I have a problem I am trying to resolve. I have Linux firewalls protecting the users on many networks. Everything works but Domain logons to the NT4 Domain. This is due to NETBIOS and NAT problem. So I have users that have a private address and a PDC that has a pubilc address due to the network design that can?t be changed. I have install Samba 3.x and thought I could join it to the domain to allow the samba server to handle the connection for the NATed users. Is there a way to do this? I need the local users to be able to authenticate to an NT4 domain or I...

...files, IPv6, 64-bit system inums, 64-bit internal inums rsync comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions. See the GNU General Public Licence for details. -- Patrick Hsieh<pahud@ezplay.tv> GnuPG Pubilc Key at http://www.ezplay.tv/~pahud/pahudatezplay.pubkey MD5 checksum: b948362c94655b74b33e859d58b8de91

...cen "foo" has no write permission under /var/www, he cannot rsync from remote server to the local filesystem because rsync will try to make temp file and unlink the original file before writing over it. Is there any solution to this problem? -- Patrick Hsieh<pahud@ezplay.tv> GnuPG Pubilc Key at http://www.ezplay.tv/~pahud/pahudatezplay.pubkey MD5 checksum: b948362c94655b74b33e859d58b8de91

...tinc-up ip link set tiutl up ip address add 172.16.0.11/24 dev tiutl                     <- works ip route add 172.16.1.0/24 via 172.16.0.5 dev tiutl    <- doesn't work ## The backup servers tinc.conf root at backup-1:~# cat /etc/tinc/tiutl/hosts/gateway_1 Address = 40.10.70.200  # the pubilc connect_to IP Port = 655 Subnet = 172.16.0.5/32 Subnet = 172.16.1.0/24 -----BEGIN RSA PUBLIC KEY----- -----END RSA PUBLIC KEY----- ## From backup, when I try to ping the "gateway" server in the "tiutl" tinc network, this works: root at backup-1:~# ping -c 1 172.16.0.5 PING...

...tinc-up ip link set tiutl up ip address add 172.16.0.11/24 dev tiutl                     <- works ip route add 172.16.1.0/24 via 172.16.0.5 dev tiutl    <- doesn't work ## The backup servers tinc.conf root at backup-1:~# cat /etc/tinc/tiutl/hosts/gateway_1 Address = 40.10.70.200  # the pubilc connect_to IP Port = 655 Subnet = 172.16.0.5/32 Subnet = 172.16.1.0/24 -----BEGIN RSA PUBLIC KEY----- -----END RSA PUBLIC KEY----- ## From backup, when I try to ping the "gateway" server in the "tiutl" tinc network, this works: root at backup-1:~# ping -c 1 172.16.0.5 PING...

...tinc-up ip link set tiutl up ip address add 172.16.0.11/24 dev tiutl                     <- works ip route add 172.16.1.0/24 via 172.16.0.5 dev tiutl    <- doesn't work ## The backup servers tinc.conf root at backup-1:~# cat /etc/tinc/tiutl/hosts/gateway_1 Address = 40.10.70.200  # the pubilc connect_to IP Port = 655 Subnet = 172.16.0.5/32 Subnet = 172.16.1.0/24 -----BEGIN RSA PUBLIC KEY----- -----END RSA PUBLIC KEY----- ## From backup, when I try to ping the "gateway" server in the "tiutl" tinc network, this works: root at backup-1:~# ping -c 1 172.16.0.5 PING...

...address add 172.16.0.11/24 dev tiutl                     <- works > ip route add 172.16.1.0/24 via 172.16.0.5 dev tiutl    <- doesn't work > > > ## The backup servers tinc.conf > > root at backup-1:~# cat /etc/tinc/tiutl/hosts/gateway_1 > Address = 40.10.70.200  # the pubilc connect_to IP > Port = 655 > Subnet = 172.16.0.5/32 > Subnet = 172.16.1.0/24 > > -----BEGIN RSA PUBLIC KEY----- > -----END RSA PUBLIC KEY----- > > > ## From backup, when I try to ping the "gateway" server in the "tiutl" > tinc network, this works: &...

How do I initiate a certificate request without going into non-daemon mode ? According to "Pro Puppet" book, so far the only way I know that can trigger a certficate request with puppet master is like this puppet agent --server=puppetmaster.test.com --no-daemonize --verbose but doing so will break my intention of automation I need to create a puppet client package. A control-C is