search for: iptunneling

Hi, I''m tring to compile iproute2-2.4.7-now-ss020116-try.tar.bz2 whith kernel 2.6.5 and I''m getting these error: root@localhost:/home/oluap/iproute2# make make[1]: Entering directory `/home/oluap/iproute2/lib'' make[1]: Nada a ser feito para `all''. make[1]: Leaving directory `/home/oluap/iproute2/lib'' make[1]: Entering directory

Now that 2.6.9 is final. Here is an update of the iproute2 utilities that contains all the patches in my queue. * lnstat to replace rtstat and ctstat (from Harald Welte) * latest xfrm related changes * several small typo''s and build fixes for older systems http://developer.osdl.org/dev/iproute2/download/iproute2-2.6.9-041019.tar.gz

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

Hi, i''m just new here, i''m searching for how to compile tc (if i''ve understood correctly, i must compile the whole iproute2 thing). So i did like the read me file said: ------ 1. Look at start of Makefile and set correct values for: KERNEL_INCLUDE ----- i did that, and then i doesn''t understand a damn thing about the reste of the the 1st step about ADDLIB

Hi, I'm trying to generate a multiple domain browselist but I don't get it to work. I've tried everyting by the book but the result is always the same: I can see the other workgroup(s) but they are empty. Currently I've added the following rules to the smb.conf remote browse sync = 192.168.2.2 192.168.2.4 remote announce = 192.168.2.2 192.168.2.4 As far as I understand

This is really strange behavior .. root@garfield ~# ip tunnel add testing123 mode ipip remote 192.168.1.1 local 192.168.1.12 root@garfield ~# ip tunnel show .. testing123: ip/ip remote 192.168.1.1 local 192.168.1.12 ttl inherit root@garfield ~# ip tunnel add testingabc mode ipip remote 192.168.1.1 local 192.168.1.12 root@garfield ~# echo $? 0 root@garfield ~# ip tunnel show .. testing123:

Hi, I have a box with RH 7,2 upgraded to Fedora Core 1. with: kernel 2.4.26 iptables 1.2.9 gcc 3.2.2 In this momment I''m using a binary TC version, but when I try to compile, get errors in Make process. Any hints ? Bests. Andres. ----> iproute2-2.4.7-now-ss010824.tar.gz make[1]: Cambiando a directorio `/usr/local/src/iproute2/lib'' gcc -D_GNU_SOURCE -O2

Hi! I'm trying to increase security on my FreeBSD 4.8 firewall/DSL router/VPN router. My problem is with firewalling the VPN part. I'm using a tunnel to a RedHat 7.1 box running FreeS/WAN. This tunnel allows traffic from my internal net (172.17.0.0/24) to that box only: spdadd 172.17.0.0/24 $REDHAT/32 any -P out ipsec esp/tunnel/$MYADDR-$REDHAT/unique; spdadd $REDHAT/32 172.17.0.0/24

On 10/10/2016 09:31 PM, John R Pierce wrote: > > oh. Yeah, the entire "net-tools" package is deprecated. I tend to forget which of the two (ethtool or mii-tool) is in that set. # Avoid using any of these: $ rpm -ql net-tools

Dzien Dobry Is there some error witch iproute2-050929.tar.gz becouse when i compile I don''t get tc I have kernel 2.6.12.3 this is my log with compile # make make[1]: Entering directory `/home/src/a/04102005/iproute2-050929/lib'' gcc -D_GNU_SOURCE -O2 -Wstrict-prototypes -Wall -I../include -DRESOLVE_HOSTNAMES -c -o ll_map.o ll_map.c gcc -D_GNU_SOURCE -O2 -Wstrict-prototypes

...the client standpoint, receive traffic for that given public IP network, deliver it accordingly to computers, and also, send out traffic from the computers on it''s network with the correct public IP source address. it''s actually a lot like the http://www.linuxvirtualserver.org/VS-IPTunneling.html diagram, but instead of the "server" sending / manipulating packets to go to three destinations, it''s taking a complete (sub)network of 16 or so IP''s and sending them directly to one computer. Any suggestions are greatly appreciated Thanks -Joe Comeaux ____________...

On 10/10/2016 11:21 PM, Gordon Messmer wrote: > On 10/10/2016 09:31 PM, John R Pierce wrote: >> >> oh. > > Yeah, the entire "net-tools" package is deprecated. I tend to forget > which of the two (ethtool or mii-tool) is in that set. > > # Avoid using any of these: > $ rpm -ql net-tools /bin/dnsdomainname /bin/domainname /bin/hostname /bin/netstat

Hi! Can I create the unnumbered GRE tunnel with iproute2 utility? Can someone provide me a link/howto/example_config how to do it? The topology is one tunnel between two linux boxes: -- eth1-|__|-eth0 <-------------> eth0-|__|-eth1 -- I''m trying now with: ip tu add tun1 mode gre local loc.IP remote rem.IP ttl 255 dev eth0 ip addr add tun1 0.0.0.0 ip link set tun1 up but it

Hi, I have a severe filesystem crash on a machine with a single ext3 filesystem. It is the second time that this happens to me (on two different machines that are identical in hardware setup and mostly in software - I cloned them when I started to work). It looks like the journal (or something else, i am not an expert here) has gone wild and overwritten loads of inodes. I have a single filesys

This is based on an earlier patch from Eric Biederman adding forwarding between macvlans. I extended his approach to allow the administrator to choose the mode for each macvlan, and to implement a functional VEPA between macvlan. Still missing from this is support for communication between the lower device that the macvlans are based on. This would be extremely useful but as others have found out

This is based on an earlier patch from Eric Biederman adding forwarding between macvlans. I extended his approach to allow the administrator to choose the mode for each macvlan, and to implement a functional VEPA between macvlan. Still missing from this is support for communication between the lower device that the macvlans are based on. This would be extremely useful but as others have found out

This is based on an earlier patch from Eric Biederman adding forwarding between macvlans. I extended his approach to allow the administrator to choose the mode for each macvlan, and to implement a functional VEPA between macvlan. Still missing from this is support for communication between the lower device that the macvlans are based on. This would be extremely useful but as others have found out