Re: wake-on-lan support? (WOL)

2003-11-01 Thread Alexander Kühn
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Wake-On-Lan (WOL) is something that has next to nothing to do with the
installed OS. If it's a x86 PC you need a ATX power supply and board, a
network card that supports WOL, have the powerconnector of the network
card connected to the board, so it has power even if the machine is
powered down. You need to enable it in the PC bios and for some NICs
also in the NIC's BIOS as well (e.g. RTL 8139) using a NIC specific tool
(usually under DOS). Then you should do a soft powerdown (e.g. halt -p)
and then send the magic packet to the subnet the WOL machine is in.
Unfortunatly there are also different magic packets send by different
tools and some of the are not available on FreeBSD (e.g. Donald Becker's
ether-wake, which works for me).
I hope this helps,
Alexander.
Alexander Mayer wrote:

| Hi,
|
| is wake-on-lan possible on a PC running FreeBSD? I want to boot my
| FreeBSD-PC with wake-on-lan. In Linux there is a problem with many
| drivers because they disable wake-on-lan. Only a few drivers give the
| possibility to enable this feature. What about FreeBSD?
|
| Alex
|
| ___
| [EMAIL PROTECTED] mailing list
| http://lists.freebsd.org/mailman/listinfo/freebsd-questions
| To unsubscribe, send any mail to
| [EMAIL PROTECTED]
- --
Alexander Kuehn
Papendorf Software Engineering
Cell phone: +49 (0)177 6461165
Cell fax:   +49 (0)177 6468001
Tel @Calw:  +49 (0)7051 936980
Fax @Calw:  +49 (0)7051 9369822
Mail @Calw mailto:[EMAIL PROTECTED]
- -BEGIN PGP PUBLIC KEY BLOCK-
Version: GnuPG v1.2.3 (FreeBSD)
mQGiBD9rZYgRBAD5JesIz29bwmNHhVIJdiH8yuhbJ9I+TYdpLuxIKr1OU2ZVn9FL
ONC85Za6ElMDm6qjqyy2UECCxl8F+HXXFfkpyDqB5KwtGFUA9sEa99ArC0tLWMaT
XHhSKcUsS6HPjgWTNn504vZm5pu4A54ALPbKA0BB8/XKBhfg+AzFNSRp9wCgtfM2
ILb+zs4f7JRbsKb8P+MIWC8EAJdevnxVaw3RpJGPDR+iZPTL9mGLkydlNyBplaoM
EzCiDI6GZv4Mxs78fGOh5DBui28LaJ/t1SpXGLd1NI9vgY9G/RLxdphvw3srmwBM
XfIdfQOkHkpcbBOaFypLDIVEoMV9a3UJ71jhqFL1yD2bcKXY/bkml/Tq/IwXsG7C
DNoiA/49SiLxvyNa7XkpDIHNjo+q/o8DXPvHa3Qc5vvAMnrzh7ocLKNBvUWUvy62
Lkw07GEp9Pxd16Tj1TNdIeEmMHKzUYt24cjoZ0y6HJ6rdQs9IXwyEx9vQ5KsL44u
SYH1XtBVr07N7DcsRMEU2hy7N/EJALtwV89vP7bVxsLWQ658wLQ2QWxleGFuZGVy
IEvDvGhuICh3d3cubmFnaWx1bS5vcmcpIDxha0BwYXBlbmRvcmYtc2UuZGU+iGQE
ExECACQFAj9rZYgCGwMFCQHhM4AGCwkIBwMCAxUCAwMWAgECHgECF4AACgkQk1Eo
cpNxA0Ye8ACgg11GVr2HkPxU6ebR9PN5j3I78DsAn2ON/SKQaxnIJk0hQlPu9dej
/UmxuQINBD9rZg4QCADmxQf6NT8sWgZQRJY812HZQK4icKwy6KgyVsx2cRtAyoi8
YiSHBBQ7qWEeBwhjk1RaDn4jP8bPMnnwQkW1YQ6Zh/LCEcl0j0LH9GZyZ8Glqdit
NfDktboWSBSaRWBjdOhLleGfplPEfWuq/neid9SgWy27fSo6+Yz/jAJ4BWBBdpH/
5khUTUjdPo4G+DXQW0+Mqp81fmSdeOxjfukF90fKq/LmLfqseTic6xnITaDMGOtV
1jeu6zp5GEcbtRr8aNTj+Gisg4EDoeZxihgnC2TWJtX4nfVk6aP0R8QlifYaukjf
Nye6qkfWiG0LwLDP/L4/6FlMDsg0u/ZcyPZFPyUrAAMGB/wJ+OaHzrKSxl0AmCZB
efq8kdrVqlH+fEbHbBhXTv3EKZbj75UWWe4QZI6A3eT9EKv7XMqhk9w/bRsnsVB6
Qx6uv1tXGV041TdnaQ0xezdHEAY81SixnntxyS6aiCPXeR+Bzpc2JL81vPt5Zftn
nofozDdiinpms0PkjEb1onR3rsIG9A4d/8Z70repweydQ+YWnLFDanP+B5Fw/jf0
HlU1fBWQvxtWXWqYagH6o9JbgdA2NqCtcAdq3FWwCTQUcJYzugjdmSgHVWSTpt7Y
n1IibfO/ELHyLQ8JivdOQNw1YcTtmoSHudJwRZRndYsc2JbbvpVz9TMiofN2dWAg
QehSiE8EGBECAA8FAj9rZg4CGwwFCQHhM4AACgkQk1EocpNxA0aOjQCfTe4ERTvh
99pDGdF5kZ0fwrnyYVcAoKxAsskAPM9JV86ugvxeQJIOqohB
=YSR6
- -END PGP PUBLIC KEY BLOCK-
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3-nr1 (Windows 2000)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQE/o6HVk1EocpNxA0YRAs8XAJsEKgMXqomuHy/KDOUzI3wRQfa8OgCcChbf
QXPtqpDuTd5BqJS0jxqPWj8=
=hLPr
-END PGP SIGNATURE-
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


RE: tranparent proxying, squid, nat, ipfw

2003-10-06 Thread Alexander Kühn
Hi,
my advice is, take it step by step. Set up your nat, apache (if you need it),
squid (don't use httpd_accel at the beginning!).
Now I'm a bit unsure what you want to do, if you want to force the use of a
proxy for your NAT-Users, so create your redirection rule which redirects
outgoing traffic to port 80 (,https,...) to your localhost squid.
httpd_accel is for accelerating a specific webserver in your realm, you can use
it to speed up the responses from your local apache or any other webserver in
your lan (and thereby making it accessible from outside, if you set the ACL
accordingly).
The question is, what do you want to accomplish?
Kind regards,
Alex.

Quoting Gil Agno Virtucio [EMAIL PROTECTED]:

 so far this was the simpliest squid configuration that i've seen...
 
 http://ezine.daemonnews.org/200209/squid.html
 
 
 hope this helps...
 
 -
 Gil Agno Virtucio
 Janitor/Collector/Messenger
 NEC System Integration and Construction Philippines Inc. 
 15th Floor BPI Buendia Center
 Gil Puyat Ave. Makati City 1200
 Cellphone : +639163989695
 Office Phone: +6328914167
 -
 
 
 -Original Message-
 From: synrat [mailto:[EMAIL PROTECTED]
 Sent: Monday, October 06, 2003 11:40 AM
 To: [EMAIL PROTECTED]
 Subject: tranparent proxying, squid, nat, ipfw
 
 
 I'm having a hard time getting this working together.
 I have squid 2.5 stable working and with all the required
 setting for transparent proxying. The machine has the kernel with IPFW 
 and
 forwarding options. NAT is on, firewall type is simple with some
 modifications. Internal interface address is 192.168.1.1. Squid runs 
 fine
 when the browser is setup to access it, but the goal is not to have to 
 do
 that.
 
 http_port 3128
 httpd_accel_host virtual
 httpd_accel_port 80
 httpd_accel_with_proxy  on
 httpd_accel_uses_host_header on
 
 I have the forwarding rule as well
 
 fwd 127.0.0.1,3128 tcp from any to any 80
 
 I tried 192.168.1.1,3128 in the rule. Tried putting it before both 
 divert
 rules. Here's my ipfw list output
 
 
 
 00050 divert 8668 ip from any to any via rl0
 00100 allow ip from any to any via lo0
 00200 deny ip from any to 127.0.0.0/8
 00300 deny ip from 127.0.0.0/8 to any
 00400 deny ip from 192.168.1.0/24 to any in recv rl0
 00500 deny ip from 66.92.100.0/24 to any in recv rl1
 00600 deny ip from any to 10.0.0.0/8 via rl0
 00700 deny ip from any to 172.16.0.0/12 via rl0
 00800 deny ip from any to 192.168.0.0/16 via rl0
 00900 deny ip from any to 0.0.0.0/8 via rl0
 01000 deny ip from any to 169.254.0.0/16 via rl0
 01100 deny ip from any to 192.0.2.0/24 via rl0
 01200 deny ip from any to 224.0.0.0/4 via rl0
 01300 deny ip from any to 240.0.0.0/4 via rl0
 01400 divert 8668 ip from any to any via rl0
 01500 deny ip from 10.0.0.0/8 to any via rl0
 01600 deny ip from 172.16.0.0/12 to any via rl0
 01700 deny ip from 192.168.0.0/16 to any via rl0
 01800 deny ip from 0.0.0.0/8 to any via rl0
 01900 deny ip from 169.254.0.0/16 to any via rl0
 02000 deny ip from 192.0.2.0/24 to any via rl0
 02100 deny ip from 224.0.0.0/4 to any via rl0
 02200 deny ip from 240.0.0.0/4 to any via rl0
 02300 allow tcp from any to any established
 02400 allow ip from any to any frag
 02500 allow tcp from any to 66.92.100.221 25 setup
 02600 allow tcp from 192.168.1.0/24 to 192.168.1.0/24
 02700 allow tcp from 192.168.1.0/24 to 192.168.1.0/24
 02800 allow udp from 192.168.1.0/24 to 192.168.1.0/24
 02900 allow udp from 192.168.1.0/24 to 192.168.1.0/24
 03000 allow tcp from any to 66.92.100.221 80 setup
 03100 allow tcp from any to 66.92.100.221 8080 setup
 03200 allow tcp from any to 66.92.100.221 8021 setup
 03300 allow tcp from any to 66.92.100.221 21 setup
 03400 allow tcp from any to 66.92.100.221 22 setup
 03500 allow tcp from any to 66.92.100.221 110 setup
 03600 allow tcp from any to 66.92.100.221 143 setup
 03700 allow tcp from any to 66.92.100.221 993 setup
 03800 allow tcp from any to 66.92.100.221 995 setup
 03900 allow icmp from any to any
 04000 deny log tcp from any to any in recv rl0 setup
 04100 allow tcp from any to any setup
 04200 fwd 127.0.0.1,3128 tcp from any to any 80
 04300 allow udp from 66.92.100.221 to any keep-state
 04400 allow udp from 192.168.1.3 to any keep-state
 65535 deny ip from any to any
 
 


-
This mail sent through IMP: http://horde.org/imp/
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]