Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Device\s+naming\s+for\s+wireless\s+NICs\.\.\.\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Device\s+naming\s+for\s+wireless\s+NICs\.\.\.\s*$/: 18 ]

Total 18 documents matching your query.

1. Device naming for wireless NICs... (score: 1): Author: xxxxxxxx>; Date: Thu, 11 Mar 2004 10:28:23 -0600; If this topic been hashed a lot already, please let me know the keywords I might search for in the archives to find the threads. I've had a few requests by users of the IPW2100 wireless driver to swi; /archives/netdev/2004-03/msg00195.html (11,257 bytes)
2. Re: Device naming for wireless NICs... (score: 1): Author: xxxxxxxx>; Date: Thu, 11 Mar 2004 17:36:57 +0100; This could be handled by nameif in userspace. I personally find them broken. I had to remove checking the name from ethtool to make it work. Ethtool checks for 'eth' or 'usb' in name, which do not wo; /archives/netdev/2004-03/msg00196.html (11,154 bytes)
3. Re: Device naming for wireless NICs... (score: 1): Author: u@xxxxxx>; Date: Thu, 11 Mar 2004 11:54:40 -0500 (EST); TBH I don't think it much matters. I know that at least Red Hat's networking scripts (and possibly other distributions) did at one point assume that each interface would be named ethX, but I don't th; /archives/netdev/2004-03/msg00197.html (10,843 bytes)
4. Re: Device naming for wireless NICs... (score: 1): Author: xxxxxxxx>; Date: Thu, 11 Mar 2004 10:22:04 -0800; This is my personal rule of thumb : o if the interface use Ethernet frames (i.e. offer Ethernet emulation), then it should be name 'ethX'. o if the interface use 802.11 frames (rawe/native), it shoul; /archives/netdev/2004-03/msg00198.html (9,269 bytes)
5. Re: Device naming for wireless NICs... (score: 1): Author: xxxxxxxx>; Date: Thu, 11 Mar 2004 13:23:12 -0500; James Ketrenos wrote: If this topic been hashed a lot already, please let me know the keywords I might search for in the archives to find the threads. I've had a few requests by users of the IPW2100; /archives/netdev/2004-03/msg00199.html (11,068 bytes)
6. Re: Device naming for wireless NICs... (score: 1): Author: xxxxxxxx>; Date: Thu, 11 Mar 2004 13:25:15 -0500; Matthew Galgoci wrote: Going forward it might be worth while to standardize all wireless interface names, just to show at a glance that an interface is 802.11x, and also to differentiate the fact tha; /archives/netdev/2004-03/msg00200.html (9,956 bytes)
7. Re: Device naming for wireless NICs... (score: 1): Author: xxxxxxxx>; Date: Thu, 11 Mar 2004 14:33:58 -0500 (EST); neat is old and outdated :) Have a look at the redhat-config-network tools in Red Hat Linux or in Fedora, the system-config-network tools. I am sure the author of the tools would appreciate feedback; /archives/netdev/2004-03/msg00202.html (7,659 bytes)
8. Re: Device naming for wireless NICs... (score: 1): Author: xxxxxxxx>; Date: Thu, 11 Mar 2004 11:47:28 -0800; I don't use Red-Hat, it's just that people here complain to me when their Red-Hat doesn't work. The joy of being the "Linux expert". My approach has always been 'edit the darn text file', so I may no; /archives/netdev/2004-03/msg00203.html (9,308 bytes)
9. Re: Device naming for wireless NICs... (score: 1): Author: xxxxxxxx>; Date: Fri, 12 Mar 2004 10:30:49 +0000; Jeff Garzik wrote: James Ketrenos wrote: Like Matthew said, any code that assumes a specific interface prefix, be it eth%d or wlan%d, is buggy. Users are allowed to choose random interface names for; /archives/netdev/2004-03/msg00207.html (10,840 bytes)
10. Device naming for wireless NICs... (score: 1): Author: James Ketrenos <jketreno@xxxxxxxxxxxxxxxxxx>; Date: Thu, 11 Mar 2004 10:28:23 -0600; If this topic been hashed a lot already, please let me know the keywords I might search for in the archives to find the threads. I've had a few requests by users of the IPW2100 wireless driver to swi; /archives/netdev/2004-03/msg00859.html (11,709 bytes)
11. Re: Device naming for wireless NICs... (score: 1): Author: Tomasz Torcz <zdzichu@xxxxxx>; Date: Thu, 11 Mar 2004 17:36:57 +0100; This could be handled by nameif in userspace. I personally find them broken. I had to remove checking the name from ethtool to make it work. Ethtool checks for 'eth' or 'usb' in name, which do not wo; /archives/netdev/2004-03/msg00860.html (11,445 bytes)
12. Re: Device naming for wireless NICs... (score: 1): Author: Matthew Galgoci <mgalgoci@xxxxxxxxxx>; Date: Thu, 11 Mar 2004 11:54:40 -0500 (EST); TBH I don't think it much matters. I know that at least Red Hat's networking scripts (and possibly other distributions) did at one point assume that each interface would be named ethX, but I don't th; /archives/netdev/2004-03/msg00861.html (10,865 bytes)
13. Re: Device naming for wireless NICs... (score: 1): Author: Jean Tourrilhes <jt@xxxxxxxxxxxxxxxxxx>; Date: Thu, 11 Mar 2004 10:22:04 -0800; This is my personal rule of thumb : o if the interface use Ethernet frames (i.e. offer Ethernet emulation), then it should be name 'ethX'. o if the interface use 802.11 frames (rawe/native), it shoul; /archives/netdev/2004-03/msg00862.html (9,322 bytes)
14. Re: Device naming for wireless NICs... (score: 1): Author: Jeff Garzik <jgarzik@xxxxxxxxx>; Date: Thu, 11 Mar 2004 13:23:12 -0500; If this topic been hashed a lot already, please let me know the keywords I might search for in the archives to find the threads. I've had a few requests by users of the IPW2100 wireless driver to swi; /archives/netdev/2004-03/msg00863.html (11,512 bytes)
15. Re: Device naming for wireless NICs... (score: 1): Author: Jeff Garzik <jgarzik@xxxxxxxxx>; Date: Thu, 11 Mar 2004 13:25:15 -0500; Matthew Galgoci wrote: Going forward it might be worth while to standardize all wireless interface names, just to show at a glance that an interface is 802.11x, and also to differentiate the fact tha; /archives/netdev/2004-03/msg00864.html (10,081 bytes)
16. Re: Device naming for wireless NICs... (score: 1): Author: Matthew Galgoci <mgalgoci@xxxxxxxxxx>; Date: Thu, 11 Mar 2004 14:33:58 -0500 (EST); neat is old and outdated :) Have a look at the redhat-config-network tools in Red Hat Linux or in Fedora, the system-config-network tools. I am sure the author of the tools would appreciate feedback; /archives/netdev/2004-03/msg00866.html (7,688 bytes)
17. Re: Device naming for wireless NICs... (score: 1): Author: Jean Tourrilhes <jt@xxxxxxxxxxxxxxxxxx>; Date: Thu, 11 Mar 2004 11:47:28 -0800; I don't use Red-Hat, it's just that people here complain to me when their Red-Hat doesn't work. The joy of being the "Linux expert". My approach has always been 'edit the darn text file', so I may no; /archives/netdev/2004-03/msg00867.html (9,471 bytes)
18. Re: Device naming for wireless NICs... (score: 1): Author: P@xxxxxxxxxxxxxx; Date: Fri, 12 Mar 2004 10:30:49 +0000; Like Matthew said, any code that assumes a specific interface prefix, be it eth%d or wlan%d, is buggy. Users are allowed to choose random interface names for their interfaces, often via nameif(8) pro; /archives/netdev/2004-03/msg00871.html (11,142 bytes)

Current List: 1 - 18
Page: [1]