devil-linux-discuss — General Mailing List for all discussions

Re: [Devil-Linux-discuss] Updating to 1.2.11

[Bruce S. <bw...@ar...>]

> Whilst these are minor irritants it does bother me that things are being added 
> to the system without proper auditing.  This is supposed to be a secure system 
> and addition of unverified software obviously gives an opportunity for malware 
> to be unwittingly installed.

Can you be more specific about what unverified software you're referring to?

 - BS

Re: [Devil-Linux-discuss] Updating to 1.2.11

[Dick M. <di...@li...>]

Dick Middleton wrote:
> Hello,
> 
> 	I've just updated from 1.2.9 to 1.2.11 and have encountered an odd problem. 

Some more things:

   The recently added aide is broken.  It's obviously copied from Debian and 
some needed parts don't exist (such as /var/lib/aide, /etc/default, tempfile 
command and others).  That's all very well except the script in /etc/cron.daily 
exists and fails.  Firstly it fails because it doesn't have execute permission 
and secondly it fails because programs and directories it references don't exist.

   The recently added awstats is also broken for a similar reason.  The script 
in cron.daily doesn't have execute permissions. I've not tried to run this but I 
notice various files with 1980 timestamps such as the aforementioned and 
/etc/awstats/awstats.model.conf.

Whilst these are minor irritants it does bother me that things are being added 
to the system without proper auditing.  This is supposed to be a secure system 
and addition of unverified software obviously gives an opportunity for malware 
to be unwittingly installed.

Dick

[Devil-Linux-discuss] OT: Spam Blacklists

[drew e. <dre...@gm...>]

Apparently this list has been using a bogus blacklist.
My mail to the list has been silently disappearing into a blackhole
for the past week or so.

Finally I discovered
http://www.mxtoolbox.com/blacklists.aspx?AG=GBL&gclid=CI7gntKM1YgCFQR8VAod9FJsZg

It told I was on the http://www.moensted.dk/spam/no-more-funn/ blacklist
because netblk-q0228-65-125-188-0 is home to spammers.

This makes no sense.  My ip 209.181.116.109 is not even in that netblock!

Fortunately the automated whitelist tool promptly removed me from the
blacklist.
So you should see this email.

Or maybe I have to wait a while longer for your dns cache to expire.

Arghhhhhh!

Please discontinue using this buggy blacklist!

-- 
Drew Einhorn

[Devil-Linux-discuss] Traffic Shaping on a Transparent Bridge not working!

[drew e. <dre...@gm...>]

My first DL project was going well.  Then I ran into problems attempting
to shape my bandwidth.

First I'll describe the parts that I believe are working correctly.

I have a DL 1.2.11 box running the default kernel, 2.4.33.3-grsec

I have br0 bridging all four ports eth0, eth1, eth2, eth3 on a quad port
pci card.  The bridge has not been assigned an ip number on the theory
that this makes it much more difficult to attack.  The bridge connects
four devices on the 3bit public static ip block from my ISP.

I have a single port ethernet pci card, eth4 with a static ip, on my
internal private ip network.  It is used for remote managent of the DL
box from anywhere on my internal network.

eth0 is connected to my ISP's router via the ethernet port on my
ISDN modem.  I know ISDN is a nearly dead technology, but it's the best
thing my crappy telco offers.  Tried a satellite ISP, but that's another
long story.

eth1 is connected to a hardened publicly accessible host.

eth2 and eth3 are connected to the WAN ports on a couple of Linksys
Cable/DSL routers.  Eventually most of their functions will migrate to the
DL box, but that is more than I wanted to bite off in my first DL project.

The first Linksys box NATs one of my public ips to my internal private
ip network.  The second Linksys box is newer and includes a wireless
access point used by a couple neighbors.  It NATs a second public ip to
a separate private ip network.

All of the above appears to be working as expected.

After pondering the mysteries of traffic shaping I decided to start with
wondershaper 1.1a from lartc.org, rather than starting from scratch.

Tried both the cbq and htb versions without any success.

RTFM time.  The htb section of http://lartc.org/howto/index.html is easier
reading than the cbq section.  And the howto claims htb is better anyway.
Let's focus on the htb version of wondershaper.

OK, First we edit wshaper.htb and configure the shell variables.  Then we
run:  sh -x wshaper.htb
to echo the commands as they are executed.

Then we start pinging the router at the other end of the ISDN line.

Then we start downloading a file to generate some traffic that really
needs to be shaped.

Then we run: sh -x wshaper.htb status
to gather some statistics

then we kill the download.

