<br><span style="color: rgb(0, 0, 153);">Hi Greg,</span><br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>One key questions: Will you have one DSL line or two going in to the<br>
school?</blockquote><div style="color: rgb(0, 0, 153);">>> I think we will have one line going into the school. Internet connection is somewhat expensive, but are pretty reliable, with decend bandwidth, and it rarely goes down. <br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br><br>On your network diagram <a href="http://blog.olenepal.org/index.php/archives/138" target="_blank">http://blog.olenepal.org/index.php/archives/138</a><br>
a few comments:<br><br>1 - It looks all wireless in the school. It may be better to add a hub<br>and cables between wireless AP, XS and Squid. I think that's the<br>recommended design. Just get a good hub and have a back up. I hate it<br>
when the cheapest box in the design fails and brings the whole network<br>down! Could be you don't want to pull cables in the school and that's a<br>reason to go wireless.</blockquote><div><span style="color: rgb(0, 0, 153);">>>My mistake :(. All the connections are wired excpet the network provided by the wireless router (which i have not shown) and the mesh created by the active antenna. Will correct that and update the post. Thanks for pointing that out.</span><br>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">A few things to test ASAP on that front. Can an XS connect to wireless<br>AP and Internet using WEP? Which wireless NIC will it use (active<br>
antenna or one on a USB port)? Same for the squid box.</blockquote><div style="color: rgb(0, 0, 153);">>>I think so. Both the XS and the XO can connect to the wireless router using WEP. XO's can easily do so, all you have to do is select that wireless network on the neighbourhood. I actually have wireless nic cards on both the XS and the Proxy boxes, they didnt work and I didnt put much work into making it work, but looks like a good ideas to make it do so. I will get that working and update you guys on it. <br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br><br>2 - The squid on its own box helps but you need to work out the network<br>between it and the XS. The main point is to ensure all traffic goes in<br>
this order:<br>XO <-> XS/default gateway <-> Squid <-> Internet</blockquote><div><span style="color: rgb(0, 0, 153);">>>Yeah, this configuration does that. If you look at the iptables lines that comes after the config file, it is prerouting all requests on port 80 to squid from XS to cache to the internet. THe XO always talk to XS inside the mesh so all their request is heding down port 80 of the XS.</span><br style="color: rgb(0, 0, 153);">
<span style="color: rgb(0, 0, 153);">>>I guess i can add more for forward packets and for other ports, but yeah it handles that.</span><br style="color: rgb(0, 0, 153);"><span style="color: rgb(0, 0, 153);">>>I tested the whole structure and it works. My bad for not including the log files from squid. It would have made things more clear( but they were very long :))</span><br>
</div><div><br><span style="color: rgb(0, 0, 153);">>> best,</span><br style="color: rgb(0, 0, 153);"><span style="color: rgb(0, 0, 153);">>>Sulochan </span><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
________________________________<br><div class="Ih2E3d"><br>From: sulochan acharya [mailto:<a href="mailto:sulochan@gmail.com">sulochan@gmail.com</a>]<br></div>Sent: Tuesday, February 12, 2008 1:14 PM<br>To: Greg Smith (gregmsmi)<br>
<div class="Ih2E3d">Subject: Re: [Server-devel] Nepal Server Open Issues<br><br><br><br></div><div><div></div><div class="Wj3C7c">Hi Greg,<br><br><br><br><br> Here's what I see for phase 1:<br> - XS build 150 (unless Wad or someone else comes up with a must<br>
have<br> reason and stable build in time)<br> - No SSO (also means no Moodle tracking by student, grade or<br>group)<br> - 2 x XS servers<br> - No automated XO backup on XS<br><br><br>>> That sounds good :)<br>
<br><br><br><br> Let me know if you agree and we can revisit all in phase 2 with<br>a newer<br> XS build.<br><br> Still open questions on phase 1:<br> 1 - Network design.<br> I think we need this based on Wads comment it's the only one<br>
supported<br> for >150 Xos:<br> (ISP)-------------(hub)---------eth0 [XS] eth1 ------------<br>(WiFi)----[<br><br><br><br> XO ]<br><br>>>I agree this is a good network structure.<br>Please take a look at my blog post:<br>
<a href="http://blog.olenepal.org/index.php/archives/138" target="_blank">http://blog.olenepal.org/index.php/archives/138</a><br>Let me know what you guys think.<br><br><br><br><br></div></div></blockquote></div><br>