Project

General

Profile

Actions

Task #6648

closed

Task #6557: Rebuild the whole DCL infrastructure - aka place9

Configure (reset cleanly) a Mikrotik hapAC as a fiber2copper bridge, connect all servers with copper

Added by Nico Schottelius almost 5 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
-
Start date:
05/01/2019
Due date:
% Done:

0%

Estimated time:
PM Check date:

Description

  • Configure WiFi on it with essid = "place9"
    • save password in pass, place9-dcl-rebuild/mikrotik
  • Use it to bridge fiber2copper
  • Connect all servers to it / another "dumb" switch
  • Give it an IP address, :19 in the transfer network
Actions #1

Updated by Samuel Hailu almost 5 years ago

1 * Pinging from Client to router-internal

samuel@in-the:~$ ping 2a0a:e5c0:107:4::1
PING 2a0a:e5c0:107:4::1(2a0a:e5c0:107:4::1) 56 data bytes
64 bytes from 2a0a:e5c0:107:4::1: icmp_seq=1 ttl=64 time=2.67 ms
64 bytes from 2a0a:e5c0:107:4::1: icmp_seq=2 ttl=64 time=1.89 ms

--- 2a0a:e5c0:107:4::1 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 3ms
rtt min/avg/max/mdev = 1.885/2.277/2.670/0.395 ms

2 * Pinging from Client to router-external

samuel@in-the:~$ ping 2a0a:e5c0:107:4::2
PING 2a0a:e5c0:107:4::2(2a0a:e5c0:107:4::2) 56 data bytes
^C
--- 2a0a:e5c0:107:4::2 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 36ms

3 * Pinging from Client to upstream

samuel@in-the:~$ ping 2a0a:e5c0:1:7::18
PING 2a0a:e5c0:1:7::18(2a0a:e5c0:1:7::18) 56 data bytes
From 2a0a:e5c0:107:3::1: icmp_seq=1 Destination unreachable: Address unreachable
From 2a0a:e5c0:107:3::1: icmp_seq=2 Destination unreachable: Address unreachable
From 2a0a:e5c0:107:3::1: icmp_seq=3 Destination unreachable: Address unreachable

--- 2a0a:e5c0:1:7::18 ping statistics ---
5 packets transmitted, 0 received, +3 errors, 100% packet loss, time 74ms
pipe 3

4 * Pinging from another-device to upstream (another-device=another-network)

samuel@in-the:~$ ping 2a0a:e5c0:1:7::19
PING 2a0a:e5c0:1:7::19(2a0a:e5c0:1:7::19) 56 data bytes
64 bytes from 2a0a:e5c0:1:7::19: icmp_seq=1 ttl=63 time=1.83 ms
64 bytes from 2a0a:e5c0:1:7::19: icmp_seq=2 ttl=63 time=1.87 ms
^C
--- 2a0a:e5c0:1:7::19 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 2ms
rtt min/avg/max/mdev = 1.831/1.850/1.869/0.019 ms

5 * Pinging from another-device to router-external

samuel@in-the:~$ ping 2a0a:e5c0:107:4::2
PING 2a0a:e5c0:107:4::2(2a0a:e5c0:107:4::2) 56 data bytes
From 2a0a:e5c0:2:5::7: icmp_seq=1 Destination unreachable: Address unreachable
From 2a0a:e5c0:2:5::7: icmp_seq=2 Destination unreachable: Address unreachable
From 2a0a:e5c0:2:5::7: icmp_seq=3 Destination unreachable: Address unreachable
From 2a0a:e5c0:2:5::7: icmp_seq=4 Destination unreachable: Address unreachable

--- 2a0a:e5c0:107:4::2 ping statistics ---
4 packets transmitted, 0 received, +4 errors, 100% packet loss, time 69ms
pipe 4

6 * Pinging from another-device to router-internal
samuel@in-the:~$ ping 2a0a:e5c0:107:4::1
PING 2a0a:e5c0:107:4::1(2a0a:e5c0:107:4::1) 56 data bytes
From 2a0a:e5c0:2:5::7: icmp_seq=1 Destination unreachable: Address unreachable
From 2a0a:e5c0:2:5::7: icmp_seq=2 Destination unreachable: Address unreachable
From 2a0a:e5c0:2:5::7: icmp_seq=3 Destination unreachable: Address unreachable
--- 2a0a:e5c0:107:4::1 ping statistics ---
5 packets transmitted, 0 received, +3 errors, 100% packet loss, time 61ms
pipe 3

7 * Pinging from another-device to client
 
ping 2a0a:e5c0:107:3:ae53:a589:6106:5fd8
PING6(56=40+8+8 bytes) 2a0a:e5c0:2:5:a0b0:de4b:d56e:37f7 --> 2a0a:e5c0:107:3:ae53:a589:6106:5fd8

--- 2a0a:e5c0:107:3:ae53:a589:6106:5fd8 ping6 statistics ---
131 packets transmitted, 0 packets received, 100.0% packet loss

8 * Pinging from Client to another-device

 ping 2a0a:e5c0:2:5:a0b0:de4b:d56e:37f7
PING 2a0a:e5c0:2:5:a0b0:de4b:d56e:37f7(2a0a:e5c0:2:5:a0b0:de4b:d56e:37f7) 56 data bytes
^C
--- 2a0a:e5c0:2:5:a0b0:de4b:d56e:37f7 ping statistics ---
58 packets transmitted, 0 received, 100% packet loss, time 417ms
Actions #2

Updated by Samuel Hailu almost 5 years ago

  • Status changed from New to In Progress
Actions #3

Updated by Samuel Hailu over 4 years ago

  • Status changed from In Progress to Resolved
Actions #4

Updated by Nico Schottelius over 4 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF