dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
2
share rss forum feed


graysonf
Premium,MVM
join:1999-07-16
Fort Lauderdale, FL
kudos:2
reply to JoelC707

Re: [IPv6] Seeing two different LAN side ranges

You can save your current configuration file at any time and restore it later into your next install. No need to recreate anything from scratch.

JoelC707
Premium
join:2002-07-09
Lanett, AL
kudos:5
Yeah but I'm worried there might be something hidden that is messing this up and restoring the config would restore the fault too. I guess I don't really see what that might be since everything else says it should be working but I'm stumped at this point.


graysonf
Premium,MVM
join:1999-07-16
Fort Lauderdale, FL
kudos:2
Maybe you should consider a simpler product just to see if it will configure IPv6 correctly for you. If it won't, then the problem lies on Comcast's side and you are spinning your wheels.

I run m0n0wall here, the product that was forked to form pfsense.

It might take you ten minutes to try it. I can paste screenshots of the configuration for you if you want them.

Tell me more about what type of pfsense install you are running and I'll point you to the right m0n0wall image.

JoelC707
Premium
join:2002-07-09
Lanett, AL
kudos:5
Good point. This could all be some bug in pfSense that has come up. The IPv6 forum at pfSense.com is filled with Comcast IPv6 questions I haven't even connected it direct to my desktop to test it direct (though considering I can ping from the firewall I suspect it will work connected direct to my desktop).

I've considered Untangle as well and have seen m0n0wall though I've never used either. I have two WAN circuits, one being PPPoE DSL, the other Comcast. It's being used for just a basic internet router/firewall. I have used HAVP (inline virus scanner) and played around with snort but do not use either currently. Nothing special really


graysonf
Premium,MVM
join:1999-07-16
Fort Lauderdale, FL
kudos:2
m0n0wall doesn't handle multi-WAN. But it still would be worth trying on your Comcast circuit.

I suggest the Live-CD with a floppy or USB stick to store the configuration. Nothing to install, just try it and see what happens.


plencnerb
Premium
join:2000-09-25
Carpentersville, IL
kudos:3
reply to JoelC707
said by JoelC707:

I haven't even connected it direct to my desktop to test it direct (though considering I can ping from the firewall I suspect it will work connected direct to my desktop).

I would highly suggest doing that. It should only take a few minutes to pull your pfsense box out of the mix, and plug a device (desktop or laptop) directly into your modem and verify that IPv6 is fully working in your area.

That will help rule out any issues on Comcast's side.

For me, that was the first thing I did. Once I knew I was getting a real IPv6 IP from Comcast, and could doing pings, trace routes, and the IPv6 test sites came back with a 10/10 score, I knew it was time to configure pfsense.

--Brian
--
============================
--Brian Plencner

E-Mail: CoasterBrian72Cancer@gmail.com
Note: Kill Cancer to Reply via e-mail

JoelC707
Premium
join:2002-07-09
Lanett, AL
kudos:5
reply to graysonf
It's certainly worth a try, just with the Comcast circuit but yeah if no support for multi-wan then that's a no-go for me as a permanent solution. That may be why I went with pfSense instead of m0n0 at first because I've been using pfSense since the 1.2.1 days lol.

JoelC707
Premium
join:2002-07-09
Lanett, AL
kudos:5
reply to plencnerb
I confirmed with NetDog See Profile that my CMTS was IPv6 enabled before beginning this adventure but alas what should work what that actually happens are sometimes two entirely different things LOL. Regardless, I should try that and see what happens.

Though I did note in the thread you pointed me to, your IPv6 IP shown was a 2001: address. If the PD provided 2601: address is the source of the issue, I may very well be able to connect the modem direct to my computer and get IPv6 connectivity and then turn around and still not get it to work with pfSense.