then we sh -x wshaper.htb stop to shut down the malfunctioning shaper.

Here's the output from the ping:

$ ping 67.0.192.10
PING 67.0.192.10 (67.0.192.10) 56(84) bytes of data.

Link is idle, normal ping times.

64 bytes from 67.0.192.10: icmp_seq=0 ttl=254 time=48.5 ms
64 bytes from 67.0.192.10: icmp_seq=1 ttl=254 time=48.4 ms
64 bytes from 67.0.192.10: icmp_seq=2 ttl=254 time=48.4 ms
64 bytes from 67.0.192.10: icmp_seq=3 ttl=254 time=48.4 ms
64 bytes from 67.0.192.10: icmp_seq=4 ttl=254 time=48.5 ms
64 bytes from 67.0.192.10: icmp_seq=5 ttl=254 time=67.8 ms
64 bytes from 67.0.192.10: icmp_seq=6 ttl=254 time=48.3 ms
64 bytes from 67.0.192.10: icmp_seq=7 ttl=254 time=48.2 ms

Download starts.  Shaping is not working!  Queues in
router and/or ISDN modem grow, and ping times rapidly
become huge.

64 bytes from 67.0.192.10: icmp_seq=8 ttl=254 time=184 ms
64 bytes from 67.0.192.10: icmp_seq=9 ttl=254 time=1080 ms
64 bytes from 67.0.192.10: icmp_seq=10 ttl=254 time=2025 ms
64 bytes from 67.0.192.10: icmp_seq=11 ttl=254 time=1551 ms
64 bytes from 67.0.192.10: icmp_seq=12 ttl=254 time=1078 ms
64 bytes from 67.0.192.10: icmp_seq=13 ttl=254 time=896 ms
64 bytes from 67.0.192.10: icmp_seq=14 ttl=254 time=1088 ms
64 bytes from 67.0.192.10: icmp_seq=15 ttl=254 time=1171 ms
64 bytes from 67.0.192.10: icmp_seq=16 ttl=254 time=1272 ms
64 bytes from 67.0.192.10: icmp_seq=17 ttl=254 time=1280 ms
64 bytes from 67.0.192.10: icmp_seq=18 ttl=254 time=1101 ms
64 bytes from 67.0.192.10: icmp_seq=19 ttl=254 time=1258 ms
64 bytes from 67.0.192.10: icmp_seq=20 ttl=254 time=1211 ms
64 bytes from 67.0.192.10: icmp_seq=21 ttl=254 time=1259 ms
64 bytes from 67.0.192.10: icmp_seq=22 ttl=254 time=1373 ms
64 bytes from 67.0.192.10: icmp_seq=23 ttl=254 time=1424 ms
64 bytes from 67.0.192.10: icmp_seq=24 ttl=254 time=1461 ms
64 bytes from 67.0.192.10: icmp_seq=25 ttl=254 time=1277 ms
64 bytes from 67.0.192.10: icmp_seq=26 ttl=254 time=1521 ms
64 bytes from 67.0.192.10: icmp_seq=27 ttl=254 time=1467 ms
64 bytes from 67.0.192.10: icmp_seq=28 ttl=254 time=1335 ms
64 bytes from 67.0.192.10: icmp_seq=29 ttl=254 time=1329 ms
64 bytes from 67.0.192.10: icmp_seq=30 ttl=254 time=1386 ms
64 bytes from 67.0.192.10: icmp_seq=31 ttl=254 time=1360 ms
64 bytes from 67.0.192.10: icmp_seq=32 ttl=254 time=1416 ms
64 bytes from 67.0.192.10: icmp_seq=33 ttl=254 time=1480 ms
64 bytes from 67.0.192.10: icmp_seq=34 ttl=254 time=1345 ms
64 bytes from 67.0.192.10: icmp_seq=35 ttl=254 time=1356 ms
64 bytes from 67.0.192.10: icmp_seq=36 ttl=254 time=1370 ms
64 bytes from 67.0.192.10: icmp_seq=37 ttl=254 time=1278 ms
64 bytes from 67.0.192.10: icmp_seq=38 ttl=254 time=1612 ms
64 bytes from 67.0.192.10: icmp_seq=39 ttl=254 time=1520 ms
64 bytes from 67.0.192.10: icmp_seq=40 ttl=254 time=1322 ms
64 bytes from 67.0.192.10: icmp_seq=41 ttl=254 time=1545 ms

Kill the download queues empty and ping times return to normal

64 bytes from 67.0.192.10: icmp_seq=42 ttl=254 time=975 ms
64 bytes from 67.0.192.10: icmp_seq=43 ttl=254 time=67.4 ms
64 bytes from 67.0.192.10: icmp_seq=44 ttl=254 time=73.6 ms
64 bytes from 67.0.192.10: icmp_seq=45 ttl=254 time=45.2 ms
64 bytes from 67.0.192.10: icmp_seq=46 ttl=254 time=45.2 ms
64 bytes from 67.0.192.10: icmp_seq=47 ttl=254 time=44.8 ms


And, here's the shell commands and their output:

root@Devil:~ # sh -x wshaper.htb
+ DOWNLINK=100
+ UPLINK=100
+ DEV=eth0
+ NOPRIOHOSTSRC=
+ NOPRIOHOSTDST=
+ NOPRIOPORTSRC=
+ NOPRIOPORTDST=
+ '[' '' = status ']'
+ tc qdisc del dev eth0 root
+ tc qdisc del dev eth0 ingress
+ '[' '' = stop ']'
+ tc qdisc add dev eth0 root handle 1: htb default 20
+ tc class add dev eth0 parent 1: classid 1:1 htb rate 100kbit burst 6k
+ tc class add dev eth0 parent 1:1 classid 1:10 htb rate 100kbit burst 6k
prio 1
+ tc class add dev eth0 parent 1:1 classid 1:20 htb rate 90kbit burst 6k
prio 2
+ tc class add dev eth0 parent 1:1 classid 1:30 htb rate 80kbit burst 6k
prio 2
+ tc qdisc add dev eth0 parent 1:10 handle 10: sfq perturb 10
+ tc qdisc add dev eth0 parent 1:20 handle 20: sfq perturb 10
+ tc qdisc add dev eth0 parent 1:30 handle 30: sfq perturb 10
+ tc filter add dev eth0 parent 1:0 protocol ip prio 10 u32 match ip tos
0x10 0xff flowid 1:10
+ tc filter add dev eth0 parent 1:0 protocol ip prio 10 u32 match ip
protocol 1 0xff flowid 1:10
+ tc filter add dev eth0 parent 1: protocol ip prio 10 u32 match ip protocol
6 0xff match u8 0x05 0x0f at 0 match u16 0x0000 0xffc0 at 2 match u8 0x10
0xff at 33 flowid 1:10
+ tc filter add dev eth0 parent 1: protocol ip prio 18 u32 match ip dst
0.0.0.0/0 flowid 1:20
+ tc qdisc add dev eth0 handle ffff: ingress
+ tc filter add dev eth0 parent ffff: protocol ip prio 50 u32 match ip src
0.0.0.0/0 police rate 100kbit burst 10k drop flowid :1


root@Devil:~ # sh -x wshaper.htb status
+ DOWNLINK=100
+ UPLINK=100
+ DEV=eth0
+ NOPRIOHOSTSRC=
+ NOPRIOHOSTDST=
+ NOPRIOPORTSRC=
+ NOPRIOPORTDST=
+ '[' status = status ']'
+ tc -s qdisc ls dev eth0
qdisc htb 1: r2q 10 default 20 direct_packets_stat 0
 Sent 18649 bytes 191 pkts (dropped 0, overlimits 0)
qdisc sfq 10: parent 1:10 limit 128p quantum 1514b perturb 10sec
 Sent 10582 bytes 147 pkts (dropped 0, overlimits 0)
qdisc sfq 20: parent 1:20 limit 128p quantum 1514b perturb 10sec
 Sent 8067 bytes 44 pkts (dropped 0, overlimits 0)
qdisc sfq 30: parent 1:30 limit 128p quantum 1514b perturb 10sec
 Sent 0 bytes 0 pkts (dropped 0, overlimits 0)
qdisc ingress ffff: ----------------
 Sent 0 bytes 0 pkts (dropped 0, overlimits 0)
+ tc -s class ls dev eth0
class htb 1:1 root rate 100000bit ceil 100000bit burst 6Kb cburst 1724b
 Sent 18649 bytes 191 pkts (dropped 0, overlimits 0)
 rate 1320bit 1pps
 lended: 0 borrowed: 0 giants: 0
 tokens: 398459 ctokens: 108855

class htb 1:10 parent 1:1 leaf 10: prio 1 rate 100000bit ceil 100000bit
burst 6Kb cburst 1724b
 Sent 10582 bytes 147 pkts (dropped 0, overlimits 0)
 rate 656bit 1pps
 lended: 147 borrowed: 0 giants: 0
 tokens: 398459 ctokens: 108855

