Re: why to reinvent the glue? [Re: Starting isp and going to use Debian]

2004-02-26 Thread IOhannes m zmoelnig
Emmanuel Halbwachs wrote:
Adam ENDRODI a écrit :

-apache


What information could Apache read from LDAP?


Authentication ?

exactly, that is why i am using mod_ldap
(libapache-mod-ldap).
so ldap-support is kind of built-in.

mfg.a.fr
IOhannes
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]


Re: squid-wccp-kernel-2.6

2004-02-26 Thread Konstantin Kostadinov
http://ftp.yars.free.net/pub/software/unix/platforms/linux/kernel/drivers/ip_wccp-for2.6.0.c
> 
> echo 'obj-m := ip_wccp-for2.6.0.o' > Makefile
> make -C /usr/src/linux SUBDIRS=$PWD O=$PWD V=1 modules
> 
> Arkadiusz Mi¶kiewicz CS at FoE, Wroclaw University of Technology
> arekm.pld-linux.org, 1024/3DB19BBD, JID: arekm.jabber.org, PLD/Linux

that's it. 
if fire-up module compile after kernel build like that:

- this is modules section in /usr/src/linux-2.6.3/.config

# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
# CONFIG_MODULE_FORCE_UNLOAD is not set
CONFIG_OBSOLETE_MODPARM=y
# CONFIG_MODVERSIONS is not set
CONFIG_KMOD=y

- this is Arkadiusz's hint fo makefile compose:

cd dir-with-ip-wccp-for2.60.o ; echo 'obj-m := ip_wccp-for2.6.0.o' > Makefile 

make -C /usr/src/linux-2.6.3 SUBDIRS=$PWD modules  -- V=1 in Arkadiusz's hint is for 
verbose output.

note: module must be compiled with kernel that we want to use with. e.g 2.6.x

tanx a lot to everybody. 
oo and read in /usr/src/linux-2.6.x/Documentation/kbuild before google searches ;-) it 
helps very very ;)).

-- 

Konstantin Kostadinov

Public PGP : http://www.fadata.bg/pgp/konstantinpgp.asc
---

The lunatic, the lover, and the poet,
Are of imagination all compact...
-- Wm. Shakespeare, "A Midsummer Night's Dream"


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Not detecting Ethernet

2004-02-26 Thread Prashanth Venkatesh
Hi,
 
I installed debian woody on the server. On booting only one ethernet is active. The second one is not being detected. Both ethernets are onboard. eepro100 is the driver used. Following shows the details:
 
Detected:
--
02:08.0 Ethernet controller: Intel Corp. 82557 [Ethernet Pro 100] (rev 10)    Subsystem: Intel Corp.: Unknown device 1040    Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B-    Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR-     Latency: 66 (2000ns min, 14000ns max), cache line size 10    Interrupt: pin A routed to IRQ 18    Region 0: Memory at f4122000 (32-bit, non-prefetchable) [size=4K]    Region 1: I/O ports at 2400 [size=64]    Region 2: Memory at f410 (32-bit, non-prefetchable)
 [size=128K]    Capabilities: [dc] Power Management version 2    Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+)    Status: D0 PME-Enable- DSel=0 DScale=2 PME-
 
Not Detected:
---
 
00:0b.0 Ethernet controller: Intel Corp.: Unknown device 100f (rev 01)    Subsystem: Intel Corp.: Unknown device 1001    Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B-    Status: Cap+ 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR-     Latency: 64 (63750ns min), cache line size 10    Interrupt: pin A routed to IRQ 19    Region 0: Memory at f400 (32-bit, non-prefetchable) [size=128K]    Region 2: I/O ports at 1000 [size=64]    Capabilities: [dc] Power Management version
 2    Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold-)    Status: D0 PME-Enable- DSel=0 DScale=1 PME-    Capabilities: [e4] #07 [0002]    Capabilities: [f0] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable-    Address:   Data: 
Can anyone please provide me some hints on making the second ethernet active.
 
 
Regards,
Prashanth
Do you Yahoo!?
Get better spam protection with Yahoo! Mail

Re: Not detecting Ethernet

2004-02-26 Thread Nicolas Rueff
Ainsi parla Prashanth Venkatesh le 057ème jour de l'an 2004:

> Hi,
>  
> I installed debian woody on the server. On booting only one ethernet
> is active. The second one is not being detected. Both ethernets are
> onboard. eepro100 is the driver used. Following shows the details:
>  
> Detected:
> --
> 02:08.0 Ethernet controller: Intel Corp. 82557 [Ethernet Pro 100] (rev
> 10)
> Subsystem: Intel Corp.: Unknown device 1040
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop-
> ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF-
> FastB2B+ ParErr- DEVSEL=medium >TAbort-  >SERR-  Latency: 66 (2000ns min, 14000ns max), cache line size 10
> Interrupt: pin A routed to IRQ 18
> Region 0: Memory at f4122000 (32-bit, non-prefetchable)
> [size=4K] Region 1: I/O ports at 2400 [size=64]
> Region 2: Memory at f410 (32-bit, non-prefetchable)
> [size=128K] Capabilities: [dc] Power Management version 2
> Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA
> PME(D0+,D1+,D2+,D3hot+,D3cold+) Status: D0 PME-Enable-
> DSel=0 DScale=2 PME-
>  
> Not Detected:
> ---
>  
> 00:0b.0 Ethernet controller: Intel Corp.: Unknown device 100f (rev 01)
> Subsystem: Intel Corp.: Unknown device 1001
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop-
> ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz+ UDF-
> FastB2B- ParErr- DEVSEL=medium >TAbort-  >SERR-  Latency: 64 (63750ns min), cache line size 10
> Interrupt: pin A routed to IRQ 19
> Region 0: Memory at f400 (32-bit, non-prefetchable)
> [size=128K] Region 2: I/O ports at 1000 [size=64]
> Capabilities: [dc] Power Management version 2
> Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA
> PME(D0+,D1-,D2-,D3hot+,D3cold-) Status: D0 PME-Enable-
> DSel=0 DScale=1 PME-
> Capabilities: [e4] #07 [0002]
> Capabilities: [f0] Message Signalled Interrupts: 64bit+
> Queue=0/0 Enable-
> Address:   Data: 
> 
> Can anyone please provide me some hints on making the second ethernet
> active.

Any clue about the brand of the second card ? If not, please provide the
output of the following command:

 cut here 
lspci -n | grep "Class 0200"
 cut here 


-- 
  Nicolas Rueff · Montbéliard · France · http://rueff.homelinux.org
 (^>[EMAIL PROTECTED] · GPG 0xDD44DAB4
 /v\   Jabber [EMAIL PROTECTED] · ICQ 97700474
<__/  « We are Penguin. Resistance is futile. You will be assimilated. »
 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: Not detecting Ethernet

2004-02-26 Thread Nicolas Rueff
Ainsi parla Prashanth Venkatesh le 057ème jour de l'an 2004:

> Hi,
>  
> Only thing I know is that, its Intel Based.
>  
> The output :
>  
> ##
> # lspci -n | grep "Class 0200"
> 00:0b.0 Class 0200: 8086:100f (rev 01)
> 02:08.0 Class 0200: 8086:1229 (rev 10)
> 

according to http://pciids.sourceforge.net/iii/?i=8086100f, your network
controller seems to be an « 82545EM Gigabit Ethernet Controller ».

Then my friend google send me there: 

http://downloadfinder.intel.com/scripts-df/Detail_Desc.asp?strState=LIVE&ProductID=983&DwnldID=2897

where it is said that:

« Base driver (5.2.30.1) for the Intel® PRO/1000 family of Desktop
and Server Adapters [are] known to build properly on Linux* kernels
on 2.4.x kernels through 2.4.20. »

So if you are using a 2.4.x kernel, you have to load « e1000.o » . If
you are using a 2.2.x, you can download the driver from the url above.
Don't know for 2.6.x.


-- 
  Nicolas Rueff · Montbéliard · France · http://rueff.homelinux.org
 (^>[EMAIL PROTECTED] · GPG 0xDD44DAB4
 /v\   Jabber [EMAIL PROTECTED] · ICQ 97700474
<__/  « We are Penguin. Resistance is futile. You will be assimilated. »
 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: off subject - ip & bandwidth management

2004-02-26 Thread Arnt Karlsen
On Wed, 25 Feb 2004 17:39:00 -0600, 
Rich Puhek <[EMAIL PROTECTED]> wrote in message 
<[EMAIL PROTECTED]>:

> Gregory Wood wrote:
> 
> > Problem 1: I have a couple of sites, one with 30 users, another with
> > 500 users. The switches are unmanaged. Occasionally, someone won't
> > be able to log in or they will loose a network printer. I suspect
> > one or more PCs are soaking up the bandwidth.

..for bandwidth throttling, I (and my isp alias business client) use my 
http://fmb.no/ipcop/setup-cbq-0.0.5.tar.bz2 on an ip-less bridge.
I guess it could use a web interface or a webmin module, if you don't
like to edit text files.  My isp has about 200 clients now, some of them
businesses, there is ip room for another 600, and AFAICT, any recent 
box can handle it, we use a Duron 1.2G with 128 MB ram.

..it and the gateway box is going to be replaced with one throttling
gateway, same hardware, it rarely sees any load at all, I've even
compiled kernels on the bridge while in throttle service.  ;-)

> > Problem 2: I work with a local ISP. He has his system subnetted BUT
> > there are still folks who find a 'free' IP and use it. When the
> > owner of the IP fires up his system, he can't connect. Also, as
> > above, he has seen the'steady state' bandwidth increase but can't
> > identify the users. He has CISCO switches and I would have though
> > they would have the tools to identify the user consumption.
> > Apparently not.
> > 
> > Is there a tool for monitoring who is using the bandwidth and with
> > what MAC? I've used Ethereal but it generates way too much detail. I
> > would like to load up a notebook and a hub and stick it between the
> > server and the rest of the network or between the Internet firewall
> > and the network.
> > 
> > Ideas? Thoughts?

..ntop, www.ntop.org.  Very nice web interface for lookup's, used to be
a resource hog, but I had it running for months on the bridge, and could
not get it to run for much more than 5 minutes on my own 3 box lan 2
years back. 
Same HW and SW, so we figured it just needed traffic to survive.  ;-) 

> If the Ciscos are managed switches, try using MRTG to graph port
> usage. You should also be able to log on and show port info, check the
> docs for the switches CLI. Haven't used Cisco switches here, but
> something along the lines of "show int" should get what you need.
> 
> For individual bandwidth usage on a local subnet, iptraf provides a
> neat glance at "real-time" usage. If you're on a switched network,
> you'll need some way to see all the traffic on the network. For 3com
> switches, it's called something like the "roving analysis port"
> (better than using a hub near the firewall, just analyze the
> firewall's port). Iptraf will give a nice display of traffic in and
> traffic out, listed by MAC. Then it's just a matter of tracing down
> the MAC's location, and going to said location with a big stick in
> hand :-)
>  
> You might also want to nmap your network periodically. Look for 
> surprising IP addresses.
> 
> You'll probably find misbehaving KaZaa servers to blame. They're very 
> bad about playing well on a network, and will happily saturate your 
> bandwidth.

...and set a policy first, then police it.  ;-)

-- 
..med vennlig hilsen = with Kind Regards from Arnt... ;-)
...with a number of polar bear hunters in his ancestry...
  Scenarios always come in sets of three: 
  best case, worst case, and just in case.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



unsubscribe

2004-02-26 Thread cjrsneo
 

_
Voce quer um iGMail protegido contra vírus e spams? 
Clique aqui: http://www.igmailseguro.ig.com.br



Re: Not detecting Ethernet

2004-02-26 Thread Prashanth Venkatesh
Hi,
 
Only thing I know is that, its Intel Based.
 
The output :
 
##
# lspci -n | grep "Class 0200"00:0b.0 Class 0200: 8086:100f (rev 01)02:08.0 Class 0200: 8086:1229 (rev 10)
 
Thanks,
Prashanth
Nicolas Rueff <[EMAIL PROTECTED]> wrote:
Ainsi parla Prashanth Venkatesh le 057ème jour de l'an 2004:> Hi,> > I installed debian woody on the server. On booting only one ethernet> is active. The second one is not being detected. Both ethernets are> onboard. eepro100 is the driver used. Following shows the details:> > Detected:> --> 02:08.0 Ethernet controller: Intel Corp. 82557 [Ethernet Pro 100] (rev> 10)> Subsystem: Intel Corp.: Unknown device 1040> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop-> ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF-> FastB2B+ ParErr- DEVSEL=medium >TAbort- > >SERR- > Latency: 66 (2000ns min, 14000ns max), cache line size 10> Interrupt: pin A routed to IRQ 18> Region 0: Memory at f4122000 (32-bit,
 non-prefetchable)> [size=4K] Region 1: I/O ports at 2400 [size=64]> Region 2: Memory at f410 (32-bit, non-prefetchable)> [size=128K] Capabilities: [dc] Power Management version 2> Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA> PME(D0+,D1+,D2+,D3hot+,D3cold+) Status: D0 PME-Enable-> DSel=0 DScale=2 PME-> > Not Detected:> ---> > 00:0b.0 Ethernet controller: Intel Corp.: Unknown device 100f (rev 01)> Subsystem: Intel Corp.: Unknown device 1001> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop-> ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz+ UDF-> FastB2B- ParErr- DEVSEL=medium >TAbort- > >SERR- > Latency: 64 (63750ns min), cache line size 10> Interrupt: pin A routed to IRQ 19> Region 0: Memory at f400 (32-bit, non-prefetchable)> [size=128K] Region 2: I/O ports at 1000
 [size=64]> Capabilities: [dc] Power Management version 2> Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA> PME(D0+,D1-,D2-,D3hot+,D3cold-) Status: D0 PME-Enable-> DSel=0 DScale=1 PME-> Capabilities: [e4] #07 [0002]> Capabilities: [f0] Message Signalled Interrupts: 64bit+> Queue=0/0 Enable-> Address:  Data: > > Can anyone please provide me some hints on making the second ethernet> active.Any clue about the brand of the second card ? If not, please provide theoutput of the following command: cut here lspci -n | grep "Class 0200" cut here -- Nicolas Rueff · Montbéliard · France · http://rueff.homelinux.org(^> [EMAIL PROTECTED] · GPG 0xDD44DAB4/v\ Jabber [EMAIL PROTECTED] · ICQ 97700474<__/ « We are Penguin. Resistance is futile. You will be assimilated. »-- To UNSUBSCRIBE, email to
 [EMAIL PROTECTED]with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Do you Yahoo!?
Get better spam protection with Yahoo! Mail