Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*patch\:\s+tunnels\s+not\s+setting\s+inputdev\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*patch\:\s+tunnels\s+not\s+setting\s+inputdev\s*$/: 14 ]

Total 14 documents matching your query.

1. Re: patch: tunnels not setting inputdev (score: 1): Author: Patrick McHardy <kaber@xxxxxxxxx>; Date: Sat, 01 Jan 2005 17:10:47 +0100; jamal wrote: For the remaining changes, why not simply set input_dev in netif_receive_skb before the call to ing_filter ? You want to be able to filter on indev at ingress - it is safer for whoever c; /archives/netdev/2005-01/msg00003.html (8,968 bytes)
2. Re: patch: tunnels not setting inputdev (score: 1): Author: jamal <hadi@xxxxxxxxxx>; Date: 01 Jan 2005 18:33:27 -0500; I want to understand the repurcasssions instead of blindly setting. Let users complain, thats why the printk exists. For example what does input_dev mean for netbios or a 802.3ad interface? You alrea; /archives/netdev/2005-01/msg00007.html (10,059 bytes)
3. Re: patch: tunnels not setting inputdev (score: 1): Author: Patrick McHardy <kaber@xxxxxxxxx>; Date: Sun, 02 Jan 2005 01:24:08 +0100; jamal wrote: I want to understand the repurcasssions instead of blindly setting. Let users complain, thats why the printk exists. For example what does input_dev mean for netbios or a 802.3ad interfa; /archives/netdev/2005-01/msg00011.html (10,007 bytes)
4. Re: patch: tunnels not setting inputdev (score: 1): Author: jamal <hadi@xxxxxxxxxx>; Date: 03 Jan 2005 09:46:18 -0500; This is exactly why i am not just setting things arbitraliy at input. Different _types_ of devices that need different _types_ of treatment (with dependency of where they are in the path as well). Tu; /archives/netdev/2005-01/msg00031.html (11,999 bytes)
5. lter debug messages (score: 1): Author: f@xxxxxxx>; Date: 31 Dec 2004 12:16:33 -0500; . Quick scan shows the register/unregister state machine may be at fault. Just changed the subject because there have been threads on this topic that other peo; /archives/netdev/2004-12/msg00943.html (7,620 bytes)
6. in U32 classifier. (score: 1): Author: jamal <hadi@xxxxxxxxxx>; Date: Fri, 31 Dec 2004 19:02:04 +0100; know the length of the matches and their data in order to store them. This is why i was earlier preaching putting them in TLVs. Some things dont need the data; /archives/netdev/2004-12/msg00945.html (9,142 bytes)
7. lter debug messages (score: 1): Author: @xxxxxxxxx>; Date: 31 Dec 2004 15:11:32 -0500; , Wichert Akkerman wrote: Previously jamal wrote: Try also the attached patch with netfilter on and your rules installed. That seems to do the trick: I no long; /archives/netdev/2004-12/msg00949.html (9,006 bytes)
8. Re: patch: tunnels not setting inputdev (score: 1): Author: Patrick McHardy <kaber@xxxxxxxxx>; Date: Sat, 01 Jan 2005 17:10:47 +0100; For the remaining changes, why not simply set input_dev in netif_receive_skb before the call to ing_filter ? You want to be able to filter on indev at ingress - it is safer for whoever calls netif_r; /archives/netdev/2005-01/msg01493.html (9,160 bytes)
9. Re: patch: tunnels not setting inputdev (score: 1): Author: jamal <hadi@xxxxxxxxxx>; Date: 01 Jan 2005 18:33:27 -0500; I want to understand the repurcasssions instead of blindly setting. Let users complain, thats why the printk exists. For example what does input_dev mean for netbios or a 802.3ad interface? You alrea; /archives/netdev/2005-01/msg01497.html (10,281 bytes)
10. Re: patch: tunnels not setting inputdev (score: 1): Author: Patrick McHardy <kaber@xxxxxxxxx>; Date: Sun, 02 Jan 2005 01:24:08 +0100; jamal wrote: I want to understand the repurcasssions instead of blindly setting. Let users complain, thats why the printk exists. For example what does input_dev mean for netbios or a 802.3ad interfa; /archives/netdev/2005-01/msg01501.html (10,180 bytes)
11. Re: patch: tunnels not setting inputdev (score: 1): Author: jamal <hadi@xxxxxxxxxx>; Date: 03 Jan 2005 09:46:18 -0500; This is exactly why i am not just setting things arbitraliy at input. Different _types_ of devices that need different _types_ of treatment (with dependency of where they are in the path as well). Tu; /archives/netdev/2005-01/msg01521.html (12,278 bytes)
12. patch: tunnels not setting inputdev (score: 1): Author: jamal <hadi@xxxxxxxxxx>; Date: 31 Dec 2004 12:16:33 -0500; Dave, Patch attached that has tunnels setting input dev correctly. Incorporates what ive sent to Wichert already. A lot of the stuff the tunnels do is very similar, so maybe wiser to have something l; /archives/netdev/2004-12/msg01894.html (7,620 bytes)
13. Re: patch: tunnels not setting inputdev (score: 1): Author: Patrick McHardy <kaber@xxxxxxxxx>; Date: Fri, 31 Dec 2004 19:02:04 +0100; Patch attached that has tunnels setting input dev correctly. Incorporates what ive sent to Wichert already. A lot of the stuff the tunnels do is very similar, so maybe wiser to have something like tu; /archives/netdev/2004-12/msg01896.html (9,041 bytes)
14. Re: patch: tunnels not setting inputdev (score: 1): Author: jamal <hadi@xxxxxxxxxx>; Date: 31 Dec 2004 15:11:32 -0500; Same logic can apply to xfrm6_input then - since both are not exactly tunnels. I didnt check the code path - iam gonna assume you are right and kill those two. You want to be able to filter on indev; /archives/netdev/2004-12/msg01900.html (9,087 bytes)

Current List: 1 - 14
Page: [1]