ADSL connection (wifi) breaks down over and over again

Discussion in 'LnS English Forum' started by Edwin024, Sep 24, 2005.

Thread Status:
Not open for further replies.
  1. Edwin024

    Edwin024 Registered Member

    Joined:
    Nov 14, 2004
    Posts:
    1,000
    Whenever I install any version of LnS my ADSL connection (wifi) breaks down over and over again. Pitty.
     
  2. Frederic

    Frederic LnS Developer

    Joined:
    Jan 9, 2003
    Posts:
    4,354
    Location:
    France
  3. Edwin024

    Edwin024 Registered Member

    Joined:
    Nov 14, 2004
    Posts:
    1,000
    Can't this become a normal import able rule? This is way over my head... And after installing LnS AGAIN, the wifi connection breaks AGAIN too...
     
  4. JF

    JF LnS Support

    Joined:
    Jan 12, 2003
    Posts:
    294
    Hi,

    You can import this rule :

    http://www.looknstop.com/En/rules/other_eth_protocols.rie

    which authorizes non IP and non ARP ethernet types, and so 0x888E ethernet types used by WPA protocol of WiFi encryption.

    In a next release, the 0x888E ethernet type may appear directly in the Ethernet type drop box to open less eth types. To do this now, raw rules (see plugin section) are needed which is a little more complex to setup.

    Regards,
    JF
     
  5. Edwin024

    Edwin024 Registered Member

    Joined:
    Nov 14, 2004
    Posts:
    1,000
    Thanks alot! I will immediately try this one! Hopefullky the crashes of the ADSL line are over then :)
     
  6. Raccoon

    Raccoon Guest

    Iv been using LnS with my dial up till now. Just got ADSL (not wi fi) and its almost completely throttling the data transfer! ADSL connection works fine if I unload LnS.

    Will this rule set help my case? Any other solution?
     
  7. Frederic

    Frederic LnS Developer

    Joined:
    Jan 9, 2003
    Posts:
    4,354
    Location:
    France
    No, this rule doesn't correspond to your case. This rule is to solve WiFi authentification only.
    Not sure if by "unload" you meant uninstall. If you absolutely need to uninstall Look 'n' Stop, then there could be a driver conflict. If just exiting from Look 'n' Stop is sufficient, then probably it is only a configuration issue (either the network adapter or some rules need to be added/refined).

    Regards,

    Frederic
     
  8. Raccoon

    Raccoon Guest

    No, just EXITING from LnS solves the problem! Else I would have used the word "uninstall"! But I'v been forced to uninstall only because I have to install another firewall ...can't stay online without one!

    I like LnS mainly because of its easy on resources ...tho it lacks features ...the new one I'v installed isn't so good in that respect.

    Is there something I can do?
     
  9. Edwin024

    Edwin024 Registered Member

    Joined:
    Nov 14, 2004
    Posts:
    1,000
    Frederic: thanks for the rule, so far so good on my wifi system :)

    Raccoon: I'm very glad that LnS lacks features, as you call it. I don't need the firewall to do ad blocking, doc blocking, anti spyware and such. There are better programs for that.
     
  10. Raccoon

    Raccoon Guest

    Edwin, I definitely agree on that! But those were not the features I had in mind! Im was refering to firewall specific features...
    Just for eg. - the ZA I had used on my old comp used to have an option to totally debar data transfer, etc. Not so in LnS...

    Any solution to my problem, pleaseo_O :-(
     
  11. Edwin024

    Edwin024 Registered Member

    Joined:
    Nov 14, 2004
    Posts:
    1,000
    I don't have a soultion for you. I have used ADSl without wifi for quite some time too and never had a problem with LnS. It started with the wifi and that seems to be solved now with the new rule.
     
  12. Raccoon

    Raccoon Guest

    Nobody else with a solution?

    Seems I'll just have to abandon LnS... :(
     
  13. Frederic

    Frederic LnS Developer

    Joined:
    Jan 9, 2003
    Posts:
    4,354
    Location:
    France
    The only information we have is "Just got ADSL (not wi fi) and its almost completely throttling the data transfer". This is not sufficient to give you a direct solution.
    If you agree to investigate a little, the first thing to do is to check if the problem is coming from the Internet Filtering or Application filtering (just deactivate one of the filtering and see if it makes a difference). Next, if the problem is coming from Internet filtering, check the logs to see what has been blocked.

    Frederic
     
  14. Raccoon

    Raccoon Guest

    Sorry If I havent given enough info...

    Problem of getting the info now is that I'v had to uninstall LnS since I had to install another firewall...
    Anyway, if it helps - there was a check box at the bottom in 1 of the windows ..."Internet filtering" if I remember correctly. I had tried deselecting it, and that did prevent the connection from being stifled!

    And if by application filtering you literally mean individual application filtering, then ALL programs were being blocked from accessing the net ...not just particular programs.

    Would def. like to investigate further! But for that I'll have to uninstall the current firewall and reinstall LnS...

    Meanwhile, if what Iv mentioned above helps, please do let me know...
     
  15. Raccoon

    Raccoon Guest

    I'v reinstalled LnS...
    Im pasting the contents of the log file below.
    The connection seems to works normally if I deselect Internet Filtering check box.
    Strangely, the connection using my normal telephone modem seems to work without a hitch!

    Can somebody pleaseeeeeee helpo_O

    Please do let me know if any more info would help.

    11-04-05,19:52:57 U-27 'UDP : Any other UDP pack' 221.5.251.222 UDP Ports Dest:netbios-ns Src:netbios-ns
    11-04-05,19:52:59 U-28 'UDP : Any other UDP pack' 221.5.251.222 UDP Ports Dest:netbios-ns Src:netbios-ns
    11-04-05,19:53:00 U-29 'UDP : Any other UDP pack' 221.5.251.222 UDP Ports Dest:netbios-ns Src:netbios-ns
    11-04-05,19:53:41 D-30 'TCP : Any other packet ' 59.95.163.4 TCP Ports Dest:loc-srv Src:1620
    11-04-05,19:53:41 U-31 'UDP : Any other UDP pack' 59.95.163.4 UDP Ports Dest:netbios-ns Src:netbios-ns
    11-04-05,19:53:42 U-32 'UDP : Any other UDP pack' 59.95.163.4 UDP Ports Dest:netbios-ns Src:netbios-ns
    11-04-05,19:53:44 D-33 'TCP : Any other packet ' 59.95.163.4 TCP Ports Dest:loc-srv Src:1620
    11-04-05,19:53:44 U-34 'UDP : Any other UDP pack' 59.95.163.4 UDP Ports Dest:netbios-ns Src:netbios-ns
    11-04-05,19:53:45 U-35 'UDP : Any other UDP pack' 59.95.163.4 UDP Ports Dest:netbios-ns Src:netbios-ns
    11-04-05,19:53:47 U-36 'UDP : Any other UDP pack' 59.95.163.4 UDP Ports Dest:netbios-ns Src:netbios-ns
    11-04-05,19:53:48 U-37 'UDP : Any other UDP pack' 59.95.163.4 UDP Ports Dest:netbios-ns Src:netbios-ns
    11-04-05,19:53:50 D-38 'TCP : Any other packet ' 59.95.1.160 TCP Ports Dest:loc-srv Src:2206
    11-04-05,19:53:50 U-39 'UDP : Any other UDP pack' 59.95.1.160 UDP Ports Dest:netbios-ns Src:netbios-ns
    11-04-05,19:53:51 U-40 'UDP : Any other UDP pack' 59.95.1.160 UDP Ports Dest:netbios-ns Src:netbios-ns
    11-04-05,19:53:53 D-41 'TCP : Any other packet ' 59.95.1.160 TCP Ports Dest:loc-srv Src:2206
    11-04-05,19:53:53 U-42 'UDP : Any other UDP pack' 59.95.1.160 UDP Ports Dest:netbios-ns Src:netbios-ns
    11-04-05,19:53:54 U-43 'UDP : Any other UDP pack' 59.95.1.160 UDP Ports Dest:netbios-ns Src:netbios-ns
    11-04-05,19:53:56 U-44 'UDP : Any other UDP pack' 59.95.1.160 UDP Ports Dest:netbios-ns Src:netbios-ns
    11-04-05,19:53:57 U-45 'UDP : Any other UDP pack' 59.95.1.160 UDP Ports Dest:netbios-ns Src:netbios-ns
    11-04-05,19:54:02 D-46 'TCP : Any other packet ' 59.95.5.213 TCP Ports Dest:loc-srv Src:4969
     
  16. Frederic

    Frederic LnS Developer

    Joined:
    Jan 9, 2003
    Posts:
    4,354
    Location:
    France
    Hi,

    There alerts are simply related to netbios access, and nothing here could explain the connection problem.
    Is there the only kind of alerts you got from the log ?

    Did you modify the ruleset ? (for instance removing the ! flag on some rules).

    Thanks,

    Frederic
     
  17. Raccoon

    Raccoon Guest

    I definitely haven't modified any ruleset. Also, reinstalled LnS twice after this problem, so even if something was modified, I guess a reinstall would have reinstated the defaults.

    Meanwhile, I was on the LnS website and I found under the FAQ section the "I can not connect anymore to the internet" sub-section suggests that the "club_internet_adsl.rie" file be imported. I tried it and the connection is working!!! However, tests on 3 firewall testing sites including GRC say that my comp is no longer Stealthed ...the firewall is failing ALL tests! :-(

    Should I retain the .rie file? If yes, how do I secure my machine?

    I'm pasting records from the log taken just before the above .rie file was loaded, and when Lns was blocking everthing.

    Please help! :-(
    ---------------------

    11-07-05,00:04:37 D-2717 'TCP : Block incoming con' 80.239.156.195 TCP Ports Dest:4560 Src:ftp-data
    11-07-05,00:04:38 U-2718 'UDP : Any other UDP pack' 80.239.156.195 UDP Ports Dest:netbios-ns Src:netbios-ns
    11-07-05,00:04:39 U-2719 'UDP : Any other UDP pack' 80.239.156.195 UDP Ports Dest:netbios-ns Src:netbios-ns
    11-07-05,00:04:40 D-2720 'TCP : Block incoming con' 80.239.156.195 TCP Ports Dest:4560 Src:ftp-data
    11-07-05,00:04:41 U-2721 'UDP : Any other UDP pack' 80.239.156.195 UDP Ports Dest:netbios-ns Src:netbios-ns
    11-07-05,00:04:42 U-2722 'UDP : Any other UDP pack' 80.239.156.195 UDP Ports Dest:netbios-ns Src:netbios-ns
    11-07-05,00:04:43 D-2723 'TCP : Block incoming con' 80.239.156.195 TCP Ports Dest:4560 Src:ftp-data
    11-07-05,00:04:44 U-2724 'UDP : Any other UDP pack' 80.239.156.195 UDP Ports Dest:netbios-ns Src:netbios-ns
    11-07-05,00:04:45 U-2725 'UDP : Any other UDP pack' 80.239.156.195 UDP Ports Dest:netbios-ns Src:netbios-ns
    11-07-05,00:04:46 D-2726 'TCP : Block incoming con' 80.239.156.195 TCP Ports Dest:4560 Src:ftp-data
    11-07-05,00:04:46 D-2727 'UDP : Any other UDP pack' 221.12.40.144 UDP Ports Dest:1026 Src:33418
    11-07-05,00:04:46 D-2728 'UDP : Any other UDP pack' 221.12.40.144 UDP Ports Dest:1027 Src:33418
    11-07-05,00:04:47 U-2729 'UDP : Any other UDP pack' 221.12.40.144 UDP Ports Dest:netbios-ns Src:netbios-ns
    11-07-05,00:04:48 U-2730 'UDP : Any other UDP pack' 221.12.40.144 UDP Ports Dest:netbios-ns Src:netbios-ns
    11-07-05,00:04:49 D-2731 'TCP : Block incoming con' 80.239.156.195 TCP Ports Dest:4560 Src:ftp-data
    11-07-05,00:04:50 U-2732 'UDP : Any other UDP pack' 221.12.40.144 UDP Ports Dest:netbios-ns Src:netbios-ns
    11-07-05,00:04:51 U-2733 'UDP : Any other UDP pack' 221.12.40.144 UDP Ports Dest:netbios-ns Src:netbios-ns
    11-07-05,00:04:52 D-2734 'TCP : Block incoming con' 80.239.156.195 TCP Ports Dest:4560 Src:ftp-data
    11-07-05,00:04:53 U-2735 'UDP : Any other UDP pack' 221.12.40.144 UDP Ports Dest:netbios-ns Src:netbios-ns
    11-07-05,00:04:54 U-2736 'UDP : Any other UDP pack' 221.12.40.144 UDP Ports Dest:netbios-ns Src:netbios-ns
    11-07-05,00:04:55 U-2737 'UDP : Any other UDP pack' 64.4.12.200 UDP Ports Dest:7001 Src:4573
     
  18. Frederic

    Frederic LnS Developer

    Joined:
    Jan 9, 2003
    Posts:
    4,354
    Location:
    France
    Hi,

    The rule you imported allows fragmented packets.
    Normally this rule is not supposed to unstealth the PC.
    Could you confirm you are stealth without the rules and not stealth when the rule is enabled (when running GRC test) ?

    Thanks,

    Frederic
     
  19. Raccoon

    Raccoon Guest

    Yes, when I was on dial up, everthing was working well, and I had tested LnS on GRC, PC Flank, etc ...and it definitely was stelthed.
    As of now, on my ADSL, if I don't import the rules, LnS simply stops all data ...so the question of checking on GRC or wherever isn't possible.
    And when I import the rules, I can test, as the connection works ...but then not a single port is stealthed! :-(
     
  20. Raccoon

    Raccoon Guest

    No solutiono_O :-(((((((((
     
Thread Status:
Not open for further replies.