GRE tunnel problem om FreeBSD 5.2.1

From: Erik Mossberg (omikjam_at_spray.se)
Date: 10/20/04

  • Next message: Ronald F. Guilmette: "Re: aio_connect ?" 
    To: freebsd-net@freebsd.org
Date: Wed, 20 Oct 2004 20:11:04 GMT

       Hello,
       I have a weird problem with a GRE tunnel, the setup is as follows;
       gre0: flags=b051<UP,POINTOPOINT,RUNNING,LINK0,LINK1,MULTICAST> mtu
       1476
               tunnel inet 213.67.20.137 --> 194.145.248.113
               inet 194.145.248.138 --> 194.145.248.137 netmask 0xfffffffc
       And I've tried both w/ and w/o the link1 option mentioned in the man
       page for gre.
       and netstat -rn -f inet:
       Destination Gateway Flags Refs Use Netif
       Expire
       default 213.67.20.1 UGS 17 19250541 rl1
       127.0.0.1 127.0.0.1 UH 1 1802 lo0
       192.168.0 link#1 UC 0 0 rl0
       192.168.0.54 00:04:75:c8:18:d8 UHLW 2 5683090 rl0
       608
       192.168.0.55 link#1 UHLW 2 140 rl0
       192.168.0.91 00:0d:54:9a:d2:d1 UHLW 0 13538 rl0
       1039
       192.168.0.95 00:0d:88:81:fd:98 UHLW 0 766395
       rl0 5
       192.168.5.2 192.168.5.1 UH 0 12 gif2
       194.145.248.137 194.145.248.138 UH 0 1177 gre0
       213.67.20 link#2 UC 0 0 rl1
       213.67.20.1 00:10:67:00:c4:39 UHLW 1 0 rl1
       234
       213.67.20.108 00:10:67:00:c4:39 UHLW 0 12 rl1
       822
       213.67.20.137 127.0.0.1 UGHS 0 136 lo0
       when I try to ping 194.195.248.137 I have a 95% packet loss, but when
       pinging from remote to 194.145.248.138 works just fine with no packet
       loss.
       tcpdump -eni rl1 shows this:
       22:05:55.148354 0:10:a7:13:bf:58 0:10:67:0:c4:39 0800 122:
       213.67.20.137 > 194.145.248.113: gre (frag 49403:88@752+)
       22:05:56.158351 0:10:a7:13:bf:58 0:10:67:0:c4:39 0800 122:
       213.67.20.137 > 194.145.248.113: gre (frag 49410:88@51176)
       Sometimes the packet 1 or 2 packets goes through and gets a reply
       though.
       I use:
       FreeBSD 5.2.1-RELEASE-p5 #3: Sun Apr 18 22:25:17 CEST 2004
       omicron@fisken:/usr/obj/usr/src/sys/merltock i386
       When google-ing for this problem I found this:
       http://lists.freebsd.org/pipermail/freebsd-current/2004-February/02039
       4.html
       Which seems to be the same problem, can the bug have been brought back
       afterwards?
       I hope I didn't miss any info..
       Regards,
       Erik

    _______________________________________________
    freebsd-net@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-net
    To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"

  • Next message: Ronald F. Guilmette: "Re: aio_connect ?"

    Relevant Pages

    • GRE tunnel problem om FreeBSD 5.2.1
      ... I have a weird problem with a GRE tunnel, ... And I've tried both w/ and w/o the link1 option mentioned in the man ... when I try to ping 194.195.248.137 I have a 95% packet loss, ... pinging from remote to 194.145.248.138 works just fine with no packet ...
      (freebsd-questions)
    • Re: Beyond multicore
      ... Transmission systems are not perfect, ... At the other end there is a decoder that wants to take the packet, ... We can do packet loss concealment. ... See ITU-T G.729B or ETSI/3GPP GSM 06.90 for a thorough treatise ...
      (comp.arch)
    • Re: Copy hangs - File opened twice?
      ... If the BIG file is copied temporarily locally to server_1 and the batch job ... If all works "locally" then really all you have is the network, ... tcp/IP MTU value and when a PC filled a packet ... Some packet loss is to be expected but above a certain ...
      (microsoft.public.win2000.file_system)
    • Re: CPU utilisation cap?
      ... hopefully some possible scheduler effects), and might shed more light on ... i.e., when a packet source sends a UDP packet, does it ... > a sampling process that polls the kernel's notion of CPU% measurement ... What I see is little-to-no packet loss ...
      (freebsd-performance)
    • Re: Telnet over WAN latency troubleshooting
      ... Have you tried pinging with ever increasing packet sizes? ... pings have 100% packet loss). ... > about any MTU padding on the modems. ... The padding issue is at the PPPoE level. ...
      (comp.os.vms)