similar to: Cannot access other computers on LAN

On 12/1/19 2:29 pm, Lars Kruse wrote: > Hello > > > Am Thu, 10 Jan 2019 11:58:33 +0100 > schrieb Julien dupont <marcelvierzon at gmail.com>: > >> The two tunnels are working. From a client I can ping or ssh VPN_office on >> both tunnel and LAN IPs 172.16.0.2 and 192.168.1.3. I cannot however ping >> any other computer on the LAN, I get no pong back but it

Hello Julien, Am Mon, 14 Jan 2019 22:15:47 +0100 schrieb Julien dupont <marcelvierzon at gmail.com>: > ** Test 1 ** > On VPN_office I use 'tcpdump -npi any icmp and host 192.168.1.3' > When pinging 192.168.1.1 from client 1, with no success, I see no packet > passing. Sorry - the tcpdump command should end with "192.168.1.1" instead of

Hi Julien, Am Mon, 14 Jan 2019 18:04:40 +0100 schrieb Julien dupont <marcelvierzon at gmail.com>: > Investigating with tcpdump withoug guidelines is beyond my skills I'm > afraid. Try this on your VPN_office host: tcpdump -npi any icmp and host 192.168.1.3 In parallel you start a ping from the other network: ping 192.168.1.1 I assume, that tcpdump will show all packets from

Hello Julien, Am Tue, 15 Jan 2019 09:30:23 +0100 schrieb Julien dupont <marcelvierzon at gmail.com>: > In that case I see: > IP 172.16.0.3 > 192.168.1.1: ICMP echo request, id2135, seq1, length 64 > IP 172.16.0.3 > 192.168.1.1: ICMP echo request, id2135, seq2, length 64 > IP 172.16.0.3 > 192.168.1.1: ICMP echo request, id2135, seq3, length 64 > > Packet goes

Hello Julien, Am Tue, 15 Jan 2019 16:33:26 +0100 schrieb Julien dupont <marcelvierzon at gmail.com>: > ip_forward was not enabled, now it is. a good step forward :) (you should do this permanently via /etc/sysctl.d/) > 'iptables -L -vn' yields: > [..] OK. The output tells us, that there are firewall rules. Now you should take a look at your firewall configuration

Le mar. 15 janv. 2019 à 03:13, Lars Kruse <lists at sumpfralle.de> a écrit : > Hello Julien, > > > Am Mon, 14 Jan 2019 22:15:47 +0100 > schrieb Julien dupont <marcelvierzon at gmail.com>: > > > > ** Test 1 ** > > On VPN_office I use 'tcpdump -npi any icmp and host 192.168.1.3' > > When pinging 192.168.1.1 from client 1, with no success, I

I cannot even ping the LAN router on 192.168.1.1, but if I ssh though the tunnel to 192.168.1.3, I can ping it. Investigating with tcpdump withoug guidelines is beyond my skills I'm afraid. I used tinc in router mode because it is proposed like in most howto I found... Would just switching to switch mode makes things easier or that's not related? Le sam. 12 janv. 2019 à 05:17, Hamish

Hello Am Thu, 10 Jan 2019 11:58:33 +0100 schrieb Julien dupont <marcelvierzon at gmail.com>: > The two tunnels are working. From a client I can ping or ssh VPN_office on > both tunnel and LAN IPs 172.16.0.2 and 192.168.1.3. I cannot however ping > any other computer on the LAN, I get no pong back but it is not complaining > he has no route to host. wild guess: maybe the

Hi Lars, Thanks for the help ** Test 1 ** On VPN_office I use 'tcpdump -npi any icmp and host 192.168.1.3' When pinging 192.168.1.1 from client 1, with no success, I see no packet passing. When pinging 192.168.1.3 from client 1, with success, I see packet passing: IP 172.16.0.3 > 192.168.1.3: ICMP echo request, id 2648, seq 23, length 64 IP 192.168.1.3 > 172.16.0.3: ICMP echo

