SixXS::Sunset 2017-06-06

openbsd and rtadvd
[nl] Shadow Hawkins on Thursday, 06 November 2003 22:36:15
I am running openbsd 3.3 and am trying to get rtadvd up and running for my subnet, which is 2001:838:364::/48. I have assigned 2001:838:364:1::1 to fxp0 (which is my localnet if). This is the rtadvd.conf I got: fxp0:\ :addrs#1:addr="2001:838:364:1::": -- sysctl -w net.inet6.ip6.forwarding=1 (enabeling ip6 forwarding seems to be necessary according to this error msg in /var/log/daemon: Nov 6 21:02:00 xxxx rtadvd[2810]: <getconfig> non zero router lifetime is specified for fxp0, which must not be allow ed for hosts. you must change router lifetime or enable IPv6 forwarding. ) I started it using the -d parameter: rtadvd -d fxp0, it seems to be up and running . In /var/log/daemon this line shows up (and keeps showing up): Nov 6 22:21:48 xxxx rtadvd[27766]: <ra_output> sendmsg on fxp0: No route to host After al this I tried to get an ip6 number on my other machine (openbsd 3.4) using "rtsol fxp0" nothing seems to happen. After this I tried "rtsol -d fxp0" for some more verbose output which is: checking if fxp0 is ready... fxp0 is ready send RS on fxp0, whose state is 2 send RS on fxp0, whose state is 2 send RS on fxp0, whose state is 2 No answer after sending 3 RSs stop timer for fxp0 there is no timer --- I don't have a clue where to go next. Anyone any suggestion?
openbsd and rtadvd
[ch] Jeroen Massar SixXS Staff on Friday, 07 November 2003 10:34:09
See Using Subnets on *BSD (KAME) which describes the correct format of the rtadvd.conf file. Next to that did you route the /64 to that interface?
openbsd and rtadvd
[nl] Shadow Hawkins on Friday, 07 November 2003 13:57:16
I used the format described in the faq. Know I get this error: # rtadvd -fd fxp0 rtadvd[27582]: <getconfig> fxp0 isn't defined in the configuration file or the configuration file doesn't exist. Treat it as default rtadvd[27582]: <getconfig> need addr as a prefix for interface fxp0 My /etc/rtadvd.conf looks like this: # cat /etc/rtadvd.conf fxp0:\ :addrs#1:\ :addr="2001:838:364:2::":prefixlen#64\ :tc=ether: -- My fxp0 has ip6 inet6 2001:838:364:2::1 prefixlen 64 (ifconfig fxp0 inet6 2001:0838:0364:0002::1 prefixlen 64 alias) I've setup my route for the subnet like this: route add -inet6 2001:838:364:: -prefixlen 64 2001:838:300:bc::2 Any clue on the rtadvd error? (and is the routing correct?)
openbsd and rtadvd
[ch] Jeroen Massar SixXS Staff on Friday, 07 November 2003 17:01:36
I've setup my route for the subnet like this:
route add -inet6 2001:838:364:: -prefixlen 64 2001:838:300:bc::2
Thus you are routing the subnet over the tunnel instead? :) You should nullroute the /48: # route add -inet6 2001:838:364:: -prefixlen 48 ::1 And only configure the /64 on fxp0 and it should work...
openbsd and rtadvd
[nl] Shadow Hawkins on Saturday, 08 November 2003 17:37:34
I feel pretty stupid right now |:( but, I deleted the routing and made the nullroute. Fxp0 now has inet6 2001:838:364:2::1 prefixlen 64. I didn't changed the /etc/rtadvd.conf but started it in a differentway. # rtadvd -c/etc/rtadvd.conf fxp0 # ps -awx |grep rtadvd 11118 ?? Is 0:00.00 rtadvd -c/etc/rtadvd.conf fxp0 15958 p1 I+ 0:00.00 grep rtadvd the process is running. In /var/log/daemon this shows up: Nov 8 17:35:09 xxxx rtadvd[11118]: <ra_output> sendmsg on fxp0: No route to host Looks like we're back to the old problem ... Did I miss anything?
openbsd and rtadvd
[nl] Shadow Hawkins on Saturday, 08 November 2003 20:28:12
*OOPS* did I mention I didn't change my fw? O-) I've just editted my fw (remote) and the message to /var/log/daemon doesn't show up anymore. Will try tomorrow to see if it works when I allow inet6 for fxp0 })
openbsd and rtadvd
[nl] Shadow Hawkins on Sunday, 09 November 2003 12:26:53
Ok, I feel really stupid right now :( Looks like it was my fw afterall. I allowed everything in and out for inet6 on fxp0. Restarted the rtadvd, no warning in /var/log/daemon this time. I tried my client (openbsd 3.4) sjaak# rtsol -d fxp0 checking if fxp0 is ready... fxp0 is ready send RS on fxp0, whose state is 2 received RA from fe80::2d0:b7ff:fee7:d046 on fxp0, state is 2 As you see it got an ip from the advertisment daemon HIT ME PLEASE |:(
openbsd and rtadvd
[ch] Jeroen Massar SixXS Staff on Sunday, 09 November 2003 12:43:25
<grin>

Please note Posting is only allowed when you are logged in.

Static Sunset Edition of SixXS
©2001-2017 SixXS - IPv6 Deployment & Tunnel Broker