Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*controlling\s+ARP\s+Proxy\s+scope\?\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*controlling\s+ARP\s+Proxy\s+scope\?\s*$/: 14 ]

Total 14 documents matching your query.

1. controlling ARP Proxy scope? (score: 1): Author: Zdenek Radouch <zdenek@xxxxxxx>; Date: Fri, 01 Jul 2005 22:16:13 -0400; I haven't been able to locate anything discussing how to control the scope of Linux proxy ARP. So, left with only a binary flag in /proc, and network definition on the interface, I assumed (perhaps n; /archives/netdev/2005-07/msg00025.html (8,102 bytes)
2. Re: controlling ARP Proxy scope? (score: 1): Author: Henrik Nordstrom <hno@xxxxxxxxxxxxxxx>; Date: Sat, 2 Jul 2005 23:21:37 +0200 (CEST); On Fri, 1 Jul 2005, Zdenek Radouch wrote: So, left with only a binary flag in /proc, and network definition on the interface, I assumed (perhaps naively) that the arp would proxy only for the address; /archives/netdev/2005-07/msg00028.html (9,100 bytes)
3. Re: controlling ARP Proxy scope? (score: 1): Author: Zdenek Radouch <zdenek@xxxxxxx>; Date: Tue, 05 Jul 2005 21:55:29 -0400; Unfortunately I can't. Not without adding more code to what is quite obviously a bunch of kludgy patches for an ill-conceived ARP proxy design. In my case, the proxy replies to a request seen on the; /archives/netdev/2005-07/msg00068.html (10,287 bytes)
4. Re: controlling ARP Proxy scope? (score: 1): Author: Henrik Nordstrom <hno@xxxxxxxxxxxxxxx>; Date: Wed, 6 Jul 2005 04:20:32 +0200 (CEST); On Tue, 5 Jul 2005, Zdenek Radouch wrote: proxy_arp simply ARPs if there is a route for the requested destination going out on another interface than where the ARP was seen. In my case, the proxy rep; /archives/netdev/2005-07/msg00069.html (11,742 bytes)
5. Re: controlling ARP Proxy scope? (score: 1): Author: Zdenek Radouch <zdenek@xxxxxxx>; Date: Wed, 06 Jul 2005 00:32:44 -0400; Yes, I am very sure about it. Of all attached networks, only one is a 10.* network, and the address answered, 10.1.2.1 happens to be the main router/gateway to the rest of the world. My machine (with; /archives/netdev/2005-07/msg00070.html (13,231 bytes)
6. Re: controlling ARP Proxy scope? (score: 1): Author: Henrik Nordstrom <hno@xxxxxxxxxxxxxxx>; Date: Wed, 6 Jul 2005 17:32:16 +0200 (CEST); On Wed, 6 Jul 2005, Zdenek Radouch wrote: Well, how do I tell it that I want to proxy for all machines on the 192.168.13.128/29 net attached to eth0.5, but not for any of the machines on 192.168.2.0/; /archives/netdev/2005-07/msg00072.html (11,775 bytes)
7. Re: controlling ARP Proxy scope? (score: 1): Author: Zdenek Radouch <zdenek@xxxxxxx>; Date: Wed, 06 Jul 2005 22:46:33 -0400; The setup is actually quite complex. I have a linear array of machines communicating over a proprietary (L1 and L2) protocol. The machines are connected point-to-point, and they use a proprietary VLA; /archives/netdev/2005-07/msg00080.html (11,733 bytes)
8. controlling ARP Proxy scope? (score: 1): Author: Zdenek Radouch <zdenek@xxxxxxx>; Date: Fri, 01 Jul 2005 22:16:13 -0400; I haven't been able to locate anything discussing how to control the scope of Linux proxy ARP. So, left with only a binary flag in /proc, and network definition on the interface, I assumed (perhaps n; /archives/netdev/2005-07/msg00249.html (8,102 bytes)
9. Re: controlling ARP Proxy scope? (score: 1): Author: Henrik Nordstrom <hno@xxxxxxxxxxxxxxx>; Date: Sat, 2 Jul 2005 23:21:37 +0200 (CEST); So, left with only a binary flag in /proc, and network definition on the interface, I assumed (perhaps naively) that the arp would proxy only for the addresses within the subnet defined for the inte; /archives/netdev/2005-07/msg00252.html (9,189 bytes)
10. Re: controlling ARP Proxy scope? (score: 1): Author: Zdenek Radouch <zdenek@xxxxxxx>; Date: Tue, 05 Jul 2005 21:55:29 -0400; Unfortunately I can't. Not without adding more code to what is quite obviously a bunch of kludgy patches for an ill-conceived ARP proxy design. In my case, the proxy replies to a request seen on the; /archives/netdev/2005-07/msg00292.html (10,374 bytes)
11. Re: controlling ARP Proxy scope? (score: 1): Author: Henrik Nordstrom <hno@xxxxxxxxxxxxxxx>; Date: Wed, 6 Jul 2005 04:20:32 +0200 (CEST); proxy_arp simply ARPs if there is a route for the requested destination going out on another interface than where the ARP was seen. In my case, the proxy replies to a request seen on the very same i; /archives/netdev/2005-07/msg00293.html (12,271 bytes)
12. Re: controlling ARP Proxy scope? (score: 1): Author: Zdenek Radouch <zdenek@xxxxxxx>; Date: Wed, 06 Jul 2005 00:32:44 -0400; Yes, I am very sure about it. Of all attached networks, only one is a 10.* network, and the address answered, 10.1.2.1 happens to be the main router/gateway to the rest of the world. My machine (with; /archives/netdev/2005-07/msg00294.html (13,364 bytes)
13. Re: controlling ARP Proxy scope? (score: 1): Author: Henrik Nordstrom <hno@xxxxxxxxxxxxxxx>; Date: Wed, 6 Jul 2005 17:32:16 +0200 (CEST); Well, how do I tell it that I want to proxy for all machines on the 192.168.13.128/29 net attached to eth0.5, but not for any of the machines on 192.168.2.0/24 attached to eth0.6 ? For whom going wh; /archives/netdev/2005-07/msg00296.html (12,183 bytes)
14. Re: controlling ARP Proxy scope? (score: 1): Author: Zdenek Radouch <zdenek@xxxxxxx>; Date: Wed, 06 Jul 2005 22:46:33 -0400; The setup is actually quite complex. I have a linear array of machines communicating over a proprietary (L1 and L2) protocol. The machines are connected point-to-point, and they use a proprietary VLA; /archives/netdev/2005-07/msg00304.html (11,911 bytes)

Current List: 1 - 14
Page: [1]