IPv6 Route: FAQ IPv6 Route - Revision history

Onnowpurbo at 01:40, 23 May 2013

2013-05-23T01:40:01Z

← Older revision		Revision as of 01:40, 23 May 2013
Line 7:		Line 7:
	===Client (tidak merouting paket)===		===Client (tidak merouting paket)===

	Client ~~can setup a~~ default route ~~like~~ prefix “::/0”~~, they also learn such~~ route on autoconfiguration ~~e.g. using~~ radvd ~~on the~~ link ~~like following example shows:~~		Client dapat mensetup default route menggunakan prefix seperti “::/0”. Client juga dapat belajar route tersebut menggunakan autoconfiguration seperti menggunakan radvd di link seperti contoh berikut

	# ip -6 route show \| grep ^default		# ip -6 route show \| grep ^default
	default via fe80::212:34ff:fe12:3450 dev eth0 proto kernel metric 1024 expires 29sec mtu 1500 advmss 1440		default via fe80::212:34ff:fe12:3450 dev eth0 proto kernel metric 1024 expires 29sec mtu 1500 advmss 1440

	~~7.6.1.2. Routers in case of~~ packet forwarding		===Router dalam packet forwarding===

	~~Older~~ Linux ~~kernel~~ (~~at least~~ <= 2.4.17) ~~don't support~~ default ~~routes~~. ~~You can set them up~~, ~~but the~~ route ~~lookup fails when a packet should be forwarded (normal intention of a router)~~. ~~If you're still using such older~~ kernel, ~~“default routing” can be setup using the currently used~~ global address prefix “2000::/3”.		Di kernel Linux yang lama (<=2.4.17) tidak mendukung default route. Kita dapay menset default route, tapi pencarian route juga gagal saat paket harus di forward ke default. Untuk kernel lama, "routing default" dapat di set menggunakan global address prefix seperti “2000::/3”.

	~~Note~~: ~~take care about~~ default routing ~~without~~ address filtering on edge ~~routers~~. ~~Otherwise unwanted~~ multicast ~~or site-~~local ~~traffic can leave the~~ edge.		Catatan: berhati-hari dengan default routing tanpa address filtering di edge router. Karena mungkin multicast atau traffic local dapat saja meninggalkan edge router.

Onnowpurbo at 01:32, 23 May 2013

2013-05-23T01:32:49Z

← Older revision		Revision as of 01:32, 23 May 2013
Line 1:		Line 1:
	~~7.6. FAQ for IPv6 routes~~

	==Dukungan untuk route default IPv6==		==Dukungan untuk route default IPv6==

	~~One~~ idea of IPv6 ~~was a hierachical~~ routing, ~~therefore only less~~ routing ~~entries are needed in routers~~.		Salah satu idea dari IPv6 adalah routing hierarkis, oleh karenanya akan lebih sedikit routing entri di butuhkan di router.
			Ada beberapa isu di kernel linux saat ini

	~~There are some issues in current Linux kernels:~~

	~~7.6.1.1. Clients~~ (~~not routing any packet!~~)		===Client (tidak merouting paket)===

	Client can setup a default route like prefix “::/0”, they also learn such route on autoconfiguration e.g. using radvd on the link like following example shows:		Client can setup a default route like prefix “::/0”, they also learn such route on autoconfiguration e.g. using radvd on the link like following example shows:

Onnowpurbo at 01:13, 23 May 2013

2013-05-23T01:13:13Z

← Older revision		Revision as of 01:13, 23 May 2013
Line 1:		Line 1:
	7.6. FAQ for IPv6 routes		7.6. FAQ for IPv6 routes
	~~7.6.1. Support of an~~ IPv6 ~~default route~~
			==Dukungan untuk route default IPv6==

	One idea of IPv6 was a hierachical routing, therefore only less routing entries are needed in routers.		One idea of IPv6 was a hierachical routing, therefore only less routing entries are needed in routers.

	There are some issues in current Linux kernels:		There are some issues in current Linux kernels:

	7.6.1.1. Clients (not routing any packet!)		7.6.1.1. Clients (not routing any packet!)

	Client can setup a default route like prefix “::/0”, they also learn such route on autoconfiguration e.g. using radvd on the link like following example shows:		Client can setup a default route like prefix “::/0”, they also learn such route on autoconfiguration e.g. using radvd on the link like following example shows:

	# ip -6 route show \| grep ^default		# ip -6 route show \| grep ^default
	default via fe80::212:34ff:fe12:3450 dev eth0 proto kernel metric 1024 expires		default via fe80::212:34ff:fe12:3450 dev eth0 proto kernel metric 1024 expires 29sec mtu 1500 advmss 1440
	¬ 29sec mtu 1500 advmss 1440

	7.6.1.2. Routers in case of packet forwarding		7.6.1.2. Routers in case of packet forwarding

Onnowpurbo: New page: 7.6. FAQ for IPv6 routes 7.6.1. Support of an IPv6 default route One idea of IPv6 was a hierachical routing, therefore only less routing entries are needed in routers. There are some iss...

2013-05-22T04:11:27Z

New page: 7.6. FAQ for IPv6 routes 7.6.1. Support of an IPv6 default route One idea of IPv6 was a hierachical routing, therefore only less routing entries are needed in routers. There are some iss...

New page

7.6. FAQ for IPv6 routes
7.6.1. Support of an IPv6 default route

One idea of IPv6 was a hierachical routing, therefore only less routing entries are needed in routers.

There are some issues in current Linux kernels:
7.6.1.1. Clients (not routing any packet!)

Client can setup a default route like prefix “::/0”, they also learn such route on autoconfiguration e.g. using radvd on the link like following example shows:

# ip -6 route show | grep ^default
default via fe80::212:34ff:fe12:3450 dev eth0 proto kernel metric 1024 expires
¬ 29sec mtu 1500 advmss 1440

7.6.1.2. Routers in case of packet forwarding

Older Linux kernel (at least <= 2.4.17) don't support default routes. You can set them up, but the route lookup fails when a packet should be forwarded (normal intention of a router). If you're still using such older kernel, “default routing” can be setup using the currently used global address prefix “2000::/3”.

Note: take care about default routing without address filtering on edge routers. Otherwise unwanted multicast or site-local traffic can leave the edge.