North American Network Operators Group|
Date Prev | Date Next |
Date Index |
Thread Index |
Author Index |
- From: Tom Sanders
- Date: Sun Aug 21 12:13:42 2005
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=kDoBocA/7xyShpydXAln+VKSrSLkFVsjzJ5NGyToDnqFZNX2vGQLHlEfKcorEf5mxn+1pjiec+OSeRsIndf5v0sBqVKcHXyajFuoxHGdiziTEh09vwpb8YAHy/IsVxG47wQKyLstW0XrJ7KL740awmzmaJihvfJbxYfAXheO2as=
There isnt IMO a way in RIP to identify the source of the RIP packet
(the way we have Router ID in OSPF, system ID in ISIS, etc.)
Now assume we have 2 vlans defined on an ethernet. Thus we would have
two IP interfaces, 188.8.131.52/24 and 184.108.40.206/24 and both using the same
physical interface. RIP is running on both these interfaces.
My doubt is that how will another router, which is configured in the
same way (2 vlans) be able to differentiate between the RIP responses
originated by 220.127.116.11 and 18.104.22.168?