Re: Comcast Business static IPv6 setup?

2017-10-06 Thread Ed D.
I was wondering if it was some kinf of routing issue
that I haven't yet comprehended.

On 6 Oct 2017 at 23:17, Stuart Henderson wrote:

On 2017/10/06 18:05, Ed  D. wrote:
> They all get an IPv6 address and gateway, but no IPv6  DNS
> server addresses of leases.

The RDNSS stuff isn't very supported everywhere yet. As far as Windows
goes I think it's just on creator's update.

> From a PC I can ping the internal interface of the router and
> the IPv6 address of te external interface of the router.
> 
> But no PC's can actually "talk" to the Internet. and they fail
> http://test-ipv6-ct.comcast.net/.

I am thinking your ISP router is setup to expect the machines to be
directly on its internal interface. It probably doesn't have a route to
the addresses you're actually using.

___
Openbsd-newbies mailing list
Openbsd-newbies@sfobug.theapt.org
http://mailman.theapt.org/listinfo/openbsd-newbies
___
Openbsd-newbies mailing list
Openbsd-newbies@sfobug.theapt.org
http://mailman.theapt.org/listinfo/openbsd-newbies


Re: Comcast Business static IPv6 setup?

2017-10-06 Thread Ed D.
On 6 Oct 2017 at 23:17, Stuart Henderson wrote:

On 2017/10/06 18:05, Ed  D. wrote:
> They all get an IPv6 address and gateway, but no IPv6  DNS
> server addresses of leases.

The RDNSS stuff isn't very supported everywhere yet. As far as Windows
goes I think it's just on creator's update.

> From a PC I can ping the internal interface of the router and
> the IPv6 address of te external interface of the router.
> 
> But no PC's can actually "talk" to the Internet. and they fail
> http://test-ipv6-ct.comcast.net/.

I am thinking your ISP router is setup to expect the machines to be
directly on its internal interface. It probably doesn't have a route to
the addresses you're actually using.

___
Openbsd-newbies mailing list
Openbsd-newbies@sfobug.theapt.org
http://mailman.theapt.org/listinfo/openbsd-newbies
___
Openbsd-newbies mailing list
Openbsd-newbies@sfobug.theapt.org
http://mailman.theapt.org/listinfo/openbsd-newbies


Re: Comcast Business static IPv6 setup?

2017-10-06 Thread Robert Szasz
The routing issue is why I suggest giving your internal network a different
/64 then your external interface.  (Comcast assigns a /fiftysomething)

On Oct 6, 2017 15:17, "Stuart Henderson"  wrote:

> On 2017/10/06 18:05, Ed  D. wrote:
> > They all get an IPv6 address and gateway, but no IPv6  DNS
> > server addresses of leases.
>
> The RDNSS stuff isn't very supported everywhere yet. As far as Windows
> goes I think it's just on creator's update.
>
> > From a PC I can ping the internal interface of the router and
> > the IPv6 address of te external interface of the router.
> >
> > But no PC's can actually "talk" to the Internet. and they fail
> > http://test-ipv6-ct.comcast.net/.
>
> I am thinking your ISP router is setup to expect the machines to be
> directly on its internal interface. It probably doesn't have a route to
> the addresses you're actually using.
>
> ___
> Openbsd-newbies mailing list
> Openbsd-newbies@sfobug.theapt.org
> http://mailman.theapt.org/listinfo/openbsd-newbies
>
___
Openbsd-newbies mailing list
Openbsd-newbies@sfobug.theapt.org
http://mailman.theapt.org/listinfo/openbsd-newbies


Re: Comcast Business static IPv6 setup?

2017-10-06 Thread Stuart Henderson
On 2017/10/06 18:05, Ed  D. wrote:
> They all get an IPv6 address and gateway, but no IPv6  DNS
> server addresses of leases.

The RDNSS stuff isn't very supported everywhere yet. As far as Windows
goes I think it's just on creator's update.

> From a PC I can ping the internal interface of the router and
> the IPv6 address of te external interface of the router.
> 
> But no PC's can actually "talk" to the Internet. and they fail
> http://test-ipv6-ct.comcast.net/.

I am thinking your ISP router is setup to expect the machines to be
directly on its internal interface. It probably doesn't have a route to
the addresses you're actually using.

___
Openbsd-newbies mailing list
Openbsd-newbies@sfobug.theapt.org
http://mailman.theapt.org/listinfo/openbsd-newbies


Re: Comcast Business static IPv6 setup?

2017-10-06 Thread Robert Szasz
Are you sure you have ipv6 routing enabled in sysctl?

On Oct 6, 2017 15:05, "Ed D."  wrote:

> On 6 Oct 2017 at 14:11, Stuart Henderson wrote:
>
> On 2017-10-01, Ed  D.  wrote:
> > NOTE: fe80:0:0:0:f44b:2aff:fe77:33d0%em2
> > in mygate is based on Comcast stating
> > "The IPv6 default gateway will be the
> > IPv6 link local address of the
> > LAN interface of the Business IP Gateway."
> > I got in as admin and got this value.
>
> Ah, so this is a bit of important information that was missing. This
> "business IP gateway" is already the router then and is presumably
> doing
> DHCPv6-PD. With that type of setup you will probably need to either
> bridge or NAT.
>
> ===
>
> Thanks for the reply.
>
> In my case, I have a block of 5 static IPv4 addresses and
> when checking my account I see that I've been given a
> static IPv6 address too.
>
> I have no trouble connecting my OpenBSD based router
> (6.2 AMD64  as of 10-4-17)
>
> I'm using various tweaks of the read-me dhcpcd.conf file
> with the dhcpcd-6.11.5p4 package at
> /usr/local/share/doc/pkg-readmes
>
> I also see when I log into the Comcast box that it recognises
> my router.
>
> My only problem now is getting my PC's on my LAN to work.
>
> They all get an IPv6 address and gateway, but no IPv6  DNS
> server addresses of leases.
>
> From a PC I can ping the internal interface of the router and
> the IPv6 address of te external interface of the router.
>
> But no PC's can actually "talk" to the Internet. and they fail
> http://test-ipv6-ct.comcast.net/.
>
> I'm spending my time on this trying to figure out why.
>
> Any suggestions?  Thanks,  Ed
>
> ___
> Openbsd-newbies mailing list
> Openbsd-newbies@sfobug.theapt.org
> http://mailman.theapt.org/listinfo/openbsd-newbies
> ___
> Openbsd-newbies mailing list
> Openbsd-newbies@sfobug.theapt.org
> http://mailman.theapt.org/listinfo/openbsd-newbies
>
___
Openbsd-newbies mailing list
Openbsd-newbies@sfobug.theapt.org
http://mailman.theapt.org/listinfo/openbsd-newbies


Re: Comcast Business static IPv6 setup?

2017-10-06 Thread Ed D.
On 6 Oct 2017 at 14:11, Stuart Henderson wrote:

On 2017-10-01, Ed  D.  wrote:
> NOTE: fe80:0:0:0:f44b:2aff:fe77:33d0%em2
> in mygate is based on Comcast stating
> "The IPv6 default gateway will be the 
> IPv6 link local address of the 
> LAN interface of the Business IP Gateway."
> I got in as admin and got this value.

Ah, so this is a bit of important information that was missing. This
"business IP gateway" is already the router then and is presumably 
doing
DHCPv6-PD. With that type of setup you will probably need to either
bridge or NAT.

===

Thanks for the reply.

In my case, I have a block of 5 static IPv4 addresses and
when checking my account I see that I've been given a
static IPv6 address too.

I have no trouble connecting my OpenBSD based router
(6.2 AMD64  as of 10-4-17)

I'm using various tweaks of the read-me dhcpcd.conf file
with the dhcpcd-6.11.5p4 package at
/usr/local/share/doc/pkg-readmes

I also see when I log into the Comcast box that it recognises
my router.

My only problem now is getting my PC's on my LAN to work.

They all get an IPv6 address and gateway, but no IPv6  DNS
server addresses of leases.

>From a PC I can ping the internal interface of the router and
the IPv6 address of te external interface of the router.

But no PC's can actually "talk" to the Internet. and they fail
http://test-ipv6-ct.comcast.net/.

I'm spending my time on this trying to figure out why.

Any suggestions?  Thanks,  Ed

___
Openbsd-newbies mailing list
Openbsd-newbies@sfobug.theapt.org
http://mailman.theapt.org/listinfo/openbsd-newbies
___
Openbsd-newbies mailing list
Openbsd-newbies@sfobug.theapt.org
http://mailman.theapt.org/listinfo/openbsd-newbies


Re: Comcast Business static IPv6 setup?

2017-10-06 Thread Stuart Henderson
On 2017-10-01, Ed  D.  wrote:
> NOTE: fe80:0:0:0:f44b:2aff:fe77:33d0%em2
> in mygate is based on Comcast stating
> "The IPv6 default gateway will be the 
> IPv6 link local address of the 
> LAN interface of the Business IP Gateway."
> I got in as admin and got this value.

Ah, so this is a bit of important information that was missing. This "business
IP gateway" is already the router then and is presumably doing DHCPv6-PD. With
that type of setup you will probably need to either bridge or NAT.



___
Openbsd-newbies mailing list
Openbsd-newbies@sfobug.theapt.org
http://mailman.theapt.org/listinfo/openbsd-newbies


Re: Comcast Business static IPv6 setup?

2017-10-01 Thread Ed D.
Hi,
Since my previous post I began
at square one again.

I got further along than the last attempt.

WITHOUT starting dhcpcd.

Using the following type of setup
suggested by somebody on this list
(I don't have permission to use his name)
I get the CLOSEST to what I'm trying to do.

All of my router interfaces end up with a
IPv6 unicast global address, as well as
all Windows 7 based computers on my LAN.
They all get a default gateway of
fe80::a236:9fff:fe87:60b
according to "Network Connection Details"
on the windows 7 computers.

ping6 works
I just don't yet get inet6 tcp coming back in.
 Thanks,  Ed




em1 is my internal (LAN) interface
em2 is my external interface
rtadvd_flags="em1"

# cat hostname.em1
inet 192.168.0.1 255.255.255.0 NONE description "Private Network"
inet6  2603:xx0f:1603:8000::2/64
#
#
# cat hostname.em2
inet 96.85.179.161 255.255.255.248 NONE description "Internet 
Interface"
inet alias 96.xx.179.162 255.255.255.255 NONE
inet alias 96.xx.179.163 255.255.255.255 NONE
inet alias 96.xx.179.164 255.255.255.255 NONE
inet alias 96.xx.179.165 255.255.255.255 NONE
inet6 2603:xx0f:1603:8000::1/64
#
# cat rtadvd.conf
em1:\#my internal interference
:prefixlen#64:\
:rdnss="2001:558:FEED::1,2001:558:FEED::2":
#
#
# cat mygate
96.xx.179.166
fe80:0:0:0:f44b:2aff:fe77:33d0%em2
#

NOTE: fe80:0:0:0:f44b:2aff:fe77:33d0%em2
in mygate is based on Comcast stating
"The IPv6 default gateway will be the 
IPv6 link local address of the 
LAN interface of the Business IP Gateway."
I got in as admin and got this value.


#
#
# ifconfig -A
lo0: flags=8049 mtu 32768
index 6 priority 0 llprio 3
groups: lo
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x6
inet 127.0.0.1 netmask 0xff00
em1: flags=8843 mtu 1500
lladdr a0:36:9f:87:06:0b
description: Private Network
index 2 priority 0 llprio 3
media: Ethernet autoselect (1000baseT 
full-duplex,master,rxpause,txpause)
status: active
inet 192.168.0.1 netmask 0xff00 broadcast 192.168.0.255
inet6 fe80::a236:9fff:fe87:60b%em1 prefixlen 64 scopeid 0x2
inet6 2603:xx0f:1603:8000::2 prefixlen 64
em2: flags=8843 mtu 1500
lladdr 0c:c4:7a:6d:3b:0e
description: Internet Interface
index 3 priority 0 llprio 3
groups: egress
media: Ethernet autoselect (1000baseT 
full-duplex,rxpause,txpause)
status: active
inet 96.xx.179.161 netmask 0xfff8 broadcast 96.85.179.167
inet 96.xx.179.162 netmask 0x
inet 96.xx.179.163 netmask 0x
inet 96.xx.179.164 netmask 0x
inet 96.xx.179.165 netmask 0x
inet6 fe80::ec4:7aff:fe6d:3b0e%em2 prefixlen 64 scopeid 0x3
inet6 2603:xx0f:1603:8000::1 prefixlen 64
enc0: flags=0<>
index 5 priority 0 llprio 3
groups: enc
status: active
pflog0: flags=141 mtu 33136
index 7 priority 0 llprio 3
groups: pflog
#
#



On 30 Sep 2017 at 22:16, Ed  D. wrote:

Thanks for the reply.

I'll start at ground zero, as when I begin
changing things I just get in deeper. :-)

I've had no problem since the beginning of
doing ping6 at the router command line and
having it work.
# ping6 yahoo.com
ping6: Warning: yahoo.com has multiple addresses; using 
2001:4998:58:c02::a9
PING yahoo.com (2001:4998:58:c02::a9): 56 data bytes
64 bytes from 2001:4998:58:c02::a9: icmp_seq=0 hlim=50 time=66.158 ms 
64
bytes from 2001:4998:58:c02::a9: icmp_seq=1 hlim=50 time=54.363 ms 64
bytes from 2001:4998:58:c02::a9: icmp_seq=2 hlim=50 time=54.686 ms 64
bytes from 2001:4998:58:c02::a9: icmp_seq=3 hlim=50 time=54.165 ms ^C
--- yahoo.com ping statistics --- 4 packets transmitted, 4 packets
received, 0.0% packet loss round-trip min/avg/max/std-dev =
54.165/57.343/66.158/5.093 ms #


I'm just getting nowhere being able to get
an IPv6 address to Windows 7 based computers
on my LAN.

I'm using em2 as my external interface
and em1 as my internal LAN interface.

I have "inet6 autoconf" in both of them
and using using the default rtadvd settings.
(empty rtadvd.conf file)

My rc.conf.local rtadvd_flags="em1".

At this point, a computer on the LAN
does get am IPv6 default gateway, but not
a IPv6 address.
  Thanks,  Ed

my dhcpcd.conf file I'm currently trying is
this, and I run it by putting
pkg_scripts=dhcpcd
in /etc/rc.conf.local

=
# cat dhcpcd.conf
ipv6only
duid
persistent
option rapid_commit
require dhcp_server_identifier

# disable running any hooks; not typically required for simple 
DHCPv6-PD setup
script /usr/bin/true

# Disable dhcpcd's own router solicitation support; allow the kernel to
# do this instead by setting "inet6 autoconf" in hostname.pppoe0
noipv6rs
denyinterfaces em0 em3  # Don't touch at all

# List interfaces explicitly so that dhcpcd doesn't touch others
allowinterfaces em0 em1

interface em2
ia_na 1# request an IPv6 address
# 

Re: Comcast Business static IPv6 setup?

2017-09-30 Thread Ed D.
Thanks for the reply.

I'll start at ground zero, as when I begin
changing things I just get in deeper. :-)

I've had no problem since the beginning of
doing ping6 at the router command line and
having it work.
# ping6 yahoo.com
ping6: Warning: yahoo.com has multiple addresses; using 
2001:4998:58:c02::a9
PING yahoo.com (2001:4998:58:c02::a9): 56 data bytes
64 bytes from 2001:4998:58:c02::a9: icmp_seq=0 hlim=50 time=66.158 ms
64 bytes from 2001:4998:58:c02::a9: icmp_seq=1 hlim=50 time=54.363 ms
64 bytes from 2001:4998:58:c02::a9: icmp_seq=2 hlim=50 time=54.686 ms
64 bytes from 2001:4998:58:c02::a9: icmp_seq=3 hlim=50 time=54.165 ms
^C
--- yahoo.com ping statistics ---
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 54.165/57.343/66.158/5.093 ms
#


I'm just getting nowhere being able to get
an IPv6 address to Windows 7 based computers
on my LAN.

I'm using em2 as my external interface
and em1 as my internal LAN interface.

I have "inet6 autoconf" in both of them
and using using the default rtadvd settings.
(empty rtadvd.conf file)

My rc.conf.local rtadvd_flags="em1".

At this point, a computer on the LAN
does get am IPv6 default gateway, but not
a IPv6 address.
  Thanks,  Ed

my dhcpcd.conf file I'm currently trying is
this, and I run it by putting
pkg_scripts=dhcpcd
in /etc/rc.conf.local

=
# cat dhcpcd.conf
ipv6only
duid
persistent
option rapid_commit
require dhcp_server_identifier

# disable running any hooks; not typically required for simple 
DHCPv6-PD setup
script /usr/bin/true

# Disable dhcpcd's own router solicitation support; allow the kernel
# to do this instead by setting "inet6 autoconf" in hostname.pppoe0
noipv6rs
denyinterfaces em0 em3  # Don't touch at all

# List interfaces explicitly so that dhcpcd doesn't touch others
allowinterfaces em0 em1

interface em2
ia_na 1# request an IPv6 address
# request prefix delegation for downstream interfaces.
ia_pd 2 em1/1
#
=

# ifconfig -A
lo0: flags=8049 mtu 32768
index 6 priority 0 llprio 3
groups: lo
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x6
inet 127.0.0.1 netmask 0xff00
em0: flags=8843 mtu 1500
lladdr a0:36:9f:87:06:0a
description: Public Network
index 1 priority 0 llprio 3
media: Ethernet autoselect (1000baseT 
full-duplex,master,rxpause,txpause)
status: active
inet 10.0.0.1 netmask 0xff00 broadcast 10.0.0.255
em1: flags=208843 mtu 
1500
lladdr a0:36:9f:87:06:0b
description: Private Network
index 2 priority 0 llprio 3
media: Ethernet autoselect (1000baseT 
full-duplex,master,rxpause,txpause)
status: active
inet 192.168.0.1 netmask 0xff00 broadcast 192.168.0.255
inet6 fe80::a236:9fff:fe87:60b%em1 prefixlen 64 scopeid 0x2
em2: flags=208843 mtu 
1500
lladdr 0c:c4:7a:6d:3b:0e
description: Internet Interface
index 3 priority 0 llprio 3
groups: egress
media: Ethernet autoselect (1000baseT 
full-duplex,rxpause,txpause)
status: active
inet xx.85.179.161 netmask 0xfff8 broadcast 96.85.179.167
inet xx.85.179.162 netmask 0x
inet xx.85.179.163 netmask 0x
inet xx.85.179.164 netmask 0x
inet xx.85.179.165 netmask 0x
inet6 fe80::ec4:7aff:fe6d:3b0e%em2 prefixlen 64 scopeid 0x3
inet6 2603:xx0f:1603:8000:1ce3:1efc:8d6c:bfde prefixlen 64 
autoconf autoconfprivacy pltime 84152 vltime 343501
inet6 2603:xx0f:1603:8000:ec4:7aff:fe6d:3b0e prefixlen 64 
autoconf pltime 345598 vltime 345598
enc0: flags=0<>
index 5 priority 0 llprio 3
groups: enc
status: active
pflog0: flags=141 mtu 33136
index 7 priority 0 llprio 3
groups: pflog
#


=
# slaacctl show interface
em2:
 index:   3 running: yes privacy: yes
lladdr: 0c:c4:7a:6d:3b:0e
 inet6: fe80::ec4:7aff:fe6d:3b0e%em2
Router Advertisement from fe80::f44b:2aff:fe77:33d0%em2
received: 2017-09-30 21:53:28; 1s ago
Cur Hop Limit:  64, M: 1, O: 1, Router Lifetime:   180s
Default Router Preference: Medium
Reachable Time: 0ms, Retrans Timer: 0ms
prefix: 2603:xx0f:1603:8000::/64
On-link: 1, Autonomous address-configuration: 1
vltime: 345600, pltime: 345600
rdns: 2001:558:feed::2, lifetime: 300
rdns: 2001:558:feed::1, lifetime: 300
Address proposals
id:2, state:  CONFIGURED, privacy: y
vltime: 345600, pltime:  86251, timeout:  
84671s
updated: 2017-09-30 21:27:24; 1565s ago
2603:xx0f:1603:8000:1ce3:1efc:8d6c:bfde, 
2603:300f:1603:8000::/64
id:3, stat

Re: Comcast Business static IPv6 setup?

2017-09-30 Thread Stuart Henderson
On 2017-09-30, Peter Hessler  wrote:
> Can you share your dhcpcd.conf file, and the way you run it?

Also the log entries from dhcpcd.

>:I'm using em2 for my Internet facing interface
>:and em1 for my LAN facing interface.
>:
>:By simply adding "inet6 autoconf" to
>:both hostname.em1 and hostname.em2, I get my IPv6 static IP
>:assigned to the router as shown below from ifconfig -A.
>:I and can ping6 any web address.

The ISP is not on em1 - don't set "autoconf" on em1.

Configured correctly, dhcpcd will ask the ISP (on em2) to delegate
a prefix to use on em1. If the ISP grants this, dhcpcd would configure
an address from within that prefix on em1.

You want rtadvd handing out the address to clients on em1.

>:Sep 27 23:20:21 meenon rtadvd[8704]: M flag inconsistent on em2: ON 
>:from:fe80::f44b:2aff:fe77:33d0, OFF from us

Don't run rtadvd on em2. This is equivalent to running a dhcp server on
the interface facing your ISP.

"rcctl set rtadvd flags em1" and "rcctl restart rtadvd" to run it on
just the internal interface.

If you don't get it working from this information, the best place
to ask is probably the dhcpcd mailing list.

>:===
>:# ifconfig -A
>:lo0: flags=8049 mtu 32768
>:index 6 priority 0 llprio 3
>:groups: lo
>:inet6 ::1 prefixlen 128
>:inet6 fe80::1%lo0 prefixlen 64 scopeid 0x6
>:inet 127.0.0.1 netmask 0xff00
>:em1: flags=208843 mtu
>:1500
>:lladdr xx:36:9f:87:06:0b
>:description: Private Network
>:index 2 priority 0 llprio 3
>:media: Ethernet autoselect (1000baseT 
>:full-duplex,master,rxpause,txpause)
>:status: active
>:inet 192.168.0.1 netmask 0xff00 broadcast 192.168.0.255
>:inet6 fe80::a236:9fff:fe87:60b%em1 prefixlen 64 scopeid 0x2

btw, if you're going to mask (part of) the mac address, you need to
also mask the link-local address which is derived from it. ...so now
we can all find out that you have Intel and Supermicro NICs :-)

But it doesn't really matter. Usually you're better off not masking.
If it's done inconsistently you just cause confusion for people who
are trying to help.

___
Openbsd-newbies mailing list
Openbsd-newbies@sfobug.theapt.org
http://mailman.theapt.org/listinfo/openbsd-newbies


Re: Comcast Business static IPv6 setup?

2017-09-30 Thread Peter Hessler
Can you share your dhcpcd.conf file, and the way you run it?