class htb 1:20 parent 1:1 leaf 20: prio 2 rate 90000bit ceil 90000bit burst
6Kb cburst 1711b
 Sent 8067 bytes 44 pkts (dropped 0, overlimits 0)
 rate 712bit
 lended: 44 borrowed: 0 giants: 0
 tokens: 432284 ctokens: 109555

class htb 1:30 parent 1:1 leaf 30: prio 2 rate 80000bit ceil 80000bit burst
6Kb cburst 1699b
 Sent 0 bytes 0 pkts (dropped 0, overlimits 0)
 lended: 0 borrowed: 0 giants: 0
 tokens: 503316 ctokens: 139264

+ exit
root@Devil:~ # sh -x wshaper.htb stop
+ DOWNLINK=100
+ UPLINK=100
+ DEV=eth0
+ NOPRIOHOSTSRC=
+ NOPRIOHOSTDST=
+ NOPRIOPORTSRC=
+ NOPRIOPORTDST=
+ '[' stop = status ']'
+ tc qdisc del dev eth0 root
+ tc qdisc del dev eth0 ingress
+ '[' stop = stop ']'
+ exit

root@Devil:~ #

Don't think we generated enough uplink traffic to exercise the htb qdiscs.

But it doesn't look like the ingress qdisc is working at all.

I'm out of ideas for now.

-- 
Drew Einhorn

Re: [Devil-Linux-discuss] Updating to 1.2.11

[Dick M. <di...@li...>]

Dick Middleton wrote:
> Hello,
> 
>     I've just updated from 1.2.9 to 1.2.11 and have encountered an odd 
> problem. Maybe someone knows the cause:
> 
>   I have a /etc/postfix/local.d to keep my site config files. The mode 
> of the directory is being set to 644 when I reboot even though it is 
> correct when saving config.  Curiously when I change the mode it also 
> changes the mode of the same directory in the postfix jail 

I should clarify - the two are not linked at all - just an observational error.
I'm not too sure what's happening except the mode is not staying how I set it.

Dick

[Devil-Linux-discuss] Updating to 1.2.11

[Dick M. <di...@li...>]

Hello,

	I've just updated from 1.2.9 to 1.2.11 and have encountered an odd problem. 
Maybe someone knows the cause:

   I have a /etc/postfix/local.d to keep my site config files. The mode of the 
directory is being set to 644 when I reboot even though it is correct when 
saving config.  Curiously when I change the mode it also changes the mode of the 
same directory in the postfix jail - as if the two were linked.  I suspect when 
the jail is created and this directory is copied the directory mode is being 
changed.


Nothing to do with this upgrade but shouldn't there be a /var/run/saslauthd 
directory created in the postfix jail?  How do I get it to create this?


Dick

[Devil-Linux-discuss] Bridge with Traffic Shaping

[drew e. <dre...@gm...>]

Just getting started with DL.  (Still waiting for the download to complete
on my pathetic ISDN line.)

Planning on putting a pci 4 port ethernet card in an old pc.

Want to bridge the 4 ports and do traffic shaping.

   port 0: goes an ethernet port on my ISDN modem
   port 1: goes to the WAN port on a Linksys Cable/DSL router.
   port 2: goes to the WAN port on another Linksys Cable/DSL router with a
wireless access point.
   port 3: goes to a hardened DMZ host

Eventually most of the functions of the Linksys boxes, and the DMZ host will
move into the DL box.
But that's more than I want in my first DL project.

I'd appreciate any pointers to get me started in the right direction.

-- 
Drew Einhorn

Re: [Devil-Linux-discuss] raid device scan at boot

[Heiko Z. <he...@zu...>]

On Fri, November 17, 2006 10:19, Bruce Smith wrote:
>>>>> In new version of devil linux there is a raid device (/dev/mdm)
>>>>> scan that burn about 2 minutes at every boot.
>>>>>
>>>>> i've not aver raid device, can i disable it   ?
>>>>
>>>> Create an empty file /etc/mdadm.conf , this will disable the
>>>> automatic search for raid devices.
>>>
>>> Should we add an empty mdadm.conf file in our default etc.tar.bz2?
>>>
>>
>> No, because the auto-detection of raid devices should be the prefered
>> solution. It seems to work fine for the majority of the users.
>>
>
> Wouldn't someone have to create their own mdadm.conf if they wanted
> software raid?
>
> Or, are you saying if the file doesn't exit, it auto-detects?

Yes correct, file doesn't exist means auto-detect.

-- 

Regards
  Heiko Zuerker
  http://www.devil-linux.org

Re: [Devil-Linux-discuss] raid device scan at boot

[Bruce S. <bw...@ar...>]

> >>> In new version of devil linux there is a raid device (/dev/mdm) scan
> >>> that burn about 2 minutes at every boot.
> >>>
> >>> i've not aver raid device, can i disable it   ?
> >>
> >> Create an empty file /etc/mdadm.conf , this will disable the automatic
> >> search for raid devices.
> >
> > Should we add an empty mdadm.conf file in our default etc.tar.bz2?
> 
> No, because the auto-detection of raid devices should be the prefered
> solution.
> It seems to work fine for the majority of the users.

Wouldn't someone have to create their own mdadm.conf if they wanted
software raid?

Or, are you saying if the file doesn't exit, it auto-detects?

 - BS

Re: [Devil-Linux-discuss] raid device scan at boot

[Heiko Z. <he...@zu...>]

On Fri, November 17, 2006 08:25, Bruce Smith wrote:
>>> In new version of devil linux there is a raid device (/dev/mdm) scan
>>> that burn about 2 minutes at every boot.
>>>
>>> i've not aver raid device, can i disable it   ?
>>
>> Create an empty file /etc/mdadm.conf , this will disable the automatic
>> search for raid devices.
>
> Should we add an empty mdadm.conf file in our default etc.tar.bz2?

No, because the auto-detection of raid devices should be the prefered
solution.
It seems to work fine for the majority of the users.

-- 

Regards
  Heiko Zuerker
  http://www.devil-linux.org

Re: [Devil-Linux-discuss] raid device scan at boot

[Bruce S. <bw...@ar...>]

> > In new version of devil linux there is a raid device (/dev/mdm) scan that
> > burn about 2 minutes at every boot.
> >
> > i've not aver raid device, can i disable it   ?
> 
> Create an empty file /etc/mdadm.conf , this will disable the automatic
> search for raid devices.

Should we add an empty mdadm.conf file in our default etc.tar.bz2?

 - BS

Re: [Devil-Linux-discuss] raid device scan at boot

[Heiko Z. <he...@zu...>]

On Tue, November 14, 2006 10:39, LoSpippolo wrote:
>

> In new version of devil linux there is a raid device (/dev/mdm) scan that
> burn about 2 minutes at every boot.
>
> i've not aver raid device, can i disable it   ?

Create an empty file /etc/mdadm.conf , this will disable the automatic
search for raid devices.

-- 

Regards
  Heiko Zuerker
  http://www.devil-linux.org

Re: [Devil-Linux-discuss] Quagga 0.99.5

[Heiko Z. <he...@zu...>]

On Thu, November 16, 2006 08:55, Devil-Linux wrote:
> Hi,
>
>
> Any chans of updating to Quagga 0.99
>
>
> I see that the md5 patch is not updated, I do not know if this have been
> included I dont use MD5 myself.
>

Any complains about updating this and getting rid of the not maintained
md5 patch?


-- 

Regards
  Heiko Zuerker
  http://www.devil-linux.org

[Devil-Linux-discuss] Quagga 0.99.5

[Devil-Linux <dev...@js...>]

Hi,

Any chans of updating to Quagga 0.99

I see that the md5 patch is not updated, I do not know if this have been =
included I dont use MD5 myself.


Kind Regards
/Jacob=20

[Devil-Linux-discuss] raid device scan at boot

[LoSpippolo <los...@gm...>]

In new version of devil linux there is a raid device (/dev/mdm) scan that burn about 2 minutes at every boot.

i've not aver raid device, can i disable it   ?

best regards

-- 
LoSpippolo <los...@gm...>

Re: [Devil-Linux-discuss] Link monitoring / CACTI

[James H. <ha...@wa...>]

Cacti, is a PHP front end to RRDTOOL.  It requires a web server and PHP to =
function correctly.  I don't think you really want to put that much =
overhead on a DL firewall.
=20
Personally I use DL because there are so little processes running.
=20
If you were going to monitor, I would think you would want a separate =
machine running Cacti ( http://cacti.net/ ), JFFNMS ( http://www.jffnms.org=
/ ), Nagios  ( http://nagios.org/ )or some other data collection software.
=20
If you have a extra machine lying around you might want to try this, even =
though it's a dead project.
http://sentinix.tigerteam.se/=20
=20
It's called Sentinix and has Cacti, Nagios, and some other useful =
utilities built into the distribution.  I have one of these boxes running =
and it monitors just fine.  Might give you a idea of what you like, then =
you could build your own system on a more recent distribution like SuSE, =
or Slack.

>>> Kari Mattsson <kar...@tr...> 11/13/2006 10:16 AM >>>
Matthew Hattersley wrote:
> Snmp monitoring could be the easiest. We also put bin versions of bwm
> and iperf on our DL boxes.
>=20
> Iperf, to generate ip traffic, bwm to watch interfaces in realtime.
>=20
> In order to graph the interfaces cacti is probably the easiest software
> to setup rather than writing your own RRD or MRTG scripts.

I have heard many really good news about Cacti.
Would it be an easy/good addition to DL?

> Cheers
>=20
> Mat
>=20

> Hi,
>=20
> I have a devil linux box either side of a wireless link which is used to
> connect 2 offices. Can anyone tell me if there is a simple way to
> monitor the speed of the link between the 2 routers?
>=20
> Am a bit of a newbie so the easiest solution wins!
>=20
> Thanks
>=20
> Ross

Re: [Devil-Linux-discuss] Link monitoring / CACTI

[Matthew H. <mat...@va...>]

It really is a nice piece of software, however it may be a little
intensive for the majority of peoples tastes. We currently have around
50 DL boxes out in the wild, but we choose to monitor them from one
central location running cacti, which proves much more effective.=20

As regards being a good additional to a box acting as firewall/router
and monitoring station, I would say yes.

It all depends on whether you would like your firewall monitoring your
snmp based devices or not. For us, this would be no, as the statistics
would have to be held on the flash card or disk on module, neither of
which seems like a good idea. Those deploying on a HDD may find this
system much more effective.

Cheers

Mat

-----Original Message-----
From: dev...@li...
[mailto:dev...@li...] On Behalf Of
Kari Mattsson
Sent: 13 November 2006 15:16
To: dev...@li...
Subject: Re: [Devil-Linux-discuss] Link monitoring / CACTI

Matthew Hattersley wrote:
> Snmp monitoring could be the easiest. We also put bin versions of bwm
> and iperf on our DL boxes.
>=20
> Iperf, to generate ip traffic, bwm to watch interfaces in realtime.
>=20
> In order to graph the interfaces cacti is probably the easiest
software
> to setup rather than writing your own RRD or MRTG scripts.

I have heard many really good news about Cacti.
Would it be an easy/good addition to DL?

> Cheers
>=20
> Mat
>=20

> Hi,
>=20
> I have a devil linux box either side of a wireless link which is used
to
> connect 2 offices. Can anyone tell me if there is a simple way to
> monitor the speed of the link between the 2 routers?
>=20
> Am a bit of a newbie so the easiest solution wins!
>=20
> Thanks
>=20
> Ross

Re: [Devil-Linux-discuss] Link monitoring / CACTI

[Kari M. <kar...@tr...>]

Matthew Hattersley wrote:
> Snmp monitoring could be the easiest. We also put bin versions of bwm
> and iperf on our DL boxes.
> 
> Iperf, to generate ip traffic, bwm to watch interfaces in realtime.
> 
> In order to graph the interfaces cacti is probably the easiest software
> to setup rather than writing your own RRD or MRTG scripts.

I have heard many really good news about Cacti.
Would it be an easy/good addition to DL?

> Cheers
> 
> Mat
> 

> Hi,
> 
> I have a devil linux box either side of a wireless link which is used to
> connect 2 offices. Can anyone tell me if there is a simple way to
> monitor the speed of the link between the 2 routers?
> 
> Am a bit of a newbie so the easiest solution wins!
> 
> Thanks
> 
> Ross

Re: [Devil-Linux-discuss] Link monitoring

[Matthew H. <mat...@va...>]

Snmp monitoring could be the easiest. We also put bin versions of bwm
and iperf on our DL boxes.

Iperf, to generate ip traffic, bwm to watch interfaces in realtime.

In order to graph the interfaces cacti is probably the easiest software
to setup rather than writing your own RRD or MRTG scripts.

Cheers

Mat

-----Original Message-----
From: dev...@li...
[mailto:dev...@li...] On Behalf Of
Ross Petrie
Sent: 13 November 2006 11:22
To: dev...@li...
Subject: [Devil-Linux-discuss] Link monitoring

Hi,

I have a devil linux box either side of a wireless link which is used to
connect 2 offices. Can anyone tell me if there is a simple way to
monitor the speed of the link between the 2 routers?

Am a bit of a newbie so the easiest solution wins!

Thanks

Ross

________________________________________________________________________
IMPORTANT - our "canoffshore.ltd.uk" address is scheduled for
cancellation.  Address books should be changed to use our "cangroup.net"
address.  Thank you for your cooperation.

This transmission contains information which may be confidential and
that may also be privileged.  It is intended for the named addressee
only.  Unless you are the named addressee, or authorised to receive it
on behalf of the addressee, you may not copy or use it, or disclose it
to anyone else.  If you have received this transmission in error please
contact the sender.  Thank you for your cooperation.

This email has been scanned for all viruses by the MessageLabs SkyScan
service.  CAN also uses the MessageLabs spam filtering service.  This
should not affect routine messages but in rare cases a bona-fide message
could be blocked.  Please contact CAN if you experience any
difficulties.
________________________________________________________________________

[Devil-Linux-discuss] Link monitoring

[Ross P. <ros...@ca...>]

Hi,

I have a devil linux box either side of a wireless link which is used to
connect 2 offices. Can anyone tell me if there is a simple way to
monitor the speed of the link between the 2 routers?

Am a bit of a newbie so the easiest solution wins!

Thanks

Ross

________________________________________________________________________
IMPORTANT – our “canoffshore.ltd.uk” address is scheduled for cancellation.  Address books should be changed to use our “cangroup.net” address.  Thank you for your cooperation.

This transmission contains information which may be confidential and that may also be privileged.  It is intended for the named addressee only.  Unless you are the named addressee, or authorised to receive it on behalf of the addressee, you may not copy or use it, or disclose it to anyone else.  If you have received this transmission in error please contact the sender.  Thank you for your cooperation.

This email has been scanned for all viruses by the MessageLabs SkyScan service.  CAN also uses the MessageLabs spam filtering service.  This should not affect routine messages but in rare cases a bona-fide message could be blocked.  Please contact CAN if you experience any difficulties.
________________________________________________________________________

Re: [Devil-Linux-discuss] Building Devil-Linux from the sources

[Patrick S. <pat...@we...>]

Hello,

Heiko Zuerker schrieb:
> You checked out the 1.3 sources.
> Add a
> -p rel-1-2-patches
> to the cvs co command.

Thanks for the fast reply. I cleaned the chroot environment and untared 
it again. I guess you meant "-r rel-1-2-patches" ? -p just fetched it to 
STDOUT ;)


