11–20 of 24 posts
8 ip addresses per attendee? That's a little high. It's incredibly hard to make DHCP work at that scale, and allocating 8 per attendee is wrong. Try 4 - if you're being nice - or 2 if you're constrained. (2 = one smartphone/tablet and a computer).
8 ip addresses per attendee? That's a little high. It's incredibly hard to make DHCP work at that scale, and allocating 8 per attendee is wrong. Try 4 - if you're being nice - or 2 if you're constrained. (2 = one smartphone/tablet and a computer).
one of the reasons to go high on IP addresses is because many devices don't release their leases properly, which can cause all sorts of havoc.
8 ip addresses per attendee? That's a little high. It's incredibly hard to make DHCP work at that scale, and allocating 8 per attendee is wrong. Try 4 - if you're being nice - or 2 if you're constrained. (2 = one smartphone/tablet and a computer).
one of the reasons to go high on IP addresses is because many devices don't release their leases properly, which can cause all sorts of havoc.
Earlier quoted context omitted.
one of the reasons to go high on IP addresses is because many devices don't release their leases properly, which can cause all sorts of havoc.
That's true. but having dhcp capacity for more than 255 IPs is hard (or, expensive). for a 20-30 person hackday, the organizer shouldn't be worrying about overkill network provision, and should spend that time/money worrying about good food, or something else. (imho)
Earlier quoted context omitted.
one of the reasons to go high on IP addresses is because many devices don't release their leases properly, which can cause all sorts of havoc.
20/30 people on a regular router that has an IP range of 255 IPs will quite often fall over, I've seen it happen more than once.
Earlier quoted context omitted.
one of the reasons to go high on IP addresses is because many devices don't release their leases properly, which can cause all sorts of havoc.
20/30 people on a regular router that has an IP range of 255 IPs will quite often fall over, I've seen it happen more than once.
This is awesome. Thank you for putting it together. As I am in a group scheduling a Hackathon, we can put it to immediate use. I'd like to see a lot more articles of this usefulness and information density on HN. I would like to complain about a very minor point though, but one that drives me bonkers. The overuse of the word "manifesto" must stop. I even wrote an article attempting to collect all the internet manifes…
It's actually a "manifest" -- a list of things that are included (well, should be included) -- in any hack event.
On a less snarky note (sorry about that), it seems like a good check list for putting together an event I'd like to attend. As someone else noted, none of the demo-parties and hackathons I've attended have ever checked off every box. On the other hand, it might be a cultural thing -- I imagine these events to be more developed around the valley where they're more common.
Earlier quoted context omitted.
one of the reasons to go high on IP addresses is because many devices don't release their leases properly, which can cause all sorts of havoc.
20/30 people on a regular router that has an IP range of 255 IPs will quite often fall over, I've seen it happen more than once.
Either this causes them to reboot (if they're crappy) or truncate the table, killing the oldest connection.
Earlier quoted context omitted.
20/30 people on a regular router that has an IP range of 255 IPs will quite often fall over, I've seen it happen more than once.
right, I'm not so sure that's because of DHCP, though.