To get your external IP, you could write a small perl script like the following:
#!/usr/bin/perl -w
use Socket;
$hostname = "insert.hostname.here";
print inet_ntoa(inet_aton($hostname));
I actually have a qualified domain name pointing to my network, but if you don't have that you can use the hostname that your ISP gives you assuming that it doesn't change along with your IP address.
Finally decided to try this theme out after seeing it again while browsing. I wanted to see how the theme dealt with output from "ip", as it's quite a lot to filter through. After a quick glance at the theme file, I saw that the prog being used is "hostname -i".
Here's the problem with that. On my system, "hostname -i" returns 127.0.0.1. I'm pretty sure that's not my external IP :-). The problem is that I use a custom hostname versus the one that my ISP assigns me automatically ("HAL-9000" if you must know). I have this hostname mapped to the loopback address, so that when my internet connection goes down on rare occassions X will still respond normally (otherwise applications load extremely slowly, as it's trying to resolve a hostname that has no entry in /etc/hosts, and no, I can't put an entry there as the auto assigned hostname changes from time to time). Anyhow, the point is, in some instances (i.e mine) the hostname has nothing to do with the external IP.
I would suggest the theme use something like the following:
program="/sbin/ip addr show eth0 | grep 'inet ' | cut -d t -f2 | cut -d / -f1"
It still has a trailing space in front, and I'm sure there's a way to get rid of that, but this is just what I banged up in a min. or so. In any case, it's more ideal than "hostname -i". Oh yeah, and looking at that sequence I just realized some people may be working with multiple interfaces (eth1, eth2, etc.). In fact, I have another system here that I use eth1, since eth0 is an onboard network device that has probs. Anyhow, maybe you could have the user specify from which device they'd like to get info.
a basic karamba theme, but still useful. what i would like to see expanded by this project:
- both ip addresses utilized on one machine. (meaning both the real ip, and the ip assigned by a router)
- would be cool if it displayed the service you were connected to. (basically dns'ing the ip and reporting the service it comes from?)
- ping time included (so we can see the non existant lag on our faster connections :p)
- and maybe even a visual route readout of where the connection originates.
I know some of these might not happen, but it would be cool if we could organize all of these ideas into one nice theme. I would like to assist in this project and develop it further.
That should be simple, actually. Any command that provides text output can be displayed on the desktop via karamba. So, traceroute, for instance, could be run and displayed on the desktop. If you can figure out how to produce the output in bash, you can easily do it in karamba :-)
You're right. I have been working on it and am making some progress. I hope to finish up the output and get it working perfectly and produce a nice karamba theme. I will keep the group informed.
Ratings & Comments
6 Comments
To get your external IP, you could write a small perl script like the following: #!/usr/bin/perl -w use Socket; $hostname = "insert.hostname.here"; print inet_ntoa(inet_aton($hostname)); I actually have a qualified domain name pointing to my network, but if you don't have that you can use the hostname that your ISP gives you assuming that it doesn't change along with your IP address.
Finally decided to try this theme out after seeing it again while browsing. I wanted to see how the theme dealt with output from "ip", as it's quite a lot to filter through. After a quick glance at the theme file, I saw that the prog being used is "hostname -i". Here's the problem with that. On my system, "hostname -i" returns 127.0.0.1. I'm pretty sure that's not my external IP :-). The problem is that I use a custom hostname versus the one that my ISP assigns me automatically ("HAL-9000" if you must know). I have this hostname mapped to the loopback address, so that when my internet connection goes down on rare occassions X will still respond normally (otherwise applications load extremely slowly, as it's trying to resolve a hostname that has no entry in /etc/hosts, and no, I can't put an entry there as the auto assigned hostname changes from time to time). Anyhow, the point is, in some instances (i.e mine) the hostname has nothing to do with the external IP. I would suggest the theme use something like the following: program="/sbin/ip addr show eth0 | grep 'inet ' | cut -d t -f2 | cut -d / -f1" It still has a trailing space in front, and I'm sure there's a way to get rid of that, but this is just what I banged up in a min. or so. In any case, it's more ideal than "hostname -i". Oh yeah, and looking at that sequence I just realized some people may be working with multiple interfaces (eth1, eth2, etc.). In fact, I have another system here that I use eth1, since eth0 is an onboard network device that has probs. Anyhow, maybe you could have the user specify from which device they'd like to get info.
Ok, I will update it. With this command line: /sbin/ip addr show eth0 | grep 'inet ' | cut -d t -f2 | cut -d / -f1 | cut -b 2-
a basic karamba theme, but still useful. what i would like to see expanded by this project: - both ip addresses utilized on one machine. (meaning both the real ip, and the ip assigned by a router) - would be cool if it displayed the service you were connected to. (basically dns'ing the ip and reporting the service it comes from?) - ping time included (so we can see the non existant lag on our faster connections :p) - and maybe even a visual route readout of where the connection originates. I know some of these might not happen, but it would be cool if we could organize all of these ideas into one nice theme. I would like to assist in this project and develop it further.
That should be simple, actually. Any command that provides text output can be displayed on the desktop via karamba. So, traceroute, for instance, could be run and displayed on the desktop. If you can figure out how to produce the output in bash, you can easily do it in karamba :-)
You're right. I have been working on it and am making some progress. I hope to finish up the output and get it working perfectly and produce a nice karamba theme. I will keep the group informed.