Score:0

Is there a de-facto 'standard' for the gateway address on a LAN

cn flag

Is there a de-facto 'standard' for the gateway address on class C subnets?

Asking because I've been fighting a docker-compose issue with macvlans where it assumes the gateway is always at 192.x.x.1, while the actual gateway is 192.x.x.251

Score:1
us flag

Technically it can be whatever you want and no standards impact it bar any in an organisation.

In practice its almost always .1, sometimes .254 or one of the others above 250, but its noticeably rare for it to be not be .1.

I'd guess 90%+ are .1

For your docker-compose issue I believe the below will work, taken from: https://forums.docker.com/t/how-do-i-attach-a-macvlan-network-and-assign-a-static-ip-address-in-compose-file/107419 and not tested by me.

networks:
  vlan:
    driver: macvlan
    driver_opts:
      parent: eth0
    ipam:
      config:
        - subnet: "192.168.0.0/24"
          ip_range: "192.168.0.64/26"
          gateway: "192.168.0.1"
cn flag
Thanks. FYI it seems there's a docker compose issue open on this still https://github.com/docker/compose/issues/6569
Sam Foley avatar
us flag
@Roddy oh yeah didn't see that one, looks like its resolved and working and the open issue is just a code fix though!
mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.