I'm using a WRT54G with Tomato, and today upgraded from 1.23 to 1.25. Afterward, my PAP2T absolutely would not re-register, no matter how many times I reset or power-cycled it.

I dug around through all the settings in Tomato and couldn't find anything weird, so I finally dusted off my old 10Base-T hub and started capturing traffic. From behind the router, everything looked fine -- the PAP2T was sending out its registration requests, but never getting a response. I popped a USB ethernet adapter into my main PC and moved the hub around between the FiOS ONT and the router. Then the problem was clear -- Tomato was not NATting the PAP2T's requests. They were going out with the non-routable LAN source address, and of course, no replies were coming in.

I finally unplugged the PAP2T from power to shut it up, purged the idle forwarded connections and deleted the PAP2T's lease in Tomato, then plugged the PAP2T back in -- success!

I did not try resetting the Tomato router. I remember when I first installed 1.23, the PAP2T could not register until the next morning sometime, and I never found out why. I think there's something funny about Tomato's state tracking if it boots up after the PAP2T has already been registered.

Anybody else have similar experiences?