Network Topology

From Comp519

Jump to: navigation, search

Contents

Overall Network Layout

Hosts Accessible from Comp519

These computers are not accessible from the Internet. They are only accessible after you have logged in to comp519, as they all have private IP addresses. The name column is the symbol host name (set in /etc/hosts), and you can use it directly, e.g. "ssh -Y netfpga01".

IP Name Comments
192.168.0.202 netfpga02 NetFPGA system - Group 2
192.168.0.203 netfpga03 NetFPGA system - Group 3
192.168.0.204 netfpga04 NetFPGA system - Group 4
192.168.0.205 netfpga05 NetFPGA system - Group 5
192.168.0.206 netfpga06 NetFPGA system - Group 6
192.168.0.2 server1 Class server
192.168.0.3 server2 Class server
192.168.0.4 server3 Class server


Network Layout for NetFPGA Hub / Switch

For the purpose of this example, we focus on machine #1 which uses the octet 201 in all of its addresses. Other machines use 202, 203, 204, etc...

Description IP (Decimal) IP (Binary ) Netmask (Decimal) Netmask (Binary)
Server-1 port (connects to NF) 10.143.201.2 00001010 10001111 11001001 00000010 255.255.255.0 11111111 11111111 11111111 00000000
Server-2 port (connects to NF) 10.143.201.66 00001010 10001111 11001001 01000010 255.255.255.0 11111111 11111111 11111111 00000000
Server-3 port (connects to NF) 10.143.201.130 00001010 10001111 11001001 10000010 255.255.255.0 11111111 11111111 11111111 00000000
Cisco port (connects to NF) 10.143.201.194 00001010 10001111 11001001 11000010 255.255.255.0 11111111 11111111 11111111 00000000

In the binary representation of the IP address, bits that are part of the subnet address are shown in bold. Bits that are the host address are normal. Note that all addresses in this configuration are on the same subnet. This is appropriate for a hub or a switch, as the machines are all on the same Ethernet segment and therefore should all be on the same subnet. In this configuration, the NetFPGA ports do not have IP addresses, as switches and hubs do not have addresses.

Network Layout for NetFPGA Router

For the purpose of this example, we focus on machine #1 which uses the octet 201 in all of its addresses. Other machines use 202, 203, 204, etc...

Description IP (Decimal) IP (Binary ) Netmask (Decimal) Netmask (Binary)
NF port (connects to Server-1) 10.143.201.1 00001010 10001111 11001001 00000001 255.255.255.192 11111111 11111111 11111111 11000000
Server-1 port (connects to NF) 10.143.201.2 00001010 10001111 11001001 00000010 255.255.255.192 11111111 11111111 11111111 11000000
NF port (connects to Server-2) 10.143.201.65 00001010 10001111 11001001 01000001 255.255.255.192 11111111 11111111 11111111 11000000
Server-2 port (connects to NF) 10.143.201.66 00001010 10001111 11001001 01000010 255.255.255.192 11111111 11111111 11111111 11000000
NF port (connects to Server-3) 10.143.201.129 00001010 10001111 11001001 10000001 255.255.255.192 11111111 11111111 11111111 11000000
Server-3 port (connects to NF) 10.143.201.130 00001010 10001111 11001001 10000010 255.255.255.192 11111111 11111111 11111111 11000000
NF port (connects to Cisco ) 10.143.201.193 00001010 10001111 11001001 11000001 255.255.255.192 11111111 11111111 11111111 11000000
Cisco port (connects to NF) 10.143.201.194 00001010 10001111 11001001 11000010 255.255.255.192 11111111 11111111 11111111 11000000

Again, in the binary representation of the IP address, bits that are part of the subnet address are shown in bold. Bits that are the host address are normal. Note that in this configuration, the four NetFPGA ports are each on different subnets. The last 2 bits of the subnet address are different for each NetFPGA port. This is appropriate for a router, as each interface of a router has its own IP address and connects to a different subnet. In practice, the subnets do not need to be so closely related, but doing so simplifies the differences between the hub/switch configuration and the router configuration. Note that the machines connected to NetFPGA all retain the same IP addresses, they just have a longer subnet mask which places each of them on their own subnet.


NAT Translations

Server1 and one port on your router is directly accessible outside of the Rice network through a set of static NAT mappings created by Rice IT. All other IPs are only accessible from inside the Rice network.


Public IP Private IP (inside Rice)
168.7.208.37 10.143.202.66 (server1)
168.7.208.38 10.143.203.66
168.7.208.39 10.143.204.66
168.7.208.40 10.143.205.66
168.7.208.41 10.143.206.66
168.7.208.28 10.143.202.193 (NetFPGA port attached to Cisco router)
168.7.208.29 10.143.203.193
168.7.208.30 10.143.204.193
168.7.208.31 10.143.205.193
168.7.208.42∗ 10.143.206.193

Not a typo


Router Ports

The specified routers ports are connected to the following networks. Remember to use your group IP (e.g. 202-205) instead of the example shown (201).

Router Port Host (CPU) Port
(on local machine)
Network (Physical Device / IP) Cable Color
eth0 nf2c0 Server1 (10.143.201.2) and rest of 255.255.255.192 subnet Gray
eth1 nf2c1 Server2 (10.143.201.66) and rest of 255.255.255.192 subnet Blue
eth2 nf2c2 Server3 (10.143.201.130) and rest of 255.255.255.192 subnet Black
eth3 nf2c3 Cisco router (10.143.201.194), rest of 255.255.255.192 subnet, and public internet White


Views
Personal tools