On 2017 Sep 29 (Fri) at 01:57:48 -0400 (-0400), Ed  D. wrote:
:
:Hi,
: After several long days of trying to figure this out
:I must say I'm stumped.
: I'm running OpenBSD 6.2 (GENERIC.MP) as of 9/26/17
:AMD64 version with dhcpcd-6.11.5p4
:
:  Does anybody have a working IPv6 setup
:that works with Comcast Business class service
:that will allow me to use IPv6 on my LAN that
:I could look at?
:
:So far, all I can get to work is what I get
:from placing "inet6 autoconf" in my WAN
:and LAN interfaces.
:
:I've now gotten rtadvd.conf to where i don't get errors
:in /var/log/daemon.
:
:I can ping from the command line of the router
:any web address I enter.
:
:I have dhcpcd-6.11.5p4 installed and have tried
:countless variations of the readme file
:example, the dist /etc/dhcpcd.conf, and various
:other examples I've gotten from various places.
:
:I've googled, searched mailing list archives,
:and none of what I've found is helping me.
:
:If ANYBODY has gotten this to work, could you
:let me know what you did?
:
:I'm just spinning my wheels, and I have RTFM
:for days but just not fnding the answer.
: Thanks, Ed
:
:
:On 27 Sep 2017 at 23:25, Ed  D. wrote:
:
:Hi,
:I'm having trouble getting IPv6 working on
:my router to assign IPv6 addresses to the computers
:on my LAN.
:I'm SURE there's something obvious I've been missing
:and hope I can get a nudge back on track.
:
:I have Comcast Business Class service, with a static
:IPv6 address, 26xx:300f:1603:8000::/56
:as well as a working block of IPv4 addresses.
:
:I'm running OpenBSD 6.2 (GENERIC.MP) as of 9/26/17
:AMD64 version.
:
:I'm using em2 for my Internet facing interface
:and em1 for my LAN facing interface.
:
:By simply adding "inet6 autoconf" to
:both hostname.em1 and hostname.em2, I get my IPv6 static IP
:assigned to the router as shown below from ifconfig -A.
:I and can ping6 any web address.
:
:THE problem is taking the next step of getting IPv6
:addresses assigned to computers on my LAN, which are 
:Windows 7 64bit Professional based systems.
:
:In reading mailing list archives and te web, I see
:dhcpcd being recommended to do this.
:
:I've looked at the read-me file from the dhcpcd package,
:the default /etc/dhcpcd.conf file, various posts
:from email archives, and web posts.
:I've experimented with them all in various configurations
:and I get nothing that will simply add the capability
:to assign IPv6 addresses to the computers on my LAN.
:
:I also want to leave me present working IPv4 dhcp setup intact.
:
:I would REALLY appreciate any direction with this, as there's
:something I'm missing.
:   Thanks,  Ed
:
:I also get this in my daemon log
:# cd /var/log
:# cat daemon
:Sep 27 23:20:21 meenon rtadvd[8704]: M flag inconsistent on em2: ON 
:from
:fe80::f44b:2aff:fe77:33d0, OFF from us Sep 27 23:20:21 meenon
:rtadvd[8704]: O flag inconsistent on em2: ON from
:fe80::f44b:2aff:fe77:33d0, OFF from us Sep 27 23:20:21 meenon
:rtadvd[8704]: preferred lifetime for 2603:300f:1603:8000::/64
:inconsistent on em2: 345600 from fe80::f44b:2aff:fe77:33d0, 604800 from
:us Sep 27 23:20:21 meenon rtadvd[8704]: valid lifetime for
:2603:300f:1603:8000::/64 inconsistent on em2: 345600 from
:fe80::f44b:2aff:fe77:33d0, 2592000 from us Sep 27 23:20:24 meenon
:rtadvd[8704]: M flag inconsistent on em2: ON from
:fe80::f44b:2aff:fe77:33d0, OFF from us Sep 27 23:20:24 meenon
:rtadvd[8704]: O flag inconsistent on em2: ON from
:fe80::f44b:2aff:fe77:33d0, OFF from us Sep 27 23:20:24 meenon
:rtadvd[8704]: preferred lifetime for 2603:300f:1603:8000::/64
:inconsistent on em2: 345600 from fe80::f44b:2aff:fe77:33d0, 604800 from
:us Sep 27 23:20:24 meenon rtadvd[8704]: valid lifetime for
:2603:300f:1603:8000::/64 inconsistent on em2: 345600 from
:fe80::f44b:2aff:fe77:33d0, 2592000 from us Sep 27 23:20:27 meenon
:rtadvd[8704]: M flag inconsistent on em2: ON from
:fe80::f44b:2aff:fe77:33d0, OFF from us Sep 27 23:20:27 meenon
:rtadvd[8704]: O flag inconsistent on em2: ON from
:fe80::f44b:2aff:fe77:33d0, OFF from us Sep 27 23:20:27 meenon
:rtadvd[8704]: preferred lifetime for 2603:300f:1603:8000::/64
:inconsistent on em2: 345600 from fe80::f44b:2aff:fe77:33d0, 604800 from
:us Sep 27 23:20:27 meenon rtadvd[8704]: valid lifetime for
:2603:300f:1603:8000::/64 inconsistent on em2: 345600 from
:fe80::f44b:2aff:fe77:33d0, 2592000 from us Sep 27 23:20:30 meenon
:rtadvd[8704]: M flag inconsistent on em2: ON from
:fe80::f44b:2aff:fe77:33d0, OFF from us Sep 27 23:20:30 meenon
:rtadvd[8704]: O flag inconsistent on em2: ON from
:fe80::f44b:2aff:fe77:33d0, OFF from us Sep 27 23:20:30 meenon
:rtadvd[8704]: preferred lifetime for 2603:300f:1603:8000::/64
:inconsistent on em2: 345600 from fe80::f44b:2aff:fe77:33d0, 604800 from
:us Sep 27 23:20:30 meenon rtadvd[8704]: valid lifetime for
:2603:300f:1603:8000::/64 inconsistent on em2: 345600 from
:fe80::f44b:2aff:fe77:33d0, 2592000 fro

Re: Comcast Business static IPv6 setup?

2017-09-29 Thread Eric B
Hi Ed,
If searching the mailing lists like misc@ haven’t been helpful, there’s an 
active group on Facebook that has a large group of users as well as some of the 
OpenBSD devs. Possible you might get the info you need there-
https://www.facebook.com/groups/2210554563

Cheers, Eric

