ip route
A ------ hub ------- B ---------- D
2 | 1 3 4
|
C -------|5
1: 192.168.15.1
2: 192.168.15.2
5: 192.168.15.3
3: 192.168.20.1
4: 192.168.20.2
At D
route add 192.168.15.1 netmask 255.255.255.0 gw 192.168.20.1
Is the static route at D is correct?
If it is, is 192.168.15.1 at respond to boardcast to the 192.168.15.2 & 192.168.15.3?
Patrick
_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
Hi folks,
How with ip route permanently delete default route and add a new one? I use RedHat 7.3.
Thank you in advance
Rimas
[LARTC] IP ROUTE
In reply to King Yung TongHello, my linux show me that:
server2 root # ip route add default scope global nexthop via 192.168.5.1 dev eth2 weight 1 nexthop via 192.168.160.1 dev eth0 weight 1 RTNETLINK answers: Invalid argument
What can I do????
Thanks
Matias
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.726 / Virus Database: 481 - Release Date: 22/07/2004
Re: [LARTC] IP ROUTE
In reply to King Yung TongQuoted 13 lines · Matias Namiot
Hello, my linux show me that:
/server2 root # ip route add default scope global nexthop via 192.168.5.1 dev eth2 weight 1 nexthop via 192.168.160.1 dev eth0 weight 1 RTNETLINK answers: Invalid argument
/
//
What can I do????
Thanks
Matias
Quoted 4 lines
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.726 / Virus Database: 481 - Release Date: 22/07/2004
Hi,
you need to recompile your kernel with the following enabled :
CONFIG_IP_ADVANCED_ROUTERCONFIG_IP_MULTIPLE_TABLESCONFIG_IP_ROUTE_FWMARK (not sure it's needed here but let's enable it)
Julien
_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
Re: [LARTC] IP ROUTE
In reply to King Yung TongThanks
----- Original Message -----
From: Julien
To: [email protected]
Sent: Monday, July 26, 2004 5:07 PM
Subject: Re: [LARTC] IP ROUTE
Quoted 13 lines · Matias Namiot
Hello, my linux show me that:
/server2 root # ip route add default scope global nexthop via 192.168.5.1 dev eth2 weight 1 nexthop via 192.168.160.1 dev eth0 weight 1 RTNETLINK answers: Invalid argument
/
//
What can I do????
Thanks
Matias
Quoted 4 lines
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.726 / Virus Database: 481 - Release Date: 22/07/2004
Hi,
you need to recompile your kernel with the following enabled :
CONFIG_IP_ADVANCED_ROUTER
CONFIG_IP_MULTIPLE_TABLES
CONFIG_IP_ROUTE_FWMARK (not sure it's needed here but let's enable it)
Julien
_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.726 / Virus Database: 481 - Release Date: 22/07/2004
Re: [LARTC] IP ROUTE
In reply to King Yung TongThe problem was the module CONFIG_IP_ROUTE_MULTIPATH of the kernel
Thanks for all, now I fight with what is de module of tc filter because I can't do that:
server2 linux # tc filter add dev eth0 parent 1:0 protocol ip prio 2 handle 2 fw classid 1:11 RTNETLINK answers: Invalid argument
server2 linux #
----- Original Message -----
From: Matias Namiot
To: [email protected]
Sent: Monday, July 26, 2004 3:47 PM
Subject: [LARTC] IP ROUTE
Hello, my linux show me that:
server2 root # ip route add default scope global nexthop via 192.168.5.1 dev eth2 weight 1 nexthop via 192.168.160.1 dev eth0 weight 1 RTNETLINK answers: Invalid argument
What can I do????
Thanks
Matias
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.726 / Virus Database: 481 - Release Date: 22/07/2004
Re: [LARTC] IP ROUTE
In reply to King Yung TongI need resolv this problem now, because I haven't any time, and my problem is:
server2 root # ip route add default scope global nexthop via 192.168.5.1 dev eth2 weight 1 nexthop via 192.168.160.1 dev eth0 weight 1 RTNETLINK answers: Invalid argument
I want make this is my configuration:
# Configuración TC para Bariloche Wireless
# Salida a internet eth1
# Subida 128k y bajada 128k
# Valores:
# mbps = 1024 kbps = 1024 * 1024 bps => byte/s # mbit = 1024 kbit => kilobit/s. # mb = 1024 kb = 1024 * 1024 b => byte # mbit = 1024 kbit => kilobit. # Internamente, los números se almacenan en bps, pero cuando tc imprime las tasas, usa lo siguiente: # 1Mbit = 1024 Kbit = 1024 * 1024 bps => byte/s
##### Limpiamos reglas anteriores
tc qdisc del dev eth1 root 2> /dev/null > /dev/null
tc qdisc del dev eth1 ingress 2> /dev/null > /dev/null
##### Definimos las qdisc
# Definimos tasa superior y dispositivo de internet CEIL=128
DEV_INT=eth1
# Esta línea se encargará de enviar por defecto a la clase 1:15 tc qdisc add dev eth1 root handle 1: htb default 15
# Qdisc padre
tc class add dev eth1 parent 1: classid 1:1 htb rate ${CEIL}kbit ceil ${CEIL}kbit
# Esta línea se encargará de enviar paquetes de baja latencia (telnet, ssh, SYN, etc) como interactivas tc class add dev eth1 parent 1:1 classid 1:10 htb rate 80kbit ceil 80kbit prio 0
# Esta línea se encargará de tráfico masivo WEB
tc class add dev eth1 parent 1:1 classid 1:11 htb rate 80kbit ceil ${CEIL}kbit prio 1
# Esta línea se encargará de tráfico TOS de maximizar transferencia y el tráfico local #tc class add dev eth1 parent 1:1 classid 1:12 htb rate 20kbit ceil ${CEIL}kbit prio 2
# Esta línea se encargará de las máquinas con NAT
tc class add dev eth1 parent 1:1 classid 1:13 htb rate 80kbit ceil ${CEIL}kbit prio 2
# Esta línea se encargará del correo SMTP y POP3 con un TOS de minimizar costo. tc class add dev eth1 parent 1:1 classid 1:14 htb rate 20kbit ceil ${CEIL}kbit prio 3
# Esta línea se encargará de tráfico masivo de las máquinas con NAT con Kazaa, e-Donkey, etc tc class add dev eth1 parent 1:1 classid 1:15 htb rate 10kbit ceil ${CEIL}kbit prio 3
# Aplicamos SFQ para el tráfico pesado con hash cada 10 segundos #tc qdisc add dev eth1 parent 1:12 handle 120: sfq perturb 10 tc qdisc add dev eth1 parent 1:13 handle 130: sfq perturb 10 tc qdisc add dev eth1 parent 1:14 handle 140: sfq perturb 10 tc qdisc add dev eth1 parent 1:15 handle 150: sfq perturb 10
##### Clasificación de paquetes con iptables
# Se prefiere por los paquetes porque son muy flexibles y puedes hacer conteo de paquetes por cada regla, y con el objetivo # RETURN los paquetes no necesitan pasar por todas las reglas. Los paquetes con FWMARK (handle x fw) van en la clase indicada
tc filter add dev eth0 parent 1:0 protocol ip prio 1 handle 1 fw classid 1:10 tc filter add dev eth0 parent 1:0 protocol ip prio 2 handle 2 fw classid 1:11 #tc filter add dev eth0 parent 1:0 protocol ip prio 3 handle 3 fw classid 1:12 tc filter add dev eth0 parent 1:0 protocol ip prio 4 handle 4 fw classid 1:13 tc filter add dev eth0 parent 1:0 protocol ip prio 5 handle 5 fw classid 1:14 tc filter add dev eth0 parent 1:0 protocol ip prio 6 handle 6 fw classid 1:15
##### Acá hay que hacer NAT con iptables.
##### Marcando paquetes
# No olvidarse el -j RETURN de manera que los paquetes no atraviesen todas las reglas
##### Para clase 10
# Marcando iptables para paquetes ICMP
iptables -t mangle -A PREROUTING -p icmp -j MARK --set-mark 0x1 iptables -t mangle -A PREROUTING -p icmp -j RETURN iptables -t mangle -A OUTPUT -p icmp -j MARK --set-mark 0x1 iptables -t mangle -A OUTPUT -p icmp -j RETURN
# Marcando iptables para paquetes con TOS para Minimizar el tiempo iptables -t mangle -A PREROUTING -m tos --tos Minimize-Delay -j MARK --set-mark 0x1 iptables -t mangle -A PREROUTING -m tos --tos Minimize-Delay -j RETURN iptables -t mangle -A OUTPUT -m tos --tos Minimize-Delay -j MARK --set-mark 0x1 iptables -t mangle -A OUTPUT -m tos --tos Minimize-Delay -j RETURN
# Marcando iptables para paquetes SSH
iptables -t mangle -A PREROUTING -p tcp -m tcp --sport 22 -j MARK --set-mark 0x1 iptables -t mangle -A PREROUTING -p tcp -m tcp --sport 22 -j RETURN iptables -t mangle -A OUTPUT -p tcp -m tcp --sport 22 -j MARK --set-mark 0x1 iptables -t mangle -A OUTPUT -p tcp -m tcp --sport 22 -j RETURN
# Marcando iptables para paquetes de sincronismo
iptables -t mangle -I PREROUTING -p tcp -m tcp --tcp-flags SYN,RST,ACK SYN -j MARK --set-mark 0x1 iptables -t mangle -I PREROUTING -p tcp -m tcp --tcp-flags SYN,RST,ACK SYN -j RETURN iptables -t mangle -I OUTPUT -p tcp -m tcp --tcp-flags SYN,RST,ACK SYN -j MARK --set-mark 0x1 iptables -t mangle -I OUTPUT -p tcp -m tcp --tcp-flags SYN,RST,ACK SYN -j RETURN
##### Para clase 11
iptables -t mangle -A PREROUTING -p tcp -m tcp --sport 80 -j MARK --set-mark 0x2 iptables -t mangle -A PREROUTING -p tcp -m tcp --sport 80 -j RETURN iptables -t mangle -A OUTPUT -p tcp -m tcp --sport 80 -j MARK --set-mark 0x2 iptables -t mangle -A OUTPUT -p tcp -m tcp --sport 80 -j RETURN
##### Para clase 13
# Marcando iptables para paquetes FTP y FTP-DATA
iptables -t mangle -A PREROUTING -p tcp -m tcp --sport 21 -j MARK --set-mark 0x4 iptables -t mangle -A PREROUTING -p tcp -m tcp --sport 21 -j RETURN iptables -t mangle -A OUTPUT -p tcp -m tcp --sport 21 -j MARK --set-mark 0x4 iptables -t mangle -A OUTPUT -p tcp -m tcp --sport 21 -j RETURN iptables -t mangle -A PREROUTING -p tcp -m tcp --sport 20 -j MARK --set-mark 0x4 iptables -t mangle -A PREROUTING -p tcp -m tcp --sport 20 -j RETURN iptables -t mangle -A OUTPUT -p tcp -m tcp --sport 20 -j MARK --set-mark 0x4 iptables -t mangle -A OUTPUT -p tcp -m tcp --sport 20 -j RETURN
##### Para clase 14
# Marcando iptables para paquetes con TOS para Minimizar el costo iptables -t mangle -A PREROUTING -m tos --tos Minimize-Cost -j MARK --set-mark 0x5 iptables -t mangle -A PREROUTING -m tos --tos Minimize-Cost -j RETURN iptables -t mangle -A OUTPUT -m tos --tos Minimize-Cost -j MARK --set-mark 0x5 iptables -t mangle -A OUTPUT -m tos --tos Minimize-Cost -j RETURN
# Marcando iptables para paquetes SMTP
iptables -t mangle -A PREROUTING -p tcp -m tcp --sport 25 -j MARK --set-mark 0x5 iptables -t mangle -A PREROUTING -p tcp -m tcp --sport 25 -j RETURN iptables -t mangle -A OUTPUT -p tcp -m tcp --sport 25 -j MARK --set-mark 0x5 iptables -t mangle -A OUTPUT -p tcp -m tcp --sport 25 -j RETURN
# Marcando iptables para paquetes POP3
iptables -t mangle -A PREROUTING -p tcp -m tcp --sport 110 -j MARK --set-mark 0x5 iptables -t mangle -A PREROUTING -p tcp -m tcp --sport 110 -j RETURN iptables -t mangle -A OUTPUT -p tcp -m tcp --sport 110 -j MARK --set-mark 0x5 iptables -t mangle -A OUTPUT -p tcp -m tcp --sport 110 -j RETURN
##### Para clase 15
# Marcando iptables para paquetes con TOS para Maximizar transferencias iptables -t mangle -A PREROUTING -m tos --tos Maximize-Throughput -j MARK --set-mark 0x6 iptables -t mangle -A PREROUTING -m tos --tos Maximize-Throughput -j RETURN iptables -t mangle -A OUTPUT -m tos --tos Maximize-Throughput -j MARK --set-mark 0x6 iptables -t mangle -A OUTPUT -m tos --tos Maximize-Throughput -j RETURN
# Marcando iptables para paquetes por defecto (es redundante) iptables -t mangle -A PREROUTING -j MARK --set-mark 0x6 iptables -t mangle -A OUTPUT -j MARK --set-mark 0x6
My kernel config is:
CONFIG_X86=yCONFIG_UID16=yCONFIG_EXPERIMENTAL=yCONFIG_MODULES=yCONFIG_MODVERSIONS=yCONFIG_KMOD=yCONFIG_MXP31=yCONFIG_X86_WP_WORKS_OK=yCONFIG_X86_INVLPG=yCONFIG_X86_CMPXCHG=yCONFIG_X86_XADD=yCONFIG_X86_BSWAP=yCONFIG_X86_POPAD_OK=yCONFIG_RWSEM_XCHGADD_ALGORITHM=yCONFIG_X86_L1_CACHE_SHIFT=6CONFIG_X86_HAS_TSC=yCONFIG_X86_GOOD_APIC=yCONFIG_X86_USE_3DNOW=yCONFIG_X86_PGE=yCONFIG_X86_USE_PPRO_CHECKSUM=yCONFIG_X86_MCE=yCONFIG_NOHIGHMEM=yCONFIG_1GB=yCONFIG_PREEMPT=yCONFIG_X86_TSC=yCONFIG_HAVE_DEC_LOCK=yCONFIG_NET=yCONFIG_PCI=yCONFIG_PCI_GOANY=yCONFIG_PCI_BIOS=yCONFIG_PCI_DIRECT=yCONFIG_PCI_NAMES=yCONFIG_HOTPLUG=yCONFIG_SYSVIPC=yCONFIG_SYSCTL=yCONFIG_KCORE_ELF=yCONFIG_BINFMT_AOUT=yCONFIG_BINFMT_ELF=yCONFIG_BINFMT_MISC=yCONFIG_PACKET=yCONFIG_PACKET_MMAP=yCONFIG_NETLINK_DEV=yCONFIG_NETFILTER=yCONFIG_NETFILTER_DEBUG=yCONFIG_FILTER=yCONFIG_UNIX=yCONFIG_INET=yCONFIG_IP_MULTICAST=yCONFIG_IP_ADVANCED_ROUTER=yCONFIG_IP_MULTIPLE_TABLES=yCONFIG_IP_ROUTE_FWMARK=yCONFIG_IP_ROUTE_NAT=yCONFIG_IP_ROUTE_MULTIPATH=yCONFIG_IP_ROUTE_TOS=yCONFIG_IP_ROUTE_VERBOSE=yCONFIG_NET_IPIP=yCONFIG_IP_MROUTE=yCONFIG_IP_PIMSM_V1=yCONFIG_IP_PIMSM_V2=yCONFIG_INET_ECN=yCONFIG_IP_NF_CONNTRACK=yCONFIG_IP_NF_FTP=yCONFIG_IP_NF_QUEUE=yCONFIG_IP_NF_IPTABLES=yCONFIG_IP_NF_MATCH_LIMIT=yCONFIG_IP_NF_MATCH_MAC=yCONFIG_IP_NF_MATCH_PKTTYPE=yCONFIG_IP_NF_MATCH_MARK=yCONFIG_IP_NF_MATCH_MULTIPORT=yCONFIG_IP_NF_MATCH_TOS=yCONFIG_IP_NF_MATCH_RECENT=yCONFIG_IP_NF_MATCH_LENGTH=yCONFIG_IP_NF_MATCH_TTL=yCONFIG_IP_NF_MATCH_TCPMSS=yCONFIG_IP_NF_MATCH_STEALTH=yCONFIG_IP_NF_MATCH_HELPER=yCONFIG_IP_NF_MATCH_STATE=yCONFIG_IP_NF_MATCH_CONNTRACK=yCONFIG_IP_NF_FILTER=yCONFIG_IP_NF_TARGET_REJECT=yCONFIG_IP_NF_TARGET_MIRROR=yCONFIG_IP_NF_NAT=yCONFIG_IP_NF_NAT_NEEDED=yCONFIG_IP_NF_TARGET_MASQUERADE=yCONFIG_IP_NF_TARGET_REDIRECT=yCONFIG_IP_NF_NAT_FTP=yCONFIG_IP_NF_MANGLE=yCONFIG_IP_NF_TARGET_TOS=yCONFIG_IP_NF_TARGET_MARK=yCONFIG_IP_NF_TARGET_LOG=yCONFIG_IP_NF_TARGET_TCPMSS=yCONFIG_IP_NF_ARPTABLES=yCONFIG_IP_NF_ARPFILTER=yCONFIG_NET_DIVERT=yCONFIG_NET_FASTROUTE=yCONFIG_NET_SCHED=yCONFIG_NET_SCH_CBQ=yCONFIG_NET_SCH_HTB=yCONFIG_NET_SCH_CSZ=yCONFIG_NET_SCH_HFSC=yCONFIG_NET_SCH_PRIO=yCONFIG_NET_SCH_RED=yCONFIG_NET_SCH_SFQ=yCONFIG_NET_SCH_TEQL=yCONFIG_NET_SCH_TBF=yCONFIG_NET_SCH_GRED=yCONFIG_NET_SCH_DELAY=yCONFIG_NET_SCH_DSMARK=yCONFIG_NET_SCH_INGRESS=yCONFIG_NET_QOS=yCONFIG_NET_ESTIMATOR=yCONFIG_NET_CLS=yCONFIG_NET_CLS_TCINDEX=yCONFIG_NET_CLS_ROUTE4=yCONFIG_NET_CLS_ROUTE=yCONFIG_NET_CLS_FW=yCONFIG_NET_CLS_U32=yCONFIG_NET_CLS_RSVP=yCONFIG_NET_CLS_POLICE=yCONFIG_IDE=yCONFIG_BLK_DEV_IDE=yCONFIG_BLK_DEV_IDEDISK=yCONFIG_IDEDISK_MULTI_MODE=yCONFIG_BLK_DEV_IDECD=yCONFIG_BLK_DEV_CMD640=yCONFIG_BLK_DEV_IDEPCI=yCONFIG_BLK_DEV_GENERIC=yCONFIG_IDEPCI_SHARE_IRQ=yCONFIG_BLK_DEV_IDEDMA_PCI=yCONFIG_IDEDMA_PCI_AUTO=yCONFIG_BLK_DEV_IDEDMA=yCONFIG_BLK_DEV_PIIX=yCONFIG_IDEDMA_AUTO=yCONFIG_NETDEVICES=yCONFIG_DUMMY=mCONFIG_NET_ETHERNET=yCONFIG_NET_VENDOR_3COM=yCONFIG_VORTEX=yCONFIG_R8169=yCONFIG_PPP=yCONFIG_PPP_MULTILINK=yCONFIG_PPP_ASYNC=yCONFIG_PPP_SYNC_TTY=yCONFIG_PPPOE=yCONFIG_NET_RADIO=yCONFIG_HERMES=yCONFIG_PLX_HERMES=yCONFIG_TMD_HERMES=yCONFIG_PCI_HERMES=yCONFIG_NET_WIRELESS=yCONFIG_VT=yCONFIG_VT_CONSOLE=yCONFIG_SERIAL=yCONFIG_UNIX98_PTYS=yCONFIG_UNIX98_PTY_COUNT=256CONFIG_AGP=yCONFIG_AGP_NVIDIA=yCONFIG_AUTOFS4_FS=yCONFIG_REISERFS_FS=yCONFIG_REISERFS_CHECK=yCONFIG_REISERFS_PROC_INFO=yCONFIG_EXT3_FS=yCONFIG_JBD=yCONFIG_JBD_DEBUG=yCONFIG_TMPFS=yCONFIG_RAMFS=yCONFIG_ISO9660_FS=yCONFIG_JOLIET=yCONFIG_PROC_FS=yCONFIG_DEVFS_FS=yCONFIG_DEVFS_MOUNT=yCONFIG_MSDOS_PARTITION=yCONFIG_NLS=yCONFIG_NLS_DEFAULT="iso8859-1"CONFIG_VGA_CONSOLE=yCONFIG_VIDEO_SELECT=yCONFIG_FB=yCONFIG_DUMMY_CONSOLE=yCONFIG_FB_LOGO_TUX=yCONFIG_FB_VESA=yCONFIG_VIDEO_SELECT=yCONFIG_FBCON_CFB8=yCONFIG_FBCON_CFB16=yCONFIG_FBCON_CFB24=yCONFIG_FBCON_CFB32=y
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=yCONFIG_LOG_BUF_SHIFT=0CONFIG_CRC32=y
----- Original Message -----
From: [email protected]
To: Matias Namiot
Sent: Wednesday, July 28, 2004 10:21 AM
Subject: Re: [LARTC] IP ROUTE
Please send earlier commands you are doing before that tc filter add....
--- Original Message -----
From: Matias Namiot
To: [email protected]
Sent: Tuesday, July 27, 2004 4:01 PM
Subject: Re: [LARTC] IP ROUTE
The problem was the module CONFIG_IP_ROUTE_MULTIPATH of the kernel
Thanks for all, now I fight with what is de module of tc filter because I can't do that:
server2 linux # tc filter add dev eth0 parent 1:0 protocol ip prio 2 handle 2 fw classid 1:11 RTNETLINK answers: Invalid argument
server2 linux #
----- Original Message -----
From: Matias Namiot
To: [email protected]
Sent: Monday, July 26, 2004 3:47 PM
Subject: [LARTC] IP ROUTE
Hello, my linux show me that:
server2 root # ip route add default scope global nexthop via 192.168.5.1 dev eth2 weight 1 nexthop via 192.168.160.1 dev eth0 weight 1 RTNETLINK answers: Invalid argument
What can I do????
Thanks
Matias
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.726 / Virus Database: 481 - Release Date: 22/07/2004
Re: [LARTC] IP ROUTE
In reply to King Yung TongThanks, the problem was the kernel with CONFIG_IP_ROUTE_MULTIPATH
----- Original Message -----
From: Matias Namiot
To: [email protected]
Sent: Monday, July 26, 2004 3:47 PM
Subject: [LARTC] IP ROUTE
Hello, my linux show me that:
server2 root # ip route add default scope global nexthop via 192.168.5.1 dev eth2 weight 1 nexthop via 192.168.160.1 dev eth0 weight 1 RTNETLINK answers: Invalid argument
What can I do????
Thanks
Matias
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.726 / Virus Database: 481 - Release Date: 22/07/2004