Hi, Frederic, If the Wan miniport is selected, does LnS allow ethernet type 8863/4 automatically? LnS can filter this kind of ethernet frame, so why don't you add 'PPPoE' in the Ethernet type drop box? thanks in advance.
Hi nuser, When you are using a PPPoE connection, you have usually 2 network interfaces. The Ethernet one, on which the PPPoE protocol is, and the Wan Miniport one, on which all the usual IP packets are seen. With this configuration, Look 'n' Stop has to be configured on the Wan Miniport interface and therefore Look 'n' Stop never sees PPPoE packets. So this protocol is not in the list because there is no reason to filter at this level. And if you filter at this level, Look 'n' Stop doesn't retrieve the IP packet inside the PPPoE frame. Frederic
Thanks a lot, Frederic, At the Wan miniport interface, PPPoE packets have been transformed into IP packets (discarding the 8-byte PPPoE header and ID, modifying Ethernet type and FCS). Generally, LnS binds to the interface where usual IP packets pass. Right? On traditional modem (56K), which interface will LnS bind? I notice that my Wan Miniport has a suffix: Look’n’St-11:22:33:44:55:66. Is this a Miniport driver added by LnS? My PC is in a Lan. If I select the Wan miniport interface (ip 0:0:0:0), will LnS still monitor the traffic? (I mean, do the packets through Ethernet pass through Wan miniport interface again?)
Hi nuser, Yes, exactly. Also the Wan-Miniport one. Not exactly, the miniport already exists, and Look 'n' Stop is just monitoring it, and it appears like that because of Windows internals. No, Wan miniport is only for PPP connection types (either direct PPP with traditional modems, or PPPoE with new modems). Frederic
Thanks, Frederic, At the miniport level, how does Look'n'stop distinguish these 2 kind of IP packets (direct PPP type without ethernet header and PPPoE type with ethernet header)? Another question: suppose LnS still filters at the Ethernet level and I add a rule like this: Ethernet type: All TCP: block incoming connections Does LnS be able to locate the exact position of TCP flag in the PPPoE frame? Or will it find something we don't expect?
Just by monitoring the right network interface. No, it won't be able to get and check the content at the right position of the TCP Flag. That's why this protocol is not supported. Frederic
Hi, I am also having same problem with LnS on my laptop. its WAN Miniport (PPPOE) connection and its wireless modem and connected to laptop. I am not technical person, can I get an easy way to come out from this problem.
Hi ankupan, This thread was not about a problem, it was just some clarifications about PPPoE. If the problem is still the same as mentioned in this thread: https://www.wilderssecurity.com/showthread.php?t=176014 then, are you saying the PC is using a PPPoE connection on top of WiFi ? This looks strange but maybe it is possible. Usually if you have a modem/router, then only the modem is using PPPoE to your ISP, and the PC just connects to the modem by using WiFi, but the PC doesn't use PPPoE directly. To go further, we just need you to give the detail of the log when Look 'n' Stop is started and it is not working. Please do it in the first thread, not here. Thanks, Frederic
Hi, Frederic, a little typing error: Wifi should be PPPoE. Hi, ankupan, Just upload a copy of your log.
Hi, ankupan, In the Option tab, tick the 'Log file'. Press the "Apply" button. Press the 'Show logs' button, you will find the log file. Make sure that the log file contains the information when you have trouble. Upload this file. Then Frederic or other gurus can analyze and guide you.
