similar to: Source address problem

Keith, Thanks for the reply and the pointers. > Did you remember to activate kernel ip forwarding? > i.e. echo 1 > /proc/sys/net/ipv4/ip_forward ? I actually forgot to do this, but I have enabled it now in /etc/systctl.conf and can confirm now after a reboot that it's enabled. Unfortunately, still can't ping the node on the LAN. > and when I saw that I was about to cancel

Hallo, after change net-infrastructure on a multinetwork-server can on segment not find the logon-server. Source problem is, that nmbd sending UDP/138 answers from a false IP. 12:08:08.909997 IP 123.4.5.6.138 > 123.4.7.7.138: NBT UDP PACKET(138) 12:08:08.910083 IP 10.9.0.1.138 > 123.4.5.5.138: NBT UDP PACKET(138) UDP/137 and all TCP-traffic are O.K. My server has two active netcards for

Hallo, after change net-infrastructure on a multinetwork-server can on segment not find the logon-server. Source problem is, that nmbd sending UDP/138 answers from a false IP. 12:08:08.909997 IP 123.4.5.6.138 > 123.4.7.7.138: NBT UDP PACKET(138) 12:08:08.910083 IP 10.9.0.1.138 > 123.4.5.5.138: NBT UDP PACKET(138) UDP/137 and all TCP-traffic are O.K. My server has two active netcards for

I have a 4 Node Tinc VPN setup with 2 nodes on my LAN and the other 2 outside the LAN in the cloud. Everything has been working great for about 5 years now, until today when I decided to move one of the nodes to another box. I basically, copied over the /etc/tinc folder to the new server and also moved the /etc/network/interfaces file, so that the new server was an exact mirror (more or less).

Thank you guys for a great product. I have successfully setup a VPN between a cloud server and an internal one (details below). However, I am unable to pass traffic from the cloud to the internal machines behind the tunnel. Internal subnet: 172.23.6.0/24 Host Public IP: 50.242.184.132 Host LAN IP: 172.23.6.148 Host VPN IP: 10.9.0.2 Cloud Server IP: 107.170.55.181 Cloud Server

I tried to build a setup to model and hence learn how to configure samba servers for the setup that I described below. However, a user login in which the profile is defined to be on a samba server that is not the PDC never gets a roaming profile -- instead the user always gets a temporary profile. Looking at the Windows logs, it is complaining about a permissions issue. However, once logged in