Showing posts with label Client. Show all posts
Showing posts with label Client. Show all posts

Tuesday, 10 February 2015

Openvpn client source address on lan topic






I'm wanting my openvpn clients to keep their virtual IP address assigned by the openvpn server when connecting to other resources over the LAN on the openvpn server's network (As well as the internet via the openvpn server's network, the router should see the virtual address as the source address so I can handle the traffic separately from other LAN devices (force an different ext address))

Currently when doing this the other devices on the LAN report the openvpn server's address instead of the virtual address they're assigned.

I.E.


Code:


Server 172.19.195.18
Client 172.19.197.6
FTP 172.19.195.13


If I'm connected to openvpn as the client (172.19.197.6) and I make a connection to the FTP @ 172.19.195.13 it says I'm connecting from 172.19.195.18(Openvpn Server) I want the client to keep it's address ( 172.19.197.6, and I want the FTP server/device to report the client is connecting from there rather then the Openvpn server).

I've looked into Routed Lans,
And attempted integrating this but it doesn't seem to help in my situation.

Any advice/direction or help would be greatly appreciated,
So far I know that the directive "push redirect-gateway def1" should probably be removed and I should not be using NAT via iptables to handle the traffic or at least this is what I think from what I've read now.


server configuration

Code:


dev tun
proto tcp-server
port 1095

ca /etc/openvpn/ca.crt
cert /etc/openvpn/server.crt
key /etc/openvpn/server.key
dh /etc/openvpn/dh1024.pem
tls-auth /etc/openvpn/ta.key 0

client-cert-not-required
username-as-common-name

server 172.19.197.0 255.255.255.0

client-to-client
client-config-dir /etc/openvpn/ccd/


route 172.19.197.0 255.255.255.0
push "route 172.19.197.0 255.255.255.0"
push "dhcp-option DNS 8.8.8.8"
push "dhcp-option DNS 8.8.4.4"

push "redirect-gateway def1"

log-append /var/log/openvpn/server.log
tmp-dir /tmp

plugin /usr/local/lib/openvpn/openvpn-otp.so


client configuration

Code:


remote XXX 1095
ca [inline]
tls-auth [inline] 1

client
dev tun
tls-client
proto tcp-client
route-method exe
route-delay 2
resolv-retry infinite
nobind
persist-key
persist-tun
auth-user-pass
auth-nocache
reneg-sec 0
verb 3


ccd configuration

Code:


iroute 172.19.197.0 255.255.255.0







Nfs: Client won't connect topic






New to Ubuntu. Running 14.04 64bit. Have installed nfs-common, confirmed it's installed, rebooted and tried to mount my non-Ubuntu server unsuccessfully. All the other boxes on the LAN have no problem. Checked to see if the nfs module is loaded.


Code:


# modprobe nfs
modprobe: FATAL: Module nfs not found.


Somehow I don't think it's going to work without the module. Could someone please give me a suggestion.






Friday, 6 February 2015

LTSP client watch youtube video very slow topic






Hello, I just install Ubuntu 14.04 LTSP Server following in this TUT

http://ubuntuforums.org/showthread.php?t=2173749

- Everything good. I create vmware machine as client but When I watch video on youtube, the motion lagging like time lapse video.
- My network switch is 100Mbs
My Server system hardware:
core i5 430M
Ram 4GB
VGA: NVIDIA GeForce GT 330MThank you.






Unable to mount NFS share on client using autofs topic






Hi,
I have a debian wheezy distribution running on a pocket server (cubox-i) on my home network.
I export the NFS shares in /etc/exports on the server:

Code:


/media/myShare  192.168.1.*(rw,all_squash,sync,no_subtree_check)

I can mount it on my ubuntu laptop (client side) and I can access the files:

Code:


mount 192.168.1.2:/media/myShare /mnt/

However, I try to automount it using autofs but it doesn't work (I don't see any information in /var/log/syslog)
Here is the content of my /etc/auto.master file :

Code:


# Mount Cubox NFS shares
/mnt/nfs    /etc/auto.nfs    --timeout=30


Here is the content of my /etc/auto.nfs file :

Code:


# NFS shares rules
myShare  -fstype=auto    192.168.1.2:/media/myShare


Do you have any idea about why it doesn't work?
Or any help to debug it? Where should I look?
Thanks!
Djib'






Thursday, 5 February 2015

Setting up LTSP to build a thin client system topic






I'm am trying to set up on Zorin 9 (Based on Ubuntu 14.04) but am having problems.

