Displaying 4 results from an estimated 4 matches for "grev0".
Did you mean:
greve
2006 Sep 11
2
[HELP] Mutlicast over GRE tunnel
...e -k
23 /usr/sbin/smcroute -d
24 sleep 3
25 /usr/sbin/smcroute -a eth1 192.168.60.250 $MGROUP gretun
26 /usr/sbin/smcroute -j gretun $MGROUP
On RtrB (while running #ping 192.168.50.250 on HOSTB):
/usr/sbin/tcpdump -i eth0 -n
10:46:21.470623 IP 192.168.20.98 > 192.168.20.100: GREv0, length 88: IP
192.168.60.250 > 192.168.50.250: ICMP echo request, id 44558, seq 1,
length 64
10:46:21.476843 IP 192.168.20.100 > 192.168.20.98: GREv0, length 88: IP
192.168.50.250 > 192.168.60.250: ICMP echo reply, id 44558, seq 1, length 64
10:46:22.487867 IP 192.168.20.98 > 192.16...
2013 Apr 10
1
What about port 2048 for GRE(47) packaged in ip protocol
...? ?10.0.4.1/24
? ? ? ? ?---------- MA ------------------------------------------- ?MB?----------
? ? ? ? ? ? ?tun0 ? ? ? ? ?eth0 ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?eth0 ? ? ? ? ?tun0
? ? ? ? ?When I ping MB in MA, and tcpdump eth0 in MA, I get:?
15:06:39.712390 IP 192.168.0.31 > 192.168.0.124: GREv0, length 88: IP 10.0.3.1 > 10.0.4.1: ICMP echo request, id 28797, seq 1, length 64
15:06:39.713232 IP 192.168.0.124 > 192.168.0.31: ICMP 192.168.0.124 protocol 47 port 2048 unreachable, length 116
15:06:39.713667 IP 192.168.0.124 > 192.168.0.31: GREv0, length 88: IP 10.0.4.1 > 10.0.3.1:...
2014 Feb 25
1
Multicast packages dropped
...ndewarteschlangenl?nge:0
RX bytes:18388666 (17.5 MiB) TX bytes:38376786 (36.5 MiB)
While doing a tcpdump (tcpdump ?ni eth0 proto 47 | grep 224.0.0.9), I can see the multicast packages arriving inside the GRE tunnel (see last package):
10:40:34.366661 IP 10.139.10.2 > 192.168.252.26: GREv0, length 536: IP 192.168.250.25.router > 224.0.0.9.router: RIPv2, Response, length: 504
10:40:34.366680 IP 10.139.10.2 > 192.168.252.26: GREv0, length 536: IP 192.168.250.25.router > 224.0.0.9.router: RIPv2, Response, length: 504
10:40:34.366702 IP 10.139.10.2 > 192.168.252.26: GREv0, le...
2013 Dec 10
1
MTU issue when using GRE over tinc
...terface provided by tinc, I'm experiencing MTU problems and I'm not sure how to fix them. The manifestation of the problem is, from the user point of view, communication hang. And using "tcpdump -i there" displays lines such as :
18:54:00.345666 IP 10.111.1.1 > 10.111.1.2: GREv0, key=0x5, length 1438: IP ceph.com.https > 10.0.3.15.57429: Flags [P.], seq 4917:6293, ack 658, win 71, length 1376
18:54:00.345746 IP 10.111.1.2 > 10.111.1.1: ICMP 10.111.1.2 unreachable - need to frag (mtu 1445), length 556
My actual use case very much ressembles what is described here...