|
Route advertise
![[pl]](/s/countries/pl.gif) Shadow Hawkins on Saturday, 27 September 2003 19:11:49
Hello!
I have two tunnels
1. tunnel to psinet by sixxs
2. tunnel to freenet6
So I have two classes of /64
First: 2001:768:1941::/64
Second: 3ffe:b80:1c3d::/64
I have whole routing set to sixxs tunnel.
but there is much better connection to Viagene by my self tunnel to freenet6
than normal route by sixxs.
So I have setup a manual routing of 3ffe:b80::/32 and 3ffe:bc0::/32 to route via freenet6 tunnel.
All working fine, when I do something from my computer working as router which
have these tunnels
Worse is from, when I for ex. traceroute from 2001:768.... to 3ffe:bc0... from computer inside my LAN, sending is over freenet6 but receiving is by sixxs tunnel.
That's normal because freenet6 don't know that he can route sixxs class via freenet6 tunnel.
So my question is: how to adveriste to local freenet6 router that he can route
my sixxs class via my tunnel to freenet6?
Route advertise
Assymetric routing is the worst thing there is. And Freenet should not even be accepting packets coming from a block not owned by them. Your OS should select the correct source address and pick the correct outgoing route based on that.
Route advertise
Shadow Hawkins on Monday, 29 September 2003 15:46:24
How to do it?
when:
2001:768:1941:a::2
|
V
2001:768:1941:a::1
2001:768:1941::1 -> sixxs
3ffe:b80:1c3d::1 -> freeneet
ip -6 r s
2001:768:1900:7f::/64 via :: dev sixxs proto kernel metric 256 mtu 1280 advmss 1220
2001:768:1941:a::/64 via :: dev bjaly proto kernel metric 256 mtu 1280 advmss 1220
2001:768:1941:a::/64 via 2001:768:1941:a::2 dev bjaly metric 1024 mtu 1280 advmss 1220
3ffe:b80::/32 dev freenet metric 1024 mtu 1480 advmss 1420
3ffe:bc0::/32 dev freenet metric 1024 mtu 1480 advmss 1420
[...]
2000::/3 via 2001:768:1900:7f::1 dev sixxs metric 1024 mtu 1280 advmss 1220
[...]
default via 2001:768:1900:7f::1 dev sixxs metric 1024 mtu 1280 advmss 1220
unreachable default dev lo proto none metric -1 error -101 advmss 1220
and ifconfig:
sixxs Link encap:IPv6-in-IPv4
inet6 addr: 2001:768:1900:7f::2/64 Scope:Global
inet6 addr: 2001:768:1941::1/128 Scope:Global
inet6 addr: fe80::3eb3:40e/128 Scope:Link
UP POINTOPOINT RUNNING NOARP MTU:1280 Metric:1
RX packets:1017030 errors:0 dropped:0 overruns:0 frame:0
TX packets:1021503 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:387892183 (369.9 Mb) TX bytes:96792600 (92.3 Mb)
bjaly Link encap:IPv6-in-IPv4
inet6 addr: 2001:768:1941:a::1/64 Scope:Global
inet6 addr: fe80::3eb3:40e/128 Scope:Link
UP POINTOPOINT RUNNING NOARP MTU:1280 Metric:1
RX packets:11262 errors:0 dropped:0 overruns:0 frame:0
TX packets:10788 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1063191 (1.0 Mb) TX bytes:1730308 (1.6 Mb)
freenet Link encap:IPv6-in-IPv4
inet6 addr: 3ffe:b80:1c3d::1/128 Scope:Global
inet6 addr: fe80::3eb3:40e/128 Scope:Link
UP POINTOPOINT RUNNING NOARP MTU:1480 Metric:1
RX packets:569 errors:0 dropped:0 overruns:0 frame:0
TX packets:849 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:137586 (134.3 Kb) TX bytes:300216 (293.1 Kb)
Route advertise
Make your OS do source based routing :)
It is possible with IPv4, but not with IPv6 on Linux yet, so pick a BSD or code it yourself, it is all Open Source now isn't it.
Route advertise
Shadow Hawkins on Tuesday, 30 September 2003 18:30:01
I'm not C programmer so I have to leave it's as is now :-(
Route advertise
![[de]](/s/countries/de.gif) Shadow Hawkins on Saturday, 04 October 2003 02:07:35
Hi Marcin,
So my question is: how to adveriste to local freenet6 router that he can route
my sixxs class via my tunnel to freenet6?
that's what routing protocolls are for. BGP4+, e.g. zebra. Maybe they would be happy with RIP+. Not that I think that freenet6 would do this at all, getting many requests then from all the people in "IPv6 world" who want to do this too. And not to mention that your addresses don't belong to you, you are allowed to use them in a specific way. ;-)
The only solution I see is to run kind of a proxy on your router with the several tunnels. The packet will be rebuild then and the source address is determined by the outgoing interface, so a freenet6 address when you route this path, a SixXS address otherwise.
Regards, Marc
|
![[ch]](/s/countries/ch.gif)
on Sunday, 28 September 2003 19:48:52
Posting is only allowed when you are