search for: iprule

...SOURCE -O2 -Wstrict-prototypes -Wall -I../include -DRESOLVE_HOSTNAMES -c -o ipaddress.o ipaddress.c gcc -D_GNU_SOURCE -O2 -Wstrict-prototypes -Wall -I../include -DRESOLVE_HOSTNAMES -c -o iproute.o iproute.c gcc -D_GNU_SOURCE -O2 -Wstrict-prototypes -Wall -I../include -DRESOLVE_HOSTNAMES -c -o iprule.o iprule.c gcc -D_GNU_SOURCE -O2 -Wstrict-prototypes -Wall -I../include -DRESOLVE_HOSTNAMES -c -o rtm_map.o rtm_map.c gcc -D_GNU_SOURCE -O2 -Wstrict-prototypes -Wall -I../include -DRESOLVE_HOSTNAMES -c -o iptunnel.o iptunnel.c gcc -D_GNU_SOURCE -O2 -Wstrict-prototypes -Wall -I../include -DRESOL...

...st:/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 `/home/oluap/iproute2/ip'' gcc ip.o ipaddress.o iproute.o iprule.o rtm_map.o iptunnel.o ipneigh.o iplink.o ipmaddr.o ipmonitor.o ipmroute.o ../lib/libnetlink.a ../lib/libutil.a -lresolv -L../lib -lnetlink -lutil -o ip iptunnel.o(.text+0x65a): In function `parse_args'': : undefined reference to `__constant_htons'' iptunnel.o(.text+0x678): In func...

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

...ibc/glibc-bugs.h -I/usr/src/linux/include -I../include -DRESOLV E_HOSTNAMES -c -o iproute.o iproute.c gcc -D_GNU_SOURCE -O2 -Wstrict-prototypes -Wall -g -I../include-glibc -I/usr /include/db3 -include ../include-glibc/glibc-bugs.h -I/usr/src/linux/include -I../include -DRESOLV E_HOSTNAMES -c -o iprule.o iprule.c gcc -D_GNU_SOURCE -O2 -Wstrict-prototypes -Wall -g -I../include-glibc -I/usr /include/db3 -include ../include-glibc/glibc-bugs.h -I/usr/src/linux/include -I../include -DRESOLV E_HOSTNAMES -c -o rtm_map.o rtm_map.c gcc -D_GNU_SOURCE -O2 -Wstrict-prototypes -Wall -g -I../include-glibc -I...

...- All incoming request on device eth1 of Router 1 are redirected on 10.2.3.10 On router 1 * ftp 10.2.3.10 is OK On firewall 1 * ftp 10.2.2.10 is OK * ftp 10.2.6.11 is wrong: When I sniff eth0 on Firewall2, I see the response of ftp server with 10.2.3.10 source ip whereas my iprules and iproute are [root@firewall2 root]# ip rule list 0: from all lookup local 32764: from 10.2.2.10 lookup T2 32765: from 10.2.3.10 lookup T1 32766: from all lookup main 32767: from all lookup 253 [root@firewall2 root]# ip route list table T1 10.2.4.0/24 dev eth2 scope l...

Hello, I tried to find the answer to my problem already but it is a specialised one I think because nothing was found. I previously have a ISP who was very fast ("extreme speed" service from Cable Modem) but that blocked SMTP port and some other for poor non-commercial users... And it gives dynamic addresses so no DNS at home without tricks... So I went to another

Hello Shorewall list, I''m a happy Shorewall user since a few years now and everything works fine for me except one thing that I try to implement since a week, the multi-isp. I''ve downloaded the 2.4.0 Stable release yesterday and tried the RC2 since a week. My config is a Debian running a kernel 2.4.27 home made with the CONNMARK.diff patch applied I''m using 2 ISP,

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