Wireless Networks Thread, Strange routing issue? in Technical; I've got an issue connecting to our Cachepilot box which is connected to one of our edge switches, and set ...
4th April 2011, 01:33 PM #1
Strange routing issue?
I've got an issue connecting to our Cachepilot box which is connected to one of our edge switches, and set to be connected to our server vlan.
Machines on all our edge switches can connect to it fine, in any of the different VLANs in place. Other servers can connect to it fine, and they're connected to the core switch and in the server vlan, the same as the cachepilot.
No pinging, no traceroute. Nowt.
If I put my desktop machine in the servers vlan, it works fine.
The subnet masks are all correct too, so it isn't that.
I'm at a bit of a loss!
4th April 2011, 01:55 PM #2
I cant really see what the problem is here?
Do you mean that its just your machine that cant connect?
4th April 2011, 02:10 PM #3
All machines connected to our core switch and aren't in the server vlan cannot connect. But all machines on other switches, on othert VLANs can connect.
So, the core switch is routing between the vlans for this unit for edge switches, but not for itself.
4th April 2011, 02:11 PM #4
what can't connect? The clients?
Possibly a windows firewall misconfig?
Windows Firewall > exceptions > Custom list of domains.
You can set in Group Policy..
4th April 2011, 02:13 PM #5
All clients on the core switch, that aren't in the server vlan. No firewalls are enabled.
4th April 2011, 02:45 PM #6
When you say connect you mean as in a WEB GUI or as in just being able to ping / traceroute etc ?
Only asking as wondering if proxy settings has anything to do with it ?
It's not just the port on the switch you have your machine connected to thats duff or maybe mis configured ??
4th April 2011, 03:39 PM #7
I mean all connectivity. Not just web, so proxy has nothing to do with it.
And the ports are fine on the switch, as it'd mean 40+ of them were duff, on multiple modules. So, very unlikely.
4th April 2011, 04:10 PM #8
How are you routing between the VLAN's? Do you have an ACL somewhere only defining inter-vlan communication for specfiic protocols/IP's to route to the server VLAN?
4th April 2011, 04:13 PM #9
Inter-Vlan routing is done by our core switch, a HP Procurve 5406zl. There are no ACLs in place, other than some rules to enable some broadcast traffic to traverse the VLANs (for ABTutor Control). So, all inter-vlan traffic is permitted.
Originally Posted by AJT1
5th April 2011, 01:58 AM #10
Sounds like your VLAN config on the core switch, are the workstations on the core in the same VLAN as the clients on the edge switches, if not are they setup into another (non-default) VLAN with the same routing rules?
5th April 2011, 09:15 AM #11
Yup, same VLAN. The core vlan tables are the same as the edge switches. Everything else works across them, just not this one cachepilot box.
Originally Posted by SYNACK
All vlans are basically identical, just with different names and different IP address ranges.
I've attached the core config and the edge config so you can see. I can't see anything that could cause this.
Edit: the cachepilot is on port 24 of the edge switch there, and my machines are on C23 and D11 of the core.
Last edited by localzuk; 5th April 2011 at 09:19 AM.
5th April 2011, 11:45 AM #12
Not sure about the config as I am more used to cisco, where are the ports assigned to the VLANs. Anyhow I was just wondering how the routing back from the cachpiolet is sorted. Is it a bunch of static routes or are you grabbing advertised routing information from the core using something like RIPv2.
Have you tried creating another VLAN for the systems on the core switch with a different address space to see if that allows routing to take place.
I guess the other thing to check is the firmware level on the core, maybe a bug in the core routing that could have been fixed in a later revision although I expect that you probably have the latest firmware on there anyhow.
5th April 2011, 11:49 AM #13
I'm not sure what you mean regarding the routing. It is simply a normal 'computer' so nothing special happens routing-wise.
I've not tried anything which requires a restart of the core yet - Ofsted in today, so not willing to fiddle...
The core is on the latest firmware. Edge switches aren't.
5th April 2011, 12:09 PM #14
The cachepiolet connects to the internet right and acts as a proxy?
If it has a default route that points out to the interent it means that if you do any internal routing (which you do) it means that the cach piolet is not diretly connected to all the internal subnets and so does not know about them, in order to respond to them it would try to send the reply via its default gateway (the internet). The way around this is to tell the proxy about the internal networks and give it a route to get to them (the internal core router address). You can do this manually via static routes on the box or automagicly by advertising the routes from the core via a routing protocol like RIPv2(need v2 as you are using CIDR).
If one of these static routes in the proxy was a little screwy then it could cause issues like this.
I may have misunderstood the situation so could be off on a tangent though.
5th April 2011, 12:10 PM #15
No, we don't use it as a proxy. It is used for hosting Channel 4 Learning stuff (clipbank and espresso). So, it is a web server basically, which automatically pulls data from them and caches it.
By speckytecky in forum Windows
Last Post: 12th January 2011, 03:16 PM
By CHR1S in forum Hardware
Last Post: 3rd March 2010, 11:08 AM
By timlineuk in forum Internet Related/Filtering/Firewall
Last Post: 3rd February 2010, 02:59 PM
By richard in forum Windows
Last Post: 6th December 2007, 10:16 AM
By edie209 in forum Windows
Last Post: 3rd July 2006, 02:15 PM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)