search for: gre0

I am trying to setup GRE between two CentOS 4.5 boxes. I have tried several variations of what''s listed below, but none of them work. box1: modprobe ip_gre ip link set gre0 up ip tunnel add gretun mode gre local 66.1.1.161 remote 66.1.2.161 ttl 20 dev eth0 ip addr add dev gretun 10.253.253.1 peer 10.253.253.2/24 ip link set dev gretun up ip route add 10.2.0.0/16 via 10.253.253.2 box2: modprobe ip_gre ip link set gre0 up ip tunnel add gretun mode gre local 66.1.2.161...

...ng HOWTO" GRE tunneling has some benefits compare to IP-in-IP, on of it benefits is the ability to transport multicast traffic through a GRE tunnel. I used the mrouted daemon and I know that the daemon supports tunneling but I don''t want to use its tunneling method. Assuming I have gre0 as my tunneling device I did the following: 1. declare the following rules: Ip rul add iif eth0 table 100 prio 100 Ip rul add to 240.0.0.0/4 table 101 prio 101 2. declare the following routing table ip route add default dev gre0 tab 100 ip route add 224.0.0.0/4 dev gre0 tab 101 The result was th...

I want to send a multicast packet to multiple gre tunnel, but the packet only went to where the routing table configured to. ex. when use ip route add 224.0.0.0/4 via gre0 then the packet go to gre0 when use ip route add 224.0.0.0/4 via gre1 then the packet go to gre1 when use ip route add 224.0.0.0/4 nexthop via gre1 nexthop via gre0 then the packet go to either gre or gre1 randomly, but not both ( is it for load balance ? ) how to configure the routing...

...97/28 brd 192.168.1.255 scope global eth1 4: eth2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000 link/ether 00:0a:dc:04:7d:dd brd ff:ff:ff:ff:ff:ff 6: w1adsl: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000 link/ether 00:77:77:77:7b:b3 brd ff:ff:ff:ff:ff:ff 9: gre0: <NOARP> mtu 1428 qdisc noop link/gre 0.0.0.0 brd 0.0.0.0 12: GDC1@NONE: <POINTOPOINT,NOARP,PROMISC,UP> mtu 1514 qdisc noqueue link/gre 192.168.1.97 peer 192.168.1.1 inet 192.168.2.97 peer 192.168.2.110/28 scope global GDC1 13: ppp1: <POINTOPOINT,MULTICAST,NOARP,UP> mt...

...link/ether 00:02:a5:df:01:d9 brd ff:ff:ff:ff:ff:ff inet 20.0.0.249/24 brd 20.0.0.255 scope global eth0 3: eth1: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc htb qlen 1000 link/ether 00:0d:88:2d:94:80 brd ff:ff:ff:ff:ff:ff inet 10.0.50.1/24 brd 10.0.50.255 scope global eth1 4: gre0: <NOARP> mtu 1476 qdisc noop link/gre 0.0.0.0 brd 0.0.0.0 5: tunnel0@NONE: <POINTOPOINT,MULTICAST,NOARP,UP> mtu 1476 qdisc noqueue link/gre 20.0.0.249 peer 20.0.0.250 inet 192.168.2.4/24 scope global tunnel0 2) Where did ''gre0'' come from? This leads...

Hello, I connected the network 192.168.1.0 with 192.168.2.0 over the internet trough a GRE-Tunnel. I don''t know if I set up all things right: The client-pcs in both networks have a subnet mask of 255.255.255.0 and 192.168.2.x''s default gateway is the server wich has started the tunnel. The 192.168.1.x''s default gateway is 192.168.1.250 wich routes traffic destinated to

...ything more to make the traffic pass through iptables forward chain. Please look into the configuration ip addr 1: lo: <LOOPBACK> mtu 16436 qdisc noqueue link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: tunl0: <NOARP> mtu 1480 qdisc noop link/ipip 0.0.0.0 brd 0.0.0.0 3: gre0: <NOARP> mtu 1476 qdisc noop link/gre 0.0.0.0 brd 0.0.0.0 10: eth0: <BROADCAST,MULTICAST,PROMISC,UP> mtu 1500 qdisc pfifo_fast qlen 1000 link/ether 00:07:d9:0d:67:5a brd ff:ff:ff:ff:ff:ff 11: eth1: <BROADCAST,MULTICAST,PROMISC,UP> mtu 1500 qdisc pfifo_fast qlen 1000 li...

...e7:36:ac brd ff:ff:ff:ff:ff:ff inet 172.28.0.1/16 brd 172.28.255.255 scope global eth2 5: eth3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000 link/ether 00:0b:db:e7:36:ae brd ff:ff:ff:ff:ff:ff 6: tunl0@NONE: <NOARP> mtu 1480 qdisc noop link/ipip 0.0.0.0 brd 0.0.0.0 7: gre0@NONE: <NOARP> mtu 1476 qdisc noop link/gre 0.0.0.0 brd 0.0.0.0 216.228.3.197 dev eth2 scope link 216.228.3.196 dev eth2 scope link 216.228.3.192/29 dev eth0 proto kernel scope link src 216.228.3.194 172.25.0.0/16 via 172.30.1.239 dev eth1 172.30.0.0/16 dev eth1 proto kernel s...

...r 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff > > 4: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000 > > link/ether 00:50:fc:c3:5e:b3 brd ff:ff:ff:ff:ff:ff > > 5: tunl0@NONE: <NOARP> mtu 1480 qdisc noop > > link/ipip 0.0.0.0 brd 0.0.0.0 > > 6: gre0@NONE: <NOARP> mtu 1476 qdisc noop > > link/gre 0.0.0.0 brd 0.0.0.0 > > Notice that eth1 has no ip address. You must give it an address for > shorewall to work. > > -Alex > > -- Michel D''Astous mdastous@cqmail.net

...,NOTRAILERS,UP> mtu 1500 qdisc pfifo_fast qlen 1000 link/ether 00:30:48:53:25:b2 brd ff:ff:ff:ff:ff:ff inet 81.169.188.152/32 brd 81.169.188.152 scope global eth0 3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000 link/ether 00:30:48:53:25:b3 brd ff:ff:ff:ff:ff:ff 4: gre0: <NOARP> mtu 1476 qdisc noop link/gre 0.0.0.0 brd 0.0.0.0 81.169.188.1 dev eth0 scope link 127.0.0.0/8 via 127.0.0.1 dev lo scope link default via 81.169.188.1 dev eth0 Hello, I configured shorewall (one-interface example-configuration) on my internet server to accept pptp connecti...

...5.253.4.255 scope global eth0 inet 155.253.4.253/24 brd 155.253.4.255 scope global secondary eth0:0 3: dummy0: <BROADCAST,NOARP> mtu 1500 qdisc noop link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff 4: tunl0@NONE: <NOARP> mtu 1480 qdisc noop link/ipip 0.0.0.0 brd 0.0.0.0 5: gre0@NONE: <NOARP> mtu 1476 qdisc noop link/gre 0.0.0.0 brd 0.0.0.0 155.253.4.0/24 dev eth0 proto kernel scope link src 155.253.4.254 10.2.0.0/16 dev eth1 proto kernel scope link src 10.2.1.254 default via 155.253.4.1 dev eth0 metric 1 Bye -- Mauro G. Todeschini e-mail: m.todeschini...

[Disclaimer : I'm not a network engineer] Hi, In a setup where OpenVSwitch is used with GRE tunels on top of an interface 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

...2.LLL.IP.151 Mask:255.255.255.248 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1182092 errors:0 dropped:0 overruns:0 frame:2 TX packets:984484 errors:0 dropped:0 overruns:0 carrier:1106 collisions:10090 txqueuelen:100 Interrupt:12 Base address:0x2000 gre0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 UP RUNNING NOARP MTU:1476 Metric:1 RX packets:15 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 gre1 Link encap:UNSPEC HWaddr...

Hi List, I read this list for nearly two years and learnt a lot, but now i have a very strange problem I can''t solve.. I have a firewall machine running Debian, which connects a small office to the internet via a DSL-line (with pppoe) and which is running Shorewall. It allows all outbound traffic and accepts pptp, openvpn and ssh-connections (on a non-standard port) from the internet.

...e netdev=eth0'') After that i start xen, everything works fine. I have a questions here: shouldn''t i have a peth0 interface when i use de ifconfig command? It only shows eth0 and the loopback interface. If i add -a option it shows several vif, veth and ifb interfaces plus a tunl0, gre0, eql, dummy and bond0 interface. Maybe that''s part of the problem i have. Moving on, here is my .cfg file that i''m using for the virtual machine: kernel = "/data/kernel-debian" memory = ''512'' root = ''/dev/sda6 ro console=/dev/xvc0''...

...Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:161 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:14593 (14.2 Kb) TX bytes:0 (0.0 b) gre0 Link encap:UNSPEC HWaddr 00-00-00-00-FF-00-00-00-00-00-00-00-00-00-00-00 NOARP MTU:1476 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0....

Hi, With kernel 2.4 I was able to use equalize to send our outgoing packets to two different routers (our isp supports this setup), like this: ip route add default src ip.a.dd.rr equalize nexthop via <router1> weight 1 nexthop via <router2> weight 1 The two routes were used equally on a per packet basis, not per flow or per cached route, but per packet, each line has 800k upload

...t 192.168.1.1/24 brd 192.168.1.255 scope global eth1 inet6 fe80::250:fcff:fe4d:68ad/64 scope link valid_lft forever preferred_lft forever 5: teql0: <NOARP> mtu 1500 qdisc noop qlen 100 link/void 6: tunl0: <NOARP> mtu 1480 qdisc noop link/ipip 0.0.0.0 brd 0.0.0.0 7: gre0: <NOARP> mtu 1476 qdisc noop link/gre 0.0.0.0 brd 0.0.0.0 8: sit0: <NOARP> mtu 1480 qdisc noop link/sit 0.0.0.0 brd 0.0.0.0 9: ip6tnl0: <NOARP> mtu 1460 qdisc noop link/tunnel6 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00 brd 00:00:00:00:00:00:00:00:00:00:00:00:0...

I am puzzled. I started setting up a new box last week with Linux 2.6.10. Everything was working fine until I went to start shorewall, when all network traffic stopped. I have little doubt that it is because I missed something in configuring the machine. I''m running shorewall 2.2 and the zone, policy, and rules files are cut and paste from a machine that has been running for over a

...th1: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000 link/ether 00:40:05:a4:27:f1 brd ff:ff:ff:ff:ff:ff inet 196.25.62.97/30 brd 196.25.62.99 scope global eth1 4: dummy0: <BROADCAST,NOARP> mtu 1500 qdisc noop link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff 5: gre0@NONE: <NOARP> mtu 1476 qdisc noop link/gre 0.0.0.0 brd 0.0.0.0 ip route show [root@squid3 root]# ip route show 196.25.62.96/30 dev eth1 scope link 172.20.4.0/24 via 172.20.1.3 dev eth0 192.168.2.0/24 via 172.20.1.3 dev eth0 172.20.1.0/24 dev eth0 scope link 172.19.9.0/24 via 172.20.1.2...