Routing on PowerConnect 6024

Question

Ok, so after 2 hours of experimenting I am convinced that I have no earthly idea what I am doing.

I would like to assign 10.0.0.197 to port 7. I will then be physically connecting a 10.0.0.0 network to port 7.

I have a server connected to port 8 with an IP address of 192.168.1.177.

I would like to be able to route any traffic sent to 10.0.0.197 through to 192.168.1.177. So, in other words if I ping 10.0.0.197 I am actually getting a response from 192.168.1.177.

Can this be done with CLI commands?

Adam N · Answer

Hi,

I am not sure what it is your trying to achieve. I am not sure why would you want a server to respond instead of the switch IP address?

Maybe if you could explain what you want to achieve I can try and recommend a way of implementing it.

Thanks

MGA Systems · Answer

Fair enough.
I think what I was trying to achieve is a NAT. Which when I went through the other posts I saw was not possible. So, then I started thinking: do I really need a NAT? I don't think so. This is what I am trying to accomplish:
I have a 6024 Switch in a CoLocation facility. I have two satellite offices with dedicated ethernet (fiber) lines coming into the 6024 switch. These offices use their own IP addressing scheme. Lets say one uses 10.0.0.0. We have a series of Servers at the CoLocation facility that use 192.168.1.0 as their network (both nets use 255.255.255.0). I wanted the people at 10.0.0.0 to be able to access the servers on the 192.168.0.0 network.

So, each office would come in on their own port (g6, g7). I want each of those ports to be able to access my servers but NOT each others networks.

How do I set this up?
It seems like it should be simple.
I have always used your switches in a relatively flat network topology so I am thin on routing with them. Once I have the routing in place, I am thinking I would use ACL's to provide some security.

1. Is this possible?
2. Can you provide a CLI example?

Thank you in advance for your help.

--Scott

DRNO10 · Answer

what you want to do should be simple, however i think the way you are trying to do it is not possible(via nat). This switch doesnt support nat(correct my if i am wrong).   Here is how i would do it if i was going to do it   Create 3 vlans   vlan 10 (10.10.10.0) network vlan 20 (192.168.1.0) network vlan 30 (10.10.20.0) network   setup an interface on each vlan   vlan 10 (10.10.10.1) vlan 20 (192.168.1.1) vlan 30 (10.10.20.1)   Now if you setup all the clients and servers to use those addresses as thier default gateway it should route all traffic between the vlans with no further intervention required(obviously you need to assign the appropriate ports to the correct vlans).  And to restrict traffic between the 2 client vlans setup a couple ACL's to prevent access between the two subnets.   So clien 10.10.10.5 can access the server by its current ip (192.168.1.117), so can client 10.10.20.5. And if the ACL's get setup right the client machines wont be able to route between each other.     I think this what you are trying to do, a CLI example would take some time to generate. Give this a shot first. And if i am way off base here i am sure some of the Dell techs will come up with something that will work for you.   ** you may also be able to skip the vlan portion of this by assigning the ip's directly to the ports in use(as long as you only use 1 port for each network).

MGA Systems · Answer

Thank you. Worked perfectly. Did not even use VLANs just directly assigned the IP interfaces and put each network on its own port. Then used ACL to limit access.

Networking General

Routing on PowerConnect 6024

Was this post helpful?