GNS3

Just setup some static routes on R1 and R2, R1 needs to know what to route to R2 and visa versa

C = Connected, the routers only know about they are connected to, they have no idea what to do with the subnets on the other Routers.

On R2 you need something like:-

ip route 192.168.1.1 255.255.255.0 serial0/0

I'd lay off the IGPs at the moment ;)
 
Last edited:
R 192.168.1.0/24 [120/1] via 192.168.100.1, 00:00:01, Serial0/0

I have that at the moment so don't know if I am slowly getting there.

Changed to RIP instead of OSPF
 
When using RIP, you need to add the networks connected to that router, such as its LAN and WAN. Do this for both routers then do show ip route and see if they can see eachothers LAN routes
 
I don't think my actual configuration was the problem. I think the way I configured R2 and T25 was the problem.

I changed R2 to:

Code: 
interface FastEthernet1/0
 ip address 192.168.101.1 255.255.255.0
 duplex auto
 speed auto
!
interface FastEthernet1/0.40
 encapsulation dot1Q 40
 ip address 192.168.10.1 255.255.255.0 (from 192.168.4.1)
!
I also changed T25 to:

Code: 
interface FastEthernet0/0
 ip address 192.168.10.2 255.255.255.0 (from 192.168.4.6)
 no ip route-cache
 duplex auto
 speed auto
!

Everything is fully working again now however I am unsure whether T25 would still be classed as being in VLAN 40 even though they have a different IP address, i.e. not 192.168.4.x?
 
Just because the VLAN is 40, it doesnt mean the IP address scheme has to be. People do it like because its easy to identify which VLAN the PC is part of, if it has the same IP as the VLAN :)
 
Can't believe something as small as that would effect the whole thing haha?

I think I have sorted that then I hope haha? I'm thinking of maybe doing a DHCP Server now? Any other suggestions?

Cheers for the help guys.
 
Just a heads up as to why 192.168.4.x wouldnt work on R2 (when trying to ping hosts on R1). It was because R1 has the same network on its LAN and without NAT in place, it wouldn't of got through, as R1 would re-route it back to the 192.168.4.x on its LAN.
 
Deception said:
Just a heads up as to why 192.168.4.x wouldnt work on R2 (when trying to ping hosts on R1). It was because R1 has the same network on its LAN and without NAT in place, it wouldn't of got through, as R1 would re-route it back to the 192.168.4.x on its LAN.
Click to expand...

Ah right OK. Makes sense.

Thanks for that Deception. Just going to add a few hosts on different VLANS from SW4 then either try putting some kind of DHCP server in or another router.
 
Deception said:
How you finding WANs
Click to expand...

Hi Mate.

Been working all weekend so haven't made any further progress with it as such.

I am looking to put a router or a 'server' with dhcp services on it and see how that goes. What you think? Also what about putting some authentication in place on the Routers so only authorised people can change the config?

Cheers
Tom.
 
Sure, would be a good start to make the router also a DHCP server.

Nice idea on locking it down, should always be the first thing you do :). Also add in a log in failure rate, so if you enter password wrong 3 times, it locks you out for a period of time (good at stopping brute forcing). Look at locking it down using AAA.
 
Right I have a very basic DHCP Server running which I have got to work for One host.

The setup at the moment is; R2 goes to SW5 which goes to the 'DHCP Server'. From this I think I want a number of Users to be connected directly to this DHCP Server.

At the moment, I have one User connected from this Server via normal Ethernet and the DHCP allocation works correctly. Now when I add another User to a different interface of the Server, I have found out I have to do all the configurations again for each interface? Surely there is a way around this. For example, surely when I connect the host to the server, all's I should need to do is go into the config of that host and do 'ip address dhcp'? Also when I tried to allocate an IP address of 192.168.103.2 to Ethernet 1/1 it says there is an overlap from Ethernet 1/0.

Is there a more efficient way I could be doing this?

Config for the Server is:

Code: 
ip cef
no ip domain lookup
no ip dhcp use vrf connected
ip dhcp excluded-address 192.168.0.0 192.168.11.0
ip dhcp excluded-address 192.168.100.0 192.168.101.0
!
ip dhcp pool Users
   network 192.168.103.0 255.255.255.0
   default-router 192.168.103.1 
!
!
interface FastEthernet0/0
 ip address 192.168.102.2 255.255.255.0
 duplex auto
 speed auto
!
interface Ethernet1/0
 ip address 192.168.103.1 255.255.255.0
 half-duplex
!

Config for H1 is:

Code: 
!
interface Ethernet0/0
 ip address dhcp
 half-duplex
!
 
You're better off putting the DHCP server on the router, as this handles the VLAN sub interfaces too (a lot easier, as it will know which users are on what VLAN and then know which DHCP scope to use).

The address overlaps because technically they are on the same network, which the router doesn't like as each interface on the router has to be on a different network.
 
So try to run it through R2 yeah? Will I not have the same problem with interfaces though?

I.e. do you have to reconfigure it for every interface or can I configure it for the interface that goes to the Switch and the switch will sort it out from there?
 
TomElZ said:
So try to run it through R2 yeah? Will I not have the same problem with interfaces though?

I.e. do you have to reconfigure it for every interface or can I configure it for the interface that goes to the Switch and the switch will sort it out from there?
Click to expand...

You just create the pools on R2 and it will see what VLAN's the hosts are connected to and what the IP is on that subinterface; It will then allocate an IP from the same pool of the sub interface, to that host e.g. A host from VLAN 30 requests an IP, and on R2 the VLAN 30 subinterface has an IP of 192.168.30.1. The Router will then get pool for 192.168.30.x network and give the host an IP from it.

So, as long as the VLAN sub interfaces are configured on the router and the switch has the VLAN's etc, it should do it all for you; You just create the right DHCP pools for the sub interfaces. :)
 
You must log in or register to reply here.
Back
Top Bottom