FCS Network: Difference between revisions

From Free Geek Seattle
No edit summary
No edit summary
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
This will need an upgrade at some point. Make this a project page.
[[Category:Infrastructure]] [[Category:Projects]] [[Category:Unfinished]]
 


This page is about the network at [[FCS]]
This page is about the network at [[FCS]]
Line 5: Line 6:
=Wireless network=
=Wireless network=


Various wireless network SSIDs exist there. The one we use for the Lab is FCSTMC-LAB1
We have our own wireless ESSID in the lab. It is Freegeek / password Seattle iirc.
and the password is on the whiteboard.
 
Here is my ifconfig after connecting.
 
<pre>
wlan0    Link encap:Ethernet  HWaddr b8:76:3f:d2:95:68 
          inet addr:172.16.3.54  Bcast:172.16.3.255  Mask:255.255.255.0
          inet6 addr: fe80::ba76:3fff:fed2:9568/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:119 errors:0 dropped:0 overruns:0 frame:0
          TX packets:152 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:12622 (12.6 KB)  TX bytes:21644 (21.6 KB)
 
</pre>


 
Our netblock is 192.168.10.0/24 - if you have an IP address outside of this, then you're on the wrong network. Please let us know if this happens.
* IP/Netmask: 172.16.3.54/24
* Gateway: 172.16.3.1
* DNS Server: 172.16.3.1


=Wired Network=
=Wired Network=


There is one Ethernet jack in the lab room. It is under the table on the south wall. The other RJ-17 jacks in the room are telephone only.
There are two Ethernet jacks in the lab room. One is under the table on the south wall, the other behind the table where the admin workstation sits. The other RJ-17 jacks in the room are telephone only.
 
The Ethernet jack is connected to a switch on the same table. Each of the tables has a switch on it, daisy-chained via their uplink ports as follows:


North table ([[Intake]] and [[Eval]]) -> East table ([[Build]]) -> South table ([[QA]]) -> Wall jack
The Ethernet jack is connected to a 24-port Cisco switch on the same table.


This means that there's an ethernet cable trailing across the floor between the North and East tables. Please be careful of it, it's a trip hazard! We're looking for a rug or other covering to place over it.
Please be careful of cables on the floor. It's a trip hazard! Please remember to clean up after your cabling, otherwise people can get hurt.


Eventually we will have our own subnet, firewalled from the FCS network. After all, we don't want to provide [[DHCP]] to the [[FCS]] network, that would be bad ;^). We need to provide [[DHCP]] on our own segment for [[LTSP]] to work. Also, a learning network with a firewall, services, etc. is something we will need.
Our subnet is firewalled from the FCS network. After all, we don't want to provide [[DHCP]] to the [[FCS]] network, that would be bad ;^). We need to provide [[DHCP]] on our own segment for [[Install Server]] to work. Also, a learning network with a firewall, services, etc. is something we will need.

Latest revision as of 16:56, 27 February 2015


This page is about the network at FCS

Wireless network[edit]

We have our own wireless ESSID in the lab. It is Freegeek / password Seattle iirc.

Our netblock is 192.168.10.0/24 - if you have an IP address outside of this, then you're on the wrong network. Please let us know if this happens.

Wired Network[edit]

There are two Ethernet jacks in the lab room. One is under the table on the south wall, the other behind the table where the admin workstation sits. The other RJ-17 jacks in the room are telephone only.

The Ethernet jack is connected to a 24-port Cisco switch on the same table.

Please be careful of cables on the floor. It's a trip hazard! Please remember to clean up after your cabling, otherwise people can get hurt.

Our subnet is firewalled from the FCS network. After all, we don't want to provide DHCP to the FCS network, that would be bad ;^). We need to provide DHCP on our own segment for Install Server to work. Also, a learning network with a firewall, services, etc. is something we will need.