[9fans] simple route question - Plan9

This is a discussion on [9fans] simple route question - Plan9 ; My understanding of routes is that I ought to be able to do this: node 1: echo add 11.0.0.1 255.0.0.0 11.0.0.0 > /net/ipifc/1/ctl node 2: echo add 12.0.1.1 255.0.0.0 12.0.0.0 > /net/ipifc/1/ctl echo add 11.0.1.1 255.0.0.0 11.0.0.0 >/etc/ipifc/1/ctl notwithstanding that ...

+ Reply to Thread
Results 1 to 5 of 5

Thread: [9fans] simple route question

  1. [9fans] simple route question

    My understanding of routes is that I ought to be able to do this:
    node 1:
    echo add 11.0.0.1 255.0.0.0 11.0.0.0 > /net/ipifc/1/ctl

    node 2:
    echo add 12.0.1.1 255.0.0.0 12.0.0.0 > /net/ipifc/1/ctl
    echo add 11.0.1.1 255.0.0.0 11.0.0.0 >/etc/ipifc/1/ctl

    notwithstanding that the network number is superfluous, anything wrong
    with the above that I am missing?

    (this looks weird, there is a reason for it)

    A ping to an 11. net does not get to the interface, I am not sure I see why.

    A ping to 12. does

    thanks

    ron

  2. Re: [9fans] simple route question

    On Wed May 30 12:41:24 EDT 2007, rminnich@gmail.com wrote:
    > My understanding of routes is that I ought to be able to do this:
    > node 1:
    > echo add 11.0.0.1 255.0.0.0 11.0.0.0 > /net/ipifc/1/ctl
    >
    > node 2:
    > echo add 12.0.1.1 255.0.0.0 12.0.0.0 > /net/ipifc/1/ctl
    > echo add 11.0.1.1 255.0.0.0 11.0.0.0 >/etc/ipifc/1/ctl


    [...]

    > A ping to an 11. net does not get to the interface, I am not sure I see why.


    could the problem be that you mean /net and not /etc?

    - erik

  3. Re: [9fans] simple route question

    On 5/30/07, erik quanstrom wrote:

    > > echo add 12.0.1.1 255.0.0.0 12.0.0.0 > /net/ipifc/1/ctl
    > > echo add 11.0.1.1 255.0.0.0 11.0.0.0 >/etc/ipifc/1/ctl


    > could the problem be that you mean /net and not /etc?


    if only, I typed that wrong when I created the message.

    iproute is this one node 2:

    1/log:0.0.0.0 /96 10.0.0.1 4 none -

    1/log:10.0.0.0 /104 10.0.0.0 4i ifc -

    1/log:10.0.0.0 /128 10.0.0.0 4b ifc -

    1/log:10.0.0.1 /128 10.0.0.1 4u ifc -

    1/log:10.255.255.255 /128 10.255.255.255 4b ifc -

    1/log:11.0.0.0 /128 11.0.0.0 4ip ifc -

    1/log:11.0.0.1 /128 11.0.0.1 4u ifc -

    1/log:11.255.255.255 /128 11.255.255.255 4b ifc -

    1/log:12.0.0.0 /104 12.0.0.0 4i ifc -

    1/log:12.0.0.0 /128 12.0.0.0 4b ifc -

    1/log:12.0.0.1 /128 12.0.0.1 4u ifc -

    1/log:12.255.255.255 /128 12.255.255.255 4b ifc -

    1/log:255.255.255.255 /128 255.255.255.255 4b ifc -


    12 works fine. Pings to 11 don't make it to the medium code. I'm puzzled.

    ron

  4. Re: [9fans] simple route question

    > > > echo add 12.0.1.1 255.0.0.0 12.0.0.0 > /net/ipifc/1/ctl
    > > > echo add 11.0.1.1 255.0.0.0 11.0.0.0 >/etc/ipifc/1/ctl

    ....
    > 12 works fine. Pings to 11 don't make it to the medium code. I'm puzzled.


    How well does plan9 do multiple IP addresses on the same
    interface?

    Could it be that since you added 12.0.1.1/8 *first* by
    default the source address will be 12.0.1.1? When you ping
    11.x.x.x (presumably node1's ip address), your system sends
    an ARP request to map the ip address to a mac address. Now
    if the address where ARP response should be sent to is
    12.0.1.1, node1 wouldn't know what to do. Can you snoop to
    see the arp request? What happens if you add addresses in
    the reverse order? Then 12.x.x.x pings should fail.

  5. Re: [9fans] simple route question

    No, it just turned out to be a typo on my part.

    How is it I only see typos when I post to 9fans ...

    OH. many eyes must play into heisenberg somehow?

    ron

+ Reply to Thread