I've been following this How-to:

http://ubuntuforums.org/showthread.p...3#post13222023

I'm having problems with the second step.
sudo ltsp-build-client

I get this when running with --debug:

DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/common/001-load-configuration-file
DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/common/001-set-arch
DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/common/001-set-exclude
DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/common/010-etc-hosts
DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/common/010-mount-proc
DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/common/010-set-base
DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/common/010-set-chroot
DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/common/020-rootpath
DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/common/030-update-sshkeys
DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/common/035-update-kernels
DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/common/091-unmount-dirs
DEBUG: Loading plugins in MODE=before-install:
DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/common/000-check-paths
DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/common/000-enable-debug
DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/common/001-load-configuration-file
DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/common/001-set-arch
DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/common/001-set-exclude
DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/common/010-etc-hosts
DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/common/010-mount-proc
DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/common/010-set-base
DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/common/010-set-chroot
DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/common/020-rootpath
DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/common/030-update-sshkeys
DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/common/035-update-kernels
DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/common/091-unmount-dirs
DEBUG: Loading plugins in MODE=install:
DEBUG: Loading plugin: install: /usr/share/ltsp/plugins/ltsp-build-client/common/000-check-paths
DEBUG: Loading plugin: install: /usr/share/ltsp/plugins/ltsp-build-client/common/000-enable-debug
DEBUG: Loading plugin: install: /usr/share/ltsp/plugins/ltsp-build-client/common/001-load-configuration-file
DEBUG: Loading plugin: install: /usr/share/ltsp/plugins/ltsp-build-client/common/001-set-arch
DEBUG: Loading plugin: install: /usr/share/ltsp/plugins/ltsp-build-client/common/001-set-exclude
DEBUG: Loading plugin: install: /usr/share/ltsp/plugins/ltsp-build-client/common/010-etc-hosts
DEBUG: Loading plugin: install: /usr/share/ltsp/plugins/ltsp-build-client/common/010-mount-proc
DEBUG: Loading plugin: install: /usr/share/ltsp/plugins/ltsp-build-client/common/010-set-base
DEBUG: Loading plugin: install: /usr/share/ltsp/plugins/ltsp-build-client/common/010-set-chroot
DEBUG: Loading plugin: install: /usr/share/ltsp/plugins/ltsp-build-client/common/020-rootpath
DEBUG: Loading plugin: install: /usr/share/ltsp/plugins/ltsp-build-client/common/030-update-sshkeys
DEBUG: Loading plugin: install: /usr/share/ltsp/plugins/ltsp-build-client/common/035-update-kernels
DEBUG: Loading plugin: install: /usr/share/ltsp/plugins/ltsp-build-client/common/091-unmount-dirs
DEBUG: Loading plugins in MODE=after-install:
DEBUG: Loading plugin: after-install: /usr/share/ltsp/plugins/ltsp-build-client/common/000-check-paths
DEBUG: Loading plugin: after-install: /usr/share/ltsp/plugins/ltsp-build-client/common/000-enable-debug
DEBUG: Loading plugin: after-install: /usr/share/ltsp/plugins/ltsp-build-client/common/001-load-configuration-file
DEBUG: Loading plugin: after-install: /usr/share/ltsp/plugins/ltsp-build-client/common/001-set-arch
DEBUG: Loading plugin: after-install: /usr/share/ltsp/plugins/ltsp-build-client/common/001-set-exclude
DEBUG: Loading plugin: after-install: /usr/share/ltsp/plugins/ltsp-build-client/common/010-etc-hosts
/usr/share/ltsp/plugins/ltsp-build-client/common/010-etc-hosts: line 3: /opt/ltsp/amd64/etc/hosts: No such file or directory
error: LTSP client installation ended abnormally

I have tried uninstalling ltsp-server and reinstalling. But the same error occurs.

Simply running the build client script again gives:

NOTE: Root directory /opt/ltsp/amd64 already exists, this will lead to problems, please remove it before trying again. Exiting.
error: LTSP client installation ended abnormally

Which when I do returns me to the original error as above.

Any advice?

Thank you






Wednesday, 4 February 2015

Landscape Client not registering topic






Hello all,

I spun up two Ubuntu VM's. I can register the client on one but not the other. I followed the set up instructions the same on both, but can't get the client to register on the Landscape server.

Message says:

Please wait... We were unable to contact the server. Your internet connection may be down. The landscape client will continue to try and contact the server periodically.

Any suggestions I can try?

Thanks,
Leo