WAN IP on Switch?

Apachecow

Reputable
Jul 14, 2015
5
0
4,510
I work for a department at a technical college. I came in as part of a grant to help with general tech support. Of course, I ended up taking care of a network that someone else created and left ZERO documentation on. My knowledge on larger networks is limited.

We have a dedicated Internet connection that comes in through the same leased switch that the main campus network comes through. From that leased switch, an ethernet cable connects into an un-managed switch that belongs to the school that I cannot access without the main campus tech support staff. That switch converts the copper to fiber which is then jumped to another building on campus where our network is located. It comes in through a head-end room (that I have no access to) into another un-managed switch. There, we have one wall port connected to that switch which leads directly to the room where our firewall/router/main switch is located. That wall port plugs directly into the firewall, then router, then switch. I know it is far from the best set-up, but it's what we have to work with.

I've been here for about 7 months and I noticed the internet connection has always been a bit flaky. For the past month though, it has been really bad. We've found that if we reset the first un-managed switch that is connected to the ISP Switch, the connection tends to come right back up. For the past couple days, it has not. We tried swapping out that switch with another known good un-managed switch to see if it would work. Still nothing.

I called our ISP, and they gave me the IP scope for our connection. Our scope is X.X.X.138 through x.x.x.142. Our internal network is set up for the x.x.x.142 address. The ISP said that our first un-managed switch (the one directly connected to the ISP leased switch) must have one of the address in our scope for it's WAN interface that is not the same as the one our internal network uses.

How does that setup work? I wasn't aware that you could assign a switch a WAN IP!? If I assign that switch, let's say the x.x.x.138 address, wouldn't it pose an issue to the router that is plugged in down stream? It's public IP is setting on the x.x.x.142 address. How does the router know to pass through the switch? Can anyone help me understand!? Does anyone know a better solution?

Thanks!
 
Solution
switches typically are not assigned WAN IP but it's not impossible.
It is for unmanaged switches. They're a pure layer 2 device.

Interesting thing would be to try pinging each of your five IPs (this may need to be done from outside your network).
I don't think you can give an unmanaged switch any IP, let alone a WAN one.

I think the ISP is over-estimating the smarts of your switches. Or assuming that you don't know what you're doing and it's actually a router or firewall or something running NAT.

As best I can tell, you're simply using the switches as (slightly overkill) fibre-copper bridges.
 
U are correct, switches typically are not assigned WAN IP but it's not impossible. Whether WAN or LAN, an IP is an IP. By your description, sounds like your ISP comes in at a central point and are providing the campus with 5 WAN IP, and your department is assigned the 142. If this is a correct assumption then your department should not be touching the other 4 WAN IP at all.

Of course all of this is based on some guesses, you should really be synchronizing with the campus tech staff. Your responsibility should really start at the firewall and not beyond that with pieces that you have no access to.
 


They are definitely switches. Every one of them has the capability to be managed, but are, for some reason, being used as plug-n-play. Fiber-copper bridges are exactly what they are using all the extra switches for. Unfortunately, I have access to not one of them.
 


I receive 'Request timed out.' messages from internal network pings and pings from another network.