-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

[stano] wrote:
> http://qa.mandrakesoft.com/show_bug.cgi?id=5244
>

> ------- Additional Comments From [EMAIL PROTECTED]  2003-10-09 21:07
- -------
> Sorry, I have other things to do now, so don't expect further testing
from me
> until weekend. I investigated a bit and my GPRS provider indeed uses
10.0.0.0/8
> too :-(

IMHO, this (class A network for no specific reason) is bad practise ...

>
> Anyway, the problem has nothing to do with ppp. It can be eth where it
hurts
> (e.g. non-flatrate ADSL), it can be wlan, whatever. To try to guess
thing based
> on the interface name is also not a good idea.

Well, the question is whether ppp interfaces would benefit from lisa or
not. If there are no circumstances where a default config would want
lisa browsing over ppp, then we can prevent some problems more easily.

BTW, what interface name is your GPRS?

>
> Lisa seems to flood the whole network, regardless of what the network is.

I wouldn't say flood, but it does ping the network ... but on a /24
subnet, the traffic is negligible, in normal operation, one ping will be
sent to a host probably somewhere between once every 5 minutes and once
every 80 minutes (probably about 2 to 8 ping's per minute on the whole
network at most).

> If the
> netmask is 255.0.0.0, it will probably send at least 16 millions of
packets. I
> don't know what the lisa exactly does, I never used it and it was never
> installed and activated by default on other distros (I am trying
Mandrake for
> the second time, but am a long time Linux user).

AFAIK, it is installed and activated by default on SuSE at least. All
other distros (except for Xandros who uses their own proprietary stuff)
have a deficient out-the-box experience ...

However, lisa's operation without pinging seems to have improved
recently, so maybe pinging isn't necessary any more.

> I just don't think this is a
> sane behaviour and should IMHO not be present out of the box, if at
all. Imagine
> a large network where every machine does the same.

Lisa takes advantage of other lisa's running on the network to reduce
traffic, but I haven't experimented with >4 lisa's on a network ...

> Imagine that they are on a
> slower connection (wlan) and they all start at the similar time
(people booting
> the machines in the morning).
>

WLAN isn't substantially slower in this regard. Nothing else (ie WAN)
would be affected, since that crosses the subnet boundary (we have a 64k
WAN line, no lisa traffic goes over it).

> I agree that this is probably a problem with lisa itself and not
specifically
> with Mandrake. I will most probably file an upstream bugreport on the
weekend.

Well, lisa is deficient, but the configuration caused the behaviour. I
will have a new initscript for you before the weekend, I would like you
to test it (and if you have a LAN at home, see what the advantages are).

I will do some more testing (again ...).

[BTW, lisa isn't my responsibility, but I provided the init script, and
added the automatic configuration, otherwise it is way too difficult for
a newbie to get this working ... I actually maintain the samba packages ...]

Regards,
Buchan

- --
|--------------Another happy Mandrake Club member--------------|
Buchan Milne                Mechanical Engineer, Network Manager
Cellphone * Work            +27 82 472 2231 * +27 21 8828820x202
Stellenbosch Automotive Engineering         http://www.cae.co.za
GPG Key                   http://ranger.dnsalias.com/bgmilne.asc
1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE/X3sTrJK6UGDSBKcRAmqrAKCmek7E22Poctv2sjEQIxwGYs/pMQCgpsVM
Sd2UOPGXramNJ9ZpTSUIXjA=
=Dw39
-----END PGP SIGNATURE-----

*****************************************************************
Please click on http://www.cae.co.za/disclaimer.htm to read our
e-mail disclaimer or send an e-mail to [EMAIL PROTECTED] for a copy.
*****************************************************************

Reply via email to