> On Sep 28, 2017, at 22:57, Ed D.  wrote:
> 
> 
> Hi,
> After several long days of trying to figure this out
> I must say I'm stumped.
> I'm running OpenBSD 6.2 (GENERIC.MP) as of 9/26/17
> AMD64 version with dhcpcd-6.11.5p4
> 
>  Does anybody have a working IPv6 setup
> that works with Comcast Business class service
> that will allow me to use IPv6 on my LAN that
> I could look at?
> 
> So far, all I can get to work is what I get
> from placing "inet6 autoconf" in my WAN
> and LAN interfaces.
> 
> I've now gotten rtadvd.conf to where i don't get errors
> in /var/log/daemon.
> 
> I can ping from the command line of the router
> any web address I enter.
> 
> I have dhcpcd-6.11.5p4 installed and have tried
> countless variations of the readme file
> example, the dist /etc/dhcpcd.conf, and various
> other examples I've gotten from various places.
> 
> I've googled, searched mailing list archives,
> and none of what I've found is helping me.
> 
> If ANYBODY has gotten this to work, could you
> let me know what you did?
> 
> I'm just spinning my wheels, and I have RTFM
> for days but just not fnding the answer.
> Thanks, Ed
> 
> 
> On 27 Sep 2017 at 23:25, Ed  D. wrote:
> 
> Hi,
>I'm having trouble getting IPv6 working on
> my router to assign IPv6 addresses to the computers
> on my LAN.
> I'm SURE there's something obvious I've been missing
> and hope I can get a nudge back on track.
> 
> I have Comcast Business Class service, with a static
> IPv6 address, 26xx:300f:1603:8000::/56
> as well as a working block of IPv4 addresses.
> 
>I'm running OpenBSD 6.2 (GENERIC.MP) as of 9/26/17
> AMD64 version.
> 
> I'm using em2 for my Internet facing interface
> and em1 for my LAN facing interface.
> 
> By simply adding "inet6 autoconf" to
> both hostname.em1 and hostname.em2, I get my IPv6 static IP
> assigned to the router as shown below from ifconfig -A.
> I and can ping6 any web address.
> 
> THE problem is taking the next step of getting IPv6
> addresses assigned to computers on my LAN, which are 
> Windows 7 64bit Professional based systems.
> 
> In reading mailing list archives and te web, I see
> dhcpcd being recommended to do this.
> 
> I've looked at the read-me file from the dhcpcd package,
> the default /etc/dhcpcd.conf file, various posts
> from email archives, and web posts.
> I've experimented with them all in various configurations
> and I get nothing that will simply add the capability
> to assign IPv6 addresses to the computers on my LAN.
> 
> I also want to leave me present working IPv4 dhcp setup intact.
> 
> I would REALLY appreciate any direction with this, as there's
> something I'm missing.
>   Thanks,  Ed
> 
> I also get this in my daemon log
> # cd /var/log
> # cat daemon
> Sep 27 23:20:21 meenon rtadvd[8704]: M flag inconsistent on em2: ON 
> from
> fe80::f44b:2aff:fe77:33d0, OFF from us Sep 27 23:20:21 meenon
> rtadvd[8704]: O flag inconsistent on em2: ON from
> fe80::f44b:2aff:fe77:33d0, OFF from us Sep 27 23:20:21 meenon
> rtadvd[8704]: preferred lifetime for 2603:300f:1603:8000::/64
> inconsistent on em2: 345600 from fe80::f44b:2aff:fe77:33d0, 604800 from
> us Sep 27 23:20:21 meenon rtadvd[8704]: valid lifetime for
> 2603:300f:1603:8000::/64 inconsistent on em2: 345600 from
> fe80::f44b:2aff:fe77:33d0, 2592000 from us Sep 27 23:20:24 meenon
> rtadvd[8704]: M flag inconsistent on em2: ON from
> fe80::f44b:2aff:fe77:33d0, OFF from us Sep 27 23:20:24 meenon
> rtadvd[8704]: O flag inconsistent on em2: ON from
> fe80::f44b:2aff:fe77:33d0, OFF from us Sep 27 23:20:24 meenon
> rtadvd[8704]: preferred lifetime for 2603:300f:1603:8000::/64
> inconsistent on em2: 345600 from fe80::f44b:2aff:fe77:33d0, 604800 from
> us Sep 27 23:20:24 meenon rtadvd[8704]: valid lifetime for
> 2603:300f:1603:8000::/64 inconsistent on em2: 345600 from
> fe80::f44b:2aff:fe77:33d0, 2592000 from us Sep 27 23:20:27 meenon
> rtadvd[8704]: M flag inconsistent on em2: ON from
> fe80::f44b:2aff:fe77:33d0, OFF from us Sep 27 23:20:27 meenon
> rtadvd[8704]: O flag inconsistent on em2: ON from
> fe80::f44b:2aff:fe77:33d0, OFF from us Sep 27 23:20:27 meenon
> rtadvd[8704]: preferred lifetime for 2603:300f:1603:8000::/64
> inconsistent on em2: 345600 from fe80::f44b:2aff:fe77:33d0, 604800 from
> us Sep 27 23:20:27 meenon rtadvd[8704]: valid lifetime for
> 2603:300f:1603:8000::/64 inconsistent on em2: 345600 from
> fe80::f44b:2aff:fe77:33d0, 2592000 from us Sep 27 23:20:30 meenon
> rtadvd[8704]: M flag inconsistent on em2: ON from
> fe80::f44b:2aff:fe77:33d0, OFF from us Sep 27 23:20:30 meenon
> rtadvd[8704]: O flag inconsistent on em2: ON from
> fe80::f44b:2aff:fe77:33d0, OFF from us Se

Re: Comcast Business static IPv6 setup?

2017-09-28 Thread Ed D.

Hi,
 After several long days of trying to figure this out
I must say I'm stumped.
 I'm running OpenBSD 6.2 (GENERIC.MP) as of 9/26/17
AMD64 version with dhcpcd-6.11.5p4

  Does anybody have a working IPv6 setup
that works with Comcast Business class service
that will allow me to use IPv6 on my LAN that
I could look at?

So far, all I can get to work is what I get
from placing "inet6 autoconf" in my WAN
and LAN interfaces.

I've now gotten rtadvd.conf to where i don't get errors
in /var/log/daemon.

I can ping from the command line of the router
any web address I enter.

