NB> That doesn't seem right. Mystic still doesn't allow IPv6 connections so NB> no one is connecting to your BBS or trying to use door games with IPv6. NB> When they connect to your BBS, it's strictly IPv4 right now.
Yep agree.
NB> Then again, you did this with that AYIYA or whatever, where it's NB> straight to your machine running the BBS, correct? With that said, I'm NB> guessing there's absolutely no IPv6 firewall in place?
..and that's the rub, yes I am using the AYIYA client on the same machine Mystic runs. When I kill it the problem disappears. It also seems that even via an internal LAN connection using ipv4 the same issue happens. It's a combo of the AYIYA client and/or virtual driver used by windows to create another virtual LAN connection and netfoss not playing nice.
If I had run AYIYA on another box there would be no issue I'm sure but given the tunnel starts and ends on the box the SixXS software runs onI don't really want to do that as it would add an extra layer of complexity in to the who chain of events.
The fact that the doors seem to think the carrier has been dropped just after netfoss has been called makes me think it's related to the additional virtual lan driver.. really don't know.
First step will be to run an updated version of the fossil that I can see I can updated to using 1.11 but there's a 1.12a out now.
Not overly hopefull though...
Best, Paul
-- Agency BBS, New Zealand | bbs.geek.nz | telnet: agency.bbs.geek.nz:23
