On Sun, Aug 10, 2008 at 12:17:43AM +0100, saqmaster wrote:
| Hi,
| 
| This is my first post here so please let me know if I need to adjust
| my approach :-)
| 
| I'm in the process of setting up one of my obsd 4.2 boxes as an ipv6
| router (6to4). I've configured rtadvd, as far as I can see, correctly
| :-
| 
| # cat /etc/rtadvd.conf
| pcn0:\
| 
|         :addr="2001:08B0:0013:0001::":prefixlen#64:

I'm assuming you've configured pcn0 with an IP address in this
network. In that case, can you try skipping the rtadvd.conf
configuration ? rtadvd should do the right thing (tm) when given an
interface on the commandline and that interface has an IP configured
(it'll do RA for the /64 it's been configured in).

See rtadvd.conf(5), especially this part :

     As described in rtadvd(8), you do not have to set this configuration file
     up at all, unless you need some special configurations.  You may even
     omit the file as a whole.  In such cases, the rtadvd daemon will automat-
     ically configure itself using default values specified in the specifica-
     tion.

You've already been told to not use 4.2, you can even try ~4.4,
snapshots are currently pretty close to what eventually will be 4.4,
and there's been some changes to rtadvd which generally 'make sense'
(they're security related so won't fix your problem, but are good to
have nonetheless).

| If, on another host I try and rstol, I get :-
| 
| 
| # rtsol -d pcn0
| checking if pcn0 is ready...
| pcn0 is ready
| send RS on pcn0, whose state is 2
| invalid RA with non link-local source from 2001:8b0:13:1::1 on pcn0
| send RS on pcn0, whose state is 2
| invalid RA with non link-local source from 2001:8b0:13:1::1 on pcn0
| send RS on pcn0, whose state is 2
| invalid RA with non link-local source from 2001:8b0:13:1::1 on pcn0
| No answer after sending 3 RSs
| stop timer for pcn0
| there is no timer
| 
| 
| And on the rtadvd server :-
| 
| rtadvd[2066]: <rs_input> RS received from fe80::20c:29ff:fecd:f77a on pcn0
| rtadvd[2066]: <main> set timer to 0:185635. waiting for inputs or timeout
| rtadvd[2066]: <ra_timeout> RA timer on pcn0 is expired
| rtadvd[2066]: <ra_output> send RA on pcn0, # of waitings = 1
| rtadvd[2066]: <ra_timer_update> RA timer on pcn0 is set to 361:0
| rtadvd[2066]: <main> set timer to 361:0. waiting for inputs or timeout
| rtadvd[2066]: <ra_input> RA received from 2001:8b0:13:1::1 on pcn0
| rtadvd[2066]: <main> set timer to 360:995941. waiting for inputs or timeout
| rtadvd[2066]: <rs_input> RS received from fe80::20c:29ff:fecd:f77a on pcn0
| rtadvd[2066]: <main> set timer to 0:13146. waiting for inputs or timeout
| rtadvd[2066]: <ra_timeout> RA timer on pcn0 is expired
| rtadvd[2066]: <ra_output> send RA on pcn0, # of waitings = 1
| rtadvd[2066]: <ra_timer_update> RA timer on pcn0 is set to 259:0
| rtadvd[2066]: <main> set timer to 259:0. waiting for inputs or timeout
| rtadvd[2066]: <ra_input> RA received from 2001:8b0:13:1::1 on pcn0
| rtadvd[2066]: <main> set timer to 258:995435. waiting for inputs or timeout
| rtadvd[2066]: <rs_input> RS received from fe80::20c:29ff:fecd:f77a on pcn0
| rtadvd[2066]: <main> set timer to 0:303812. waiting for inputs or timeout
| rtadvd[2066]: <ra_timeout> RA timer on pcn0 is expired
| rtadvd[2066]: <ra_output> send RA on pcn0, # of waitings = 1
| rtadvd[2066]: <ra_timer_update> RA timer on pcn0 is set to 370:0
| rtadvd[2066]: <main> set timer to 370:0. waiting for inputs or timeout
| rtadvd[2066]: <ra_input> RA received from 2001:8b0:13:1::1 on pcn0
| rtadvd[2066]: <main> set timer to 369:995653. waiting for inputs or timeout
| 
| 
|  Could anyone point me to where i'm going wrong?

Try giving a bit more information. What do you see when you tcpdump ?
What is the current configuration of the two interfaces (the one on
the rtadvd server and the one on the client) ? Who has this
2001:8b0:13:1::1 address ? I'm guessing it's the rtadvd server, but
you haven't told us.

Cheers,

Paul 'WEiRD' de Weerd

-- 
>++++++++[<++++++++++>-]<+++++++.>+++[<------>-]<.>+++[<+
+++++++++++>-]<.>++[<------------>-]<+.--------------.[-]
                 http://www.weirdnet.nl/                 

Reply via email to