Skip to content

Conversation

Copy link
Contributor

Copilot AI commented Dec 29, 2025

Adds documentation for using proxy ARP on a Linux gateway to provide external connectivity to lab devices without NAT or routing protocols, as discussed in #2861.

Changes

  • New section: "Using Proxy ARP for External Connectivity" in docs/example/external.md
    • Solution overview with 192.18.42.0/24 example subnet
    • Sample topology with Linux gateway node and external uplink
    • User defaults configuration via netlab defaults command
    • Linux server proxy ARP setup commands

Example Topology

defaults.device: eos

nodes:
  gw:
    device: linux
    role: gateway
  r1:
  r2:

links:
- gw:
    ipv4: 192.18.42.1/24
  r1:
    ipv4: 192.18.42.10/24
  r2:
    ipv4: 192.18.42.11/24
  clab:
    uplink: eth1

Configuration Commands

# Configure addressing pool
netlab defaults --user addressing.external.ipv4=192.18.42.0/24
netlab defaults --user addressing.external.start=10

# Enable proxy ARP on gateway
sudo sysctl -w net.ipv4.conf.eth1.proxy_arp=1
sudo ip route add 192.18.42.0/24 dev eth2
sudo sysctl -w net.ipv4.ip_forward=1
Original prompt

Based on discussion in #2861, add a new section to docs/example/external.md to describe this approach. The section should include a brief overview of the solution (assuming 192.18.42.0/24 is the external subnet), a sample lab topology, the recommended changes to user defaults (use "netlab defaults" command to make them) and the proxy arp configuration on the Linux server


✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

Copilot AI changed the title [WIP] Add documentation for external subnet approach Add proxy ARP external connectivity documentation Dec 29, 2025
Copilot AI requested a review from ipspace December 29, 2025 08:26
Copy link
Owner

@ipspace ipspace left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Mostly incorrect, but a starting point. Makes no sense to try to squeeze more out of Copilot, it's obviously not capable of figuring out the gist of that discussion

@ipspace ipspace marked this pull request as ready for review December 29, 2025 15:11
@ipspace ipspace requested a review from ssasso December 29, 2025 15:11
@ipspace
Copy link
Owner

ipspace commented Dec 29, 2025

@ssasso -- I asked GH Copilot to summarize your ideas from #2861. Even though I didn't expect much, the results were still underwhelming. However, I used them as a starting point for what might be useful.

Would love to hear your feedback on the final version of the documentation (no rush though)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants