http://qa.mandrakesoft.com/show_bug.cgi?id=5244
------- Additional Comments From [EMAIL PROTECTED] 2003-10-09 20:31 ------- Allright, it is related with subnet mask indeed. I found something interesting : I tried to use static address instead of DHCP server. If I use a 192.168.0.1 with a mask 255.255.255.0, lisa can be started and works nicely. If I use a 192.168.0.1 with a mask 255.255.0.0, lisa becomes crazy. But I made a mistake : there are two lisa services that are started ! and maybe it is why it becomes crazy... $ps -A 3395 ? 00:00:00 lisa 3397 ? 00:00:00 lisa top gives the 3397 pid lisa 99% CPU !! 3395 root 9 0 1064 1060 1004 S 0.0 0.2 0:00.00 lisa 3397 root 20 0 1104 1104 1032 R 99.3 0.2 0:57.25 lisa After "service lisa stop" $ ps -A|grep lisa 3395 ? 00:00:00 lisa and top gives 3395 root 9 0 1064 1060 1004 S 0.0 0.2 0:00.00 lisa Can you reproduce it ? I am sure this is a bug with the starting of this service when not using a class C mask and can be easily corrected. -- Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. ------- Reminder: ------- assigned_to: [EMAIL PROTECTED] status: NEW creation_date: description: I have the LAN at 10.0.0.0/8. tcpdump shows that the lisa tries to do an ARP request for probably all addresses in the network and literally bombards the net with packets. I don't know what this might cause on a large network. To add to this it continues these probes even after the LAN interface goes down. This can also result in a costly problem. The following happened to me: - I configured my notebook for GPRS over bluetooth - I removed the LAN card from my notebook so it does not interfere with the experiments - I brought a PPP connection up - The defaultroute was set to ppp0 - The lisa continued to send packets - They all travelled to the phone, generating paid traffic :-( The distribution is Mandrake 9.2 Beta 2 Proposed resolution: don't enable the server by default and document this problem somewhere
