I need to change the address of this computer temporarily to a 192.168.2.? instead of 192.168.1.9 to connect to a device that I reset.
There used to be a menu that I used for this but with F16/XFCE I am lost.
Would someone be kind enough to tell me how to do this?
Bob
On 03/31/2012 12:07 PM, Bob Goodwin wrote:
I need to change the address of this computer temporarily to a 192.168.2.? instead of 192.168.1.9 to connect to a device that I reset.
There used to be a menu that I used for this but with F16/XFCE I am lost.
Would someone be kind enough to tell me how to do this?
man ifconfig
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 03/31/2012 11:07 AM, Bob Goodwin wrote:
I need to change the address of this computer temporarily to a 192.168.2.? instead of 192.168.1.9 to connect to a device that I reset.
There used to be a menu that I used for this but with F16/XFCE I am lost.
Would someone be kind enough to tell me how to do this?
Bob
You could run:
sudo route add -net 192.168.2.0/24 eth0
from a terminal. This will add a route to the 192.168.2.0/24 network that you can use to talk to the device without changing your IP address.
Mikkel - -- Do not meddle in the affairs of dragons, for thou art crunchy and taste good with Ketchup!
On 03/31/2012 09:07 AM, Bob Goodwin wrote:
There used to be a menu that I used for this but with F16/XFCE I am lost. Would someone be kind enough to tell me how to do this?
From the main menu, go to Applications, Administration. I have both Network and Network Device Control. If one doesn't help, try the other.
On 03/31/2012 01:13 PM, Joe Zeff wrote:
On 03/31/2012 09:07 AM, Bob Goodwin wrote:
There used to be a menu that I used for this but with F16/XFCE I am lost. Would someone be kind enough to tell me how to do this?From the main menu, go to Applications, Administration. I have both Network and Network Device Control. If one doesn't help, try the other.
I have neither of those although I think Network Device Control is what I used in the past?
Man ifconfig says: NOTE This program is obsolete! For replacement check ip addr and ip link. For statistics use ip -s link.
I did that: ip addr 192.168.2.0/24 dev em1
I also tried:
route add -net 192.168.2.0/24 em1
Which leaves me wondering how to verify the change has been added and then how do I access the unknown device. it is supposed to default to an address in the 192.168.2 subnet which I can access from Firefox however I haven't been able to find it with a few trial and error attempts. There must be a logical approach to this?
This is a minimum quality IP Camera [Zonet zvc7611w] that I use to watch the front driveway. I pressed the reset button and then can find the cdrom with the support information and have found nothing on-line and got no response from Zonet. Not surprisingly it is a discontinued product. It would overheat and fail until I added vent holes and a tiny fan to both of them, I have two.
Bob
On 03/31/2012 11:55 AM, Bob Goodwin wrote:
I have neither of those although I think Network Device Control is what I used in the past?
I migrated from Gnome2 to XFCE, so I probably have stuff in my menus from Gnome. If your box has always been XFCE you might not have some of the things I do. It's also possible that you have them, but they're not in the menu.
On 03/31/2012 03:26 PM, Joe Zeff wrote:
On 03/31/2012 11:55 AM, Bob Goodwin wrote:
I have neither of those although I think Network Device Control is what I used in the past?I migrated from Gnome2 to XFCE, so I probably have stuff in my menus from Gnome. If your box has always been XFCE you might not have some of the things I do. It's also possible that you have them, but they're not in the menu.
I tried yum whatprovides Network Device Control with no luck, That's probably not the name it wants, and I don't think I have been able to use it for a while, maybe it's not compatible with network manager ...
Anyway I've put that project aside for a while and put this computer in its place, just installed memory that came in today's mail, have 6 gigs now.
Thanks for the help,
Bob
On 03/31/2012 12:50 PM, Bob Goodwin - Zuni, Virginia, USA wrote:
I tried yum whatprovides Network Device Control with no luck, That's probably not the name it wants,
system-config-network is what you're looking for. And, I've checked: you can change the IP address there quite easily.
On 03/31/2012 04:01 PM, Joe Zeff wrote:
On 03/31/2012 12:50 PM, Bob Goodwin - Zuni, Virginia, USA wrote:
I tried yum whatprovides Network Device Control with no luck, That's probably not the name it wants,system-config-network is what you're looking for. And, I've checked: you can change the IP address there quite easily.
Yes that is it. yum took seven seconds to download and install it with my new satellite system! That's satisfying since I've had a lot of grief with this changeover, it feels good when stuff works for a change!
I convinced the installers that they could do their checkout from this Linux system, didn't need Windows, they left favorably impressed.
Bob
On Sat, 2012-03-31 at 14:55 -0400, Bob Goodwin wrote:
On 03/31/2012 01:13 PM, Joe Zeff wrote:
On 03/31/2012 09:07 AM, Bob Goodwin wrote:
There used to be a menu that I used for this but with F16/XFCE I am lost. Would someone be kind enough to tell me how to do this?From the main menu, go to Applications, Administration. I have both Network and Network Device Control. If one doesn't help, try the other.
I have neither of those although I think Network Device Control is what I used in the past? Man ifconfig says: NOTE This program is obsolete! For replacement check ip addr and ip link. For statistics use ip -s link. I did that: ip addr 192.168.2.0/24 dev em1 I also tried: route add -net 192.168.2.0/24 em1 Which leaves me wondering how to verify the change has been added and then how do I access the unknown device. it is supposed to default to an address in the 192.168.2 subnet which I can access from Firefox however I haven't been able to find it with a few trial and error attempts. There must be a logical approach to this? This is a minimum quality IP Camera [Zonet zvc7611w] that I use to watch the front driveway. I pressed the reset button and then can find the cdrom with the support information and have found nothing on-line and got no response from Zonet. Not surprisingly it is a discontinued product. It would overheat and fail until I added vent holes and a tiny fan to both of them, I have two. Bob
To make ifconfig obsolete is really weird. It sounds to me that developers of Fedora have to much time on their hands. Next I expect they will change the name of vi. Oh, I forgot it is now vim. Where is Ed Joy when we need him? [He was the creator of vi, in the very beginning.]
On 03/31/2012 04:01 PM, Joe Zeff wrote:
On 03/31/2012 12:50 PM, Bob Goodwin - Zuni, Virginia, USA wrote:
I tried yum whatprovides Network Device Control with no luck, That's probably not the name it wants,system-config-network is what you're looking for. And, I've checked: you can change the IP address there quite easily.
And that enabled me to access the IP Camera and reset the address to 192.168.1.51 as required to work in my system.
Thanks much,
Bob
Am 01.04.2012 00:39, schrieb Bob Goodwin - Zuni:
On 03/31/2012 04:01 PM, Joe Zeff wrote:
On 03/31/2012 12:50 PM, Bob Goodwin - Zuni, Virginia, USA wrote:
I tried yum whatprovides Network Device Control with no luck, That's probably not the name it wants,system-config-network is what you're looking for. And, I've checked: you can change the IP address there quite easily.
And that enabled me to access the IP Camera and reset the address to 192.168.1.51 as required to work in my system. Thanks much, Bob
for this cases i have a windows virtual machine with MSIE7 with bridged-network configured at the following ip-addresses
three benefits:
* no re-configure of work.machines * can access each network device with vendor-address * most of the crap needs MSIE for web-interface
192.168.196.105 192.168.172.105 192.168.10.105 192.168.2.105 192.168.1.105 10.10.0.105 10.0.0.105
On Sat, Mar 31, 2012 at 03:56:01PM -0500, Aaron Konstam wrote:
To make ifconfig obsolete is really weird. It sounds to me that developers of Fedora have to much time on their hands. Next I expect they will change the name of vi. Oh, I forgot it is now vim. Where is Ed Joy when we need him? [He was the creator of vi, in the very beginning.]
I think you mean Bill Joy.
On Sat, 2012-03-31 at 14:55 -0400, Bob Goodwin wrote:
This is a minimum quality IP Camera [Zonet zvc7611w] that I use to watch the front driveway. I pressed the reset button and then can find the cdrom with the support information and have found nothing on-line and got no response from Zonet. Not surprisingly it is a discontinued product. It would overheat and fail until I added vent holes and a tiny fan to both of them, I have two.
You should be able to access it, even from a different network, unless *IT* is denying access to the other network address, that makes things more difficult. If it isn't, and you can change your netmask, at least, it should be easily accessible.
If you can't change a netmask, and if you have a router on your network (like an ADSL modem/router), it can be used as a gateway between your networks.
I notice, later in the thread, a mention lack of the tools you want to play with in the current incarnation of Fedora. If you still have a live CD of an older release? You could boot up that, and use it to reconfigure your camera.
On Sat, 31 Mar 2012 15:56:01 -0500, Aaron Konstam wrote:
To make ifconfig obsolete is really weird. It sounds to me that developers of Fedora have to much time on their hands. Next I expect they will change the name of vi. Oh, I forgot it is now vim. Where is Ed Joy when we need him? [He was the creator of vi, in the very beginning.]
AFAIK ifconfig is deprecated in favor of iproute2, which seems not specific to Fedora. See also the link below[1].
[1] http://en.wikipedia.org/wiki/Ifconfig#Current_status
On Sat, 2012-03-31 at 19:13 -0400, fred smith wrote:
On Sat, Mar 31, 2012 at 03:56:01PM -0500, Aaron Konstam wrote:
To make ifconfig obsolete is really weird. It sounds to me that developers of Fedora have to much time on their hands. Next I expect they will change the name of vi. Oh, I forgot it is now vim. Where is Ed Joy when we need him? [He was the creator of vi, in the very beginning.]
I think you mean Bill Joy.
You are right I goofed.
On Sun, 2012-04-01 at 21:17 +0800, Alick Zhao wrote:
On Sat, 31 Mar 2012 15:56:01 -0500, Aaron Konstam wrote:
To make ifconfig obsolete is really weird. It sounds to me that developers of Fedora have to much time on their hands. Next I expect they will change the name of vi. Oh, I forgot it is now vim. Where is Ed Joy when we need him? [He was the creator of vi, in the very beginning.]
AFAIK ifconfig is deprecated in favor of iproute2, which seems not specific to Fedora. See also the link below[1].
[1] http://en.wikipedia.org/wiki/Ifconfig#Current_status
-- alick Fedora 16 (Verne) user https://fedoraproject.org/wiki/User:Alick
Again I am confused. ifconfig is an executable. iproute2 is a directory containing non-executables. How then does iproute2 replace ifconfig?
On Sat, Mar 31, 2012 at 15:56:01 -0500, Aaron Konstam akonstam@sbcglobal.net wrote:
To make ifconfig obsolete is really weird. It sounds to me that developers of Fedora have to much time on their hands. Next I expect they will change the name of vi. Oh, I forgot it is now vim. Where is Ed Joy when we need him? [He was the creator of vi, in the very beginning.]
ifconfig has been obsolete for a long time (in the sense that ip does more stuff, not in the packaging sense).
On Sun, Apr 01, 2012 at 09:10:45 -0500, Aaron Konstam akonstam@sbcglobal.net wrote:
On Sun, 2012-04-01 at 21:17 +0800, Alick Zhao wrote:
Again I am confused. ifconfig is an executable. iproute2 is a directory containing non-executables. How then does iproute2 replace ifconfig?
iproute is a package. It includes commands like ip for working with routes and interfaces and tc for doing traffic control. rpm -ql iproute will list all of the files in the package.
On 2012/04/01 07:42, Bruno Wolff III wrote:
On Sat, Mar 31, 2012 at 15:56:01 -0500, Aaron Konstam akonstam@sbcglobal.net wrote:
To make ifconfig obsolete is really weird. It sounds to me that developers of Fedora have to much time on their hands. Next I expect they will change the name of vi. Oh, I forgot it is now vim. Where is Ed Joy when we need him? [He was the creator of vi, in the very beginning.]
ifconfig has been obsolete for a long time (in the sense that ip does more stuff, not in the packaging sense).
Obsolete or not, I have macros built into my fingers that type out things like "ifconfig eth0" when I am fishing for answers. Otherwise I hand edit ifcfg-eth0 or its kith and kin. The GUI tool disappoints me when I try to use it.
{^_^}
Am 01.04.2012 16:53, schrieb jdow:
On 2012/04/01 07:42, Bruno Wolff III wrote:
On Sat, Mar 31, 2012 at 15:56:01 -0500, Aaron Konstam akonstam@sbcglobal.net wrote:
To make ifconfig obsolete is really weird. It sounds to me that developers of Fedora have to much time on their hands. Next I expect they will change the name of vi. Oh, I forgot it is now vim. Where is Ed Joy when we need him? [He was the creator of vi, in the very beginning.]
ifconfig has been obsolete for a long time (in the sense that ip does more stuff, not in the packaging sense).
Obsolete or not, I have macros built into my fingers that type out things like "ifconfig eth0" when I am fishing for answers. Otherwise I hand edit ifcfg-eth0 or its kith and kin. The GUI tool disappoints me when I try to use it.
+1
999 out of 1000 cases dealing with networks can be done with ifconfig and classical network service and will hopefully be possible this way the next 20 years for static configured machines
On Sun, Apr 01, 2012 at 07:53:41 -0700, jdow jdow@earthlink.net wrote:
Obsolete or not, I have macros built into my fingers that type out things like "ifconfig eth0" when I am fishing for answers. Otherwise I hand edit ifcfg-eth0 or its kith and kin. The GUI tool disappoints me when I try to use it.
I do something similar with the ip command. I usually use ip addr to list all of the addresses associated with all of the interfaces. Sometimes ip link, if I just want to check which ones are active. I also use it to add networks to a device when playing with cheap routers. You can just do something like ip addr add dev eth0 192.168.1.3/24 to let you talk to a reset router that comes up on 192.168.1.1 by default. I don't need to mess with the rest of my netowrking or change my config in a way that affects how things come up after the next reboot.
On 2012/04/01 07:58, Reindl Harald wrote:
Am 01.04.2012 16:53, schrieb jdow:
On 2012/04/01 07:42, Bruno Wolff III wrote:
On Sat, Mar 31, 2012 at 15:56:01 -0500, Aaron Konstamakonstam@sbcglobal.net wrote:
To make ifconfig obsolete is really weird. It sounds to me that developers of Fedora have to much time on their hands. Next I expect they will change the name of vi. Oh, I forgot it is now vim. Where is Ed Joy when we need him? [He was the creator of vi, in the very beginning.]
ifconfig has been obsolete for a long time (in the sense that ip does more stuff, not in the packaging sense).
Obsolete or not, I have macros built into my fingers that type out things like "ifconfig eth0" when I am fishing for answers. Otherwise I hand edit ifcfg-eth0 or its kith and kin. The GUI tool disappoints me when I try to use it.
+1
999 out of 1000 cases dealing with networks can be done with ifconfig and classical network service and will hopefully be possible this way the next 20 years for static configured machines
ifconfig with or without a specific network device as a parameter is my friend for information. The ifup and ifdown scripts handle most of the rest after I've hand edited files. I don't try to use the more arcane ifconfig capabilities. They get me into as much trouble as they get me out of. And once ifcfg-ethX is properly edited I'm essentially done. (One console for editing and one for up and down action.) Mostly what I've had to do is fiddle with ifup-local to get special features working smoothly here. (I setup to start internal network first. Then I start external network. I fire off iptables in the ifup-local for the external network. I have my own iptables script. Firewall tools are too much of a pain for some of the tricks I pull. And THEN I fire off the ntp startup. With it all in order everything works right. When they are out of order, chaos reigns. And so far default order means something important doesn't work right. GUI tool guarantees nothing works right.)
{o.o}
On Sun, 2012-04-01 at 09:10 -0500, Aaron Konstam wrote:
On Sun, 2012-04-01 at 21:17 +0800, Alick Zhao wrote:
On Sat, 31 Mar 2012 15:56:01 -0500, Aaron Konstam wrote:
To make ifconfig obsolete is really weird. It sounds to me that developers of Fedora have to much time on their hands. Next I expect they will change the name of vi. Oh, I forgot it is now vim. Where is Ed Joy when we need him? [He was the creator of vi, in the very beginning.]
AFAIK ifconfig is deprecated in favor of iproute2, which seems not specific to Fedora. See also the link below[1].
[1] http://en.wikipedia.org/wiki/Ifconfig#Current_status
-- alick Fedora 16 (Verne) user https://fedoraproject.org/wiki/User:Alick
Let me extend my rant a little bit further. There is no program under F16 called iproute2. Ifconfig is rather straight forward program that can be used to handle the limited things that it does. It is straightforward to use with a limited number of options, therefore easy to understand. The man page for ifconfig suggests that instead you use ip with some of its options. ip , unlike ifcongog is a very complex program. Its total numenr of options and variations is mind bogelling. Therefore to get Familist with its use is similarly complex. If you have a simple command that does what needs to be done, replacing it with an extremely complex command should be avoided.
On 04/02/2012 04:09 AM, Aaron Konstam wrote:
On Sun, 2012-04-01 at 09:10 -0500, Aaron Konstam wrote:
On Sun, 2012-04-01 at 21:17 +0800, Alick Zhao wrote:
On Sat, 31 Mar 2012 15:56:01 -0500, Aaron Konstam wrote:
To make ifconfig obsolete is really weird. It sounds to me that developers of Fedora have to much time on their hands. Next I expect they will change the name of vi. Oh, I forgot it is now vim. Where is Ed Joy when we need him? [He was the creator of vi, in the very beginning.]
AFAIK ifconfig is deprecated in favor of iproute2, which seems not specific to Fedora. See also the link below[1].
[1] http://en.wikipedia.org/wiki/Ifconfig#Current_status
-- alick Fedora 16 (Verne) user https://fedoraproject.org/wiki/User:Alick
Let me extend my rant a little bit further. There is no program under F16 called iproute2.
OK, so somewhere along the line someone misspoke or a misunderstanding arose. BFD.
The man page for ifconfig simply states: "This program is obsolete! For replacement check ip addr and ip link. For statistics use ip -s link."
The ip command is part of the iproute2 "package". Misunderstanding cleared. I'm not going to back in this thread to see where the problem arose, but if it is the documentation causing it, then by all means a bugzilla should be written.
Ifconfig is rather straight forward program that can be used to handle the limited things that it does. It is straightforward to use with a limited number of options, therefore easy to understand. The man page for ifconfig suggests that instead you use ip with some of its options. ip , unlike ifcongog is a very complex program. Its total numenr of options and variations is mind bogelling. Therefore to get Familist with its use is similarly complex. If you have a simple command that does what needs to be done, replacing it with an extremely complex command should be avoided.
The man page is just telling you the state of play regarding and the "Busg" section at the end touches on its limitations. Yes, it works just fine for most people most of the time. Go ahead. Keep using it. Just like "nslookup", it is fine for most things and no reason to go ahead and concern yourself with learning "dig".
So, go ahead, keep using ifconfig. Just don't be surprised when/if at some point it no longer is part of this or other distributions.
On Mon, 2012-04-02 at 04:45 +0800, Ed Greshko wrote:
On 04/02/2012 04:09 AM, Aaron Konstam wrote:
On Sun, 2012-04-01 at 09:10 -0500, Aaron Konstam wrote:
On Sun, 2012-04-01 at 21:17 +0800, Alick Zhao wrote:
On Sat, 31 Mar 2012 15:56:01 -0500, Aaron Konstam wrote:
To make ifconfig obsolete is really weird. It sounds to me that developers of Fedora have to much time on their hands. Next I expect they will change the name of vi. Oh, I forgot it is now vim. Where is Ed Joy when we need him? [He was the creator of vi, in the very beginning.]
AFAIK ifconfig is deprecated in favor of iproute2, which seems not specific to Fedora. See also the link below[1].
[1] http://en.wikipedia.org/wiki/Ifconfig#Current_status
-- alick Fedora 16 (Verne) user https://fedoraproject.org/wiki/User:Alick
Let me extend my rant a little bit further. There is no program under F16 called iproute2.
OK, so somewhere along the line someone misspoke or a misunderstanding arose. BFD.
The man page for ifconfig simply states: "This program is obsolete! For replacement check ip addr and ip link. For statistics use ip -s link."
The ip command is part of the iproute2 "package". Misunderstanding cleared. I'm not going to back in this thread to see where the problem arose, but if it is the documentation causing it, then by all means a bugzilla should be written.
ip is not part of the iproute2 package. It is part of the iproute package. So we can fix at least one misunderstanding.
On 04/02/2012 04:52 AM, Aaron Konstam wrote:
ip is not part of the iproute2 package. It is part of the iproute package. So we can fix at least one misunderstanding.
OMG.... I forgot the "-" too.... BFD.
On 04/02/2012 07:38 AM, Ed Greshko wrote:
On 04/02/2012 04:52 AM, Aaron Konstam wrote:
ip is not part of the iproute2 package. It is part of the iproute package. So we can fix at least one misunderstanding.
OMG.... I forgot the "-" too.... BFD.
And I forgot the () as in iproute(-2).
Everywhere one looks it is referred to this way: iproute2 is a collection of utilities for controlling TCP and UDP IP networking and traffic control in Linux, in both IPv4 and IPv6 networks.
The downloads from kernel.org has the latest download at iproute2-3.1.0.tar.bz2.
I suppose one could argue that fedora package it as iproute2-3.1.0
On 2012/04/01 13:45, Ed Greshko wrote:
On 04/02/2012 04:09 AM, Aaron Konstam wrote:
On Sun, 2012-04-01 at 09:10 -0500, Aaron Konstam wrote:
On Sun, 2012-04-01 at 21:17 +0800, Alick Zhao wrote:
On Sat, 31 Mar 2012 15:56:01 -0500, Aaron Konstam wrote:
To make ifconfig obsolete is really weird. It sounds to me that developers of Fedora have to much time on their hands. Next I expect they will change the name of vi. Oh, I forgot it is now vim. Where is Ed Joy when we need him? [He was the creator of vi, in the very beginning.]
AFAIK ifconfig is deprecated in favor of iproute2, which seems not specific to Fedora. See also the link below[1].
[1] http://en.wikipedia.org/wiki/Ifconfig#Current_status
-- alick Fedora 16 (Verne) user https://fedoraproject.org/wiki/User:Alick
Let me extend my rant a little bit further. There is no program under F16 called iproute2.
OK, so somewhere along the line someone misspoke or a misunderstanding arose. BFD.
The man page for ifconfig simply states: "This program is obsolete! For replacement check ip addr and ip link. For statistics use ip -s link."
The ip command is part of the iproute2 "package". Misunderstanding cleared. I'm not going to back in this thread to see where the problem arose, but if it is the documentation causing it, then by all means a bugzilla should be written.
Ifconfig is rather straight forward program that can be used to handle the limited things that it does. It is straightforward to use with a limited number of options, therefore easy to understand. The man page for ifconfig suggests that instead you use ip with some of its options. ip , unlike ifcongog is a very complex program. Its total numenr of options and variations is mind bogelling. Therefore to get Familist with its use is similarly complex. If you have a simple command that does what needs to be done, replacing it with an extremely complex command should be avoided.
The man page is just telling you the state of play regarding and the "Busg" section at the end touches on its limitations. Yes, it works just fine for most people most of the time. Go ahead. Keep using it. Just like "nslookup", it is fine for most things and no reason to go ahead and concern yourself with learning "dig".
So, go ahead, keep using ifconfig. Just don't be surprised when/if at some point it no longer is part of this or other distributions.
Unfortunately "ip" violates one of the earliest tenets of the 'ix family. It's command environment was envisioned as a large number of simple commands that could be strung together to create larger capabilities. "ip" is one complex rather hard to understand command that appears to be do everything for everybody at the expense of simplicity. "ifconfig" is, itself, probably past the small programs doing small things paradigm. "ip" is a behemoth trying to be all and end all for all. It is a fundamentally bad design for its position in the command hierarchy. But that's OK. It's free. So you have to accept what you can get free. Were I purchasing a formal RedHat license I'd consider some other environment if I were forced to use a small number of complex tools rather than a larger number of simpler tools. I can make my own complex tools as needed, thank you.
IMAO "ip" sucks dead bunnies through garden hoses. {^_^}
On 04/01/2012 10:37 PM, jdow wrote:
IMAO "ip" sucks dead bunnies through garden hoses.
You do know, don't you, that the official unit of Suckyness is the LoveLace?[1] How many Ll is that?
On 2012/04/02 07:45, Joe Zeff wrote:
You do know, don't you, that the official unit of Suckyness is the LoveLace?[1] How many Ll is that?
I'm a little concerned that this definition lacks a temperature coefficient. Surely the hotter it gets, the easier it would be to suck the balls?
Z
On Mon, 2012-04-02 at 08:00 +0800, Ed Greshko wrote:
On 04/02/2012 07:38 AM, Ed Greshko wrote:
On 04/02/2012 04:52 AM, Aaron Konstam wrote:
ip is not part of the iproute2 package. It is part of the iproute package. So we can fix at least one misunderstanding.
OMG.... I forgot the "-" too.... BFD.
And I forgot the () as in iproute(-2).
Everywhere one looks it is referred to this way: iproute2 is a collection of utilities for controlling TCP and UDP IP networking and traffic control in Linux, in both IPv4 and IPv6 networks.
The downloads from kernel.org has the latest download at iproute2-3.1.0.tar.bz2.
I suppose one could argue that fedora package it as iproute2-3.1.0
I would argue the latest fedora package is: iproute-2.6.39-5 Why do keep saying iproute-2.. is really iproute2-...?
-
Aaron Konstam -
Alick Zhao -
Bob Goodwin -
Bruno Wolff III -
Ed Greshko -
Fred Smith -
jdow -
Joe Zeff -
Mikkel L. Ellertson -
Reindl Harald -
Tim -
Tim Evans -
Zoltan Szecsei