From: "\"C. Bergström\"" <cbergstrom@netsyncro.com>
To: lartc@vger.kernel.org
Subject: [LARTC] Simple route 2nd look please
Date: Wed, 07 Mar 2007 12:33:54 +0000 [thread overview]
Message-ID: <45EEB132.5070302@netsyncro.com> (raw)
I want B to route (temporarily) to both the .65 gw and eventually move
to xxx.xxx.xxx.83 being the default gw, but I can't add that route..
I'm missing some obvious, but if someone would take a 2nd look it would
be appreciated. I also have requested to get access to the switch ,but
that's still waiting.
Server B
ip a s
1: eth0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc pfifo_fast qlen 100
link/ether 00:0b:db:91:84:53 brd ff:ff:ff:ff:ff:ff
inet xxx.xxx.xxx.87/26 brd xxx.xxx.xxx.127 scope global eth0
2: eth1: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc pfifo_fast qlen 100
link/ether 00:0b:db:91:84:54 brd ff:ff:ff:ff:ff:ff
inet xxx.xxx.xxx.84/32 scope global eth1
arping -I eth1 xxx.xxx.xxx.83
ARPING xxx.xxx.xxx.83 from xxx.xxx.xxx.84 eth1
Unicast reply from xxx.xxx.xxx.83 [00:00:25:C1:CC:C0] 0.956ms <--
Correct interface
Unicast reply from xxx.xxx.xxx.83 [00:00:25:C1:CC:C1] 1.210ms <-- Incorrect
Unicast reply from xxx.xxx.xxx.83 [00:00:25:C1:CC:C1] 0.712ms
Unicast reply from xxx.xxx.xxx.83 [00:00:25:C1:CC:C1] 0.711ms
---------------
ip route add default via xxx.xxx.xxx.83 dev eth1 table T1
RTNETLINK answers: Network is unreachable
eris ~ # route add -net xxx.xxx.xxx.84/31 gw xxx.xxx.xxx.83
SIOCADDRT: Network is unreachable
ip r s
127.0.0.0/8 dev lo scope link
default via xxx.xxx.xxx.65 dev eth0
Server C
2: eth0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:00:25:c1:cc:c0 brd ff:ff:ff:ff:ff:ff
inet xxx.xxx.xxx.83/31 scope global eth0
valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:00:25:c1:cc:c1 brd ff:ff:ff:ff:ff:ff
inet xxx.xxx.xxx.82/26 scope global eth1
(Temporary)
ip r s
xxx.xxx.xxx.64/26 dev eth1 proto kernel scope link src 207.135.120.82
xxx.xxx.xxx.64/26 dev eth0 proto kernel scope link src 207.135.120.83
127.0.0.0/8 dev lo scope link
default via xxx.xxx.xxx.65 dev eth1
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next reply other threads:[~2007-03-07 12:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-07 12:33 "C. Bergström" [this message]
2007-03-10 2:26 ` [LARTC] Simple route 2nd look please Martin A. Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45EEB132.5070302@netsyncro.com \
--to=cbergstrom@netsyncro.com \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.