MXUnlimited broken?

[Kal]

For at least the last several days the MXUnlimited channel list is no longer automatically adding new rooms, so any host whos IP changed is apparently stranded.

Is there a fix in the works?
Is this still the only web list?

[White Stripes]

mxunlimited somewhat recently sprang back to life.... the bad part is you really need to give it a day or two to have a new room or changed room show up...

[Kal]

Yeah, I saw the list go from 101 up to 116. Lots of rooms are still stranded tho, Cleos rooms have been up the whole time and arent there.
I'm using her as my canary since I'm still on ouka and its still under DDoS, lol

[Pri]

Josh has been rewriting the website and its database was cleared recently. It is currently rebuilding the list of rooms but to be detected you need to operate your room in online mode until the room shows on the list and then you can go back to running it in offline mode.

A way to manually add rooms to the list will be returning eventually, when that is I can't say as Josh is busy with other things.

[Kal]

If it takes more than a day [some unlisted rooms have been in online mode since the start] is there a more efficacious set of blocklists for using in peerblock?
I've observed that the default lists on peerblock only stop ~40%, at best, of the tidal wave of outgoing udp traffic. I live in a country that has little sense of humor about people cyber-attacking their war department, etc.

[White Stripes]

try https://www.iblocklist.com/list.php?list=ijfqtofzixtwayqovmxn -- this was used as the base for a 'junk' list on winmxgroup.net once .. should work again.. ...in all honesty you can only protect it from spitting data at the wrong addresses... so much randomness its hard to get through...

[Pri]

One thing to be mindful of, if winmxworld cannot ping your room it wont list it. Some users have explained to us that peerblock lists they were using had the winmxunlimited IP's in their blocklist.

To further clarify, the website has two IP's the one that you use to browse the site and a separate one that pings rooms. It is this second IP you need to whitelist, I do not currently know the IP I think it's either hosted by Amazon, Microsoft Azure, Heroku or Digital Ocean.

[Pri]

Blegh I meant to say "if winmxunlimited cannot ping your room" so many winmx addresses I'm getting confused

[GhostShip]

You had my interest there with that typo, had me thinking along the lines of "I turn my back for a few minutes and god knows whats going on", sort of pleased it was all a delusion  *phew* 

[Kal]

Well that could certainly explain why people cant get on the list!
I tried setting Peerblock>Port Settings to allow in/out on my ouka port 5 hrs ago but so far no luck.

What we could really use is a whitelist for peerblock to protect certain important IPs, such as the caches, josh's bot, and the major winmx help rooms.

[Kal]

OK  setting Peerblock>Port Settings to allow in/out on the chat server port did work in the end.

A whitelist would probably still be a good idea to avoid future issues.

[Pri]

Due to the way that the port checks winmxunlimited perform are done from random IP's and locations it would make a whitelist hard. It's hosted from cloud computing platforms so the gateway IP's change all the time and we're not made aware of what they are etc

It's best not to run peerblock with such broad blocks as you just saw it's inaccurate if it is blocking winmxunlimited, we're clearly not a malware organisation etc