Hi,
I know RIP is outdated and IETF doesnt support it anymore. Knowing
this i couldnt think of a more appropriate place to post this query:
I keep seeing RIP packets with a tag field filled with some non zero
number. Any clues on why this is happening?
I know that the border routers were meant
>
> The other side is where your customers are living. There are living real
> system and network managers who know what they are doing. I dont think they
> let slip RIP into your network.
ok
> But there are also people who believe in windows, who believe it makes sense
> to use netbios packets
Hi,
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, 1.1.1.1/24 and 2.2.2.2/24 and both using the same
physical interface. RIP
> >
> > Legend: {} denotes the sequence, while [] denotes the set
> >
> > Path {1 2} [3 4] {5}
>
> As I understand the specs, that is -not- allowed. an unordered set
> can appear only as the _last_ element of the AS path list.
Yes, I understand that right now it is not possible to receieve or
g
>
> You can *not* merge AS_SET's, as the current BGP specs imply an
> AS_SET has a fixed path-length, hence you should NOT merge the sets
> in:
>
>{1 2} [3 4] [5 6]
>
> into:
>
>{1 2} [3 4 5 6]
>
> as the former path has a length of 3, the latter a length of just 2 -
> merging
