In my blacklist file, if it autobans someone, it puts ipv6 addresses. Can you make it use ipv4 instead?


--
yrNews Usenet Reader for iOS
http://appstore.com/yrNewsUsenetReader

--- Mystic BBS/NNTP v1.12 A39 2018/04/21 (Linux/64)
* Origin: The ByteXchange BBS | bbs.thebytexchange.com (21:1/107)

On 11/10/18, nugax said the following...

In my blacklist file, if it autobans someone, it puts ipv6 addresses.
Can you make it use ipv4 instead?

I think it bans people based on the IP address they're using. So, probably
just disable IPv6 in your config, I'd think.

--- Mystic BBS v1.12 A39 2018/04/21 (Raspberry Pi/32)
* Origin: throwbackbbs.com -\- meriden, ct -\- (21:1/114)

In my blacklist file, if it autobans someone, it puts ipv6 addresses.
Can you make it use ipv4 instead?

Well, I can see two things, you can disable IPV6 altogether in your OS, but
in some occasions, I've seen it was not enough.

You must also tell Mystic MIS to listen only on IPV4 instead of the default IPV4 + IPV6.

I had the exact observation, but since IPV6 is not routed on my WAN, only LAN connected machines were using IPV6. You can validate by using the pipe code
UX or UY (don't remember which is which) to see what Mystic actually sees.

I might put you in the right direction.

Cheers,

ß Þ
úúúÄÄÄÄÄúÄÄúúÄÄÄÄúÄú Ý ßúÄúÄÄÄúÄÄÄÄÄÄúúÄÄÄÄÄúÄÄÄÄúÄÄÄÄÄÄúúÄÄÄÄÄÄÄÄÄúÄÄÄÄúúú
Dave aka Stackfault ß Ýß bbs.bottomlessabyss.net (telnet/2023ússh/2222)
Bottomless Abyss BBS ÜßÞ 21:1/172@fsxNet þ 1:249/317@FidoNet
-úúú --- - - --- -- ú-úú ú úúú úúú ú- -úúú -ú-- úúú úúú -úúú -úúú úúú

--- Mystic BBS v1.12 A39 2018/04/21 (Linux/64)
* Origin: The Bottomless Abyss BBS (21:1/172)

On 11-10-18 06:47, nugax wrote to All <=-

@TZ: 4168
In my blacklist file, if it autobans someone, it puts ipv6 addresses.
Can you make it use ipv4 instead?

It's actually IPv6 coded IPv4 addresses, in otherwords, they are IPv4 addresses, but in IPv6 syntax. There is a special IPv6 prefix that represents IPv4 space. This is possible, because all of IPv4 can fit in a single /96 of IPv6 space.


... Boy, I'm tellin you fer yer own good, I studied them things.
=== MultiMail/Win v0.51
--- SBBSecho 3.03-Linux
* Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (21:1/109)

On 11-10-18 10:31, StackFault wrote to nugax <=-

Well, I can see two things, you can disable IPV6 altogether in your OS, but in some occasions, I've seen it was not enough.

You must also tell Mystic MIS to listen only on IPV4 instead of the default IPV4 + IPV6.

I actually have mine set to listen IPv6 only. Linux does the rest. :)

I had the exact observation, but since IPV6 is not routed on my WAN,
only LAN connected machines were using IPV6. You can validate by using
the pipe code UX or UY (don't remember which is which) to see what
Mystic actually sees.

I run full native IPv6 here, so turning IPv6 off is not an acceptable option. I can live with the block list being in IPv6 notation for IPv4 addresses. If I wanted to, I could write a program to parse the block list to display IPv4 addresses in the normal format, but I don't see a need. :)


... Because that's what the holidays are all about: SUFFERING.
=== MultiMail/Win v0.51
--- SBBSecho 3.03-Linux
* Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (21:1/109)

You must also tell Mystic MIS to listen only on IPV4 instead of the default IPV4 + IPV6.

I actually have mine set to listen IPv6 only. Linux does the rest. :)

Yes, if IPV6 is available where you are, this is definitely the way to go.

I had the exact observation, but since IPV6 is not routed on my WAN, only LAN connected machines were using IPV6. You can validate by usin the pipe code UX or UY (don't remember which is which) to see what Mystic actually sees.

I run full native IPv6 here, so turning IPv6 off is not an acceptable option. I can live with the block list being in IPv6 notation for IPv4 addresses. If I wanted to, I could write a program to parse the block list to display IPv4 addresses in the normal format, but I don't see a need. :)

IPV6 adoption is much better in Europe. Here in Canada, unless you are
located in a datacenter, you pretty much still get IPV4 only.

I use IPV6 on some segment of my lab network but I still have to gate it to IPV4 for outbound.

Regards,

ß Þ
úúúÄÄÄÄÄúÄÄúúÄÄÄÄúÄú Ý ßúÄúÄÄÄúÄÄÄÄÄÄúúÄÄÄÄÄúÄÄÄÄúÄÄÄÄÄÄúúÄÄÄÄÄÄÄÄÄúÄÄÄÄúúú
Dave aka Stackfault ß Ýß bbs.bottomlessabyss.net (telnet/2023ússh/2222)
Bottomless Abyss BBS ÜßÞ 21:1/172@fsxnet þ 1:249/317@fidonet
-úúú --- - - --- -- ú-úú ú úúú úúú ú- -úúú -ú-- úúú úúú -úúú -úúú úúú

--- Mystic BBS v1.12 A39 2018/04/21 (Linux/64)
* Origin: The Bottomless Abyss BBS (21:1/172)

On 11-10-18 21:43, StackFault wrote to Vk3jed <=-

Yes, if IPV6 is available where you are, this is definitely the way to
go.

I've been IPv6 native for over 7 years. :)

IPV6 adoption is much better in Europe. Here in Canada, unless you are located in a datacenter, you pretty much still get IPV4 only.

Australia lags behind too, but there is at least one IP that provides IPv6 as standard. Gues which ISP I use! :D

I use IPV6 on some segment of my lab network but I still have to gate
it to IPV4 for outbound.

I'd be interested to see exactly how you did that. Might be something to experiment with on an IPv6 only subnet. I do have a /56 to play with. :)


... A self-starting oscillator won't.
=== MultiMail/Win v0.51
--- SBBSecho 3.03-Linux
* Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (21:1/109)