Source address selection for ICMP error message

2019-08-05 Thread Chun Wang
d and I have no intention to change this).  Is the source address selection in this case correct? Will the latest inux version return 172.16.23.1 instead of 172.16.20.1 in this case? If not, what's the best way to solve this? I haven't subscribed to this list yet, please CC me the answe

next-20150714 - busted IPv6 source address selection...

2015-07-14 Thread Valdis Kletnieks
next-20150714 w/ one ethernet commit reverted. -0706 w/ same revert works. "ip addr show" for the wireless says: 5: wlp3s0b1: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether bc:85:56:1f:4f:6d brd ff:ff:ff:ff:ff:ff inet 172.30.42.75/27 brd 172.30.42.95 scope global dy

[PATCH 3.2 06/87] ipv4: fix ineffective source address selection

2013-11-25 Thread Ben Hutchings
3.2.53-rc1 review patch. If anyone has any objections, please let me know. -- From: Jiri Benc [ Upstream commit 0a7e22609067ff524fc7bbd45c6951dd08561667 ] When sending out multicast messages, the source address in inet->mc_addr is ignored and rewritten by an autoselected one.

[PATCH 3.8 20/91] ipv4: fix ineffective source address selection

2013-11-07 Thread Kamal Mostafa
3.8.13.13 -stable review patch. If anyone has any objections, please let me know. -- From: Jiri Benc [ Upstream commit 0a7e22609067ff524fc7bbd45c6951dd08561667 ] When sending out multicast messages, the source address in inet->mc_addr is ignored and rewritten by an autoselect

[PATCH 3.10 13/54] ipv4: fix ineffective source address selection

2013-11-01 Thread Greg Kroah-Hartman
3.10-stable review patch. If anyone has any objections, please let me know. -- From: Jiri Benc [ Upstream commit 0a7e22609067ff524fc7bbd45c6951dd08561667 ] When sending out multicast messages, the source address in inet->mc_addr is ignored and rewritten by an autoselected one.

[PATCH 3.11 15/66] ipv4: fix ineffective source address selection

2013-11-01 Thread Greg Kroah-Hartman
3.11-stable review patch. If anyone has any objections, please let me know. -- From: Jiri Benc [ Upstream commit 0a7e22609067ff524fc7bbd45c6951dd08561667 ] When sending out multicast messages, the source address in inet->mc_addr is ignored and rewritten by an autoselected one.

[ 08/32] ipv4: fix ineffective source address selection

2013-11-01 Thread Greg Kroah-Hartman
3.4-stable review patch. If anyone has any objections, please let me know. -- From: Jiri Benc [ Upstream commit 0a7e22609067ff524fc7bbd45c6951dd08561667 ] When sending out multicast messages, the source address in inet->mc_addr is ignored and rewritten by an autoselected one.

[PATCH 3.5 44/64] ipv4: fix ineffective source address selection

2013-10-28 Thread Luis Henriques
3.5.7.24 -stable review patch. If anyone has any objections, please let me know. -- From: Jiri Benc commit 0a7e22609067ff524fc7bbd45c6951dd08561667 upstream. When sending out multicast messages, the source address in inet->mc_addr is ignored and rewritten by an autoselected o

Re: Source address selection

2000-12-13 Thread Julian Anastasov
Hello, Chris Dunlop wrote: > using the IPs on the aliases as source addresses, except of course when > an application binds to that address. > > Is there a way to do this ? ip addr add 192.168.0.1/24 brd + dev eth0 scope host ^^ default

Source address selection

2000-12-13 Thread Chris Dunlop
Hi, In 2.2.x and/or 2.4.x, is there any way of preventing IP address[es] attached to interface aliases being selected as a source address when userland code creates a socket without binding to a particular address ? >From Documentation/proc.txt: /proc/sys/net/ipv4/conf/hidden Hide addresse