From: "Rob Sterenborg" <rob@sterenborg.info>
To: netfilter@lists.netfilter.org
Subject: RE: Wol Magic Packets
Date: Tue, 29 Aug 2006 13:55:33 +0200 (CEST) [thread overview]
Message-ID: <64876.193.173.147.3.1156852533.squirrel@webmail.sterenborg.info> (raw)
In-Reply-To: <J4RCCQ$90300DFBE572C56BB53FC8E3AEB5BD68@libero.it>
On Tue, August 29, 2006 13:38, claudio987\@libero\.it wrote:
>>> packet enters only if I send it to a port opened into the router...: for
>>> example: if I forward port 30 tcp\udp to
>>> 192.168.0.2 (pc of my lan) and I send a wol packet for
>>> another internet address out of my lan to poty 30 of external ppp0
>>> interface of my router, pc 192.168.0.2 turns on
>>>
>>
>> Yes, well, you've said that before and as I said: if these *do* enter
>> your network then I don't know how to block them. Perhaps you can search for
>> the String match (it's in an older POM-ng and which I never used) and try to
>> catch those WOL packets by matching it's contents. Since each WOL packet
>> looks the same (6 bytes FF followed by 16 bytes containing the MAC address
>> of the PC to wake up), you should be able to do it.
>>
>> Gr,
>> Rob
>>
> how can I do it?
By downloading a kernel, POM-ng (patch-o-matic-ng) and an older POM-ng that
still has the string patchlet, and iptables. Patch the kernel using the older
POM-ng for the string match and use the newer POM-ng for recent stuff. Install
the new kernel and iptables and see if everything (still) works.
If you've never done this I suggest you search the internet for howto's, read
the README's and/or INSTALL files and try it with a test-PC first.
Howto's on patching a kernel is not really the scope of this list.
next prev parent reply other threads:[~2006-08-29 11:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-29 11:38 Wol Magic Packets claudio987
2006-08-29 11:55 ` Rob Sterenborg [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-08-28 19:45 claudio987
2006-08-29 5:54 ` Rob Sterenborg
2006-08-28 13:03 claudio987
2006-08-28 16:25 ` Rob Sterenborg
2006-08-24 16:00 claudio987
[not found] <J4I52P$07AD17049DE455463CE6BF9E6D425F69@libero.it>
2006-08-24 12:48 ` Rob Sterenborg
[not found] <J4H7AL$3755F2FB0EF94967751D3C49D3390021@libero.it>
2006-08-24 5:45 ` Rob Sterenborg
2006-08-23 9:33 claudio987
2006-08-23 10:13 ` Rob Sterenborg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=64876.193.173.147.3.1156852533.squirrel@webmail.sterenborg.info \
--to=rob@sterenborg.info \
--cc=netfilter@lists.netfilter.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox