SYNACK (11th October 2012)
Well.. They were right..
Threw together a small subnet in CISCO Packet Tracer, working on building a small network, pretty much just for funs (and as a learning experience).
So, I've got a small network set up where the workstations can communicate with each other. Wonderful. Let's try and emulate an internet connection, shall we?
Cut to a few days later and I regret everything - but I'm determined to figure out how it works.
I've tried way more things than I can list - or even remember.. Different IP's.. Static route settings, (blindly) attempting to use RIP - short of putting the 'ISP Router' on the same network.
Anybody mind taking a look at what I've got and pointing me in the right direction?
Last edited by Garacesh; 11th October 2012 at 12:22 PM.
SYNACK (11th October 2012)
Hadn't seen this before, shall have to find a download for it and give it a go on a VM at some point, might refresh my memory a bit
Aha! I figured it outish...!
I needed to Bridge the routers.. Although I'm thinking putting a bridge in-between them is cheating.. Ought I to set something in the config?
Diving in at the deep end is often an odd experience when it comes to gaining new knowledge..
Moving to Networks forum.
just had a look at your original upload, for info, assuming the router is yours you wouldn't use RIP,
set a default route on your router for anything it doesnt know and just shove it out of your interface to the internet either with:
ip default-network 188.8.131.52
ip route 0.0.0.0 0.0.0.0 fastEthernet 0/1
EDIT: and just looked at your vlans, VLAN1 should always be management vlan, so really you should use another for all your machines, or possible a separate vlan for desktops, servers and wireless devices to isolate potential issues. I can put together an example if you want? Or I can butt out
Last edited by british_government; 12th October 2012 at 03:43 PM.
Pretty much going-in-blind with this, learning as I go along and make (many.. many..) mistakes. Building a network isn't exactly in my job description as an apprentice, but it's something I'd like to learn regardless.
I wasn't aware VLAN1, by standards, was management vlan - but I know zilch about inter-vlan-routing, so I think I'll leave sorting that one out until I've got this 'internet connection' sorted.
Also, I don't even know if I've done 'the internet' right.. So I might even have b0rk'd that up.
(Also, yes, it says Port 23: Modem instead of Router. My bad.)
Last edited by Garacesh; 12th October 2012 at 03:54 PM.
a bridge is a router.
what do you exactly mean by this?Wonderful. Let's try and emulate an internet connection, shall we
you have a switch connected to one side of the router for the internal network correct? and somethign on the outside being th internet?
and vlan1 can be used just fine.
to actualy connect the router to the internet your going to need to either have a public IP for each client PC or be running NAT.
Well - Like I said - Going in blind here, that's why I'm using Packet Tracer and not any of the spare switches we have lay around . The 'internet' cluster is basically just another network with an outward-facing router. Nowhere specific, it could be Google, Edugeek or Andromeda Research Corporation. Just another network that isn't part of mine. (Or at least, that's the plan!)
See attached, I have just put that together quickly using a few different vlans. There are many benefites of a system like this, for example security as you can apply different access lists to different vlans for different permissions.
As a basic example only machines on the ADMIN vlan can telnet to the switch, in practise you would have this as ssl and probably only 1 or 2 machines, but the idea is the same.
What you could try is assigning an access list so wireless devices can only ping the server vlan, but no others?
And another note, the only downside to vlanning really is that inter-vlan traffic goes through your router rather than just the switch, as it is changing networks so must be routed. The router is running a simple rip setup.
Have you got routing tables on the client devices that specify the router to use to find the other network?
your diagram also shows a 12.11.x.x network connected to a 12.16.x.x does that fall in the same subnet?
I have default gateway set, but since nothing connects to the router without hitting a switch first, the switch sends the traffic forward. Plus, now with that bridge there (for now..) a client on the network can ping the router inside the cluster (seemingly) without a problem, so I wasn't sure if I needed a routing table..
The 12.11.x.x and 12.16.x.x aren't meant to be on the same network - they're just representing external IP addresses, 12.11 being someone else's network somewhere - anywhere - it doesn't really matter too much. It's really the only way I could think of representing an internet link.
There are currently 1 users browsing this thread. (0 members and 1 guests)