tech-net archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: Cannot get IPv6 router working



On Wed, Jul 01, 2009 at 05:40:21PM -0400, Brian A. Seklecki wrote:
> Just out of curiosity:  Does this mean your provider is handing you
> FE80::/10 space on the WAN?  

Unlikely, but our IPv6 code selects a real adress (if any is assigned
to whatever interface) and uses that as route, so it just works.

I have this on my router:

pppoe0: flags=8851<UP,POINTOPOINT,RUNNING,SIMPLEX,MULTICAST> mtu 1456
        inet 82.139.198.17 -> 82.139.222.46 netmask 0xff000000
        inet6 fe80::a00:20ff:fe99:fc91%pppoe0 ->  prefixlen 64 scopeid 0xa
hme0: flags=8a63<UP,BROADCAST,NOTRAILERS,RUNNING,ALLMULTI,SIMPLEX,MULTICAST> 
mtu 1500
        capabilities=3c00<TCP4CSUM_Rx,TCP4CSUM_Tx,UDP4CSUM_Rx,UDP4CSUM_Tx>
        enabled=c00<TCP4CSUM_Rx,TCP4CSUM_Tx>
        address: 08:00:20:99:fc:91
        media: Ethernet autoselect (100baseTX full-duplex)
        status: active
        inet 192.168.150.10 netmask 0xffffff00 broadcast 192.168.150.255
        inet6 fe80::a00:20ff:fe99:fc91%hme0 prefixlen 64 scopeid 0x1
        inet6 2a01:170:1032:1::1 prefixlen 64

and it all just seems to work fine.

What I found strange is that I can't distinguish a v6 "enabled" pppoe
connection from a non-v6 one:

pppoe1: flags=8851<UP,POINTOPOINT,RUNNING,SIMPLEX,MULTICAST> mtu 1492
        inet 79.218.103.121 -> 217.0.118.173 netmask 0xff000000
        inet6 fe80::a00:20ff:fe99:fc91%pppoe1 ->  prefixlen 64 scopeid 0xb

But this is just like normal ethernet - they get a link local v6 address and
you can't see if v6 works on the wire.

However, to help avoid confusion, I plan to add a command to pppoectl that
allows listing of active controll programs, so I could see "LCP IPCP IPv6CP"
on pppoe0 but only "LCP IPCP" on pppoe1.

Martin


Home | Main Index | Thread Index | Old Index