Paul de Weerd wrote:
> Well, all looks well from what you've sent.
Sorry Paul, it did work. The new IP was hiding at the bottom of a
large list of aliases on the interface and I didn't notice it. All
good now, thanks everyone :)
On Mon, Aug 11, 2008 at 02:54:46PM +0100, saqmaster wrote:
| Paul de Weerd wrote:
|
| > Try again with link-local addresses on your interfaces, no rtadvd.conf
| > file and tcpdump to see what's going on. Post back if you have more
| > details.
|
| Sorry, I have mislead you slightly (getting the l
Paul de Weerd wrote:
> Try again with link-local addresses on your interfaces, no rtadvd.conf
> file and tcpdump to see what's going on. Post back if you have more
> details.
Sorry, I have mislead you slightly (getting the link-local address
back in and testing reminded me).
With the link-local
On Mon, Aug 11, 2008 at 02:14:46PM +0100, saqmaster wrote:
| > And here's the gist of your problem. Your vic0 interface doesn't have
| > a link-local address.
| >
| > That's very interesting - did you somehow configure this yourself ?
| > Generally speaking, when an interface is up and your kernel
Paul de Weerd wrote:
> And here's the gist of your problem. Your vic0 interface doesn't have
> a link-local address.
>
> That's very interesting - did you somehow configure this yourself ?
> Generally speaking, when an interface is up and your kernel supports
> IPv6, the interface gets a link-local
On Mon, Aug 11, 2008 at 01:56:14PM +0100, saqmaster wrote:
| Paul de Weerd wrote:
| # ifconfig -A
| lo0: flags=8049 mtu 33208
| groups: lo
| inet 127.0.0.1 netmask 0xff00
| inet6 ::1 prefixlen 128
| inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3
| vic0: flags=8843 mt
Paul de Weerd wrote:
> Although we see RA's with a non-link-local source IP (bad), some more
> verbose output (tcpdump -vv) would've been nice. Here's a proper
> exchange (`tcpdump -nepvvs 1500 -i fxp0 icmp6`, in my case) :
My apologies, i've posted this in a couple of places and i've lost
track
On Mon, Aug 11, 2008 at 01:30:05PM +0100, saqmaster wrote:
| This is the output of tcpdump on the server whilst the client attempts
| to get an IP:
|
| 12:19:15.728006 fe80::20c:29ff:fecd:f77a > ff02::2: icmp6: router solicitation
| 12:19:15.755793 2001:8b0:13:1::1 > ff02::1: icmp6: router adverti
Paul de Weerd wrote:
> 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
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, correc
I've upgraded the router to 4.3-release and it's the same. I'd be
quite surprised if rtadvd was completely broken in something as late
as 4.2.
For reference, pcn0 is now vic0 in the 4.3 configuration.
Any thoughts people? Thanks.
2008/8/10 Daniel Ouellet <[EMAIL PROTECTED]> wrote:
> Do yourself
saqmaster wrote:
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
I haven't looked at any other informations you provided, but I can tell
you the last thing you should do if you want to setup a router is
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
13 matches
Mail list logo
