Well, I thought I'll sort a simple DHCPv6 on the LAN side first for testing. Not too hard. Apart from some power glitch at office meant I could not get started for a few hours...
Yeh, right...
I can't see how to send a gateway or even prefix length, so looks like devices have to have router announcement handling and DHCPv6 to work. So why would you have DHCPv6 in the first place. OK never mind.
Finally got it answering on the LAN and go for PPP side.
Of course the DHCPv6 is different coding for the two, and the PPP side is bypassing all the normal routing. Great, except it means doing the wrong things on the wrong processor. Eventually got it sending the IPv6 PPP DHCPv6 replies...
Now to see what the router makes of what I sent :-)
Subscribe to:
Post Comments (Atom)
Fencing
Bit of fun... We usually put up some Christmas lights on the house - some fairy lights on the metal fencing at the front, but a pain as mean...
-
Broadband services are a wonderful innovation of our time, using multiple frequency bands (hence the name) to carry signals over wires (us... -
For many years I used a small stand-alone air-conditioning unit in my study (the box room in the house) and I even had a hole in the wall fo... -
It seems there is something of a standard test string for anti virus ( wikipedia has more on this). The idea is that systems that look fo...
Will you be wanting Beta Testers on this for those of us already on PPPoE? :-)
ReplyDeleteOnce I have the server side working with off-the-shelf routers I will then code the client side.
ReplyDeletePPPoE is not required.
Well, just to confirm, we are sending nice DHCPv6 responses.
ReplyDeleteThe router does a solicit
We do an advertise
The router does a request
We do a reply
All fine.
Then, a second later, the router sends a release for the IA_NA and IA_PD (separately).
And that is it??!?!??
Stupid bloody thing.