| In other words, design the network software and architecture in such a way
that network managers are assured jobs that pay well for centuries to come.
>I'm so confused ! Okay, someone please tell me how far off base I am here. It
>works the same way in v4.1 ECO1 so I guess that's the way it's supposed to work
>and I'm totally on the wrong track, right ? :)
Yes, that is the way that it's supposed to work. The way that addresses are
represented/interpreted was not designed/specified by Digital. It was specified
by Internet hackers, eerrr, designers, who knew how things were implemented.
An address that is too short gets padded with zeros in the middle based on the
network class. Thus 16.1.2 becomes 16.0.1.2 while 129.1.2 becomes 129.1.0.2.
If you are an IP advocate, you see the elegance in the extra code that makes
this happen.
>How do we get 129.53.78.0 [Class C subnet] to go to one router, and everything
>in 129.53.anything_but_78.anything to go to a different router ???
If you want 129.53.78.0, then say 129.53.78.0, not 129.53.78:
UCX> SET ROUT 129.53.78 /GATE=131.25.48.5 /NETWORK/perm
UCX> sho rou/perm
PERMANENT database
Type Destination Gateway
PN 0.0.0.0 16.135.32.10
PN 129.53.0.78 131.25.48.5
UCX> SET ROUT 129.53.78.0 /GATE=131.25.48.5 /NETWORK/perm
UCX> sho rou/perm
PERMANENT database
Type Destination Gateway
PN 0.0.0.0 16.135.32.10
PN 129.53.0.78 131.25.48.5
PN 129.53.78.0 131.25.48.5
UCX>
If you don't know this, step aside and let me come in and help you
out for $500 an hour.
;-)
|