[–] 3 points 1 week ago

By adding a host, or /32, route to the gateway you should then be able to use it as the default gateway on your main subnet. I was not being serious when I suggested it, as another comment says, it's a pretty stupid idea, and there really isn't any sane usecase for it, except possibly one of those 1am "if it's stupid but it works it's still stupid, but it'll do until morning" type fixes that you shudder to recall years later.

  • source
  • parent
  • context
  • [–] 3 points 1 week ago

    The real nightmare when someone puts two ip addresses on the same host through different interfaces. Now that makes for some confusing troubleshooting and explanations in various applications.

    What really gets me is in about 3/4 networks in the last couple of weeks I've been asked to help troubleshoot, the problem has been duplicate IP addresses. I don't know what is going on with people...

  • source
  • parent
  • context
  • [–] 5 points 1 week ago (1 child)

    It can be made to work, just really really stupid.

    Ultimately the 'gateway' is really a mac address, and the IP is just the thing to ARP to get the mac address. And you can do some gnarly things to pull off things like off-subnet gateway addresses.

    You should never ever do it, but you can if you hate yourself enough.

    Becomes easier in IPv6 to do these shenigans too.

  • source
  • parent
  • context
  • I recently had a ticket for a university that had a /12 of public IPs. They gave every computer, printer, etc. a public IP on their whole network. Nothing has NAT. It was insane. They could buy an entire other university building with the money they'd make selling some of that address space down to even a /24.

  • source
  • parent
  • context
  • [–] 4 points 1 week ago (1 child)

    That’s mostly because it violates established standards, but you know that already. Lol.

    Hey, for all you know he might actually be the proper owner of that subnet.....

    I know if by some crazy coincedence I had that in my subnet I'd be using it for fun.

  • source
  • parent
  • context
  • That's another private range that was added for Carrier-Grade NAT that is part of RFC6598. It's a non-Internet routable 100.64.0.0/10 subnet for things like WISPs, Satellite providers like Starlink, Tailscale, and cellular providers that are strapped for IPv4 addresses.

  • source
  • parent
  • context
  • [–] 1 point 1 week ago (2 children)

    Your question is already answered here, but it also reduces traffic by keeping packets within a network defined by the subnet mask. It establishes guardrails so packet broadcasts aren't sent everywhere. The Internet is a single network. But not all of it can communicate with other parts without the right access permissions. Subnet masks are one very basic aspect of that access control.

  • source
  • parent
  • context
  • [–] 13 points 1 week ago (9 children)

    That's mostly because it violates established standards, but you know that already. Lol.

    Also, if you're talking to a network engineer, they probably have PTSD dealing with a client that did this with a 1.0.0.0/8 used internally or some shit and now huge swathes of the internet doesn't work, but somehow it's "our fault" that they can't load random web sites.

  • source
  • parent
  • context
  • [–] 5 points 1 week ago (1 child)

    Mostly to make the next sysadmin (or yourself in 6 months) weep. There's nothing preventing there being multiple IP subnets on a single network segment, but you'd usually handle that with separate VLANs, or at least an interface alias, so the machine saw both subnets. About the only reason I could see for just adding a static route would be if you're in the middle of reconfiguring your network to a new subnet but you still need the hosts you haven't updated to be able to route.

  • source
  • parent
  • context
  • view more: β€Ή prev next β€Ί