Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Allow customizing the address of source connections #183

Open
AlexDaniel opened this issue Jul 21, 2017 · 2 comments
Open

Allow customizing the address of source connections #183

AlexDaniel opened this issue Jul 21, 2017 · 2 comments
Labels
blocked ☹ Underlying issue is outside this repo, a ticket was filed whateverable Issues affecting the bot framework (and therefore all of the bots)

Comments

@AlexDaniel
Copy link
Member

Freenode does not allow more than 10 connections from the same ip, and we've reached this limit already.

The server we use right now has more than 1 IP available, so we only have to find a way to choose the ip when connecting.

Blocked by RT #131766.
@AlexDaniel AlexDaniel added blocked ☹ Underlying issue is outside this repo, a ticket was filed whateverable Issues affecting the bot framework (and therefore all of the bots) labels Jul 21, 2017
@AlexDaniel
Copy link
Member Author

OK, now we are at 11 bots, statisfiable is therefore offline :(

@AlexDaniel
Copy link
Member Author

Heh! Skarsnik++ had this wonderful idea that you can switch between ipv4 and ipv6 by connecting to ipv4/ipv6 addresses of freenode directly. In other words:

:host( (‘chat.freenode.net’, ‘185.30.166.38’).pick )

This way we can get 10 for each, so the limit is effectively 20 bots.

AlexDaniel added a commit that referenced this issue Aug 27, 2017
@AlexDaniel
Cheat by connecting to IPv4 address
93aa973 
This way we can have 10 bots on IPv4 address and 10 bots on IPv6
address, without having to wait for RT #131766.

See issue #183.
AlexDaniel added a commit that referenced this issue Sep 29, 2017
@AlexDaniel
I ♥ systemd
845db2e 
This commit resolves many long-standing problems:

* Issue #25 (RESTRICTED setting) is resolved. Bots are still not fully
  secure, but now they are more secure that they've even been given
  that RESTRICTED setting is entirely useless
* Issue #52 (predictable filenames) is no longer blocked
* Issue #55 (sandboxable) is probably no longer relevant
* Issue #118 (ramfs for /tmp) now needs an update
* Issue #144 (bots leaving stuff behind) is resolved because every bot
  has its own /tmp
* Issue #183 (source ip issue) possibly has a systemd solution for it
* Issue #197 is tackled a little bit also because now there's a memory
  limit for every bot (3G for now, we can probably make it smaller)
* Issue #238 (e.g. forkbombs) is basically resolved, but needs a bit more work
* Moreover, there's now a watchdog that makes sure that bots come back
  online if something bad happens

Not that all of this wasn't possible without systemd, it's just that
it is so much easier now. Feel free to hate me as much as you want.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
blocked ☹ Underlying issue is outside this repo, a ticket was filed whateverable Issues affecting the bot framework (and therefore all of the bots)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@AlexDaniel