All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H.H. Ding" <hhding.gnu@gmail.com>
To: lartc@vger.kernel.org
Subject: [LARTC] problem in udp route for NIC with 2 ip and gateway
Date: Mon, 19 Nov 2007 03:06:26 +0000	[thread overview]
Message-ID: <4740FDB2.1050706@gmail.com> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

hi,

I have a server with 2 ip address

2: eth0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc pfifo_fast qlen 100
link/ether 00:20:ed:32:81:76 brd ff:ff:ff:ff:ff:ff
inet 61.164.49.39/26 brd 61.164.49.63 scope global eth0
inet 60.12.230.167/26 brd 60.12.230.191 scope global eth0:0

and default gateway is default via 61.164.49.1 dev eth0

It works for tcp.

Problem is, when client connect to 60.12.230.167 by udp, server will
response the package with source ip 61.164.49.39 and client drop the
packge.

How should I config to make the udp response with correct source ip
address?


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)

iD8DBQFHQP2yJo9Njjkvy34RAkJDAKDgd5mZ/WWu8btrvrOEC6ckZXCziACgzGtt
k6jpYwohLyDcdTbr5AZxixQ=+/BV
-----END PGP SIGNATURE-----

_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

                 reply	other threads:[~2007-11-19  3:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4740FDB2.1050706@gmail.com \
    --to=hhding.gnu@gmail.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.