search for: tunl0

Hello Gurus, I am a small problem with routing and here are the details. Interfaces on my server: * ipsec0 - 172.19.58.94 * tunl0 - 172.19.58.94 * eth0 - 172.19.58.94 Now, the problem is that there is another host 172.19.58.200. All communication to 172.19.58.200 should be through tunl0, and all the data should be secured using IPSec (tunnel mode - because there are more machines on my network and 172.19.58.94 is the gate...

I''ve tried with iproute and it works now ! commands for A: ip tunnel add mode ipip tunl1 local IP_A remote IP_B ip addr add dev net1 local virtual-IP_A remote virtual-IP_B ip link set net1 up Same on B. And then from A i''m able to ping virtual-IP_B. It seems one can not use tunl0 as a tunnel name, is it true ? I think it will be a good thing to add to the section 5.2 of the LARTC HowTo the way to do a tunnel with the ''ip'' commands and to specify that new_tunnel.o is only in old kernel. But that''s perhaps already in a TODO list... Francois >...

...Yay, there is a solution, but we cannot use it: The IP of gw A is 10.157.108.4 The IP of gw B is 10.29.212.6 The IP of C is 10.157.108.213 They are in an ad-hoc network, A can see C but not B, and B can see C. The steps are: - the node C creates for each gw an IPIP tunnel to A and a second to B tunl0: ip/ip remote any local any ttl inherit nopmtudisc tunl1: ip/ip remote any local 10.157.108.214 ttl inherit - the node C assigna a different IP to each tunnel ifconfig tunl0 10.157.108.213 ifconfig tunl1 10.157.108.214 At this point we have two different interfaces and we can use the...

Hi there, I''m trying to achieve the classic load balancing using the multipath. The gateways are: A (tunl0) and B (tunl1) This is the classical situation covered by the HOWTO: one computer with two Internet connections. The problems come when I try to use the same IPs for both A and B. So A is 10.229.25.8 and B 10.229.25.8. I cannot do otherwise, I''m forced to use the same IPs. For the ru...

...''new'' new_tunnel.o ? I tried anyway to set the tunnel. ipip and tun modules are loaded on A and B. here is the config: (i cut the 192.168. part of IP addr) -----------------A-----------------B-----------------C 3.3 5.3 5.4 4.4 4.1 on A: ifconfig tunl0 192.168.3.3 pointopoint 192.168.5.4 route add -net 192.168.4.0 netmask 255.255.255.0 dev tunl0 on B: ifconfig tunl0 192.168.4.4 pointopoint 192.168.5.3 route add -net 192.168.3.0 netmask 255.255.255.0 dev tunl0 From A i can''t ping C. Traceroute shows that packets doesn''t even rea...

Hello All, The following is what I was trying to do: A packet [Dest: 10.10.10.2, Src: 10.10.10.30] has a route through "tunl0". The bigger problem is that "tunl0" is a tunnel between 10.10.10.2 and 10.10.10.20... Which means that after encapsulation takes place, the packet would look like [Dest: 10.10.10.2, Src: 10.10.10.20 [Dest: 10.10.10.2, Src: 10.10.10.30]]. Thing to be noted is that the destinati...

...hain due to which i am not able to control the traffic. Do i requie enable anything 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: <...

Hello I have /25 addressed on a box (virtual devices on eth0) and I want to tunnel some of these addresses to my home network. One address to my gateway (a.b.c.d, external IP) and one address to my internal network (192.168.0.0/24-style). I will use the tunnels for irc, smtp and surfing. What protocol and which technique is easiest and best to use? One more thing. I don''t want to set up

...2.168.2.1 (eth1) router is connected to Internet over eth0 - 145.35.160.94 netmask is /21 I wrote this two scripts (I use RedHat 6.1 on both routers with kernel 2.2.12) file rc.ipip on router A #!/bin/sh PATH=/sbin:/usr/sbin echo installing modul... modprobe ip_gre echo setting tunl0... ip tunnel add neta mode gre remote 145.35.160.94 local 145.35.162.44 ttl 255 echo adding network ariel2... ip addr add 192.168.1.1 dev neta ip route add 192.168.2.0/24 dev neta in file rc.local . . . /etc/rc.d/rc.ipip file rc.ipip on router B #!/bin/sh PATH=/sbin:/usr/sbin echo installing mod...

...ADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000 link/ether 00:0b:db: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.19...

...er 00:50:da:92:bb:20 brd ff:ff:ff:ff:ff:ff inet 24.224.173.220/24 brd 24.224.173.255 scope global eth0 3: eth1: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100 link/ether 00:50:ba:d0:f2:16 brd ff:ff:ff:ff:ff:ff inet 192.168.0.1/24 brd 192.168.0.255 scope global eth1 4: tunl0@NONE: <NOARP,UP> mtu 256 qdisc noqueue link/ipip 0.0.0.0 brd 0.0.0.0 inet 44.135.34.201/32 scope global tunl0 5: nr0: <UP> mtu 216 qdisc noqueue link/generic ac:8a:62:88:a4:8e:0e brd 00:00:00:00:00:00:00 inet 44.135.34.201/24 brd 44.135.34.255 scope global nr0 6: nr1:...

...t=87 dport=1559 use=1 tcp 6 3 TIME_WAIT src=44.135.34.201 dst=44.135.85.30 sport=1557 dport=23 src=44.135.85.30 dst=44.135.34.201 sport=23 dport=1557 [ASSURED] use=1 --- Ted Gervais Coldbrook Nova Scotia Canada B4R1A7 -------------- next part -------------- 44.137.28.48 via 62.238.66.67 dev tunl0 proto static onlink 24.224.173.0/24 dev eth0 proto kernel scope link src 24.224.173.220 192.168.0.0/24 dev eth1 proto kernel scope link src 192.168.0.1 127.0.0.0/8 dev lo scope link 44.0.0.0/8 via 24.138.74.225 dev tunl0 proto static onlink default via 24.224.173.1 dev eth0 ---------...

...pe global eth0 > > 3: dummy0: <BROADCAST,NOARP> mtu 1500 qdisc noop > > link/ether 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. > > -A...

...link/ether 00:01:02:f5:8a:61 brd ff:ff:ff:ff:ff:ff inet 155.253.4.254/24 brd 155.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...

...k-bridge 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'...

...dr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:16 errors:0 dropped:0 overruns:0 frame:0 TX packets:16 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1672 (1.6 Kb) TX bytes:1672 (1.6 Kb) tunl0 Link encap:IPIP Tunnel HWaddr NOARP MTU:1480 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.0 b) TX bytes:0 (0.0 b) eth0 is connected...

...o_fast qlen 1000 link/ether 00:50:fc:4d:68:ad brd ff:ff:ff:ff:ff:ff inet 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...

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

...PAT_IPFWADM is not set And for completeness: [root@fw linux-2.4.28]# shorewall version 2.0.10 [root@fw linux-2.4.28]# ip addr show 1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 brd 127.255.255.255 scope host lo 2: tunl0@NONE: <NOARP> mtu 1480 qdisc noop link/ipip 0.0.0.0 brd 0.0.0.0 3: gre0@NONE: <NOARP> mtu 1476 qdisc noop link/gre 0.0.0.0 brd 0.0.0.0 4: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000 link/ether 00:80:c8:64:a2:61 brd ff:ff:ff:ff:ff:ff inet 139...

I *think* we are finally making some progress in tracking our elusive performance problems. After employing a second 10Mb link from our ISP, along with another firewall box and proxy, we were able to determine the problem *is* our firewall. We don''t know exactly why yet, but our sporadic slow web access seems to have gone away since swapping a new firewall in this morning. The