Skip to main content

2026-03-27 - LixCon 2026 weekly

  • Date: 2026-03-27
  • Participants: raito,raito sinavir,(Lix/DGNum/AFNix), sinavir (DGNum), soyouzpanda (DGNum)
  • Topic: LixCon 2026 weekly

Call for Proposals (CfP)

  • Proposals received: 8-9
  • Core team talks and transactional conference talks (intro/outro, etc.) not included in the Pretalx
  • Some invited talks are pending, awaiting final approval
  • No issues anticipated regarding the current lineup.

Proposal review plan

  • 1 proposal already accepted for logistical reasons (travel support)
  • Review schedule:
    • Tonight: @raito reviews proposals
    • Tomorrow (or so): @kate reviews proposals
    • This weekend or Monday: converge on final proposals
  • Goal: complete review quickly to submit acceptance or rejections to our current proposals

Remarks

  • Overall proposals goes over the Friday talk budget but aligns with overall planning
  • No conference rooms required for Saturday and Sunday

Special attention AFNix general assembly room

  • Requires Internet setup for videoconference
  • Capacity: ~10–15 people

Postcards

  • Deadline for order 2 weeks before event; faster option: 1 week (+€2)
  • Kate is aligned with Monday deadline

Content

  • Decide back-of-card content:

    • Important information and emergency contacts
    • Room list / orientation tips
    • WiFi info (if a shorter deadline)

Assembling method Punch postcards without plastic coating

Inspiration: Good-to-Know PDF from UndoneCS 2026

Website

  • Let DGNum host this website: https://lixcon.dgnum.eu on their S3 (Garage) instead of AFNix except if AFNix redeploys it quickly

  • Announcement post email + Mastodon (high priority) β†’ owned by @raito

  • Content to finish

    • Schedule β†’ Pretalx widget
    • Venue info β†’ owned by @soyouzpanda
      • Rooms
      • Internet
    • Travel information
    • Physical Code of Conduct (LixCon/AFNix) β†’ owned by @raito
    • Cross check with https://www.undonecs.org/2026/ information to see if we are lacking something
    • Ideally: RSS feed
  • Optional: DNS CNAME https://con.lix.systems/2026/ β†’ main site (low priority)

Equipment rental

METRO refers to https://www.metro.fr/ here.

Fridges and Drinks

  • Drinks brought by @hexchen and our METRO provider
  • Suggested setup: 1–2 fridges in hacking rooms
  • Suggested: additional payment terminal purchase (SumUp Plus) as AFNix one might be used for other purpose
  • Deposit may apply to drinks, @sinavir will check with @hexchen directly

Snacks

  • METRO card available
  • A car can be lended by @sinavir
  • Which snack to buy / who will buy them β†’ Can AnaΓ«lle handle it?

Seating and tables

  • Cozy sitting (beanbags, etc.) for friendliness in hacking rooms β†’ owned by @sinavir
    1. Source price
    2. Determine quantity
    3. Propose quote
    4. Execute if approved

C3VOC equipment

  • Coordination for setup β†’ @raito connects @sinavir with @hexchen
  • Free parking at ENS: confirm dimensions and availability for the van

Room planning

  • Core team members to book tickets explicitly on Pretix for full visibility on DGNum β†’ owned by @raito
  • Expected variance: Β±10–20 people
  • Goals:
    • 3 public rooms
    • 1 non-public room
    • Release remaining rooms
  • More than 4 continuous rooms over the weekend is non-trivial
  • Final room list to be confirmed by @soyouzpanda and @sinavir
  • @raito wants to be kept in the loop and this topic should be discussed further next weekly

Network setup

  • Backbone v2 functional (Ielo uplink), deployed by @sinavir
  • Connect LixCon rooms to Internet: requires coordination with the school IT to switch VLAN on the Ethernet ports in the rooms, owned by @sinavir
  • Room setup: 1 switch and 1 AP per room min
    • 4 APs for the amphitheater
  • Multiple SSIDs (firewalled and non-firewalled, OWE)
    • Non-firewalled is not a priority
  • Forensics logging: DHCP leases and MAC/IPv6 via NDP as per law requires
    • IPv4 is already done in the current network
    • IPv6 will be new

Priorities

  1. Secure VLANs in rooms

  2. Secure hardware (APs, switches, cables)

    • Friday: 4 + 3 APs, 4 switches
    • Saturday: 6 APs, 3 switches
    • Sunday: 6 APs, 3 switches
  3. Configure router with forensic logging (DHCP + IPv6)

  4. Configure switches

  5. Configure APs

  6. Optional: non-firewalled SSID

lead by @sinavir, will delegate whatever he can to other folks

Next agenda

  • Room planning
  • Network setup
  • Commit to conference start/end information to communicate to our attendees
  • Approve the final operational details to send to our attendees