ip_forward was not enabled, now it is. Still same result: On VPN_office I use 'tcpdump -npi any icmp and host 192.168.1.1' and ping 192.168.1.1 from the client: 5:28:42.646203 IP 172.16.0.3 > 192.168.1.1: ICMP echo request, id 1584, seq 1, length 64 15:28:43.663014 IP 172.16.0.3 > 192.168.1.1: ICMP echo request, id 1584, seq 2, length 64 15:28:44.688133 IP 172.16.0.3 >

In most howtos it is instructed to enable port forwarding with 'echo 1 > /proc/sys/net/ipv4/ip_forward', but they don't say it's not permanent... So it was gone when I rebooted the machine. I then disabled the firewall on the VPN_office machine... And it works! If obviously VPN_out must be highly secured, I guess there is no problem to disable the firewall on VPN_office?

Hello, Early this year I got help here to setup tinc tunnels between users and a company LAN. Now I would like to try something different for a home usage and I have a question regarding security. The setup would look like as follows: - My home LAN has a classical topology where my ISP router is doing NAT and is blocking all incoming connection. I'm planning to enable port forwarding on the

I have done it... added on both routers a new firewall zone covering the tinc interface, policy in accept, out accept, fwd accept, interzone forwarding from/to LAN.... when I do it, I am not even able to ping the routers between them, even though the PING PONG is ok in the tinc debug.... 2018-05-24 20:28 GMT+02:00 Naemr . <naemrr at gmail.com>: > did you add a forwarding allow rule from

Dear List, We are planning a genotyping study to be analyzed using false discovery rates (FDRs) (See Storey and Tibshirani PNAS 2003; 100:9440-5). I am interested in learning if there is any consensus as to how many features (ie. how many P values) need to be studied before reasonably reliable FDRs can be derived. Does anyone know of a citation where this is discussed? Bill Dupont William D.

Hello. I''m new to the list and I hope this is not a FAQ. I searched the archives and didn''t find an answer... Quick question : Is there a limitation if the vif code cutting at 1500 bytes ?? I''m trying to implement an IPv6 router/Firewall (2 XenU) Xen 2.0.6, Linux 2.6 is used on xen0 and XenU. The physical machine has 2 interfaces, eth0 (which is connected to an

Dear all, I am trying to configure a basic TINC vpn between two sites using OpenWRT routers. The link seems to work, the ping between the two routers is ok, but I can't ping hosts between the subnets behind the routers. This is the configuration: ======== SITE 1 (CLIENT) - polimnia (subnet 192.168.4.0/24, gw 192.168.4.1) tinc.conf ------------- Name = polimnia ConnectTo = calliope

On Monday, June 22, 2015 9:15 AM ,Rowland Penny wrote: > On 22/06/15 13:55, Brian.Huffman at dupont.com wrote: > > On , June 20, 2015 5:10 AM, Rowland Penny wrote: > >> On 19/06/15 21:39, Brian.Huffman at dupont.com wrote: > >>> All, > >>> > >>> I'm trying to configure a Samba 3 AD member server including > >>> winbind. I'm

Why is there no is.Date function in R? I am running 2.1.1 does it exist in newer version? If there is a reasoning behind the lack of a is.Date function what is it? Thanks Charles -- Charles Dupont Computer System Analyst School of Medicine Phone: (615) 936-6510 Department of Biostatistics Vanderbilt University

On , June 20, 2015 5:10 AM, Rowland Penny wrote: > > On 19/06/15 21:39, Brian.Huffman at dupont.com wrote: > > All, > > > > I'm trying to configure a Samba 3 AD member server including winbind. I'm > on RHEL 6.6, so I'm using Samba version 3.6.23. > > > > Here's my configuration: > > [global] > > log level = 3 winbind:10

All, I'm trying to configure a Samba 3 AD member server including winbind. I'm on RHEL 6.6, so I'm using Samba version 3.6.23. Here's my configuration: [global] log level = 3 winbind:10 workgroup = ABC server string = LV37 netbios name = LV37 idmap config *:backend = tdb idmap config *:range = 2000-9999 idmap config