On Fri, 10 Nov 2017, Rich Shepard wrote:
I've no idea what caused this but need to learn ASAP how to get it back to using ipv4 addressing.
Fixed the issue by stopping/starting rc.inet1, the file that configures network ports. Lesson to me: apparently restarting is not as complete as stopping/starting. I've encountered this with other services, but not before with this one. Please return to your regularly scheduled Friday activities. Carpe weekend, Rich _______________________________________________ PLUG mailing list PLUG@pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