I have dhcpcd-6.11.5p4 installed and have tried
countless variations of the readme file
example, the dist /etc/dhcpcd.conf, and various
other examples I've gotten from various places.

I've googled, searched mailing list archives,
and none of what I've found is helping me.

If ANYBODY has gotten this to work, could you
let me know what you did?

I'm just spinning my wheels, and I have RTFM
for days but just not fnding the answer.
 Thanks, Ed


On 27 Sep 2017 at 23:25, Ed  D. wrote:

Hi,
I'm having trouble getting IPv6 working on
my router to assign IPv6 addresses to the computers
on my LAN.
I'm SURE there's something obvious I've been missing
and hope I can get a nudge back on track.

I have Comcast Business Class service, with a static
IPv6 address, 26xx:300f:1603:8000::/56
as well as a working block of IPv4 addresses.

I'm running OpenBSD 6.2 (GENERIC.MP) as of 9/26/17
AMD64 version.

I'm using em2 for my Internet facing interface
and em1 for my LAN facing interface.

By simply adding "inet6 autoconf" to
both hostname.em1 and hostname.em2, I get my IPv6 static IP
assigned to the router as shown below from ifconfig -A.
I and can ping6 any web address.

THE problem is taking the next step of getting IPv6
addresses assigned to computers on my LAN, which are 
Windows 7 64bit Professional based systems.

In reading mailing list archives and te web, I see
dhcpcd being recommended to do this.

I've looked at the read-me file from the dhcpcd package,
the default /etc/dhcpcd.conf file, various posts
from email archives, and web posts.
I've experimented with them all in various configurations
and I get nothing that will simply add the capability
to assign IPv6 addresses to the computers on my LAN.

I also want to leave me present working IPv4 dhcp setup intact.

I would REALLY appreciate any direction with this, as there's
something I'm missing.
   Thanks,  Ed

I also get this in my daemon log
# cd /var/log
# cat daemon
Sep 27 23:20:21 meenon rtadvd[8704]: M flag inconsistent on em2: ON 
from
fe80::f44b:2aff:fe77:33d0, OFF from us Sep 27 23:20:21 meenon
rtadvd[8704]: O flag inconsistent on em2: ON from
fe80::f44b:2aff:fe77:33d0, OFF from us Sep 27 23:20:21 meenon
rtadvd[8704]: preferred lifetime for 2603:300f:1603:8000::/64
inconsistent on em2: 345600 from fe80::f44b:2aff:fe77:33d0, 604800 from
us Sep 27 23:20:21 meenon rtadvd[8704]: valid lifetime for
2603:300f:1603:8000::/64 inconsistent on em2: 345600 from
fe80::f44b:2aff:fe77:33d0, 2592000 from us Sep 27 23:20:24 meenon
rtadvd[8704]: M flag inconsistent on em2: ON from
fe80::f44b:2aff:fe77:33d0, OFF from us Sep 27 23:20:24 meenon
rtadvd[8704]: O flag inconsistent on em2: ON from
fe80::f44b:2aff:fe77:33d0, OFF from us Sep 27 23:20:24 meenon
rtadvd[8704]: preferred lifetime for 2603:300f:1603:8000::/64
inconsistent on em2: 345600 from fe80::f44b:2aff:fe77:33d0, 604800 from
us Sep 27 23:20:24 meenon rtadvd[8704]: valid lifetime for
2603:300f:1603:8000::/64 inconsistent on em2: 345600 from
fe80::f44b:2aff:fe77:33d0, 2592000 from us Sep 27 23:20:27 meenon
rtadvd[8704]: M flag inconsistent on em2: ON from
fe80::f44b:2aff:fe77:33d0, OFF from us Sep 27 23:20:27 meenon
rtadvd[8704]: O flag inconsistent on em2: ON from
fe80::f44b:2aff:fe77:33d0, OFF from us Sep 27 23:20:27 meenon
rtadvd[8704]: preferred lifetime for 2603:300f:1603:8000::/64
inconsistent on em2: 345600 from fe80::f44b:2aff:fe77:33d0, 604800 from
us Sep 27 23:20:27 meenon rtadvd[8704]: valid lifetime for
2603:300f:1603:8000::/64 inconsistent on em2: 345600 from
fe80::f44b:2aff:fe77:33d0, 2592000 from us Sep 27 23:20:30 meenon
rtadvd[8704]: M flag inconsistent on em2: ON from
fe80::f44b:2aff:fe77:33d0, OFF from us Sep 27 23:20:30 meenon
rtadvd[8704]: O flag inconsistent on em2: ON from
fe80::f44b:2aff:fe77:33d0, OFF from us Sep 27 23:20:30 meenon
rtadvd[8704]: preferred lifetime for 2603:300f:1603:8000::/64
inconsistent on em2: 345600 from fe80::f44b:2aff:fe77:33d0, 604800 from
us Sep 27 23:20:30 meenon rtadvd[8704]: valid lifetime for
2603:300f:1603:8000::/64 inconsistent on em2: 345600 from
fe80::f44b:2aff:fe77:33d0, 2592000 from us



===
# ifconfig -A
lo0: flags=8049 mtu 32768
index 6 priority 0 llprio 3
groups: lo
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x6
inet 127.0.0.1 netmask 0xff00
em1: flags=