Chapter 11 / 17

Network

The Gennevilliers office runs two separate networks on one cabling plant. The distinction matters for day-to-day work.


Data network (192.168.0.x) — this is where work happens.

Key hosts:

  • NAS (SAUVE_DISK) at 192.168.0.17 — holds all Sodiwin file exports and office file shares. The nightly Sodiwin dump lands here at 02:30.
  • Sodiwin server at 192.168.0.88 — the ERP. Treated as a black box; nothing connects to it directly.
  • Framework Desktop (arriving this week) — goes into the server-room rack switch at gigabit speed.

Connect to the sodimo_wifi wireless network to reach the NAS and infrastructure from a laptop. Some wall ports in the office are wired to the wrong network — verify with sodimo_wifi if in doubt.


VoIP network (192.168.1.x) — phone system only. Cannot reach the NAS. Do not plug AI equipment into a VoIP wall port.


Tailscale:

The Framework Desktop, the NAS, Thomas’s laptop, Rani’s laptop, Paul’s workstation, and Jack’s workstation are all on a private overlay network. This means Thomas can reach the office server from anywhere, Paul can reach it from home, and Rani’s laptop has a direct connection to the Framework Desktop’s AI services regardless of which office network he is on.


ISP items (Jack’s ticket):

A static public IP address, PTR record delegation, and port 25 access are all pending from the ISP. These three items are the critical path for the email migration. Jack owns the ticket.

Search uses Pagefind — available after npm run build.