[00:01.260 --> 00:03.040] Good evening, everyone. [00:04.400 --> 00:08.660] It will be the closing track after this. [00:11.640 --> 00:15.440] I want to introduce to you the network team from this conference. [00:15.760 --> 00:19.480] They're about to talk about how the network worked or didn't. [00:19.840 --> 00:26.060] And I'm sorry to say this will be a little bit shorter track due to Jello's longer track. [00:27.560 --> 00:28.860] Everyone, the network team. [00:36.810 --> 00:37.470] All right. [00:37.590 --> 00:37.810] Thank you. [00:38.590 --> 00:47.570] I don't usually perform in public unless I'm drunk and as a karaoke machine, apparently, because my first public performance was last night. [00:47.790 --> 00:49.570] And hopefully this will go a little bit better. [00:51.190 --> 00:52.270] I'm Sir Saiko. [00:52.610 --> 00:54.250] This is... everybody knows Dragorn. [00:54.570 --> 00:59.350] And we have Doug, who... Doug's handled the public terminal cluster. [00:59.770 --> 01:03.970] And I coordinated all the network goings on. [01:04.370 --> 01:14.250] And everybody knows what who Dragorn is and what he does here, so... Actually, can I get the... Can I get the laptop on the screen over here? [01:17.470 --> 01:18.710] I guess I have to turn it on. [01:18.850 --> 01:19.050] Hold on. [01:21.370 --> 01:23.410] Here is the... [01:28.430 --> 01:28.990] That work? [01:29.790 --> 01:31.090] I guess I should have tested this first. [01:33.710 --> 01:34.690] Now that turns it off. [01:34.930 --> 01:35.110] I'm sorry. [01:36.570 --> 01:40.450] So whoever, uh, owns this laptop, I guess there's a password necessary to get it online. [01:40.990 --> 01:41.310] Is that... [01:42.570 --> 01:43.490] I don't know your password. [01:43.730 --> 01:46.450] I don't want to, like, have to hack into your laptop, man. [01:48.090 --> 01:48.910] Set up the network. [01:49.050 --> 01:49.530] Get wireless now. [01:49.950 --> 01:50.210] All right. [01:50.210 --> 01:50.590] Is that coming up? [01:51.390 --> 01:51.950] It's dry. [01:52.290 --> 01:53.550] We'll be about 15 minutes here. [01:53.670 --> 01:54.130] Just get it done. [01:54.670 --> 01:55.030] All right. [01:58.230 --> 01:59.470] Doug's built on an O, by the way. [02:00.590 --> 02:00.990] What's that? [02:01.290 --> 02:02.170] Go put an O on Doug. [02:02.950 --> 02:03.850] Oh, I didn't realize that. [02:03.970 --> 02:05.310] You said that there was a name. [02:05.630 --> 02:05.790] Sorry. [02:06.010 --> 02:06.290] All right. [02:06.990 --> 02:07.310] So... [02:08.850 --> 02:09.890] Let's... I guess we can begin. [02:11.370 --> 02:11.690] So... [02:13.730 --> 02:15.350] I've, uh, done the coordination... [02:15.350 --> 02:15.970] Hold the mic, close to your face. [02:15.970 --> 02:16.610] Okay. [02:16.970 --> 02:21.230] So I've done the coordination for, um, for HOPE for the past, uh, four conferences now. [02:21.630 --> 02:26.150] And the requirements don't, uh, typically change, uh, though they do, uh, sort of increase. [02:26.850 --> 02:31.490] Um, we didn't have wireless at, we didn't really have wireless at the very, uh, at, uh, H2K. [02:32.870 --> 02:41.770] We had somewhat, we somewhat had wireless during H2K2 and, uh, during, uh, the Fifth HOPE and, uh, this conference, I think, uh, wireless has been, uh, you know, pretty rock solid. [02:42.190 --> 02:49.130] Um, but some of the, uh, additional requirements that we've had for this, uh, this conference was... [02:49.650 --> 02:52.070] Everybody keeps screaming that they wanted more Internet bandwidth. [02:52.390 --> 02:55.350] And this time we actually pulled through, uh, sort of. [02:55.570 --> 03:00.050] And got a, um, I believe we got a 90 megabit connection to the Internet. [03:00.530 --> 03:04.610] Uh, I'll explain why we didn't have 90 megabit connection to the Internet even though we had it. [03:05.150 --> 03:06.970] Um, later on when we go over some of the problems. [03:07.730 --> 03:10.890] Uh, but, yeah, high-speed Internet access is something that everybody always wants. [03:10.890 --> 03:19.250] Um, we needed connectivity between the second floor, which is the main convention space, and the 18th floor, which is where all the speaker space is, uh, for a couple of purposes. [03:19.510 --> 03:21.890] Number one, um, so everybody here could get to the Internet. [03:22.190 --> 03:28.730] Um, we have... typically our Internet lines were wired lines and we can only get the wired lines to the second floor. [03:28.810 --> 03:31.550] So that's how we were getting the Internet down to, uh, the second floor. [03:31.550 --> 03:39.910] And, um, also for the audio video streaming, where, uh, some of the people, but we had overflow on the, uh, second floor. [03:40.230 --> 03:44.770] And, uh, the, uh, AV team, uh, handled the streaming. [03:47.030 --> 03:47.610] Who's that? [03:48.290 --> 03:48.850] Sorry about that. [03:48.930 --> 03:49.490] On the AV team? [03:50.510 --> 03:50.970] Okay. [03:52.590 --> 03:53.290] I hear you. [03:54.350 --> 03:54.790] Yeah. [03:54.790 --> 03:55.030] Yeah. [03:55.370 --> 03:56.530] I didn't want to... [03:56.530 --> 03:57.010] I didn't... [03:57.010 --> 03:57.330] I don't know. [03:57.410 --> 03:58.510] I'm not really experienced with this stuff. [03:58.650 --> 04:05.130] Anyway, so we had, um, we have AV requirements where we stream the, uh, talks and the presentations down to the second floor. [04:06.730 --> 04:07.170] And... [04:07.170 --> 04:07.490] Is this... [04:07.490 --> 04:08.390] All right. [04:08.890 --> 04:09.410] Let's see. [04:09.710 --> 04:12.290] Um, we also have, um... [04:14.170 --> 04:15.650] Other than the wireless spoke about... [04:15.650 --> 04:15.810] Yeah. [04:17.290 --> 04:17.730] Um... [04:17.730 --> 04:17.970] Sorry. [04:18.130 --> 04:18.770] I'm a little nervous. [04:18.770 --> 04:30.830] Uh, we have the public terminals for attendees and we have the protected subnets where, uh, we don't want the general wireless network and whatnot to interfere with, uh, speakers using the hard lines wired to the tables up here. [04:30.970 --> 04:41.530] Uh, we don't want it to interfere with the streaming network which simulcasts the talks from up here down to the second floor and, uh, the management, uh, VLAN which controls the switches and whatnot on the different floors. [04:41.790 --> 04:55.630] And, uh, typically the, uh, entire network is, uh, built, constructed and, uh, everything Everything is on a donation effort, so all the switches weren't paid for, the cabling, actually this time is the first time we've actually paid for Cat5. [04:56.710 --> 05:01.810] At H2K2 we had a, I think Bernie S brought like six spools of Cat5 cable. [05:01.990 --> 05:08.430] This time we actually got no donations, except for a single spool that I brought. [05:08.970 --> 05:13.950] And we actually had to run a, oh, sorry, PTC actually brought two spools. [05:14.110 --> 05:19.890] And then we actually ran out, so we had to run over to Home Depot to get some more, to get some more Cat5 cable. [05:20.550 --> 05:26.430] So, yeah, typically the network is 100% volunteer effort. [05:27.690 --> 05:29.210] So... I'm sorry, I'm sorry. [05:29.990 --> 05:33.930] Laptop guy, could you just like get this thing online, because I'm having issues. [05:34.110 --> 05:36.690] And this, you know, great showing from the network staff here. [05:37.050 --> 05:37.670] Thank you. [05:39.170 --> 05:39.770] All right. [05:40.790 --> 05:48.710] So, we, there's, unfortunately I forgot there's a, well, the AV team isn't on here, but they're not really a part of the network. [05:48.850 --> 05:50.110] I guess they're on the AV side. [05:50.370 --> 05:57.650] So, let's see, we have, to get the Internet up and running, we have somebody named Pyro, who we found off of the Wiki. [05:58.010 --> 06:11.790] And he volunteered to do all the, the enormous effort of all the negotiation with get, in getting a company called Rainbow Broadband to get us, our broadband wireless access. [06:11.990 --> 06:12.670] He's over there. [06:12.890 --> 06:13.410] Stand up and wave. [06:13.490 --> 06:13.950] Stand up and wave. [06:20.610 --> 06:29.830] And basically, I was very impressed that a, that a company was, you know, really, really took a strong interest in 2600. [06:29.990 --> 06:38.090] And, you know, they wanted us to showcase their connectivity for, by giving us the access bandwidth at the conference. [06:39.070 --> 06:49.110] And our, now broadband, Rainbow Broadband gave us the actual microwave to our Internet provider, who is Net Access Corporation, NAC.net. [06:49.650 --> 07:05.110] And not only did they give us the DSL, 6 megabit DSL line, which was basically our fallback in case the rainbow, or rather the microwave thing didn't work out, but also, NAC, NAC gave us the IP space and the, and the bandwidth. [07:05.390 --> 07:12.030] Yeah, I gotta say that NAC, and especially Alex, that NAC has been instrumental in networking for several of these occasions. [07:12.270 --> 07:16.150] He's pretty much been responsible for WAN connectivity wholesale. [07:16.550 --> 07:19.190] So, a lot of, a lot of props to NAC and to Alex. [07:25.920 --> 07:28.460] Now, I don't know if anybody from Rainbow is here? [07:28.680 --> 07:29.000] Pyro? [07:29.420 --> 07:30.200] Okay, they couldn't be here. [07:30.380 --> 07:41.660] So, uh, but, uh, what's the guy's name from... Right, um, we had Mark and Alex, another Alex, uh, from Rainbow Broadband, who, uh, you know, got us our great pipe. [07:41.980 --> 07:51.240] And unfortunately, I have to take the credit in, um, in the fact that we couldn't utilize the, the, uh, the broadband access because of a bad cable. [07:51.420 --> 07:53.140] So I'll explain that a little bit later on. [07:53.560 --> 07:54.580] Um, alright, so that's the Internet. [07:54.720 --> 07:55.660] We spent enough time on that routing. [07:56.200 --> 07:58.600] Um, Dragon and I set that up. [07:58.840 --> 08:01.980] Uh, the core of the network was basically, you know, pork chop, Dragon and I. [08:02.340 --> 08:05.880] Uh, all the cabling was pretty much managed by, uh, El Cruz and Pyro. [08:06.080 --> 08:09.400] Uh, the PTC was, uh, pretty much Doug, Mike, and Mike. [08:09.920 --> 08:17.020] And, uh, NAC was, you know, basically run and manned by everyone on the, on the table, on the slide. [08:17.480 --> 08:21.980] So, so now the, uh, the fun part, the planning. [08:22.440 --> 08:35.420] Uh, there wasn't a lot of planning because, um, you know, we, a lot of us have, you know, uh, uh, real lives and, you know, trying to fit in, um, the planning for the conference, a lot, and trying to fit in the planning for the conference just, uh, was very difficult. [08:35.550 --> 08:38.050] And when I was free, somebody else wasn't free. [08:38.240 --> 08:39.780] And when that person was free, I wasn't free. [08:39.980 --> 08:43.120] So it was just, uh, it was very difficult to actually, um, coordinate. [08:43.340 --> 08:59.160] Even at the, the known times for coordination, which were the 2600 meetings and the, um, and the HOPE meetings, which were the third Fridays, I didn't actually get started in much of the planning until about two weeks ago. [08:59.880 --> 09:04.980] All the concepts are the same for the past couple of years, so it wasn't like we were flying into this blind. [09:05.480 --> 09:12.500] But if I had more time, I think we could have nailed down a lot of these other problems that we've had. [09:14.860 --> 09:23.780] One of the things we did plan on was using Linux to do our routing, because in the past, the routers were BSD-based. [09:23.980 --> 09:28.660] At H2K, it was OpenBSD, and then the next two conferences were NetBSD. [09:28.960 --> 09:29.700] And why? [09:29.820 --> 09:42.160] Because I was heavily involved in it, and I know BSD very fluently, and it was easy for me, and the other people who were involved at the time to use BSD-based operating systems. [09:42.320 --> 09:55.700] But since this conference, because of my personal life and everything that was going on, there was a chance that I wasn't going to be as heavily involved in this, so I decided to switch to using Linux because there were more people who knew Linux that were involved in the networking. [09:56.280 --> 09:59.500] So that's why we decided to use a Linux router. [09:59.720 --> 10:05.560] We used Cisco switches and Aruba wireless access points. [10:07.020 --> 10:10.960] We did a fiber link between the two and the 18 floors. [10:11.900 --> 10:19.700] We had to actually... we measured the distance, and unfortunately we actually came up short, so I'll explain about that problem in a little bit. [10:20.400 --> 10:23.580] And again, we already talked about the NAC DSL and the Rainbow Broadband. [10:24.590 --> 10:32.480] And we were going to do some monitoring using Nagios to make sure that certain devices didn't disappear, but we ran out of time. [10:32.480 --> 10:39.140] And, you know, but we do have some MRTG graphs, which are now completely skewed because of, you know, the problems we were having. [10:40.120 --> 10:43.290] And the NAC staff just completely fell apart. [10:43.480 --> 10:50.670] It was, you know, basically just, you know, the core people who were involved in the networking basically stayed most of the time during the conference. [10:50.700 --> 10:56.900] And, you know, we lost track of our volunteers, so we couldn't really, you know, have the NAC as well staffed as we wanted to. [10:59.560 --> 11:01.800] So, overall, I guess the planning could have been a little bit better. [11:01.980 --> 11:06.260] But the end result, you know, is that we still had a pretty decent network. [11:06.560 --> 11:09.140] One of the better network, probably the best network we've had yet. [11:09.660 --> 11:12.240] And every conference, the network seems to get better. [11:14.180 --> 11:17.220] So, the way the setup happened, we started at 11 a.m. [11:17.300 --> 11:20.560] Thursday, and I don't think we're actually finished setting up the network yet. [11:21.480 --> 11:22.040] Let's see. [11:23.850 --> 11:28.000] So, yeah, we set up the tables at just about 11 a.m. [11:28.900 --> 11:32.040] Then, you know, getting the router set up, making sure everything was functional. [11:32.320 --> 11:34.120] Then we decided to run the fiber. [11:34.320 --> 11:38.560] And we found that we were about 200 feet short of what we actually needed. [11:39.320 --> 11:42.620] So, we actually had to move the NAC over to where the fiber ended. [11:43.630 --> 11:53.600] And more specifically, we had to use another patch at the end of our fiber, coupled with a patch panel coupler that I happened to have from last conference. [11:55.040 --> 11:58.100] And we moved the NAC over to next to where the AV room is. [11:58.540 --> 12:01.600] So, that finished about, I guess, 9 p.m. [12:01.780 --> 12:02.620] Was it about 9 p.m. that we finished that? [12:03.520 --> 12:04.240] We moved the NAC? [12:04.480 --> 12:05.680] Yeah, I think it was about 9 p.m. [12:05.680 --> 12:07.620] I think we started moving the NAC around 9 p.m. [12:07.700 --> 12:07.840] Yeah. [12:07.960 --> 12:09.260] Because it was too late to buy more fiber. [12:09.580 --> 12:10.060] Right, exactly. [12:10.400 --> 12:17.900] So, after we got the fiber actually run, we set up the switches, you know, getting all the VLANs going for, you know, between 2 and 18. [12:18.420 --> 12:24.400] Then Dragorn began doing the AP setup, getting them deployed, cabled, and on the network. [12:24.620 --> 12:27.280] And then once he was done with that, and I think that was... [12:27.280 --> 12:29.200] I think you were done about 4 a.m. [12:29.380 --> 12:29.740] with that? [12:30.260 --> 12:30.920] Around then. [12:31.340 --> 12:36.120] And at 4 a.m., we started working on the firewall and getting policy routing. [12:36.360 --> 12:39.660] And I'll explain in a bit why we needed to do policy routing. [12:41.560 --> 12:46.160] This is an example of what we... people keep asking, like, you know, are we using VLANs? [12:46.220 --> 12:47.680] Well, yes, we were using VLANs. [12:48.960 --> 12:53.060] We have, you know, VLANs for each individual's specific purpose. [12:53.240 --> 12:58.300] Like, the trunk to our Internet provider was, you know, on its own VLAN. [12:58.500 --> 13:00.540] Our uplink to the DSL was on its own VLAN. [13:01.080 --> 13:03.240] Specifically because how we were doing our routing. [13:03.860 --> 13:10.600] The wired access, if you plugged into an Ethernet jack downstairs, you would get... you would be on a specific VLAN. [13:10.840 --> 13:12.600] The PTC guys were on their own VLAN. [13:12.900 --> 13:18.380] All the streaming stuff, which we wanted to separate from the rest of the network to protect it, that's on its own VLAN. [13:18.680 --> 13:22.880] All the wireless access was a separate network. [13:23.040 --> 13:23.280] Let's see. [13:23.740 --> 13:25.960] We had an external VLAN for projects. [13:26.160 --> 13:29.200] Like, somebody wanted to set up... show people how to set up a tour. [13:29.440 --> 13:33.560] So we gave him a switch and, you know, an Ethernet connection so we could set up his equipment. [13:33.560 --> 13:38.140] And the CTF, which I believe didn't happen, you know, was also on this range. [13:38.800 --> 13:45.840] The speakers, like the Ethernet jack that's... the Ethernet cable that's running along the side, that gray cable, that's on its own VLAN because we wanted, again, we wanted to protect it. [13:46.020 --> 13:50.700] And then the VLAN that managed everything was a separate VLAN. [13:51.500 --> 13:51.800] So... [13:53.080 --> 13:54.840] Now, so for the routing... [13:55.380 --> 13:58.360] In the past, this router was pretty sufficient. [13:58.520 --> 14:00.820] We, you know, 40... 450 megahertz with a lot of RAM. [14:01.560 --> 14:02.720] Hasn't been a problem in the past. [14:02.720 --> 14:05.860] Again, we used Linux for... [14:05.860 --> 14:06.520] What do you call it? [14:07.100 --> 14:07.600] The... [14:07.600 --> 14:11.940] Slackware Linux is the router with that 2.6.17.6 for the kernel. [14:13.860 --> 14:14.360] The... [14:14.360 --> 14:21.820] We had two quad tulip cards that was handling all the uplinks to the assorted VLANs. [14:21.980 --> 14:25.720] We didn't want to use, you know, VLAN trunking because that would just have been more processing. [14:26.080 --> 14:27.900] It was easy to just do straight routing. [14:28.830 --> 14:31.540] We used IP tables for the firewall to protect the networks. [14:31.940 --> 14:35.680] And, again, we used Linux kernel advanced routing for the policy routing. [14:37.830 --> 14:38.720] I believe... [14:38.720 --> 14:39.280] Look... [14:39.280 --> 14:39.960] Should I come back to someone? [14:40.200 --> 14:41.440] Should we explain the policy routing first? [14:41.740 --> 14:42.760] Sure, we can pop back. [14:44.260 --> 14:44.820] All right. [14:45.420 --> 14:45.860] So... [14:46.560 --> 14:47.400] You guys see that? [14:47.960 --> 14:48.520] All right. [14:48.520 --> 14:53.800] So, you see over here, at the top right, we have the rainbow broadband connection. [14:54.240 --> 14:54.680] And the bottom... [14:55.160 --> 14:55.820] I'm sorry. [14:56.060 --> 15:00.080] The top left, we have the Internet via NetAccess Corp, which is... [15:00.080 --> 15:00.360] I'm sorry. [15:01.200 --> 15:02.160] Via DSL. [15:02.600 --> 15:12.180] And what we did was we routed all of the wireless access out the rainbow broadband because we figured that would be the bulk of the majority of our users would be wireless users. [15:12.180 --> 15:18.720] And the minority of our users would be, you know, wired, you know, the public terminal cluster or if you needed an Ethernet jack. [15:19.260 --> 15:26.760] We figured that would be a lot less traffic, so we sent that out to DSL because we wanted to make sure that we used both, you know, both pipes so nothing was wasted. [15:28.220 --> 15:31.980] And so that's why we had to do the policy routing is because we had a separate... [15:31.980 --> 15:37.300] We had a slash 22 subnet, which is, like, basically four class Cs. [15:38.280 --> 15:39.620] That was for the wireless. [15:40.040 --> 15:44.000] And we had a slash 24, which is basically a single class C for the wired connection. [15:44.420 --> 15:51.360] And that's where the policy routing came into play, is that if you were on one specific connection, we wanted to route you out one path, and you were on a different connection, we wanted to route you out the other path. [15:51.680 --> 15:54.760] So, it's great in concept. [15:54.920 --> 16:02.440] I mean, I do it at home where I send all my web stuff out, my cable modem and my regular SSH and send mail and all that other stuff goes out in my DSL. [16:02.980 --> 16:07.700] So, it's good in concept, but the implementation of this just was a nightmare. [16:07.980 --> 16:13.240] It probably took us a good three hours to get that part actually working properly. [16:13.400 --> 16:18.160] Of course, we also started at 5 a.m., and that probably didn't accelerate our mental processes. [16:18.980 --> 16:19.740] Hey, real quick. [16:19.880 --> 16:20.300] Sorry, guys. [16:20.480 --> 16:27.960] If there's somebody else who might have a laptop with wireless and SSH on it that I could borrow for a few minutes, you've got quite a crowd here. [16:29.440 --> 16:31.080] There's no Wi-Fi working in here? [16:31.320 --> 16:32.340] Do you have a network on here? [16:33.100 --> 16:35.100] Is there any network in here at all somebody knows about? [16:35.720 --> 16:36.640] There's Wi-Fi over there. [16:38.080 --> 16:43.060] If anybody has the ability to get online, even through a cell network, it will greatly improve the quality of the presentation. [16:46.040 --> 16:46.580] Pick one. [16:46.760 --> 16:47.240] Right or left. [16:47.480 --> 16:47.980] There we go. [16:48.280 --> 16:48.720] Let's go for that one. [16:49.500 --> 16:49.900] See, buddy. [16:50.960 --> 16:51.540] Thanks, guys. [16:51.640 --> 16:51.780] Thanks. [16:52.960 --> 16:53.400] All right. [16:53.620 --> 16:56.060] So, this is the network topology. [16:56.780 --> 16:59.480] You can see over here on the right-hand side. [16:59.740 --> 17:02.560] Well, on the left-hand side is the second floor. [17:02.680 --> 17:03.900] That's where the main router was. [17:04.030 --> 17:10.730] On the 18th floor is where we have a switch that connects to the APs and also connects to the Rainbow Broadband stuff. [17:11.250 --> 17:15.440] Those dishes are actually on the roof, and we have an Ethernet going to the switch. [17:15.440 --> 17:19.510] And it actually routes over to a switch at four times. [17:19.790 --> 17:22.180] That radio antenna, you can actually see behind that. [17:22.340 --> 17:24.420] When you're done with the talk, you can see the radio antenna. [17:24.840 --> 17:26.520] That's the biggest radio antenna. [17:26.640 --> 17:27.520] You look outside that window. [17:27.730 --> 17:29.460] That's where our Internet is going. [17:29.920 --> 17:31.500] And that's at four times square. [17:31.520 --> 17:36.700] So there's a switch there that has a fiber connection down to 60 Hudson Street, which is one of the telco hotels. [17:36.700 --> 17:40.970] And that's where we connect to our ISP, which is Net Access Corporation. [17:41.700 --> 17:47.060] And that's basically what our network topology looks like. [17:47.500 --> 17:51.860] I'm going to go back to the wireless, which I skipped over and let drag on talk for a few minutes. [17:52.180 --> 18:07.880] The wireless this year, two years ago we used some custom-built hardware, which was basically Primestar satellite cabling boxes with a small motherboard shoved in them and a couple of fans wedged in there and a lot of duct tape and hot milk glue and a prayer. [18:08.400 --> 18:11.120] This year we actually used Aruba AP70 APs. [18:11.230 --> 18:14.800] They donated 20 of them to do the wireless here. [18:15.860 --> 18:21.260] They're 200 and some odd megahertz MIPS boxes with dual ABG radios with power over Ethernet. [18:21.460 --> 18:22.840] Made it much easier to set things up. [18:23.280 --> 18:33.840] The management code this year was a plug-in for the new version of Kismet, which just lets you manage the radios over the standard protocol, so I didn't have to write nearly as much software. [18:34.620 --> 18:38.520] We targeted three BG channels and three A channels per area. [18:39.520 --> 18:40.460] 11A is good. [18:41.320 --> 18:42.500] Hopefully people used it. [18:42.600 --> 18:44.500] It seemed like we got a fair amount of usage on it. [18:46.180 --> 18:51.210] 11G will degrade itself to 11B mode the instant someone with a B only radio connects to it. [18:51.760 --> 18:54.470] So that was pretty much guaranteed to be 11 megabit only. [18:55.710 --> 18:59.920] We saw some DOS attacks against the network, but it wasn't as severe as it was two years ago. [18:59.920 --> 19:02.210] So in general, we held up a bit better. [19:02.800 --> 19:05.400] Every year we tweak where we put the APs a little bit. [19:06.080 --> 19:10.940] This year was mostly pretty good until apparently right now, but I'm up here so I don't know what's going on. [19:12.640 --> 19:14.710] And that was about it for the wireless access. [19:17.160 --> 19:19.180] Do you have anything you want to talk about or do you want me to come back to you? [19:19.800 --> 19:22.800] Yeah, I got about 30 minutes to talk, so go ahead. [19:25.340 --> 19:27.660] So let's see if there's anything else about the network. [19:28.480 --> 19:32.680] I don't think that we pretty much covered how the topology looked. [19:33.140 --> 19:34.660] All right, so I guess we can talk about some... [19:34.660 --> 19:36.560] Well, should we talk about the problems now or do you want to talk? [19:37.360 --> 19:38.040] Your choice. [19:38.200 --> 19:40.760] I'm just going to go on a big history about the PTC stuff. [19:40.840 --> 19:40.880] Okay. [19:40.880 --> 19:42.800] All right, I'll let PTC go last. [19:44.020 --> 19:47.300] So some of the problems that we had was the fiber spool ran out, as we said. [19:48.720 --> 19:50.210] Now here's where I have to own up. [19:51.060 --> 19:53.680] So we have this great 90 megabit connection to the Internet. [19:54.000 --> 20:00.420] And when we were troubleshooting the problem, we saw that one of the link lights on the switch was amber, meaning it was 10 megabit. [20:01.300 --> 20:07.970] And also we noticed that no matter what we did on the wireless, we couldn't down... our MRTG graphs were showing that it was only about 10 megabit. [20:08.400 --> 20:11.320] And I guess that connection didn't come into my mind. [20:11.420 --> 20:15.140] But when I did troubleshoot, I traced it and I thought it was going to one of the APs. [20:15.140 --> 20:19.760] It turned out that this bad patch was what was routing our wireless Internet access. [20:20.210 --> 20:23.760] So we could only get about 10 megabits per second. [20:23.900 --> 20:29.000] And not only that, but we couldn't even max out for a single session. [20:29.140 --> 20:34.900] For some reason, whenever you created a session, it was about 50K per second. [20:35.280 --> 20:41.780] So all the signs pointed to the ISP that we thought that they were... the ISP being NAC. [20:42.710 --> 20:44.960] We thought they were doing some sort of traffic shaping. [20:45.230 --> 20:49.500] Maybe they gave us IP addresses from some other customer at some point that was, you know, shaped. [20:50.360 --> 20:56.900] So I have to apologize to NetAccess Corporation and to Rainbow that, you know, this bad patch prevented us from fully utilizing the network. [20:57.040 --> 21:06.230] But right now, if you get wireless access, we were downloading at over 700K per second, which is probably the fastest we've ever downloaded here at a HOPE conference. [21:06.230 --> 21:12.180] So other problems, policy routing in Linux was just extremely complicated. [21:12.620 --> 21:14.970] Apparently to... let me go back to the network map. [21:15.600 --> 21:27.760] So if you see over here... like... so for the... on this list, we have the wired access, the wireless access, and the external. [21:27.760 --> 21:38.900] And those are... the wireless and the... it was one subnet, and the wired and the external were on the same slash 24, but we carved it up, you know, we subnetted it further. [21:39.630 --> 21:48.320] And for each of these subnets, when you're doing policy routing, you have to, you know, basically nail down a route for every single one of these. [21:48.500 --> 21:57.300] So it's not like... at least on BSD, what I've done in the past was just said if, you know, if it's going from one IP address, route it to this IP... to this gateway. [21:57.520 --> 22:01.560] If it's going from a different IP address, route it to this other gateway. [22:01.820 --> 22:09.360] And that's really... literally three lines of IPF is what you can use to get policy routing in NetBSD. [22:09.640 --> 22:15.880] Here, I think the policy route was about 12 lines, and it took us about a couple hours to... to get that working. [22:16.880 --> 22:17.320] So... [22:17.320 --> 22:25.340] Basically, we had to split the routing table into two different tables, one for each side, and we forgot to add all of the other interface routes back into it. [22:26.400 --> 22:26.920] So... [22:26.920 --> 22:27.820] We shot ourselves in the foot. [22:28.120 --> 22:28.180] Yeah. [22:30.160 --> 22:30.680] And... [22:30.680 --> 22:37.160] The other way we shot ourselves in the foot is that once, you know, we fixed the rainbow broadband problem, the router could barely keep up. [22:37.280 --> 22:38.140] It was falling over itself. [22:38.500 --> 22:39.020] So... [22:39.020 --> 22:49.020] Next time, if we do get the super-fast wireless broadband, we will have to get a super-fast good Cisco router to actually handle proper routing. [22:49.020 --> 22:52.240] Yeah, the router actually fell over from PCI interrupts. [22:52.440 --> 22:57.940] At one point, we broke 100,000 interrupts a second, and it... it didn't like it. [23:01.600 --> 23:01.960] So... [23:02.760 --> 23:05.420] Some of the other problems, you know, again, volunteers disappearing. [23:05.860 --> 23:10.440] We had a lot of people come up to us in the beginning and say, we want to be network volunteers. [23:10.720 --> 23:17.060] And this was before we even had a network, so we didn't... or even had a place to set up a network, so we didn't need them right then. [23:17.520 --> 23:22.120] And I think half of those people joined the security team, which was, you know, which happens all the time. [23:22.540 --> 23:22.940] And... [23:22.940 --> 23:34.220] But the people that we did have... that did express interest in doing exclusively the knock, I don't think we actually got anybody from the... that emailed the volunteer list and said that we wanted... they wanted a volunteer. [23:34.540 --> 23:35.880] I don't think we actually got any of the... [23:35.880 --> 23:42.060] I'm sorry, we got one person, this guy named Andrew from Cisco, and we're using one of his routers as part of the core network. [23:42.680 --> 23:43.500] And... but that was about it. [23:43.680 --> 23:52.480] So the network was... the knock was pretty much staffed by... by the core network team, the AV team, and some other project. [23:52.660 --> 23:58.460] We have... we were trying to get some webcams up to stream to, you know, the... to the Internet, but that didn't really pan out. [23:58.560 --> 24:00.900] But while they were setting up, they were pretty much manning the knock. [24:01.060 --> 24:07.560] So we barely had just enough coverage to make sure that, you know, things don't walk away and whatever, or people don't tamper with the network. [24:08.670 --> 24:10.480] So... I guess... did I write some lessons? [24:10.720 --> 24:22.020] So... some of the lessons over this experience was, which I... I think I probably said this at the last hope was, maybe we should actually review what we talked about, the problems that we had from the last hope. [24:22.200 --> 24:24.440] We didn't... I don't think... I definitely didn't do any of that. [24:25.720 --> 24:30.720] We should also try to do, again, the planning, which I didn't really get a chance to do much of. [24:31.220 --> 24:36.120] I could have been better at providing specific details of the network to the people who wanted to use stuff on the network. [24:36.120 --> 24:45.540] More specifically, you know, even... even then, I really didn't get any details of what people needed from the network until the day the network was set up, or the day before the network was set up. [24:47.660 --> 24:50.700] Everybody's heard the term... the phrase, measure twice, cut once. [24:51.540 --> 24:54.320] That's... that's pretty important, especially when you're running fiber. [24:56.040 --> 25:00.960] 450 feet of fiber did not make it from the... from the 18th floor to the second floor. [25:00.960 --> 25:03.140] We actually had to use a coupler, like I mentioned before. [25:04.160 --> 25:06.120] Again, coordinating specific times with volunteers. [25:06.280 --> 25:10.220] When we get some volunteers, we need to make sure that they're going to be where they are when... [25:10.220 --> 25:18.640] Now, we realize that people want to see the conference, but when you, you know, promise that you're going to help out the NOC and then you disappear, that makes, you know, keeping the network up and running a little bit difficult. [25:19.200 --> 25:32.720] And the last thing was keeping... making a separate project NOC where, like, if people wanted to set up a Tor router or webcams or whatever to keep that stuff out of the NOC because, you know, people tripping over the cables can, you know, take down the network and, [25:32.760 --> 25:42.020] you know, having to chase people away while we're, you know, trying to fix a problem is, you know, gets a little frustrating and time-consuming and, you know, delays getting fixing problems. [25:42.140 --> 25:44.920] So we definitely need to separate out stuff from the NOC. [25:45.880 --> 25:48.480] And I think that's about it for my part of it. [25:48.880 --> 25:51.640] So, do you... is there anything else you want to talk about before I go to Doug? [25:51.740 --> 25:51.740] Nope. [25:51.840 --> 25:52.520] Turn it over to Doug. [25:52.780 --> 25:52.860] All right. [25:52.960 --> 25:53.640] We'll turn it over to Doug. [25:54.280 --> 25:54.460] All right. [25:54.700 --> 25:55.560] We've got a video on this. [25:55.680 --> 25:56.100] Video on that. [25:56.620 --> 25:57.240] What do you want to do? [25:57.280 --> 25:57.880] Is there a net on that? [25:57.980 --> 25:58.680] I will check. [26:00.360 --> 26:00.680] Okay. [26:00.740 --> 26:05.780] We'll see if we can get some net going on here because mine's somewhat dependent on net. [26:06.620 --> 26:09.120] So what I'm supposed to talk about is the public terminal cluster. [26:09.380 --> 26:18.780] If you guys have missed this, this is a small collection smattering, really, of terminals of various types downstairs, just to the left of the escalators you get off going up. [26:19.640 --> 26:25.500] This is my sixth hope, I guess, to be involved in some manner with something like this. [26:25.680 --> 26:40.600] The very first hope, which was here in this hotel, there was an official terminal service put on by the con management, which I was not a part of, but we had our own little party going on because they allowed anyone to set up what they wanted. [26:40.800 --> 26:43.660] And so I brought a few people and a few terminals of various types. [26:43.960 --> 26:50.580] But after that, we pretty much, we were able to get on ourselves at hope.con.com, if you can get to. [26:51.260 --> 26:54.640] And so I've prepared a few documents from the earlier times. [26:56.360 --> 27:03.120] So some people feel that the public terminal cluster should provide a service, and that service is access to the Internet. [27:03.580 --> 27:07.200] Well, that, of course, is just plain stupid because this is a hacker conference. [27:07.340 --> 27:09.060] People, if they want to get online, bring your laptops. [27:09.720 --> 27:16.880] So the rendition that I've taken it to, sorry, has been more or less to do something cool. [27:18.340 --> 27:18.880] Oh, yeah. [27:19.020 --> 27:19.400] Can I see it? [27:19.540 --> 27:21.020] Oh, so I didn't think it. [27:21.380 --> 27:22.700] Can you get rid of those tabs, too? [27:23.700 --> 27:25.380] So we've been trying to do something cool. [27:25.500 --> 27:38.300] Last year, actually, there are two of us who have been the main instigators, myself, and then I'm Doug, and then Mike, with a Y, MYKE, who was pretty much in charge of everything last year. [27:38.500 --> 27:40.980] And he was much more on the side of let's try and provide a service. [27:41.520 --> 27:44.960] His system, you know, we tried to do something a little odd. [27:45.080 --> 27:49.360] So last year, he focused mainly on providing Linux access through Linux boxes. [27:50.560 --> 28:02.940] I think his core machine was a 300 megahertz, Pentium, Pentium Pro, Pentium 2, with 64, 128 megs of RAM, CD drive, 4 gigs of disk, that sort of thing. [28:03.020 --> 28:03.680] Worked very well. [28:05.740 --> 28:08.360] So the year before, we had two things. [28:08.500 --> 28:15.220] He had his Linux thing, then I had started the first year with... that was my first year with headless... rather, I'm sorry, diskless terminals. [28:15.560 --> 28:19.480] We used NCD, what we called NCD Explorer XA. [28:19.640 --> 28:33.440] Little black boxes, little smaller than a laptop, that have PS2 output, VG output, and network input output, and have no disk in them, just a bunch of RAM, and they require some sort of machine to boot off of to get their firmware and then to run. [28:33.760 --> 28:34.940] And that was very cool. [28:36.280 --> 28:40.240] The thing that was probably cool last year was the existence of token ring. [28:40.380 --> 28:41.660] The entire network was not Ethernet. [28:41.840 --> 28:42.760] It was token ring. [28:43.080 --> 28:44.580] It was twisted pair token ring. [28:44.680 --> 28:52.120] And that made it particularly interesting for people, we always have this problem, plugging their own laptops into the switches and trying to get around stuff. [28:52.380 --> 28:56.820] Well, it was pretty fun watching them plug in and trying to figure out how to get online through the token ring router. [28:57.160 --> 29:01.040] Most people didn't know what token ring was, so we got our little private laughs off of that. [29:01.660 --> 29:03.560] We had a similar thing for this year. [29:04.480 --> 29:07.060] Since the previous year, our biggest problem was providing this. [29:07.320 --> 29:14.620] You know, we'd set out switches on the tables, and we had the one year, two years, two times ago, we had about a hundred terminals, 50 of each type. [29:15.300 --> 29:17.280] And it was a massive mess, my God. [29:17.820 --> 29:30.660] But people would plug their own stuff into the switches, and pretty often those people would assign the router address to their own laptop, pretend that they're, you know, the main router gateway for everything, and you could guess what happens then. [29:30.760 --> 29:33.880] All sorts of conflict, people getting upset, and us saying, God, you're a loser. [29:34.320 --> 29:35.200] It was really annoying. [29:35.460 --> 29:38.340] So, last year, that was dealt with by having token ring on the network. [29:38.700 --> 29:47.060] Since I was doing it, since I was coming on site this year, and we didn't really have token ring as an option for the terminals that I wanted to use, this year, we did something a little different. [29:47.220 --> 29:48.160] We did use Ethernet. [29:48.840 --> 29:54.540] I guess if we wanted to, we could have had it somewhat secure, you know, assign a MAC address per port, but somebody would have gotten around that. [29:55.260 --> 30:02.740] Instead, this year, we decided not to use TCP/IP as our network protocol, but instead chose DECnet to use as our network protocol. [30:03.100 --> 30:13.340] So, people who would plug into our network and think of themselves very cool, plug in this network and assign myself the gateway address, and then sit there and nothing would happen because we weren't using TCP/IP. [30:13.600 --> 30:16.640] So, we got around that using DECnet this year, which was a lot of fun. [30:17.020 --> 30:33.540] And also, to provide an extra challenge to those who are interested in it, instead of using Linux as our operating system, or using Windows, or using VSD, or UNIX, period, we chose to use VMS as the operating system for our central terminals, for our central mainframe. [30:33.880 --> 30:40.040] So, all of our terminals ran and gave you a VMS, what they call a DCL session, so the equivalent to the terminal. [30:40.800 --> 30:44.600] And we saw several people try to hack root on this. [30:45.160 --> 30:49.660] People who are familiar with VMS know there's no actual named account, or account named root. [30:50.160 --> 30:51.380] It's system, by the way. [30:51.680 --> 30:56.500] We could have had a whole session on how not to hack root on a VMS box just by watching these guys try this. [30:57.060 --> 30:58.220] It was a lot of fun. [30:58.360 --> 31:03.200] But, you know, we did provide web service, and we provided SSH and talented access, so all the services you needed. [31:03.520 --> 31:04.700] If you typed that, it would have worked. [31:05.320 --> 31:08.080] Even if you type in capitals, you know, that's the cool thing about VMS. [31:08.260 --> 31:09.580] Case insensitivity. [31:10.020 --> 31:14.280] A lot of these new kids have forgot about that when you used to be able to type caps and get away with it. [31:15.280 --> 31:16.800] So, some of the things we have here. [31:16.980 --> 31:22.980] Mike Holling is my, the guy who has done a lot of this before, and he's done some excellent stuff. [31:23.160 --> 31:24.420] What browser is this, by the way? [31:24.480 --> 31:24.720] Firefox? [31:25.720 --> 31:26.080] Okay. [31:26.280 --> 31:29.460] There's a way to increase the font size, right? [31:29.460 --> 31:29.600] Yeah. [31:29.800 --> 31:30.480] Control plus. [31:30.780 --> 31:31.680] Control plus. [31:31.840 --> 31:32.420] Control plus. [31:33.320 --> 31:34.180] I know that. [31:35.240 --> 31:35.840] God's sakes. [31:37.840 --> 31:38.120] All right. [31:38.320 --> 31:39.180] So it's the left control. [31:39.340 --> 31:39.720] Okay, cool. [31:39.940 --> 31:41.500] So I don't know if you guys can see this or not. [31:43.800 --> 31:44.380] There we go. [31:44.780 --> 31:45.320] Clip it to myself. [31:46.160 --> 31:46.720] Too big? [31:47.260 --> 31:47.640] No. [31:47.880 --> 31:48.280] All right. [31:48.460 --> 31:48.980] That's visible. [31:49.180 --> 31:49.500] Oh, goodness. [31:50.060 --> 31:50.260] All right. [31:52.240 --> 31:52.820] Very good. [31:52.980 --> 31:53.640] My mouse is gone. [31:53.900 --> 31:56.540] So, yes. [31:57.280 --> 31:57.560] Okay. [31:57.960 --> 31:58.680] Something is wrong. [31:58.980 --> 31:59.480] One second. [31:59.600 --> 32:00.140] Oh, F11. [32:00.840 --> 32:01.480] Try F11. [32:01.740 --> 32:02.160] One second. [32:02.280 --> 32:03.320] Let me bring up IE. [32:03.840 --> 32:04.320] All right. [32:04.420 --> 32:07.900] Anyway, this is from, I believe this is from two years ago. [32:08.160 --> 32:08.560] 2002. [32:08.740 --> 32:09.680] That was two times ago, right? [32:10.880 --> 32:11.840] Oh, please. [32:12.680 --> 32:13.860] How do you get the font up, then? [32:14.940 --> 32:15.800] Can you get the font increased? [32:16.300 --> 32:16.700] Yeah. [32:17.440 --> 32:18.500] It's not the same thing. [32:19.860 --> 32:23.880] Just to let you guys know, I've been using Firefox for about six years, I think, now. [32:24.540 --> 32:26.420] And last month, switched to Opera. [32:28.780 --> 32:29.340] Oh, really? [32:29.440 --> 32:29.560] Okay. [32:29.660 --> 32:30.560] It's not open source, is it? [32:31.020 --> 32:31.940] Is Opera open source? [32:32.420 --> 32:32.780] No. [32:33.060 --> 32:33.800] And you're plotting it? [32:33.980 --> 32:34.440] What the hell? [32:35.540 --> 32:37.180] It is better than I give you that. [32:37.260 --> 32:38.760] Anyway, Opera seems to have come back. [32:39.180 --> 32:40.380] I used to love Opera. [32:40.820 --> 32:42.240] And then just didn't keep up to date. [32:42.360 --> 32:43.380] And now Firefox, now. [32:43.820 --> 32:44.900] Opera's back, and they're cool. [32:44.900 --> 32:46.200] This is visible to everyone, I hope. [32:46.580 --> 32:47.100] No problems. [32:47.880 --> 32:52.440] Let's see if I can find my, the favorite part of this that I like. [32:52.720 --> 32:53.380] Vandalism and theft. [32:53.480 --> 32:54.120] Always a problem. [32:54.300 --> 32:57.860] Oh, by the way, you guys, we'll have some stuff to give away downstairs, mostly monitors. [32:58.280 --> 32:59.900] Please don't take the terminals themselves. [33:00.340 --> 33:03.460] They're available at $400 a piece, but I can't give them away this year. [33:03.560 --> 33:04.600] They belong to someone else. [33:06.040 --> 33:06.520] Let's see. [33:06.600 --> 33:07.460] Where the heck is it? [33:08.260 --> 33:09.200] My, yeah, art points. [33:09.360 --> 33:09.600] Definitely. [33:09.760 --> 33:12.040] They did score on art points big time. [33:12.160 --> 33:13.360] This is very important to us. [33:13.360 --> 33:17.920] More than providing a service, more than doing stuff, it's sort of the art points we can get. [33:18.220 --> 33:22.200] The image of derelict youth in a semi-abandoned cyber techno ghetto is priceless. [33:22.760 --> 33:32.840] We didn't really shoot for that this year and didn't really make it, but, yeah, some girl, not a day over 13, ducked down near one of the fringe tables, consumed something nasty-looking from a bottle in a bag. [33:33.260 --> 33:35.920] Yeah, we didn't know much of that happened this year, but we're shooting for next time. [33:36.180 --> 33:36.960] A little more things. [33:37.100 --> 33:37.600] We really... [33:37.600 --> 33:40.800] This was the year we had 100 terminals, and it was way too much. [33:40.800 --> 33:42.700] So much stuff all over the place. [33:42.920 --> 33:45.340] Just, yeah, endless catacombs of computers. [33:45.660 --> 33:46.660] Just too much crap everywhere. [33:47.300 --> 33:50.140] Last year we settled on a count of 36. [33:50.360 --> 33:54.560] We did 36 again this year, and that's a pretty good number, so we don't get too nuts. [33:54.800 --> 33:58.040] We really didn't have as much usage this year as we have in past years. [33:58.180 --> 34:00.620] I think more laptops is what that's due to. [34:01.240 --> 34:04.160] I think maybe for next year we're going to try something else, cool art points. [34:04.160 --> 34:07.820] I would love suggestions on what we could try out as far as the... [34:08.180 --> 34:08.730] What is it? [34:09.740 --> 34:10.050] BOS. [34:10.340 --> 34:11.130] Well, that's UNIX, right? [34:11.680 --> 34:12.000] So... [34:12.000 --> 34:12.730] I don't know if we'd do that. [34:13.180 --> 34:13.940] We thought about... [34:13.940 --> 34:14.860] We thought about BOS. [34:15.000 --> 34:15.590] We thought about PIC. [34:15.690 --> 34:16.400] Anyone heard of PIC? [34:17.150 --> 34:18.440] Yeah, we thought about using PIC. [34:18.880 --> 34:19.000] Huh? [34:20.860 --> 34:21.170] Microcontrollers. [34:21.320 --> 34:21.630] Microcontrollers. [34:21.880 --> 34:22.500] Yeah, that's lame. [34:22.920 --> 34:23.440] We'll go ahead and do that. [34:25.150 --> 34:26.480] I just want to go back to the... [34:26.480 --> 34:27.690] Did you actually pull up the... [34:28.270 --> 34:28.940] I'll just do this. [34:29.020 --> 34:29.400] How about that? [34:29.690 --> 34:29.900] Okay. [34:30.420 --> 34:30.730] Yeah. [34:31.550 --> 34:32.500] Any good ideas? [34:32.520 --> 34:33.150] I'd love to hear. [34:33.150 --> 34:35.920] So, this is our schedule that we had planned for originally. [34:36.150 --> 34:36.550] Oh, yeah. [34:36.630 --> 34:42.880] Since Mike wasn't able to make it, we Christianed this cluster, the Michael at Halley Memorial Public Terminal Cluster. [34:43.690 --> 34:46.350] And this is our original schedule. [34:46.550 --> 34:51.570] And luckily, we didn't really stick to that schedule this year, which I am very happy to report. [34:51.880 --> 34:53.290] But we did have a lot of fun. [34:55.690 --> 34:56.090] So... [34:56.090 --> 34:57.040] Let's see. [34:57.150 --> 34:58.110] It's been six times. [34:58.290 --> 34:59.960] We've done all sorts of different technology. [35:01.000 --> 35:01.270] Yeah. [35:01.480 --> 35:02.550] So, I'm definitely going to push. [35:02.550 --> 35:08.570] And some of the guys who have been financing this for the last six times, I'm going to push for more art, less service for the next time. [35:12.040 --> 35:12.420] That's... [35:12.420 --> 35:12.960] Oh, yeah. [35:13.020 --> 35:15.550] I can show you some of the other things we had here. [35:15.830 --> 35:16.630] How do you get back? [35:17.040 --> 35:17.650] No gestures? [35:17.960 --> 35:18.130] Yeah. [35:19.190 --> 35:19.790] What is it? [35:20.900 --> 35:21.380] Oh, yeah. [35:21.380 --> 35:22.550] You can see our mascot. [35:23.500 --> 35:24.920] This is actually the mascot from last time. [35:25.790 --> 35:29.350] This is an actual person we had here at the convention. [35:29.810 --> 35:32.020] And that's what it looked like if you stared at them long enough. [35:34.440 --> 35:36.040] I actually don't know if we got these. [35:37.440 --> 35:37.830] Yeah. [35:38.000 --> 35:42.590] Hopefully, you can see things as they were a little more. [35:42.690 --> 35:43.270] This is... [35:43.270 --> 35:45.730] I guess our sponsorship has changed a bit over the years. [35:45.730 --> 35:48.710] And I guess now we have Telerama as our sponsor. [35:48.960 --> 35:51.050] It does wireless Internet in various places. [35:53.290 --> 35:53.690] Alright. [35:53.790 --> 35:54.920] This is not going to be pleasant. [35:55.130 --> 35:56.540] So, we might just give up on the pictures here. [35:57.150 --> 35:57.310] Yeah. [35:57.500 --> 35:59.000] Or about the URLs or something later. [35:59.150 --> 35:59.350] Yeah. [36:00.230 --> 36:01.690] Hope.com. [36:01.900 --> 36:03.550] So, that's my... [36:04.830 --> 36:08.500] Not only is it my anti-spam system and a cool way to create websites for places. [36:11.110 --> 36:11.440] Yeah. [36:11.810 --> 36:13.110] So, that's pretty much what I had on the PTC. [36:13.460 --> 36:14.850] Are we having questions later? [36:15.040 --> 36:16.230] Probably not because we... [36:16.230 --> 36:20.480] Probably not going to be able to have questions because, you know, we only had 45 minutes. [36:20.900 --> 36:21.550] I'm very glad to hear about that. [36:21.790 --> 36:24.330] But, I'm going to see if there's anything useful from... [36:25.030 --> 36:27.290] That looks good for our graphing that we were doing. [36:30.590 --> 36:30.920] Yeah. [36:31.110 --> 36:31.440] We've... [36:31.830 --> 36:35.520] We've had sort of sketchy volunteers over the last few years. [36:35.520 --> 36:39.670] If anybody wants to volunteer now for the one in two years, we could use you. [36:40.230 --> 36:40.630] Especially... [36:40.630 --> 36:42.330] We need a graphic designer big time. [36:42.540 --> 36:46.940] So, if somebody's really good at graphic design and wants to help us out for the next session... [36:46.940 --> 36:47.130] All right. [36:47.230 --> 36:48.540] Come on up after the thing. [36:48.670 --> 36:50.020] We need a graphic designer big time. [36:51.190 --> 36:51.690] All right. [36:51.810 --> 36:55.420] So, like I was saying before, we did get MRTG doing some graphing. [36:55.650 --> 36:58.250] And it's going to be a little bit skewed because for... [36:58.250 --> 37:01.090] Up until about an hour ago, we were pushing about 10 megabit. [37:01.380 --> 37:03.020] And so, that's all that... [37:03.020 --> 37:04.230] This is... [37:04.230 --> 37:04.750] Throughout the... [37:06.210 --> 37:07.960] Throughout the conference, we had about 10 megabit. [37:08.130 --> 37:10.130] And then we fixed the problem. [37:10.310 --> 37:11.070] And that's this. [37:11.550 --> 37:13.710] So, the graphs don't look that good. [37:14.350 --> 37:22.630] But it did show that we did pretty much come close to fully utilizing our bandwidth for, you know, the pleasure of Pyro who got us the Internet connection. [37:24.330 --> 37:27.130] And let's see what our DSL looked like. [37:29.670 --> 37:31.670] And we have pretty much... [37:31.670 --> 37:32.520] I don't know... [37:32.520 --> 37:33.670] That can't be right. [37:34.310 --> 37:38.190] How do we put out 72 megabit over our DSL? [37:38.540 --> 37:39.330] That doesn't sound right. [37:39.630 --> 37:42.130] Actually, I think that was when our... [37:42.670 --> 37:43.000] Okay. [37:43.070 --> 37:43.980] That's not actually accurate. [37:44.210 --> 37:46.550] I think I'm graphing the wrong link on that one. [37:46.730 --> 37:49.290] That one is the link to our internal network. [37:49.830 --> 37:51.020] And it's mislabeled. [37:51.570 --> 37:53.000] Let me see if... [37:56.840 --> 38:00.320] I think we were actually trying to push out that much bandwidth and it couldn't. [38:00.420 --> 38:01.880] I don't know why that looks like that. [38:02.220 --> 38:08.600] But pretty much until that spike that hit 72 megabit, we were averaging about 3 megabit a second. [38:08.880 --> 38:10.120] So, yeah, great graphs. [38:10.320 --> 38:16.280] I guess maybe what I'll do is I'll clean up the RRD files and, you know, just take it up until about 4 p.m. [38:16.340 --> 38:19.020] And maybe it will look a little bit better. [38:19.200 --> 38:20.940] I do have one question for the crowd, actually. [38:20.940 --> 38:26.280] One of the things we had planned for this year and didn't end up pulling off were VGA... [38:26.280 --> 38:28.180] Instead of monitors, VGA goggles. [38:28.940 --> 38:30.320] So, we're thinking about that for next year. [38:30.460 --> 38:32.720] Show of hands, who would use the VGA goggles? [38:33.020 --> 38:34.100] Who would attract them to... [38:34.800 --> 38:37.680] VGA goggles would attract you to the public thermal cluster to use it? [38:38.280 --> 38:40.880] Would you worry about who might have used the goggles beforehand? [38:41.600 --> 38:42.360] Anything like that? [38:42.540 --> 38:42.620] Alcohol-wise. [38:42.860 --> 38:43.460] Alcohol-wise. [38:43.600 --> 38:43.720] Okay. [38:43.860 --> 38:44.460] Excellent idea. [38:45.260 --> 38:46.540] Guys are doing great already. [38:47.420 --> 38:50.920] So, VGA goggles will be one of the things on deck for next time. [38:52.660 --> 38:54.620] And we have one more thing. [38:54.920 --> 38:55.360] Some eye candy. [38:56.440 --> 38:58.940] Let's use this as a slide show and hope it comes out. [38:59.480 --> 38:59.640] All right. [38:59.960 --> 39:00.900] So, drag on. [39:01.680 --> 39:13.280] The plan had been to get these set up on projectors but due to some iOS switch version problems and the router already being tanked, we couldn't get the span ports going and I didn't want to run tcpdump on a router that was barely working to begin with. [39:13.280 --> 39:18.040] But this shows our IP space, the Internet IP space and the port. [39:18.960 --> 39:24.520] Right after or right before we took the screenshot you can see someone port scanned the entire con space probably on port 80. [39:25.000 --> 39:28.980] And then we also mapped all the connections coming in and out and what city they went to. [39:31.420 --> 39:41.000] So, next time with more planning, which I wasn't able to do, I'll try to get somebody specifically dedicated to getting the visualization set up. [39:41.120 --> 39:45.180] Because this is a lot of great work but unfortunately nobody got to see it until now. [39:45.180 --> 39:47.860] And if you could actually barely, I don't know if you guys could see it well enough. [39:48.000 --> 39:50.060] But, yeah, next time we'll try to get that done better. [39:50.600 --> 39:51.340] I know the guy who does this. [39:52.240 --> 39:52.800] All right. [39:53.680 --> 39:54.520] Do you want to say something else? [39:55.560 --> 39:56.040] Oh, yeah. [39:56.180 --> 39:56.580] I know the guy. [39:56.740 --> 39:58.720] This was made by Steven. [40:00.240 --> 40:02.840] A dude who works at one of the national laboratories. [40:03.100 --> 40:03.340] Oh, God. [40:03.440 --> 40:04.380] Actually it's a copy of his. [40:04.500 --> 40:05.320] He never released his copy. [40:05.320 --> 40:05.700] It's a copy of his? [40:05.780 --> 40:06.320] He never released it? [40:06.400 --> 40:06.480] Really? [40:06.660 --> 40:07.240] He never released it. [40:08.200 --> 40:10.580] The program is called The Spinning Cube of Potential Doom. [40:11.240 --> 40:11.800] And he... [40:11.800 --> 40:12.240] What's his name again? [40:13.000 --> 40:13.560] Cube of Doom. [40:13.560 --> 40:14.040] Yeah. [40:14.260 --> 40:14.940] Spinning Cube of Potential. [40:15.320 --> 40:16.570] But it was written by... [40:17.180 --> 40:17.480] What's his name? [40:17.620 --> 40:18.260] Who works for the... [40:18.260 --> 40:18.560] Steven. [40:20.140 --> 40:20.500] Steven. [40:21.620 --> 40:22.820] Someone whose name... [40:22.820 --> 40:23.160] I can't remember. [40:23.480 --> 40:25.380] Anyway, he works for the government. [40:25.560 --> 40:26.320] He never released a code. [40:26.480 --> 40:27.520] So I just reimplemented it. [40:27.640 --> 40:28.900] It's about 500 lines to see. [40:29.780 --> 40:30.120] Yeah. [40:30.480 --> 40:32.020] So I had one other thing. [40:32.220 --> 40:34.580] So my lieutenant this year is a guy named Sparks. [40:35.000 --> 40:35.560] Hey, Sparks. [40:35.620 --> 40:35.960] Are you there? [40:39.120 --> 40:40.980] I'm going to put you on the microphone here. [40:41.080 --> 40:42.240] There's about 300 people listening to you. [40:42.300 --> 40:44.140] Do you want to say anything else about the public terminal cluster? [40:44.140 --> 40:46.360] We just gave a small presentation on how it was. [40:49.920 --> 40:50.360] Something? [40:55.960 --> 40:57.420] Have you got anything to report? [41:02.640 --> 41:03.080] Sparks? [41:04.620 --> 41:05.380] Any of you now? [41:06.080 --> 41:06.740] Smart guy. [41:07.640 --> 41:08.080] Awesome. [41:08.480 --> 41:14.420] You must have something to say about the cluster, how it's working, what you think of it, how much fun it was to set it up. [41:14.940 --> 41:20.660] It was fun to work on it and, you know, try to figure out what was going on with it and why it wasn't working. [41:22.220 --> 41:25.360] I don't think there's any point when it wasn't working, right? [41:27.680 --> 41:30.420] Well, the terminals themselves weren't working. [41:33.400 --> 41:37.800] Yeah, we're having some reception problems with Mike, so we'll talk to him later. [41:43.130 --> 41:50.230] So, I'll be putting up the router configs, the Visio diagram, all that other stuff on my web page. [41:50.470 --> 41:55.130] If you can remember, it'll probably be like, I think we have it from the last conference. [41:55.910 --> 41:59.770] Like, that's the Visio from the last conference. [41:59.770 --> 42:01.970] So, I'll put it up in a similar directory. [42:03.550 --> 42:05.030] And, oh yeah, there's the Knox staff. [42:07.090 --> 42:08.770] That was right before we tore it down. [42:09.070 --> 42:13.510] And that's the team from last conference. [42:13.590 --> 42:17.410] A lot of the same people were there, like El Cruz and Al Porkchop. [42:18.270 --> 42:19.590] And I don't know where you guys are. [42:20.290 --> 42:22.230] Anyway, oh, look, there's Hitman. [42:23.530 --> 42:24.890] So, last year he was pretty helpful. [42:26.290 --> 42:27.390] So, let's see what else. [42:27.390 --> 42:30.590] And I'll just put the same, you know, same documents up on my website. [42:30.630 --> 42:36.430] If anybody's actually interested in finding that stuff, I'll probably post the URL to the wiki so you can get access to the, you know, configs and whatever. [42:36.890 --> 42:38.250] And I think that's about it for me. [42:38.450 --> 42:38.910] Anything else? [42:39.530 --> 42:40.330] Nope, nothing here. [42:40.870 --> 42:42.630] And we're just about out of time. [42:42.790 --> 42:44.330] So, if you have any questions, you can email us. [42:44.490 --> 42:46.610] It's pretty easy to find out, find us. [42:46.810 --> 42:51.670] So, or you can just, you know, I don't think we'll have time to talk tonight because we have to tear down everything now. [42:51.830 --> 42:53.130] So, but that's about it. [42:53.230 --> 42:53.790] Thanks for your time.