Hey guys, so as some of you already know, I’ve started moving out of the IT world. I have taken control of a large nonprofit.
Anyway - I need routing help. I have my existing Intrus Technologies subnet (172.102.241.56/29) and I’ve been given a second subnet for my new company. (172.102.241.8/29)
The subnets are on the SAME wan ethernet port. Issue is this: I can’t seem to get the router to accept the new subnet. Has anyone else done this before and have an idea of what needs to be done?
When you say “…I can’t seem to get the router to accept the new subnet…”, what exactly do you mean. Do you get error when you add the IP on WAN interface, does it accept the address but routing not working, etc…
Please provide more details on what you have done and the symptoms you are getting
Your ISP is statically routing the 2nd subnet down to you via the 1st.
Your ISP put the 2nd subnet inside the same L2 domain as your current WAN configuration.
(or 3: They want you to peer with them with a routing protocol, but you probably would have known that)
For 1, you need to know if the 2nd subnet is routed to your WAN IP inside the first subnet, which would be static routing of subnets. You would put the new /29 on the “bottom” of your router. This is exactly what I do at work.
For example, my “ISP” (really internal network dudes) routes a boatload of /23 subnets down to my WAN IP inside of a /29 that we (me and ISP) use to connect to each other. So my IP address I use to face them in this WAN /29 is a routing target they use for subnets they route to me. I then use those subnets on the “bottom” (non WAN) side of the router, and my default gateway is their address inside of the /29. And life is good. No routing protocols to deal with.
For 2, you would just put an address from inside of your 2nd subnet on the same WAN interface, and routing down below that is up to you. I would probably put a separate downstream interface on the new /29 and that now becomes the “ISP” connection to the 2nd network. Then put another router below that to handle whatever the network layout will be for your new gig.
OKay, after hour of me going mad, it’s now working.
Turned out the ISP routed the new subnet to the wrong switch port. When I needed more rack space, I was moved to an empty rack. When I asked for the new subnet, they routed it to the switch port in the old rack instead of the new rack.