Right I noticed that too. If DNS was not working, when I put in your hostname, I would not get back any IP.

So, the problem's not DNS, but maybe something else in regards to pfsense.

I did put together a list of 12 steps that I'm going to run through tomorrow (well..later today, as its 1:30 AM!

) in regards to being directly connected to my modem. Once I do that, I'll report back with my results and then we can go from there.

--Brian

actions · 2012-Dec-10 2:25 am ·

plencnerb

plencnerb

Premium Member

2012-Dec-10 8:12 am

Picture #1
Picture #2
Picture #3

I went ahead and tested without the pfsense box. As you can of course see by the above three pictures, things are looking better already! :)

So, just so we are all on the same page, here are the steps that I did.

First, I set things up to get ready for testing, by doing the following items

• power off the pfsense box
• power off my desktop
• unpluged lan cable between desktop and switch
• reboot cable modem
• plug lan cable from my desktop directly into cable modem
• power up my desktop

Once that was complete, I ran an "ipconfig/all". Those results are below

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.
 
C:\Users\Brian A. Plencner>ipconfig /all
 
Windows IP Configuration
 
   Host Name . . . . . . . . . . . . : BRIAN-DESKTOP
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : hsd1.il.comcast.net.
 
Ethernet adapter Local Area Connection:
 
   Connection-specific DNS Suffix  . : hsd1.il.comcast.net.
   Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
   Physical Address. . . . . . . . . : F4-6D-04-F0-32-43
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   IPv6 Address. . . . . . . . . . . : 2001:558:6033:ad:18b2:dcdb:2418:a1ad(Preferred)
   Lease Obtained. . . . . . . . . . : Monday, December 10, 2012 6:34:58 AM
   Lease Expires . . . . . . . . . . : Friday, December 14, 2012 6:34:57 AM
   Link-local IPv6 Address . . . . . : fe80::34c8:339c:31d4:729b%11(Preferred)
   IPv4 Address. . . . . . . . . . . : 67.184.208.11(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.252.0
   Lease Obtained. . . . . . . . . . : Monday, December 10, 2012 6:34:55 AM
   Lease Expires . . . . . . . . . . : Monday, December 10, 2012 7:31:16 AM
   Default Gateway . . . . . . . . . : fe80::201:5cff:fe3d:4e41%11
                                       67.184.208.1
   DHCP Server . . . . . . . . . . . : 69.252.202.7
   DHCPv6 IAID . . . . . . . . . . . : 250899716
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-18-26-E4-53-F4-6D-04-F0-32-43
   DNS Servers . . . . . . . . . . . : 2001:558:feed::1
                                       2001:558:feed::2
                                       75.75.75.75
                                       75.75.76.76
   NetBIOS over Tcpip. . . . . . . . : Enabled
 
Tunnel adapter isatap.hsd1.il.comcast.net.:
 
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : hsd1.il.comcast.net.
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
 
Tunnel adapter Teredo Tunneling Pseudo-Interface:
 
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv6 Address. . . . . . . . . . . : 2001:0:9d38:953c:4b:3355:bc47:2ff4(Preferred)
   Link-local IPv6 Address . . . . . : fe80::4b:3355:bc47:2ff4%13(Preferred)
   Default Gateway . . . . . . . . . :
   NetBIOS over Tcpip. . . . . . . . : Disabled
 
C:\Users\Brian A. Plencner>

Next, I ran the following command: "netsh int ipv6 show addr"

 
C:\Users\Brian A. Plencner>netsh int ipv6 show addr
 
Interface 1: Loopback Pseudo-Interface 1
 
Addr Type  DAD State   Valid Life Pref. Life Address
---------  ----------- ---------- ---------- ------------------------
Other      Preferred     infinite   infinite ::1
 
Interface 12: isatap.hsd1.il.comcast.net.
 
Addr Type  DAD State   Valid Life Pref. Life Address
---------  ----------- ---------- ---------- ------------------------
Other      Deprecated    infinite   infinite fe80::200:5efe:67.184.208.11%12
 
Interface 13: Teredo Tunneling Pseudo-Interface
 
Addr Type  DAD State   Valid Life Pref. Life Address
---------  ----------- ---------- ---------- ------------------------
Public     Preferred     infinite   infinite 2001:0:9d38:953c:4b:3355:bc47:2ff4
Other      Preferred     infinite   infinite fe80::4b:3355:bc47:2ff4%13
 
Interface 11: Local Area Connection
 
Addr Type  DAD State   Valid Life Pref. Life Address
---------  ----------- ---------- ---------- ------------------------
Dhcp       Preferred     3d23h59m   3d23h59m 2001:558:6033:ad:18b2:dcdb:2418:a1ad
Other      Preferred     infinite   infinite fe80::34c8:339c:31d4:729b%11
 
C:\Users\Brian A. Plencner>

So far, things were looking good.

Then, using Waterfox (which, is the browser I have used all along), I went to the following three web pages

•»test-ipv6.com/
•»test-ipv6.comcast.net/
•»ipv6.speedtest.comcast.net/

The results of these are shown above as Picture #1, #2, and #3, respectability.

As a final verification, I ran some more tests from the command prompt.

nslookup commands

 
C:\Users\Brian A. Plencner>nslookup www.comcast.net
Server:  cdns01.comcast.net
Address:  2001:558:feed::1
 
Non-authoritative answer:
Name:    a1526.dscg.akamai.net
Addresses:  2001:559:0:5d::1743:3d3b
          2001:559:0:5d::1743:3d39
          96.17.77.66
          96.17.77.42
Aliases:  www.comcast.net
          www.comcast.net.edgesuite.net
 
C:\Users\Brian A. Plencner>nslookup -type=AAAA www.comcast.net
Server:  cdns01.comcast.net
Address:  2001:558:feed::1
 
Non-authoritative answer:
Name:    a1526.dscg.akamai.net
Addresses:  2001:559:0:5d::1743:3d39
          2001:559:0:5d::1743:3d3b
Aliases:  www.comcast.net
          www.comcast.net.edgesuite.net
 
C:\Users\Brian A. Plencner>nslookup www.google.com
Server:  cdns01.comcast.net
Address:  2001:558:feed::1
 
Non-authoritative answer:
Name:    www.google.com
Addresses:  2607:f8b0:400f:801::1011
          74.125.225.208
          74.125.225.211
          74.125.225.209
          74.125.225.210
          74.125.225.212
 
C:\Users\Brian A. Plencner>nslookup -type=AAAA www.google.com
Server:  cdns01.comcast.net
Address:  2001:558:feed::1
 
Non-authoritative answer:
Name:    www.google.com
Address:  2607:f8b0:400f:801::1012
 
C:\Users\Brian A. Plencner>

ping commands

 
C:\Users\Brian A. Plencner>ping ipv6.dcsenterprises.net
 
Pinging ipv6-dcs-srv.dyndns-ip.com [2601:5:c80:91:e291:f5ff:fe95:beac] with 32 bytes of data:
Reply from 2601:5:c80:91:e291:f5ff:fe95:beac: time=41ms
Reply from 2601:5:c80:91:e291:f5ff:fe95:beac: time=37ms
Reply from 2601:5:c80:91:e291:f5ff:fe95:beac: time=35ms
Reply from 2601:5:c80:91:e291:f5ff:fe95:beac: time=36ms
 
Ping statistics for 2601:5:c80:91:e291:f5ff:fe95:beac:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 35ms, Maximum = 41ms, Average = 37ms
 
C:\Users\Brian A. Plencner>ping ipv6.dcs-net.net
 
Pinging ipv6-webhost.dyndns-ip.com [2601:5:c80:91:e291:f5ff:fe95:a879] with 32 bytes of data:
Reply from 2601:5:c80:91:e291:f5ff:fe95:a879: time=47ms
Reply from 2601:5:c80:91:e291:f5ff:fe95:a879: time=43ms
Reply from 2601:5:c80:91:e291:f5ff:fe95:a879: time=45ms
Reply from 2601:5:c80:91:e291:f5ff:fe95:a879: time=44ms
 
Ping statistics for 2601:5:c80:91:e291:f5ff:fe95:a879:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 43ms, Maximum = 47ms, Average = 44ms
 
C:\Users\Brian A. Plencner>ping 2601:5:c80:91:e291:f5ff:fe95:beac
 
Pinging 2601:5:c80:91:e291:f5ff:fe95:beac with 32 bytes of data:
Reply from 2601:5:c80:91:e291:f5ff:fe95:beac: time=34ms
Reply from 2601:5:c80:91:e291:f5ff:fe95:beac: time=35ms
Reply from 2601:5:c80:91:e291:f5ff:fe95:beac: time=36ms
Reply from 2601:5:c80:91:e291:f5ff:fe95:beac: time=36ms
 
Ping statistics for 2601:5:c80:91:e291:f5ff:fe95:beac:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 34ms, Maximum = 36ms, Average = 35ms
 
C:\Users\Brian A. Plencner>ping 2601:5:c80:91:e291:f5ff:fe95:a879
 
Pinging 2601:5:c80:91:e291:f5ff:fe95:a879 with 32 bytes of data:
Reply from 2601:5:c80:91:e291:f5ff:fe95:a879: time=43ms
Reply from 2601:5:c80:91:e291:f5ff:fe95:a879: time=42ms
Reply from 2601:5:c80:91:e291:f5ff:fe95:a879: time=42ms
Reply from 2601:5:c80:91:e291:f5ff:fe95:a879: time=43ms
 
Ping statistics for 2601:5:c80:91:e291:f5ff:fe95:a879:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 42ms, Maximum = 43ms, Average = 42ms
 
C:\Users\Brian A. Plencner>

And then finally, a few trace commands. I did mix both IPv4 and IPv6 sites in this, just to be complete.

 
C:\Users\Brian A. Plencner>tracert 2601:5:c80:91:e291:f5ff:fe95:beac
 
Tracing route to 2601:5:c80:91:e291:f5ff:fe95:beac over a maximum of 30 hops
 
  1    37 ms    30 ms    29 ms  2001:558:6033:ad::1
  2     9 ms     8 ms     9 ms  te-9-1-ur04.algonquin.il.chicago.comcast.net [2001:558:322:26f::1]
  3    15 ms    15 ms    15 ms  te-0-3-0-0-ar01.area4.il.chicago.comcast.net [2001:558:300:1e::1]
  4    19 ms    23 ms    23 ms  he-3-5-0-0-cr01.350ecermak.il.ibone.comcast.net [2001:558:0:f7fb::1]
  5    25 ms    25 ms    26 ms  so-7-1-0-0-ar03.nashville.tn.nash.comcast.net [2001:558:0:f7f4::2]
  6    27 ms    26 ms    28 ms  xe-0-1-0-0-sur01.murfreesboro.tn.nash.comcast.net [2001:558:160:57::2]
  7    39 ms    34 ms    27 ms  2001:558:162:32::2
  8    36 ms    35 ms    37 ms  2001:558:6016:19:39d6:46d1:4004:e738
  9    37 ms    35 ms    38 ms  2601:5:c80:91:e291:f5ff:fe95:beac
 
Trace complete.
 
C:\Users\Brian A. Plencner>tracert 2601:5:c80:91:e291:f5ff:fe95:a879
 
Tracing route to 2601:5:c80:91:e291:f5ff:fe95:a879 over a maximum of 30 hops
 
  1    27 ms    29 ms    24 ms  2001:558:6033:ad::1
  2    24 ms     9 ms     9 ms  te-9-1-ur04.algonquin.il.chicago.comcast.net [2001:558:322:26f::1]
  3    16 ms    15 ms    15 ms  te-0-3-0-2-ar01.area4.il.chicago.comcast.net [2001:558:300:283::1]
  4    25 ms    23 ms    23 ms  he-3-11-0-0-cr01.350ecermak.il.ibone.comcast.net [2001:558:0:f683::1]
  5    93 ms    25 ms    27 ms  so-0-1-0-0-ar03.nashville.tn.nash.comcast.net [2001:558:0:f692::2]
  6    27 ms    28 ms    27 ms  2001:558:160:94::2
  7    43 ms    36 ms    41 ms  2001:558:162:32::2
  8    33 ms    37 ms    36 ms  2001:558:6016:19:39d6:46d1:4004:e738
  9    44 ms    44 ms    41 ms  2601:5:c80:91:e291:f5ff:fe95:a879
 
Trace complete.
 
C:\Users\Brian A. Plencner>tracert www.google.com
 
Tracing route to www.google.com [2607:f8b0:400f:801::1013]
over a maximum of 30 hops:
 
  1    27 ms    29 ms    29 ms  2001:558:6033:ad::1
  2     9 ms     9 ms    10 ms  te-9-1-ur04.algonquin.il.chicago.comcast.net [2001:558:322:26f::1]
  3    16 ms    16 ms    14 ms  te-0-3-0-3-ar01.area4.il.chicago.comcast.net [2001:558:300:286::1]
  4    22 ms    23 ms    17 ms  he-3-7-0-0-cr01.350ecermak.il.ibone.comcast.net [2001:558:0:f68d::1]
  5    14 ms    13 ms    13 ms  pos-1-2-0-0-pe01.350ecermak.il.ibone.comcast.net [2001:558:0:f593::2]
  6    59 ms    13 ms    12 ms  2001:559::44a
  7    13 ms    13 ms    13 ms  2001:4860::1:0:92e
  8    14 ms    13 ms    13 ms  2001:4860::8:0:2fe9
  9    35 ms    37 ms    36 ms  2001:4860::8:0:281d
 10    36 ms    33 ms    33 ms  2001:4860::8:0:3426
 11    34 ms    34 ms    43 ms  2001:4860::1:0:7a4
 12    35 ms    38 ms    36 ms  2001:4860:0:1::593
 13    34 ms    35 ms    35 ms  den03s06-in-x13.1e100.net [2607:f8b0:400f:801::1013]
 
Trace complete.
 
C:\Users\Brian A. Plencner>tracert www.dslreports.com
 
Tracing route to www.dslreports.com [209.123.109.175]
over a maximum of 30 hops:
 
  1    31 ms    22 ms    27 ms  67.184.208.1
  2    29 ms    15 ms    16 ms  te-9-1-ur04.algonquin.il.chicago.comcast.net [68.87.229.189]
  3    15 ms    15 ms    15 ms  te-0-3-0-2-ar01.area4.il.chicago.comcast.net [68.86.189.229]
  4    14 ms    23 ms    11 ms  he-3-8-0-0-cr01.350ecermak.il.ibone.comcast.net [68.86.90.49]
  5    40 ms    35 ms    35 ms  he-4-6-0-0-cr01.newyork.ny.ibone.comcast.net [68.86.88.153]
  6    41 ms    33 ms    40 ms  173.167.58.26
  7    34 ms    33 ms    32 ms  0.e1-4.tbr1.oct.nac.net [209.123.10.122]
  8    35 ms    34 ms    32 ms  vlan804.esd1.oct.nac.net [209.123.10.2]
  9    34 ms    32 ms    32 ms  www.dslreports.com [209.123.109.175]
 
Trace complete.
 
C:\Users\Brian A. Plencner>

So, my final observation here is that IPv6 is working (as best as I can tell) exactly the way it should be when I am directly connected to my cable modem. This then points me to the fact that the issue is with pfsense.

As far as I know, the only changes that I have made from a "default" install were the ones told to me in this thread. However, I have no problem re-installing pfsense just to make sure something strange did not get set or configured by mistake.

NetDog

and NetFixer

: How do things look from your end? I take it everything looks as it should?

whfsdude

: Any ideas or suggestions of things I should look at or verify as far as pfsense goes? Do you think I should re-install pfsense and start over?

--Brian

actions · 2012-Dec-10 8:12 am ·

graysonf
MVM
join:1999-07-16
Fort Lauderdale, FL

graysonf

MVM

2012-Dec-10 8:49 am

Completely reinstalling pfsense is unnecessary if you want to attempt starting over with it. Just reset it to the default configuration.

If you haven't already done so, you should post how you have configured pfsense for Comcast native IPv6. The pfsense forum is also a good source of information.

I don't run pfsense here myself, it offers way more than I need. I do run m0n0wall, which was forked years ago to start the pfsense project.

If you want to try that instead of pfsense, you'll find it much simpler to configure and use. But if you can verify that Comcast IPv6 works with m0n0wall, then it will work with the latest pfsense 2.1 snapshots.

actions · 2012-Dec-10 8:49 am ·

ropeguru
Premium Member
join:2001-01-25
Mechanicsville, VA

ropeguru to NetFixer

Premium Member

2012-Dec-10 8:51 am

to NetFixer

Maybe starting a new thread is the best idea and then maybe adding an entry here pointing to each new thread and giving a brief explanation of the issue?

actions · 2012-Dec-10 8:51 am ·

plencnerb
Premium Member
join:2000-09-25
53403-1242

plencnerb to NetDog

Premium Member

2012-Dec-10 7:26 pm

to NetDog

I wanted to post here to inform everyone that I have started a new thread to troubleshoot the issues I'm having with pfsense.

Thanks to everyone who posted in this thread to get me where I am so far.

I know I will figure it out!

--Brian

actions · 2012-Dec-10 7:26 pm ·