strange behaviour of gre(4) tunnel

2006-11-22 Thread Igor Goldenberg
I'm trying to test gre(4) tunnel. Both machines in one LAN. OpenBSD has IP 192.50.51.52, another end - 192.50.51.28. # ifconfig gre0 gre0: flags=9011UP,POINTOPOINT,LINK0,MULTICAST mtu 1476 groups: gre physical address inet 192.50.51.52 -- 192.50.51.28 inet6

Re: strange behaviour of gre(4) tunnel

2006-11-22 Thread Tonnerre LOMBARD
Salut, On Wed, Nov 22, 2006 at 08:52:11PM +0500, Igor Goldenberg wrote: 20:28:38.627914 0:4:23:ce:bb:b4 0:16:cb:a2:8e:c5 0800 122: gre 192.50.51.52 192.50.51.28: [] 192.168.254.254 192.168.254.253: icmp: echo request (id:bd53 seq:44) (ttl 255, id 3713, len 84) (DF) (ttl 64, id 26235, len

Re: strange behaviour of gre(4) tunnel

2006-11-22 Thread Igor Goldenberg
2006/11/22, Tonnerre LOMBARD [EMAIL PROTECTED]: Did you set net.inet.gre.allow to 1? Yes. # sysctl net.inet.gre net.inet.gre.allow=1 net.inet.gre.wccp=0

Re: strange behaviour of gre(4) tunnel

2006-11-22 Thread Berk D. Demir
Igor Goldenberg wrote: I'm trying to test gre(4) tunnel. Both machines in one LAN. OpenBSD has IP 192.50.51.52, another end - 192.50.51.28. [... cut ...] First of all, use an empirical methodology. Destroy your gre tunnel with ifconfig gre0 down ifconfig gre0 destroy Clear

Re: strange behaviour of gre(4) tunnel

2006-11-22 Thread Igor Goldenberg
2006/11/23, Berk D. Demir [EMAIL PROTECTED]: Destroy your gre tunnel with ifconfig gre0 down ifconfig gre0 destroy Done. Clear your ARP table. arp -ad Done. Try to reach 192.50.51.28. For example with ping or telnet to port 22. Then check arp table entry