Category Archives: Uncategorized

Native IPV6 with TWC – part 2

I kept at it, and got it to work without any static configuration (but still have to use NAT)

I still need the NAT rule, and what’s strange is that the workstation gets IP address from /56 prefix (which is configured as the WAN prefix on the modem):

my pfSense receives this IP via DHCPV6:

IA_NA address: 2605:e000:855b:de00::xxxxxxxx pltime=3600 vltime=3600
update a prefix 2605:e000:855b:def0::/60 pltime=3600, vltime=3600

The prefix pfSense gets is OUTSIDE of the DHCPv6 range configured on the LAN side of the modem (2605:e000:855b:de00::/64)

Native IPV6 via pfSense on Charter/Spectrum/TimeWarner

I’ve had cable Internet from Spectrum for about 3 years now, and about a year ago I started using pfSense as additional firewall (it’s easier for me with many VPN’s that I use, since I can terminate IPSec and OpenVPN on the pfSense).

Thing is, the IPV6 never worked for me via pfSense for some reason.

Time has come to solve it, and after 2 evenings, success (and I’m 90% satisfied, but that has to do for now).

Some facts:

  • Arris modem from Spectrum DOES give proper IPV6 via DHCPv6 to its direct clients
  • My pfSense on the WAN interface, when set up with either “None” or “/56” as IPV6 prefix DOES get IPV6 address from the modem.
  • Following various guides, it should be as simple as setting my LAN interface on pfSense to “track” the WAN interface, but to no avail, my clients behind pfSense cannot receive IP address, and I’ve tried all options: default settings, DHCPv6 Relay, DHCPV6 Server and RA with various settings.

Arris modem gets its “WAN” ip address with prefix of /56 and has prefix delegation set to /64, so that should leave me with plenty of /64 subnets to give away.

The catch – pfSense on its WAN interface (DHCPv6) gets its prefix as /128 – so that leaves me with nothing to hand over further.
I tried various settings, checking the prefix hints etc, with no luck.

Then time came for Static IPV6, so I’ve set my WAN address on pfSense to some address within the range (it’s perfectly fine to set it to whatever you’d get via DHCPV6) but with smaller subnet prefix, /96 in my case , then set LAN address to another IP address (also with /96 prefix, but in a non-colliding subnet to the WAN address, I’ve simply set the 5th hextet/group to ffff with my WAN’s hextet starting with c… ).

2 more things I needed to set, was to enable DHCPv6 server on pfSense, with range to having last 2 hextets empty (::), that’s enough IP’s for my home, then in the the Router Advertisements, set Router Mode to Assisted.

Second thing (which is why I’m not 100% happy) was to enable IPV6 NAT, since I’m effectively bypassing any prefix delegation etc. That was a simple IPV6 NAT rule and voila, we have connectivity.

Schrödinger’s cat – that is – How we got out of our apartment lease – at no cost.

…And we moved… Kind of…

After nearly 10 years in Japan, we decided it was time for a new challenge and moved to Los Angeles, where I already had my new job lined up.

The plan was pretty simple – arrive on July 20th, over the next 3-4 weeks settle down, buy a car, rent an apartment and get ready for my first day at work coming on August 15th.

After intensive apartment search we found one that was:

  • In a good school district (critical, even though LA has one big districts, schools give priority to kids from the nearby “attendance zone”)
  • Affordable (I would rather say expensive by Japanese standards for what is was, but here it was a *steal*)
  • Big enough
  • Walkable to nearby shops (can’t get used to driving 20 minutes or more for groceries)

We signed our lease on Friday the 29th and thought that was all… not…

The management gave us an EPA brochure educating about lead poisoning, risk and prevention (which is mandatory for buildings built before 1978), and also handed us a paper declaring that they do not know whether there is any lead risk in the building – “there may or may not be any”.

We did sign the lease thinking it can’t be bad, and then later inspected the unit again for cleanliness and other issues.

We had several that we requested be solved – mold spots on the shower silicone seals, cracked tiles, etc – nothing major but we expect the unit to be clean for move-in.

Then we spent a long time reading about lead and associated risks, and found that there were some areas in the apartment that could be problematic – paint rubbing on door hinges, cracked paint below the sink, chipped on the balcony railing etc.

We contacted the management asking to have the unit tested for lead in the paint.

They came back on Monday – said they won’t do that, and because they won’t be able to fulfil our demanding needs, they offered to void our lease and give us the deposit and rent back. (we haven’t moved into the unit yet)

Don’t get me wrong – our intention wasn’t to cancel the lease, we just wanted to ensure the unit was safe for us, we really did want to keep our lease and move in.

I’ve been thinking about management’s attitude, and interestingly it reminds me of Schrödinger’s cat experiment…

They DON’T WANT TO KNOW whether there is any lead in the building – if there was, by law they would have to disclose it to all the tenants and remedy the problems using very expensive lead certified contractors, and from that time onward any repairs would have to be conducted in lead-safe way.

Unless the building is tested for lead, it’s assumed to be safe, but once lead is proven to exist – that puts the owner into very expensive spiral, crazy huh?

California really needs a law reform, many other states enforce the landlord to ensure the unit is lead-safe when children below age of 6 live there.

In CA, the ONLY way to force the landlord to test the unit and resolve problems is to WAIT UNTIL SOMEONE GETS LEAD POISONING, get tested and use that as a proof… We were not willing to that…

FreePCB build – BusPirate

Finally got the PCB’s and built both of them, it was a great exercise in soldering, and eye test too, especially the SMT 0603 components.

It went pretty smoothly, one of the devices did not respond (but ftdi was visible over USB), quick test with shorted rx/tx demonstrated that ftdi was not at fault,

then quick trace verification showed that the rx pin on the PIC was lifted a tad (nearly not visible) and didn’t have contact, pushed it down, soldered, and voila – full success.

IMG_4203-copy1.jpg

Want a FreePCB ? – go to dangerousprototypes.com