Comment 2 for bug 969422
Revision history for this message
| Mathieu Trudel-Lapierre (cyphermox) wrote | #2 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
7020100
(Get the code!)
Indeed, confirming: the gateway is "correctly" marked as mandatory since it is for most connection setups.
As a workaround you may want to use "Link-local only" if both systems don't need to be using a specific IP address -- the IP will be defined automatically by avahi/zeroconf, and both systems should be reachable by name via the ".local" domain (as per avahi again, and M-DNS). For instance:
ssh pc1.local (from pc2)
ssh pc2.local (from pc1)
And both would have an IP address in the 169.254.0.0 range, selected randomly by the software on each system.
Otherwise you'll need to use a "dummy" gateway. If you really need to avoid having the gateway set as default and override wifi, for example; then you can check the "Use this connection only for the resources on its network" checkbox under Routes.
Since this was explicitly done as a conscious decision to avoid issues with users who may not have a strong knowledge of networking; I'll close this as Won't Fix. We can revisit and reopen as necessary and once discussion has been done with upstream.