> Of course you now have to wipe out the lfssystem and download the sources
> again.
> If your connection is not the fastest, copy the src directory over, it
> will only download what's missing and delete what's to much.
> 
Okay, I did that to save some bandwidth on the servers.
The build is running fine now.

Thanks again!

Regards,
Patrick
-- 
patrick schneider
pat...@we...
www.patrickschneider.info

Re: [Devil-Linux-discuss] Building Devil-Linux from the sources

[Heiko Z. <he...@zu...>]

On Thu, November 9, 2006 09:05, Patrick Schneider wrote:
> Hello,
>
>
> I'm new to Devil-Linux and I wanted to create a stripped down Distro to
> fit on my 128MB CompactFlash Drive. Unfortunately I'm stuck: Here are the
> steps I've taken so far(I tried to follow the instructions at
> http://www.devil-linux.org/documentation/1.2.x/ch03.html ):
> * Installed lftp ( lftp --version
> LFTP | Version 3.5.0 | Copyright (c) 1996-2006 Alexander V. Lukyanov )
>
>
> * Downloaded
> ftp://ftp.devil-linux.org/pub/devel/sources/lfssystem-for-DL-1.0_and_up/lf
> ssystem-cvs-20030127-i486-stripped.tar.bz2 (I want to build a version
> 1.2.x Distro)
> * untared it to /usr/src ,
> sudo tar xvjf lfssystem-cvs-20030127-i486-stripped.tar.bz2 -C /usr/src *
> fetched the "build" directory from cvs (using the new SF CVS-server
> address) cd /usr/src/lfssystem/data sudo  cvs -z3
> -d:pserver:ano...@de...:/cvsroot/devil-linux
>  co -P build
>

You checked out the 1.3 sources.
Add a
-p rel-1-2-patches
to the cvs co command.
Of course you now have to wipe out the lfssystem and download the sources
again.
If your connection is not the fastest, copy the src directory over, it
will only download what's missing and delete what's to much.

-- 

Regards
  Heiko Zuerker
  http://www.devil-linux.org

[Devil-Linux-discuss] Building Devil-Linux from the sources

[Patrick S. <pat...@we...>]

Hello,

