Ticket #14 (closed task: fixed)

Opened 3 years ago

Last modified 3 years ago

More IP's strickly for testing

Reported by: jason Owned by: scottmc
Priority: major Milestone:
Component: SpamZilla Version:
Keywords: Cc:

Description

The ip's I was going to use have run into some problems with ARIN, so I had some more ip's setup for testing purposes. We can use this to test out the system with until more offical ones are resolved.

NETWORK: 204.15.164.96 / 27

GATEWAY: 204.15.164.97

NETMASK: 255.255.255.224

USABLE: 204.15.164.98-126

BROADCAST: 204.15.164.127

currently only 204.15.164.[2-12] are being used.

Change History

Changed 3 years ago by scottmc

  • owner changed from somebody to scottmc

Changed 3 years ago by scottmc

  • status changed from new to assigned

Changed 3 years ago by scottmc

I can't even tell if these are configured on the machines, I cannot ssh into them at this time. Awaiting action from Jason.

The application is properly distributing campaign processing, I will gladly set up all of the servers to link and use all of these IPs as soon as possible.

Changed 3 years ago by jason

Just break up the IPs in block of about 25, that should be good for testing. I would imagine a centeral interface for setting up ips, for there are going to be alot of them and we would want to break them up by company.

Changed 3 years ago by scottmc

  • status changed from assigned to closed
  • resolution set to fixed

I have some components written for an older application I wrote designed to administrate FreeBSD clusters that might be able to be slapped into this thing later, but for the time being I've simply split up the 28 ips in this block over machines 2, 3, 4, and 5.

I've also written a simple relay controller for the node running on the database system that publishes requests without handling them, so it can be used as a "controller" node over the mailing nodes set up on 2, 3, 4 and 5.

Note: See TracTickets for help on using tickets.