Re: routing help
"If it works, don't fix it" is my theory.. May be a better way but I don't know it. As Jason Lim says in his post, let the list know what happens as I'm sure others will have the problem. Only change I'd consider is using the up command (man interfaces) which would execute your script after the interface was brought up, instead of on boot. That MIGHT be better. The modification would look like: auto eth0 eth1 iface eth0 inet static address 203.221.41.11 netmask 255.255.255.224 network 203.221.41.0 broadcast 203.221.41.31 up /path/to/your/script You can also, according to the man page, simply put your script directly into /etc/interfaces, preceding each command with "up", and the commands would happen in order, ie: auto eth0 eth1 iface eth0 inet static address 203.221.41.11 netmask 255.255.255.224 network 203.221.41.0 broadcast 203.221.41.31 up /sbin/route add -net 203.220.47.152/30 eth0 up /sbin/route add default gw 203.220.47.153 up /bin/ping -c1 203.220.238.152 up /sbin/ifconfig eth0 203.221.41.12 netmask 255.255.255.224 broadcast 203.221.41.31 . . . etc Rod > Hi Rod, > > After a bit more playing and a bit more thinking I finally figured it > out..I think > > What it looks like is that the router I am using as the gateway > (203.220.47.153) needed to have its ARP table updated or flushed or > something. I don't have control over it so I can't be sure. What I > now have is a script that runs after boot time that looks like: > > /sbin/route add -net 203.220.47.152/30 eth0 > /sbin/route add default gw 203.220.47.153 > /bin/ping -c1 203.220.238.152 > /sbin/ifconfig eth0 203.221.41.12 netmask 255.255.255.224 broadcast > 203.221.41.31 > /sbin/route add -net 203.220.47.152/30 eth0 > /sbin/route add default gw 203.220.47.153 > /bin/ping -c1 203.220.238.152 > /sbin/ifconfig eth0 203.221.41.13 netmask 255.255.255.224 broadcast > 203.221.41.31 > /sbin/route add -net 203.220.47.152/30 eth0 > /sbin/route add default gw 203.220.47.153 > /bin/ping -c1 203.220.238.152 > /sbin/ifconfig eth0 203.221.41.11 netmask 255.255.255.224 broadcast > 203.221.41.31 > /sbin/ifconfig eth0:0 203.221.41.12 netmask 255.255.255.224 broadcast > 203.221.41.31 > /sbin/ifconfig eth0:1 203.221.41.13 netmask 255.255.255.224 broadcast > 203.221.41.31 > /sbin/route add -net 203.220.47.152/30 eth0 > /sbin/route add default gw 203.220.47.153 > /bin/ping -c1 203.220.238.152 > > it basically cycles through the ip addresses pinging a host on just the > other side of the router so it flushes the ARP cache. Does this sound > correct or am I totally off the track here? Anyway it is all working > now but I guess I'd like to know if what I had to do was correct or > not? > > Cheers, > > Lauchlin > > On 26/01/2004, at 2:31 PM, Rod Rodolico wrote: > >> Sorry to be vague, but there was a command I remember once when I had >> this problem before. >> Seems like I had to do a route add in /network/interfaces. Seems like >> there is some parameter >> to an interface that allows you to execute a command after the >> interface is brought up, and I >> had to do a route add . . . . to get it to work. >> >> However, I'm doing a similar thing, on my server and the only >> difference is that my netmask is >> not 255.255.255.255, > > mine is 255.255.255.224. The first line in the route output was a host > entry that I don't seem to need after all. > >> which I think is incorrect on yours. Maybe it is the fact that your >> netmask is not correct? Following are the first two entries in my >> /etc/network/interfaces, and >> it works just fine. If I read your output correctly, your netmask >> should be a .224 instead of >> the .0 I use (since you only have two IP's). >> >> auto eth0 >> iface eth0 inet static >> address 66.17.131.182 >> netmask 255.255.255.0 >> network 66.17.131.0 >> broadcast 66.17.131.255 >> gateway 66.17.131.1 >> >> auto eth0:0 >> iface eth0:0 inet static >> address 66.17.131.183 >> netmask 255.255.255.0 >> > > auto eth0 eth1 > iface eth0 inet static > address 203.221.41.11 > netmask 255.255.255.224 > network 203.221.41.0 > broadcast 203.221.41.31 > > is what I have. > > >> Of course, I could be 100% wrong, in which case someone here will >> correct me. >> >> Rod >> >>> Hi, >>> >>> I have an issue with routing that I just can't figure out. >>> >>> What I have at the moment is a box set up with an IP and route as >>> follows (some of the details have >>> >>> route -n >>> Kernel IP routing table >>> Destination Gateway Genmask Flags Metric Ref >>> Use >>> Iface >>> 203.221.41.11 0.0.0.0 255.255.255.255 UH0 0 >>> 0 >>> eth0 >>> 203.220.47.152 0.0.0.0 255.255.255.252 U 0 0 >>> 0 >>> eth0 >>> 203.221.41.00.0.0.0 255.255.255.224 U 0 0 >>> 0 >>> eth0 >>> 0.0.0.0 203.220.47.153 0.0.0.0
Re: routing help
"If it works, don't fix it" is my theory.. May be a better way but I don't know it. As Jason Lim says in his post, let the list know what happens as I'm sure others will have the problem. Only change I'd consider is using the up command (man interfaces) which would execute your script after the interface was brought up, instead of on boot. That MIGHT be better. The modification would look like: auto eth0 eth1 iface eth0 inet static address 203.221.41.11 netmask 255.255.255.224 network 203.221.41.0 broadcast 203.221.41.31 up /path/to/your/script You can also, according to the man page, simply put your script directly into /etc/interfaces, preceding each command with "up", and the commands would happen in order, ie: auto eth0 eth1 iface eth0 inet static address 203.221.41.11 netmask 255.255.255.224 network 203.221.41.0 broadcast 203.221.41.31 up /sbin/route add -net 203.220.47.152/30 eth0 up /sbin/route add default gw 203.220.47.153 up /bin/ping -c1 203.220.238.152 up /sbin/ifconfig eth0 203.221.41.12 netmask 255.255.255.224 broadcast 203.221.41.31 . . . etc Rod > Hi Rod, > > After a bit more playing and a bit more thinking I finally figured it > out..I think > > What it looks like is that the router I am using as the gateway > (203.220.47.153) needed to have its ARP table updated or flushed or > something. I don't have control over it so I can't be sure. What I > now have is a script that runs after boot time that looks like: > > /sbin/route add -net 203.220.47.152/30 eth0 > /sbin/route add default gw 203.220.47.153 > /bin/ping -c1 203.220.238.152 > /sbin/ifconfig eth0 203.221.41.12 netmask 255.255.255.224 broadcast > 203.221.41.31 > /sbin/route add -net 203.220.47.152/30 eth0 > /sbin/route add default gw 203.220.47.153 > /bin/ping -c1 203.220.238.152 > /sbin/ifconfig eth0 203.221.41.13 netmask 255.255.255.224 broadcast > 203.221.41.31 > /sbin/route add -net 203.220.47.152/30 eth0 > /sbin/route add default gw 203.220.47.153 > /bin/ping -c1 203.220.238.152 > /sbin/ifconfig eth0 203.221.41.11 netmask 255.255.255.224 broadcast > 203.221.41.31 > /sbin/ifconfig eth0:0 203.221.41.12 netmask 255.255.255.224 broadcast > 203.221.41.31 > /sbin/ifconfig eth0:1 203.221.41.13 netmask 255.255.255.224 broadcast > 203.221.41.31 > /sbin/route add -net 203.220.47.152/30 eth0 > /sbin/route add default gw 203.220.47.153 > /bin/ping -c1 203.220.238.152 > > it basically cycles through the ip addresses pinging a host on just the > other side of the router so it flushes the ARP cache. Does this sound > correct or am I totally off the track here? Anyway it is all working > now but I guess I'd like to know if what I had to do was correct or > not? > > Cheers, > > Lauchlin > > On 26/01/2004, at 2:31 PM, Rod Rodolico wrote: > >> Sorry to be vague, but there was a command I remember once when I had >> this problem before. >> Seems like I had to do a route add in /network/interfaces. Seems like >> there is some parameter >> to an interface that allows you to execute a command after the >> interface is brought up, and I >> had to do a route add . . . . to get it to work. >> >> However, I'm doing a similar thing, on my server and the only >> difference is that my netmask is >> not 255.255.255.255, > > mine is 255.255.255.224. The first line in the route output was a host > entry that I don't seem to need after all. > >> which I think is incorrect on yours. Maybe it is the fact that your >> netmask is not correct? Following are the first two entries in my >> /etc/network/interfaces, and >> it works just fine. If I read your output correctly, your netmask >> should be a .224 instead of >> the .0 I use (since you only have two IP's). >> >> auto eth0 >> iface eth0 inet static >> address 66.17.131.182 >> netmask 255.255.255.0 >> network 66.17.131.0 >> broadcast 66.17.131.255 >> gateway 66.17.131.1 >> >> auto eth0:0 >> iface eth0:0 inet static >> address 66.17.131.183 >> netmask 255.255.255.0 >> > > auto eth0 eth1 > iface eth0 inet static > address 203.221.41.11 > netmask 255.255.255.224 > network 203.221.41.0 > broadcast 203.221.41.31 > > is what I have. > > >> Of course, I could be 100% wrong, in which case someone here will >> correct me. >> >> Rod >> >>> Hi, >>> >>> I have an issue with routing that I just can't figure out. >>> >>> What I have at the moment is a box set up with an IP and route as >>> follows (some of the details have >>> >>> route -n >>> Kernel IP routing table >>> Destination Gateway Genmask Flags Metric Ref >>> Use >>> Iface >>> 203.221.41.11 0.0.0.0 255.255.255.255 UH0 0 >>> 0 >>> eth0 >>> 203.220.47.152 0.0.0.0 255.255.255.252 U 0 0 >>> 0 >>> eth0 >>> 203.221.41.00.0.0.0 255.255.255.224 U 0 0 >>> 0 >>> eth0 >>> 0.0.0.0 203.220.47.153 0.0.0.0
Re: CISCO netflow graphs on Linux
From: "Craig Schneider" <[EMAIL PROTECTED]> Subject: CISCO netflow graphs on Linux Date: Mon, 26 Jan 2004 11:46:39 +0200 > Hi Guys > > Can anyone recommend software to graph Cisco's netflow traffic on Debian > ? > > Thanks > Craig Today, I have uploaded "flowscan" and "flow-tools" to debian incoming queue(for sid) as deb package sponsor. These packages are packaged by Anibal Monsalve Salazar <[EMAIL PROTECTED]>. If you want to try ASAP, following URLs maybe help you. http://www-personal.monash.edu.au/~anibal/debian/flow-tools/ http://www-personal.monash.edu.au/~anibal/debian/flowscan/ -- ARAKI Yasuhiro A Debian Official Developer <[EMAIL PROTECTED]>
Re: CISCO netflow graphs on Linux
From: "Craig Schneider" <[EMAIL PROTECTED]> Subject: CISCO netflow graphs on Linux Date: Mon, 26 Jan 2004 11:46:39 +0200 > Hi Guys > > Can anyone recommend software to graph Cisco's netflow traffic on Debian > ? > > Thanks > Craig Today, I have uploaded "flowscan" and "flow-tools" to debian incoming queue(for sid) as deb package sponsor. These packages are packaged by Anibal Monsalve Salazar <[EMAIL PROTECTED]>. If you want to try ASAP, following URLs maybe help you. http://www-personal.monash.edu.au/~anibal/debian/flow-tools/ http://www-personal.monash.edu.au/~anibal/debian/flowscan/ -- ARAKI Yasuhiro A Debian Official Developer <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: CISCO netflow graphs on Linux
In a book I am reading (Open Source Network Administration by James Kretchmar, highly recommended), they cover OSU FlowTools (http://www.net.ohio-state.edu/software) to deal with NetFlow data. While I haven't tried this myself (we don't use Cisco), if it is as good as everything else they recommend in the book, I would expect it to be pretty damn good. shawn On 26-Jan-04, at 3:46 AM, Craig Schneider wrote: Hi Guys Can anyone recommend software to graph Cisco's netflow traffic on Debian ? Thanks Craig -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: CISCO netflow graphs on Linux
In a book I am reading (Open Source Network Administration by James Kretchmar, highly recommended), they cover OSU FlowTools (http://www.net.ohio-state.edu/software) to deal with NetFlow data. While I haven't tried this myself (we don't use Cisco), if it is as good as everything else they recommend in the book, I would expect it to be pretty damn good. shawn On 26-Jan-04, at 3:46 AM, Craig Schneider wrote: Hi Guys Can anyone recommend software to graph Cisco's netflow traffic on Debian ? Thanks Craig -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: CISCO netflow graphs on Linux
You are better off sticking to flatfiles, perl and RRD. Excel wont be able to deal with the amount of data that netflow generates, and a database is just a VERY expensive way of doing it (Data grows to at least 4 times the size)... Maybe you are agregating a lot more than we did... Cheers Andrew > RRDTool gives a lot of flexibility, and is a related project of mrtg. > Recently I got to use what is marketed as pivot :) In short, if you > could dump your data in a database or even in a flat file, you can > connect to it through a spreadsheet (open-office is fully compatible > for the perticular feature wih MS excell). The beauty of this > technique is, you can give any no of different dimentions (olap word, > in short lets say in case of time -> years, months, weeks, days, > hours...), and create a report, and it allows you to drill down, just > as you like.
Re: CISCO netflow graphs on Linux
Craig Schneider wrote: Hi Guys Can anyone recommend software to graph Cisco's netflow traffic on Debian ? Thanks Craig RRDTool gives a lot of flexibility, and is a related project of mrtg. Recently I got to use what is marketed as pivot :) In short, if you could dump your data in a database or even in a flat file, you can connect to it through a spreadsheet (open-office is fully compatible for the perticular feature wih MS excell). The beauty of this technique is, you can give any no of different dimentions (olap word, in short lets say in case of time -> years, months, weeks, days, hours...), and create a report, and it allows you to drill down, just as you like. There is an application called crystal info that even alows you to design & email these files (called cubes) to people. In version 7, this tool was free. In any case, as long as you dump your data in a DB, rest of the task can be doen from a spreadsheet. I have used RRD & mrtg, and I find that pivot (MS name to this sort of basic olap functionality) is exremely powerfull. What's better, openoffice allows a similar feature, so you can actually do this on linux. regards, prasad
Re: CISCO netflow graphs on Linux
You are better off sticking to flatfiles, perl and RRD. Excel wont be able to deal with the amount of data that netflow generates, and a database is just a VERY expensive way of doing it (Data grows to at least 4 times the size)... Maybe you are agregating a lot more than we did... Cheers Andrew > RRDTool gives a lot of flexibility, and is a related project of mrtg. > Recently I got to use what is marketed as pivot :) In short, if you > could dump your data in a database or even in a flat file, you can > connect to it through a spreadsheet (open-office is fully compatible > for the perticular feature wih MS excell). The beauty of this > technique is, you can give any no of different dimentions (olap word, > in short lets say in case of time -> years, months, weeks, days, > hours...), and create a report, and it allows you to drill down, just > as you like. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: CISCO netflow graphs on Linux
Craig Schneider wrote: Hi Guys Can anyone recommend software to graph Cisco's netflow traffic on Debian ? Thanks Craig RRDTool gives a lot of flexibility, and is a related project of mrtg. Recently I got to use what is marketed as pivot :) In short, if you could dump your data in a database or even in a flat file, you can connect to it through a spreadsheet (open-office is fully compatible for the perticular feature wih MS excell). The beauty of this technique is, you can give any no of different dimentions (olap word, in short lets say in case of time -> years, months, weeks, days, hours...), and create a report, and it allows you to drill down, just as you like. There is an application called crystal info that even alows you to design & email these files (called cubes) to people. In version 7, this tool was free. In any case, as long as you dump your data in a DB, rest of the task can be doen from a spreadsheet. I have used RRD & mrtg, and I find that pivot (MS name to this sort of basic olap functionality) is exremely powerfull. What's better, openoffice allows a similar feature, so you can actually do this on linux. regards, prasad -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: CISCO netflow graphs on Linux
> -Original Message- > From: Craig Schneider [mailto:[EMAIL PROTECTED] > Can anyone recommend software to graph Cisco's netflow > traffic on Debian ? mrtg!
Re: CISCO netflow graphs on Linux
On Mon, 2004-01-26 at 09:46, Craig Schneider wrote: > Hi Guys > > Can anyone recommend software to graph Cisco's netflow traffic on Debian Not a Debian package, but it's only 4 Perl scripts... http://flavio.sf.net/ It has a few caveats, the biggest of which seems to be that it won't actually update the graphs until it's collected maybe an hour of data. Aside from that, it works well. Cheers, Gavin.
CISCO netflow graphs on Linux
Hi Guys Can anyone recommend software to graph Cisco's netflow traffic on Debian ? Thanks Craig
RE: CISCO netflow graphs on Linux
> -Original Message- > From: Craig Schneider [mailto:[EMAIL PROTECTED] > Can anyone recommend software to graph Cisco's netflow > traffic on Debian ? mrtg! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: CISCO netflow graphs on Linux
On Mon, 2004-01-26 at 09:46, Craig Schneider wrote: > Hi Guys > > Can anyone recommend software to graph Cisco's netflow traffic on Debian Not a Debian package, but it's only 4 Perl scripts... http://flavio.sf.net/ It has a few caveats, the biggest of which seems to be that it won't actually update the graphs until it's collected maybe an hour of data. Aside from that, it works well. Cheers, Gavin. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
CISCO netflow graphs on Linux
Hi Guys Can anyone recommend software to graph Cisco's netflow traffic on Debian ? Thanks Craig -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