I'm new to Devil-Linux and I wanted to create a stripped down Distro to
fit on my 128MB CompactFlash Drive. Unfortunately I'm stuck:
Here are the steps I've taken so far(I tried to follow the instructions 
at http://www.devil-linux.org/documentation/1.2.x/ch03.html ):
* Installed lftp ( lftp --version
LFTP | Version 3.5.0 | Copyright (c) 1996-2006 Alexander V. Lukyanov )

* Downloaded
ftp://ftp.devil-linux.org/pub/devel/sources/lfssystem-for-DL-1.0_and_up/lfssystem-cvs-20030127-i486-stripped.tar.bz2
(I want to build a version 1.2.x Distro)
* untared it to /usr/src ,
sudo tar xvjf lfssystem-cvs-20030127-i486-stripped.tar.bz2 -C /usr/src
* fetched the "build" directory from cvs (using the new SF CVS-server 
address)
cd /usr/src/lfssystem/data
sudo  cvs -z3
-d:pserver:ano...@de...:/cvsroot/devil-linux
co -P build

* fetched the source files from server #3
cd build
sudo ./update_src


* added alias cr='sudo chroot /usr/src/lfssystem /usr/bin/env -i 
HOME=/root TERM=$TERM /bin/bash -login' to my ~/.bashrc

* ran cr
make unpack
make menuconfig (didn't change the default settings)
make prepare build install iso dist

And this is where I'm stuck:
It complains about a missing linux/limits.h:

root:/data/build# make prepare build install iso dist
mount: proc already mounted
mount: mount point /sys does not exist
running prepare
make[1]: Entering directory `/data/build/tmp/linux-2.6.14.2'
Makefile:484: .config: No such file or directory
   CHK     include/linux/version.h
   UPD     include/linux/version.h
make[1]: Leaving directory `/data/build/tmp/linux-2.6.14.2'
insserv not found
  (in /data/build/tmp/insserv-1.00.2)
patching file insserv.c
patching file insserv.c
patching file insserv.c
make[1]: Entering directory `/data/build/tmp/insserv-1.00.2'
rm -f *.o *~ insserv
make[1]: Leaving directory `/data/build/tmp/insserv-1.00.2'
make[1]: Entering directory `/data/build/tmp/insserv-1.00.2'
gcc -Wall -O2 -mcpu=i486 -fomit-frame-pointer -fschedule-insns2 
-D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -DSUSE -DINITDIR=\"/etc/init.d\" 
-DINSCONF=\"/etc/insserv.conf\" -pipe -funroll-loops -c listing.c
In file included from /usr/include/errno.h:36,
                  from listing.c:17:
/usr/include/bits/errno.h:25:26: linux/errno.h: No such file or directory
In file included from /usr/include/bits/posix1_lim.h:126,
                  from /usr/include/limits.h:144,
                  from 
/usr/lib/gcc-lib/i486-pc-linux-gnu/3.2.1/include/limits.h:132,
                  from 
/usr/lib/gcc-lib/i486-pc-linux-gnu/3.2.1/include/syslimits.h:7,
                  from 
/usr/lib/gcc-lib/i486-pc-linux-gnu/3.2.1/include/limits.h:11,
                  from listing.c:18:
/usr/include/bits/local_lim.h:36:26: linux/limits.h: No such file or 
directory
make[1]: *** [listing.o] Error 1
make[1]: Leaving directory `/data/build/tmp/insserv-1.00.2'
ERROR
/data/build/scripts/insserv build failed
make: *** [prepare] Error 1


Can someony give me an advice or point me to some documentation I should 
read?

Thanks in advance,

Regards,
Patrick
-- 
patrick schneider
pat...@we...
www.patrickschneider.info

Re: [Devil-Linux-discuss] PHREL?

[Kari M. <kar...@tr...>]

Bruce Smith wrote:
> I read this article today and thought the 'PHREL' package might be a
> good addition to DL.  Does anyone have any experience with PHREL?
> 
> http://www.linux.com/article.pl?sid=06/11/02/1434241

Sorry, no experience, but this looks very good.  Especially the part of 
protecting sshd from Bruce (sp:-) force logins should interest almost 
everybody.

I know there have been discussion on this list earlier on how to do this 
protection with some Perl, or something.  This would be a C solution. 
The more generic nature of this special purpose traffic shaper appeals 
to me.

>  - BS

//KM

[Devil-Linux-discuss] PHREL?

[Bruce S. <br...@ar...>]

I read this article today and thought the 'PHREL' package might be a
good addition to DL.  Does anyone have any experience with PHREL?

http://www.linux.com/article.pl?sid=06/11/02/1434241

 - BS