fetch(1) vs browser download fails comparison
Hello: How might a file retrieved/downloaded by fetch(1) differ from the same file downloaded by a web browser (in this case mozilla firefox)? Specifically, if I download the free version of ZoneAlarm for Windows (about 10mb) by each of these methods, I get the file(s) and they're both the same length, but they fail comparison, both by cmp(1) and by differing md5 hashes. As a counterexample, fetching OpenOffice (some 80mb or so) works fine hash-verifies correctly. This same behavior is with both 4.10-stable and 5.4-release. Ideas? Please cc me any replies. Thanks, -kc ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Interactive Unix S51K (or S52K) support
Does FreeBSD have any support (even read only) for the S51K and/or S52K filesystems as were in Sunsoft Interactive Unix... umm... 4.1.x? FAQ/documentation pointers very welcome. :) Thanks, -kc ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
ipfw2 NAT/forwarding config for bittorrent
Hello -questions: I would like to make bittorrent work in following scenario: - machine running py-bittorrent has private ip-address 192.168.x.y and currently runs FreeBSD 5.4-RELEASE - firewall/NAT machine is FreeBSD 4.10-STABLE, last updated by source in November 2004. - firewall/NAT is ipfw2, has run just fine for months How do I configure ipfw2 for properly forwarding the bittorrent ports (6881-6889) to the destination machine? Log_in_vain is active on the firewall machine when bittorrent is active on the private-ip machine, the firewall's syslog is being cluttered with attempts on port 6881. Where in the firewall config would such rule(s) go in relation to the divert rule? Would that silence the port 6881 messages properly pass that traffic to the internal machine? So far I'm not understanding the ipfw manpage for port forwarding. FAQ/documentation/RTFM pointers/examples are quite welcome. :) Please CC me any replies. Thanks, -kc ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Replacing hdd in multiboot system
Hello -questions: I have a failing hdd and could use some input/advice as to a strategy for replacing it. See below for system/configuration information (more on request). Based on reported/logged information and on usage patterns, da1 is the failing drive I need to replace it. Notes: This system is triple-bootable via (Linux) LILO. OSes are MS-DOS, Linux and FreeBSD. Each drive contains several filesystems. da0 is MS-DOS only (+ a couple of non-bootable UFS filesystems). da0 has LILO installed into the MBR. FreeBSD boots from da1, which also contains the root filesystem. da1 has both Linux (Slackware 7.0 I think) and FreeBSD. da1 is backed up (via scp/rsync to another local FreeBSD system) and can be replaced when convenient. What I (think I) want to do: 1. Using a separate similar system, install/configure FreeBSD (4 or 5, most likely 5.4 when the CDs arrive) onto a drive that will become da1. Linux can disappear. 2. Dual-boot MS-DOS (for the time being :) and FreeBSD. DOS needs to boot from da0 and FreeBSD needs to boot/root from da1. Questions: 1. Can I boot MS-DOS from da0 and FreeBSD from da1 using boot managers available with FreeBSD? If so, how do I configure that? (In other words, replace LILO on da0.) 2. FreeBSD's boot remembers what was last booted uses that; how do I configure a default booting OS? 3. I might replace that old dpt HBA with, say, an Adaptec or a Symbios-based Tekram; will that affect things such as drive geometries? 4. Anything I might be missing here? Common overlooked issues? Warnings? Gotchas? Documentation pointers are, of course, quite welcome. Please cc me as I'm not subscribed to -questions. Thanks, -kc System/configuration: uname -a: FreeBSD localhost.my.domain 4.10-STABLE FreeBSD 4.10-STABLE #0: Sun Nov 28 03:17:35 CST 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/LOCAL i386 Drives (from dmesg.boot): da0 at dpt0 bus 0 target 0 lun 0 da0: SEAGATE ST32550W 0021 Fixed Direct Access SCSI-2 device da0: Tagged Queueing Enabled da0: 2047MB (4193546 512 byte sectors: 255H 63S/T 261C) da1 at dpt0 bus 0 target 1 lun 0 da1: SEAGATE ST34573LW 6246 Fixed Direct Access SCSI-2 device da1: Tagged Queueing Enabled da1: 4243MB (8689787 512 byte sectors: 255H 63S/T 540C) da2 at dpt0 bus 0 target 2 lun 0 da2: IBM DNES-309170W S80K Fixed Direct Access SCSI-3 device da2: Tagged Queueing Enabled da2: 8748MB (17916239 512 byte sectors: 255H 63S/T 1115C) Relevant pieces from /var/log/messages: May 12 23:13:09 kern.crit localhost /kernel: (da1:dpt0:0:1:0): READ(06). CDB: 8 0 45 57 a 0 May 12 23:13:09 kern.crit localhost /kernel: (da1:dpt0:0:1:0): MEDIUM ERROR info:4557 asc:11,0 May 12 23:13:09 kern.crit localhost /kernel: (da1:dpt0:0:1:0): Unrecovered read error field replaceable unit: e4 sks:80,101 May 12 23:21:56 kern.crit localhost /kernel: (da1:dpt0:0:1:0): READ(06). CDB: 8 0 45 57 a 0 May 12 23:21:56 kern.crit localhost /kernel: (da1:dpt0:0:1:0): MEDIUM ERROR info:4557 asc:16,0 May 12 23:21:56 kern.crit localhost /kernel: (da1:dpt0:0:1:0): Data synchronization mark error field replaceable unit: d2 sks:80,101 May 12 23:22:23 kern.crit localhost /kernel: (da1:dpt0:0:1:0): READ(06). CDB: 8 0 45 57 a 0 May 12 23:22:23 kern.crit localhost /kernel: (da1:dpt0:0:1:0): MEDIUM ERROR info:4557 asc:16,0 May 12 23:22:23 kern.crit localhost /kernel: (da1:dpt0:0:1:0): Data synchronization mark error field replaceable unit: d2 sks:80,101 May 12 23:24:57 kern.crit localhost /kernel: (da1:dpt0:0:1:0): READ(06). CDB: 8 0 45 57 a 0 May 12 23:24:57 kern.crit localhost /kernel: (da1:dpt0:0:1:0): MEDIUM ERROR info:4557 asc:16,0 May 12 23:24:57 kern.crit localhost /kernel: (da1:dpt0:0:1:0): Data synchronization mark error field replaceable unit: d2 sks:80,101 May 13 00:18:01 kern.crit localhost /kernel: (da1:dpt0:0:1:0): READ(06). CDB: 8 0 45 57 a 0 May 13 00:18:01 kern.crit localhost /kernel: (da1:dpt0:0:1:0): MEDIUM ERROR info:4557 asc:16,0 May 13 00:18:01 kern.crit localhost /kernel: (da1:dpt0:0:1:0): Data synchronization mark error field replaceable unit: d2 sks:80,101 May 13 00:18:29 kern.crit localhost /kernel: (da1:dpt0:0:1:0): READ(06). CDB: 8 0 45 57 a 0 May 13 00:18:29 kern.crit localhost /kernel: (da1:dpt0:0:1:0): MEDIUM ERROR info:4557 asc:11,0 May 13 00:18:29 kern.crit localhost /kernel: (da1:dpt0:0:1:0): Unrecovered read error field replaceable unit: e4 sks:80,101 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
USB flash drive support/usage
Hello:
I have some questions about the little USB flash drives...
Is there a FAQ or some documentation on them? So far I haven't
found much in the Handbook or manpages. Pointers welcome. :)
Do I need any driver(s) besides umass(4) its required kernel options?
Any differences between 4.x and 5.x support for them?
Apparently they come setup for a FAT32 filesystem - can I format
them for other filesystems (e.g. linux-ext2, BSD UFS/UFS2, MS
NTFS) expect them to work reliably?
Assuming they work (well) with FreeBSD, how do I properly set
them up for UFS/UFS2? Do I need to fdisk and {disk,bsd}label first?
Any favorite/least-favorite brands/models or recommendations as
to which one(s) to seek/avoid for use with FreeBSD?
Thanks,
-kc
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
traceroute: sendto: Permission denied (4.10-RELEASE)
Hello -questions:
Lately (since a few days ago) I've been getting an oddity from
traceroute, for example:
traceroute to www.freebsd.org (216.136.204.117), 64 hops max, 44 byte packets
traceroute: sendto: Permission denied
1 traceroute: wrote www.freebsd.org 44 chars, ret=-1
*traceroute: sendto: Permission denied
traceroute: wrote www.freebsd.org 44 chars, ret=-1
* 10.108.0.1 (10.108.0.1) 7.212 ms
[other hops that look just fine]
13 www.freebsd.org (216.136.204.117) 94.209 ms 87.449 ms 89.103 ms
OS is 4.10-RELEASE, built from source acquired via cvsup.
I get that Permission denied at the beginning regardless of
where I might try tracing outside (external interface - dc0)
e.g. it works just fine to my local net (local interface - dc1).
Up until a few days ago, traceroute worked fine and never (as
far as I recall) reported such a message.
Btw, that 10.108.0.1 hop has been there for ages, and while I
think it's unusual it has been there for ages hasn't
previously affected traces.
The difference between previous now is that traceroute:
sendto: Permission denied message
What does that mean? What is traceroute trying to do?
I tried the tracert from a local (NATed) Win2k machine that
seems to work as it always has. {shrug}
Any idea(s) what's (not) happening?
Is my upstream connection blocking something (again)?
Is there some kind of workaround/fix (perhaps my firewall config)?
Thanks,
-kc
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
DNS access on private (RFC 1918) network
Hello:
I get messages like the following in my syslog all the time:
Jan 20 09:00:40 kern.info localhost /kernel: Connection attempt to UDP
192.168.0.1:1990 from 192.168.0.1:53
Jan 20 09:02:48 kern.info localhost /kernel: Connection attempt to UDP
192.168.0.1:2052 from 192.168.0.1:53
Jan 20 09:02:53 kern.info localhost /kernel: Connection attempt to UDP
192.168.0.1:2053 from 192.168.0.1:53
Jan 20 09:03:03 kern.info localhost /kernel: Connection attempt to UDP
192.168.0.1:2054 from 192.168.0.1:53
Jan 20 09:03:37 kern.info localhost /kernel: Connection attempt to UDP
192.168.0.1:2055 from 192.168.0.1:53
I'm (trying to :) run a cache-only nameserver, and it seems to work,
albeit with the above messages getting generated/logged all the time.
OS: FreeBSD-stable as of 15 January 2004
BIND version: 8.3.7-REL
log_in_vain is set to 1 in /etc/rc.conf.
allow-query { 127.0.0.1; 192.168.0.0/16; }; in named.conf.
I'd like to fix this but so far haven't found the answer in the
various FMs to RT. :) (the Cricket Book, 3rd ed the manpages)
Any ideas? FAQ/documentation/howto pointers are very welcome.
Thanks,
-kc
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
(revised) 4.0-stable Linksys WRT54G won't talk w/each other
Hello: I'm having problems getting a FreeBSD machine and a Linksys WRT54G talking with each other. Interfaces: dc0 - public to outside Internet dc1 - internal 192.168.0.1/24, connects to a hub dc2 - internal 192.168.1.100/24, connects to a switched LAN port on the router dc3 - currently unused OS: FreeBSD 4.9-STABLE as of 10 December 2003 firewall: ipfw2 Running natd between dc0 dc1 ( that works fine) dc0 gets its IP address, etc., via DHCP/dhclient. dc1 is configured statically machines connected on that subnet work fine. dc2 should get its ip address, etc. from a Linksys WRT54G, but won't; syslog says address in use, so I configured it manually with ifconfig, to 192.168.1.100/24. Problems/questions: dc2 has a Linksys WRT54G on it, thus far, that box refuses to talk (not even icmp) with the fbsd machine, even if I set its ip-address that of dc2 manually. (The Linksys defaults to running a dhcp server its factory-supplied ip-address is 192.168.1.1 it tries to setup the first interface talking to it to be 192.168.1.100). The router works fine when connecting another machine (running Windows 2000) to it. As examples: $ ping -c3 192.168.0.2 ## this is a Windows2000 box on the dc1 network PING 192.168.0.2 (192.168.0.2): 56 data bytes 64 bytes from 192.168.0.2: icmp_seq=0 ttl=128 time=0.391 ms 64 bytes from 192.168.0.2: icmp_seq=1 ttl=128 time=0.177 ms 64 bytes from 192.168.0.2: icmp_seq=2 ttl=128 time=0.232 ms --- 192.168.0.2 ping statistics --- 3 packets transmitted, 3 packets received, 0% packet loss round-trip min/avg/max/stddev = 0.177/0.267/0.391/0.091 ms localhost# tcpdump -lni dc1 ## tcpdump while running the above ping tcpdump: listening on dc1 10:15:39.882162 arp who-has 192.168.0.2 tell 192.168.0.1 10:15:39.882305 arp reply 192.168.0.2 is-at 0:90:27:84:42:f 10:15:39.882318 192.168.0.1 192.168.0.2: icmp: echo request 10:15:39.882492 192.168.0.2 192.168.0.1: icmp: echo reply 10:15:40.883394 192.168.0.1 192.168.0.2: icmp: echo request 10:15:40.883511 192.168.0.2 192.168.0.1: icmp: echo reply 10:15:41.893417 192.168.0.1 192.168.0.2: icmp: echo request 10:15:41.893584 192.168.0.2 192.168.0.1: icmp: echo reply $ ping -c3 192.168.1.1 ## ip address of the router on dc2 PING 192.168.1.1 (192.168.1.1): 56 data bytes --- 192.168.1.1 ping statistics --- 3 packets transmitted, 0 packets received, 100% packet loss localhost# tcpdump -lni dc2 ## tcpdump while running the above ping tcpdump: listening on dc2 10:17:18.123385 arp who-has 192.168.1.1 tell 192.168.1.100 10:17:19.124588 arp who-has 192.168.1.1 tell 192.168.1.100 10:17:20.134583 arp who-has 192.168.1.1 tell 192.168.1.100 Any ideas on getting this thing to work? It seems to work fine when connected to a Windows2000 machine. Yes, I've tried other interfaces cables, etc, so I'm confident the hardware is fine. :) Idea(s) on further troubleshooting/fixing this? FAQs/documentation pointers are quite welcome. :) Thanks, -kc ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
(revised) 4.*9*-stable Linksys WRT54G won't talk w/each other
oops, mistype, that should've been 4.9-stable instead of 4.0... stupidfingers... Hello: I'm having problems getting a FreeBSD machine and a Linksys WRT54G talking with each other. Interfaces: dc0 - public to outside Internet dc1 - internal 192.168.0.1/24, connects to a hub dc2 - internal 192.168.1.100/24, connects to a switched LAN port on the router dc3 - currently unused OS: FreeBSD 4.9-STABLE as of 10 December 2003 firewall: ipfw2 Running natd between dc0 dc1 ( that works fine) dc0 gets its IP address, etc., via DHCP/dhclient. dc1 is configured statically machines connected on that subnet work fine. dc2 should get its ip address, etc. from a Linksys WRT54G, but won't; syslog says address in use, so I configured it manually with ifconfig, to 192.168.1.100/24. Problems/questions: dc2 has a Linksys WRT54G on it, thus far, that box refuses to talk (not even icmp) with the fbsd machine, even if I set its ip-address that of dc2 manually. (The Linksys defaults to running a dhcp server its factory-supplied ip-address is 192.168.1.1 it tries to setup the first interface talking to it to be 192.168.1.100). The router works fine when connecting another machine (running Windows 2000) to it. As examples: $ ping -c3 192.168.0.2 ## this is a Windows2000 box on the dc1 network PING 192.168.0.2 (192.168.0.2): 56 data bytes 64 bytes from 192.168.0.2: icmp_seq=0 ttl=128 time=0.391 ms 64 bytes from 192.168.0.2: icmp_seq=1 ttl=128 time=0.177 ms 64 bytes from 192.168.0.2: icmp_seq=2 ttl=128 time=0.232 ms --- 192.168.0.2 ping statistics --- 3 packets transmitted, 3 packets received, 0% packet loss round-trip min/avg/max/stddev = 0.177/0.267/0.391/0.091 ms localhost# tcpdump -lni dc1 ## tcpdump while running the above ping tcpdump: listening on dc1 10:15:39.882162 arp who-has 192.168.0.2 tell 192.168.0.1 10:15:39.882305 arp reply 192.168.0.2 is-at 0:90:27:84:42:f 10:15:39.882318 192.168.0.1 192.168.0.2: icmp: echo request 10:15:39.882492 192.168.0.2 192.168.0.1: icmp: echo reply 10:15:40.883394 192.168.0.1 192.168.0.2: icmp: echo request 10:15:40.883511 192.168.0.2 192.168.0.1: icmp: echo reply 10:15:41.893417 192.168.0.1 192.168.0.2: icmp: echo request 10:15:41.893584 192.168.0.2 192.168.0.1: icmp: echo reply $ ping -c3 192.168.1.1 ## ip address of the router on dc2 PING 192.168.1.1 (192.168.1.1): 56 data bytes --- 192.168.1.1 ping statistics --- 3 packets transmitted, 0 packets received, 100% packet loss localhost# tcpdump -lni dc2 ## tcpdump while running the above ping tcpdump: listening on dc2 10:17:18.123385 arp who-has 192.168.1.1 tell 192.168.1.100 10:17:19.124588 arp who-has 192.168.1.1 tell 192.168.1.100 10:17:20.134583 arp who-has 192.168.1.1 tell 192.168.1.100 Any ideas on getting this thing to work? It seems to work fine when connected to a Windows2000 machine. Yes, I've tried other interfaces cables, etc, so I'm confident the hardware is fine. :) Idea(s) on further troubleshooting/fixing this? FAQs/documentation pointers are quite welcome. :) Thanks, -kc ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: (revised) 4.*9*-stable Linksys WRT54G won't talk w/each other
Date: Fri, 9 Jan 2004 12:56:20 -0500 (EST)
From: Anthony Volodkin [EMAIL PROTECTED]
To: Kenneth W Cochran [EMAIL PROTECTED]
cc: [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Re: (revised) 4.0-stable Linksys WRT54G won't talk w/each other
Hey,
Apparently the WRT54G is having some arp issues. I'd check the following:
- install latest firmware
Have avoided that so far b/c I wanted to be able to do that from
FreeBSD, e.g. with tftp...
But I might just go ahead do that via Windows. {shrug}
- install Ethereal on the windows machine and watch the traffic exchange
when you would ping/access the WRT54G. It is important that this is done
right after boot so that the Windows machine does not have the MAC of
WRT54G cached. It'd be interesting to compare the arp requests from the
FreeBSD machine to ones from the Win2k one, if that seems at all
different.
Have thought about that too, especially since trying to
tcpdump dc2 with the Windows box connected to the Linksys
resulted in nothing (the inside part of the Linksys is
a switch).
- Finally, I assumed that the cable that you are using to connect the
freebsd box to WRT54G is just as good as the one you use with the Windows
machine.
Yup, cables interfaces are all good; 1st thing I checked.
-Anthony
-kc
On Fri, 9 Jan 2004, Kenneth W Cochran wrote:
Hello:
I'm having problems getting a FreeBSD machine and a Linksys
WRT54G talking with each other.
Interfaces:
dc0 - public to outside Internet
dc1 - internal 192.168.0.1/24, connects to a hub
dc2 - internal 192.168.1.100/24, connects to a switched LAN port on the router
dc3 - currently unused
OS: FreeBSD 4.9-STABLE as of 10 December 2003
firewall: ipfw2
Running natd between dc0 dc1 ( that works fine)
dc0 gets its IP address, etc., via DHCP/dhclient.
dc1 is configured statically machines connected on that subnet work fine.
dc2 should get its ip address, etc. from a Linksys WRT54G,
but won't; syslog says address in use, so I configured it manually
with ifconfig, to 192.168.1.100/24.
Problems/questions:
dc2 has a Linksys WRT54G on it, thus far, that box refuses
to talk (not even icmp) with the fbsd machine, even if I set
its ip-address that of dc2 manually. (The Linksys
defaults to running a dhcp server its factory-supplied
ip-address is 192.168.1.1 it tries to setup the first
interface talking to it to be 192.168.1.100). The router
works fine when connecting another machine (running Windows
2000) to it.
As examples:
$ ping -c3 192.168.0.2 ## this is a Windows2000 box on the dc1 network
PING 192.168.0.2 (192.168.0.2): 56 data bytes
64 bytes from 192.168.0.2: icmp_seq=0 ttl=128 time=0.391 ms
64 bytes from 192.168.0.2: icmp_seq=1 ttl=128 time=0.177 ms
64 bytes from 192.168.0.2: icmp_seq=2 ttl=128 time=0.232 ms
--- 192.168.0.2 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.177/0.267/0.391/0.091 ms
localhost# tcpdump -lni dc1 ## tcpdump while running the above ping
tcpdump: listening on dc1
10:15:39.882162 arp who-has 192.168.0.2 tell 192.168.0.1
10:15:39.882305 arp reply 192.168.0.2 is-at 0:90:27:84:42:f
10:15:39.882318 192.168.0.1 192.168.0.2: icmp: echo request
10:15:39.882492 192.168.0.2 192.168.0.1: icmp: echo reply
10:15:40.883394 192.168.0.1 192.168.0.2: icmp: echo request
10:15:40.883511 192.168.0.2 192.168.0.1: icmp: echo reply
10:15:41.893417 192.168.0.1 192.168.0.2: icmp: echo request
10:15:41.893584 192.168.0.2 192.168.0.1: icmp: echo reply
$ ping -c3 192.168.1.1 ## ip address of the router on dc2
PING 192.168.1.1 (192.168.1.1): 56 data bytes
--- 192.168.1.1 ping statistics ---
3 packets transmitted, 0 packets received, 100% packet loss
localhost# tcpdump -lni dc2 ## tcpdump while running the above ping
tcpdump: listening on dc2
10:17:18.123385 arp who-has 192.168.1.1 tell 192.168.1.100
10:17:19.124588 arp who-has 192.168.1.1 tell 192.168.1.100
10:17:20.134583 arp who-has 192.168.1.1 tell 192.168.1.100
Any ideas on getting this thing to work? It seems to work
fine when connected to a Windows2000 machine.
Yes, I've tried other interfaces cables, etc, so I'm
confident the hardware is fine. :)
Idea(s) on further troubleshooting/fixing this?
FAQs/documentation pointers are quite welcome. :)
Thanks,
-kc
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Trying to understand ipfirewall/divert/nat
Hello: I'm trying to grok overall firewall natd (ipnat?) configuration strategy using ipfirewall. Interfaces: dc0 - public to outside network(s) dc1 - internal 192.168.0.1/24 dc2 - internal 192.168.1.100/24, currently unused dc3 - currently unused OS: FreeBSD 4.9-STABLE as of 10 December 2003 firewall: ipfw2 Running natd between dc0 dc1 dc0 gets its IP address, etc., via DHCP/dhclient. Problems/questions: ICMP (for example): Would like to be able to: Ping/traceroute, etc from any machine on the local net to anywhere. Be invisible to ICMP Echo Request from outside. Be visible to other relevant ICMP messages from outside, e.g. traceroute, Path MTU Discovery For example, the following ruleset (from the Ipfw-HOWTO at http://www.freebsd-howto.com/) takes care of icmp echo request/reply on the outside-exposed machine, but breaks that ( traceroute) on internal machines. 1000 allow icmp from any to any out icmptypes 8 1100 allow icmp from any to any in icmptypes 0 1200 deny icmp from any to any in icmptypes 8 Would like to do similar things, e.g. allow/deny insert port/service/protocol here get all that to play nicely with divert/natd. For example, with divert, it appears that we should have a ruleset for before the divert another mirror-image ruleset for after divert. Where might I find some nice explanations of the logic/strategy with this? I guess what confuses me is /etc/rc.firewall does things one way the firewall(7) manpage another. Where are some, umm, good sources of information about ipfirewall (ipfw)? Seems all the books talk about are Linux's ipchains iptables *bsd's ipf. Thanks, -kc ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
4.9-stable Linksys router won't talk with each other
Hello: I'm having problems getting a FreeBSD machine and a Linksys WRT54G talking with each other. Interfaces: dc0 - public to outside network(s) dc1 - internal 192.168.0.0/24 dc2 - internal 192.168.1.100/24, currently unused, gets the router (testing) dc3 - currently unused OS: FreeBSD 4.9-STABLE as of 10 December 2003 firewall: ipfw2 Running natd between dc0 dc1 ( that works fine) dc0 gets its IP address, etc., via DHCP/dhclient. dc1 is configures statically machines connected on that subnet work fine. dc2 should get its ip address, etc. from a Linksys WRT54G, but won't; syslog says address in use. Problems/questions: dc2 has a Linksys WRT54G on it, thus far, that box refuses to talk (not even ping/traceroute) with the fbsd machine, even if I set its ip-address that of dc2 manually. (The Linksys defaults to running a dhcp server its factory-supplied ip-address is 192.168.1.00 it tries to setup the first interface talking to it to be 192.168.1.1). I've even configured that router/wap to all-static using a Windows2000 machine it the FreeBSD machine still won't talk with each other. Any ideas on getting this thing to work? It seems to work fine when connected to a Windows2000 machine. Yes, I've tried other interfaces cables, etc, so I'm confident the hardware is fine. :) FAQs/documentation pointers are quite welcome. :) Thanks, -kc ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
fetching/playing radio audio
Hello: How can I play or otherwise listen to or download articles from NPR's archive(s)? OS is 4.9-RELEASE Browser is Mozilla 1.5 (mozilla-1.5_1,2) Mplayer other ports are up-to-date as of today. Everything is built from source. It makes no difference whether or not I have mplayer-plugin installed. If I click on an article from NPR's website (http://www.npr.org/), Mozilla downloads a file, named in the form nprNNN.wax where NNN are digits. Here are the contents of an example of one of those: $ cat npr9673.wax asx version = 3.0 titleNPR's Morning Edition - Thursday, November 6, 2003/title abstractmore info at : Morning Edition Web site/abstract moreinfo href=http://www.npr.org/programs/morning/; / entry param name=track value=13 / titleVoyager Nears End of Solar System/title authorNPR's Morning Edition - Thursday, November 6, 2003/author copyright(c) 2003 NPR/copyright ref href=mms://wm.npr.na-central.speedera.net/wm.npr.na-central/me/20031106_me_13.wma / /entry /asx $ What am I looking at here? How can I further grok what's going on? If I try that file (or that URI) with mplayer, it (mplayer) looks like it's trying to work but it freezes I have to ctl-c out of it. FAQ/doc/RTFM/mailing list archive pointers are quite welcome. Thanks, -kc ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
