Attendance Gabriel, Roy
Date & Time 11/9/22, 1300-
Spaces Occupied Control room and Dome
Goals
- (Gabriel) Get DC to communicate with TCS via TCP/IP
Log
- Connected DC to TCS via gray ethernet cable. Saw changes in DC-reported
ipconfig before and after (see below). - We see that the new connections find MAC addresses and IPs, but we don't know where the IPs come from.
- We followed this tutorial https://www.maketecheasier.com/connect-two-windows-computer-on-lan/
- After the tutorial, T.C.S connects to D.C 0. With TCP/IP connection on, Zenmap detects host up on 192.168.0.2:5003 (IP address : port)
- A Wireshark scan confirms connection to T.C.S from D.C. and it also confirms packets are sent (converting hexadecimal output from wireshark to ASCII confirms command was sent)
The first 3 packets are the connection of the TCP/IP client to the TCP server. The rest are commands sent which seem to be successful, but they don't update the values in DFMTCS.
BIG NOTE:
It is very possible that the DFM software is bugging due to some change we made. Connecting to itself from T.C.S no longer works like it did previously. The DFMTCS logs confirm that DFMTCS detects both the connection from the client and the TCP packets/commands.
Connecting the T.C.S to the D.C and sending commands from D.C also doesn't work, however DFMTCS logs on the TCS confirm DFMTCS detects commands and connection again.
Other Notes
PORT STATE SERVICE
5003/tcp filtered filemaker
MAC Address: 00:18:7D:12:A1:D0 (Armorlink .Ltd)
Nmap done: 1 IP address (1 host up) scanned in 0.35 seconds
PORT STATE SERVICE
5003/tcp open filemaker
MAC Address: 00:18:7D:12:A1:D0 (Armorlink .Ltd)
Nmap done: 1 IP address (1 host up) scanned in 0.12 seconds
Changes in ipconfig
PS C:\Users\Director> ipconfig
Windows IP Configuration
Ethernet adapter Ethernet 2:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Ethernet adapter Ethernet 3:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Ethernet adapter Ethernet:
Connection-specific DNS Suffix . : umbc.edu
Link-local IPv6 Address . . . . . : fe80::ebf9:7f4d:cc98:6e41%11
IPv4 Address. . . . . . . . . . . : 130.85.72.207
Subnet Mask . . . . . . . . . . . : 255.255.255.128
Default Gateway . . . . . . . . . : 130.85.72.129
Wireless LAN adapter Wi-Fi:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : umbc.edu
Wireless LAN adapter Local Area Connection* 1:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Wireless LAN adapter Local Area Connection* 10:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
PS C:\Users\Director>
PS C:\Users\Director> ipconfig
Windows IP Configuration
Ethernet adapter Ethernet 3:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Ethernet adapter Ethernet:
Connection-specific DNS Suffix . : umbc.edu
Link-local IPv6 Address . . . . . : fe80::ebf9:7f4d:cc98:6e41%11
IPv4 Address. . . . . . . . . . . : 130.85.72.207
Subnet Mask . . . . . . . . . . . : 255.255.255.128
Default Gateway . . . . . . . . . : 130.85.72.129
Ethernet adapter Ethernet 2:
Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::3f1c:ada2:856c:6ce3%13
Autoconfiguration IPv4 Address. . : 169.254.135.211
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
Wireless LAN adapter Wi-Fi:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : umbc.edu
Wireless LAN adapter Local Area Connection* 1:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Wireless LAN adapter Local Area Connection* 10:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
PS C:\Users\Director>
You can see Ethernet2 is disconnected, then changes to have some config.