From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org
Subject: Fw: [Bug 93861] New: Problem in source route of interfaces
Date: Wed, 25 Feb 2015 16:27:00 -0800 [thread overview]
Message-ID: <20150225162700.671e558e@urahara> (raw)
Begin forwarded message:
Date: Wed, 25 Feb 2015 14:54:29 +0000
From: "bugzilla-daemon@bugzilla.kernel.org" <bugzilla-daemon@bugzilla.kernel.org>
To: "shemminger@linux-foundation.org" <shemminger@linux-foundation.org>
Subject: [Bug 93861] New: Problem in source route of interfaces
https://bugzilla.kernel.org/show_bug.cgi?id=93861
Bug ID: 93861
Summary: Problem in source route of interfaces
Product: Networking
Version: 2.5
Kernel Version: 3.10.0
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: IPV4
Assignee: shemminger@linux-foundation.org
Reporter: kidboy@brturbo.com.br
Regression: No
I have 2 internet links, where do a test to assess the connection applying a
ping on each output interface and getting the result, in version 2.6.XX i can
ping and route source works fine, but in kernel 3.X.XX its not work anymore, i
dont know why.
My configuration is here:
/etc/sysconfig/network-scripts/ifcfg-eth0
TYPE="Ethernet"
BOOTPROTO="static"
IPV4_FAILURE_FATAL="no"
NAME="eth0"
UUID="68ec71ab-62f4-41fc-9ad8-085bb3b78eae"
ONBOOT="yes"
HWADDR="10:FE:ED:07:B3:38"
IPADDR="192.168.25.2"
GATEWAY="192.168.25.1"
PREFIX="24"
NM_CONTROLLED="no"
/etc/sysconfig/network-scripts/ifcfg-eth1
TYPE="Ethernet"
BOOTPROTO="static"
IPV4_FAILURE_FATAL="no"
NAME="eth1"
UUID="6ddee48f-3296-4158-86e6-d4104593d942"
ONBOOT="yes"
HWADDR="50:E5:49:FB:AF:0D"
IPADDR="192.168.26.2"
GATEWAY="192.168.26.1"
PREFIX="24"
NM_CONTROLLED="no"
# /etc/rc.d/rc.local ( Permission is 755 in file )
ip route add 192.168.25.0 dev eth0 src 192.168.25.2 table 1
ip route add default via 192.168.25.1 table 1
# Rules for out ADSL1
ip route add 192.168.26.0 dev eth1 src 192.168.26.2 table 2
ip route add default via 192.168.26.1 table 2
# Rules for out ADSL2
ip route add 192.168.25.0 dev eth0 src 192.168.25.2
ip route add 192.168.26.0 dev eth1 src 192.168.26.2
# Rule for tables
ip rule add from 192.168.25.0 table 1
ip rule add from 192.168.26.0 table 2
ip rule add fwmark 1 lookup 1
ip rule add fwmark 2 lookup 2
ip route flush cached
So if i use command 'ping -I192.168.25.2 8.8.8.8' its work fine because its the
default route of system, but if i use command 'ping -I192.168.26.2 8.8.8.8' its
not work, in tcpdump report its out using lo interface. In kernel 2.6 the
output of tcpdump is the interface 192.168.26.2 and works fine. I dont know
what change for new kernel or if its a bug. The forwarding is enable,
configuration in kernel 2.6 and 3.x is the same.
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2015-02-26 0:27 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=20150225162700.671e558e@urahara \
--to=stephen@networkplumber.org \
--cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox