Re: Promise PDC20265
It seems Esko Petteri Matinsola wrote: Hello, I have Asus A7V motherboard that has integrated UDMA100-controller PDC20265 made by Promise and Maxtor 54098H8 hard disk. When plugged to the UDMA66-controller the Maxtor works properly, boots and is fast. But when plugged to the PDC20265 BIOS detects it, kernel boots but don't detect the controller nor the disk so it complains about root not found. I checked the ata driver (I have 4.1-STABLE by yesterday) and it has support for Promise 100 (I presume it's PDC20265) but it doesn't work ? Any suggestions will be appreciated. I have it in my local tree, it should go in soon... -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: looking for microuptime went backwards victims...
I got this last night running 'mtv' on a system with heavy disk I/O.
The errors were:
Sep 5 23:12:14 genius /kernel: pcm0: hwptr went backwards 8208 - 8192
Sep 5 23:12:47 genius /kernel: pcm0: hwptr went backwards 8420 - 8192
Sep 5 23:12:57 genius /kernel: pcm0: hwptr went backwards 8212 - 8192
Sep 5 23:13:04 genius /kernel: pcm0: hwptr went backwards 8196 - 8192
Sep 5 23:13:21 genius /kernel: pcm0: hwptr went backwards 8208 - 8192
etc.
Joe
FreeBSD genius.systems.pavilion.net 5.0-CURRENT FreeBSD 5.0-CURRENT #11: Tue Sep 5
12:45:45 BST 2000 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENIUS i386
On Mon, Sep 04, 2000 at 06:41:14PM +0200, Poul-Henning Kamp wrote:
I'm looking for the remaining victims of the dreaded "microuptime
went backwards" message.
If you can reliably reproduce the problem, please contact me, so
we can arrange for some very detailed tracing to try to find out
what exactly is going on. I have not been able to trigger the
problem in my lab in a long time.
If you see the message only occationally, please try the attached
patch and let me know if this changes the picture. The patch is
not meant as a fix, but it might reduce the impact of this condition
considerably when it happens. Basically by reducing the width of
the timecounter the magnitude of the hit we take if the timecounter
goes backwards is reduced from about an hour to approx 110msec.
Reducing the width to less than 17 bits starts to run the risk of
ambiguity due to clock rollover.
This patch may not be safe with PCAUDIO.
Poul-Henning
Index: clock.c
===
RCS file: /home/ncvs/src/sys/i386/isa/clock.c,v
retrieving revision 1.155
diff -u -r1.155 clock.c
--- clock.c 2000/07/30 21:05:22 1.155
+++ clock.c 2000/09/04 16:34:16
@@ -194,7 +194,7 @@
static struct timecounter i8254_timecounter = {
i8254_get_timecount,/* get_timecount */
0, /* no poll_pps */
- ~0u,/* counter_mask */
+ 0x1,/* counter_mask */
0, /* frequency */
"i8254" /* name */
};
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD coreteam member | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
--
Josef KarthauserFreeBSD: How many times have you booted today?
Technical Manager Viagra for your server (http://www.uk.freebsd.org)
Pavilion Internet plc. [[EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED]]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: looking for microuptime went backwards victims...
Uhm, that is from the sound driver, not from the timecounter...
Poul-Henning
In message [EMAIL PROTECTED], Josef Karthauser writes:
I got this last night running 'mtv' on a system with heavy disk I/O.
The errors were:
Sep 5 23:12:14 genius /kernel: pcm0: hwptr went backwards 8208 - 8192
Sep 5 23:12:47 genius /kernel: pcm0: hwptr went backwards 8420 - 8192
Sep 5 23:12:57 genius /kernel: pcm0: hwptr went backwards 8212 - 8192
Sep 5 23:13:04 genius /kernel: pcm0: hwptr went backwards 8196 - 8192
Sep 5 23:13:21 genius /kernel: pcm0: hwptr went backwards 8208 - 8192
etc.
Joe
FreeBSD genius.systems.pavilion.net 5.0-CURRENT FreeBSD 5.0-CURRENT #11: Tue Sep 5
12:45:45 BST 2000 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENIUS
i386
On Mon, Sep 04, 2000 at 06:41:14PM +0200, Poul-Henning Kamp wrote:
I'm looking for the remaining victims of the dreaded "microuptime
went backwards" message.
If you can reliably reproduce the problem, please contact me, so
we can arrange for some very detailed tracing to try to find out
what exactly is going on. I have not been able to trigger the
problem in my lab in a long time.
If you see the message only occationally, please try the attached
patch and let me know if this changes the picture. The patch is
not meant as a fix, but it might reduce the impact of this condition
considerably when it happens. Basically by reducing the width of
the timecounter the magnitude of the hit we take if the timecounter
goes backwards is reduced from about an hour to approx 110msec.
Reducing the width to less than 17 bits starts to run the risk of
ambiguity due to clock rollover.
This patch may not be safe with PCAUDIO.
Poul-Henning
Index: clock.c
===
RCS file: /home/ncvs/src/sys/i386/isa/clock.c,v
retrieving revision 1.155
diff -u -r1.155 clock.c
--- clock.c 2000/07/30 21:05:22 1.155
+++ clock.c 2000/09/04 16:34:16
@@ -194,7 +194,7 @@
static struct timecounter i8254_timecounter = {
i8254_get_timecount,/* get_timecount */
0, /* no poll_pps */
-~0u,/* counter_mask */
+0x1,/* counter_mask */
0, /* frequency */
"i8254" /* name */
};
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD coreteam member | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
--
Josef Karthauser FreeBSD: How many times have you booted today?
Technical Manager Viagra for your server (http://www.uk.freebsd.org)
Pavilion Internet plc. [[EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED]]
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD coreteam member | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Token Ring ??
We deal lot with AS/400 customers with TRN systems. I see 4.1 release still doesn't have a TRN card supported. Anybody got any ideas how to support TRN in FreeBSD? Len http://BIND8NT.MEIway.com: ISC BIND 8.2.2 p5 installable binary for NT4 http://IMGate.MEIway.com: Build free, hi-perf, anti-spam mail gateways To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: FYI: RSA Donated to the public domain
In message [EMAIL PROTECTED] Warner Losh writes: : RSA Security Releases RSA Encryption Algorithm into Public Domain Note that other information at the site says that RSAREF isn't released into the public domain. Its use is still governed by copyright law, so we'll have to use the international version of RSAREF if we want to get RSA into -current. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Token Ring ??
AH No Token Ring Bad Token Ring.. :) I Had to do this about 2 months ago for a client. And to be quite honest, IT WAS AWEFUL I ended up just installing Win98 (I used to be a linux freak, Then this was the final straw, installation was no fun Long Live Chuckie) Nice support would be good, But God. Why Token Ring? :) We deal lot with AS/400 customers with TRN systems. I see 4.1 release still doesn't have a TRN card supported. Anybody got any ideas how to support TRN in FreeBSD? Len # http://www.theyshoulddie.com# # Making the world a better place,# one person at a time. # # To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Duplicating packets
Title: Duplicating packets I am doing some testing on FreeBSD 3.3 platform by sending some UDP packets thru FreeBSD routers. It's found that FreeBSD duplicates some packet. That results in that the received packet are more than sent ones. How can I disable the duplication in FreeBSD config. Or did I do some wrong in the FreeBSD config. The FreeBSD 3.3 is running on Pentium III, and NIC is 3C905B-Tx. Thanks in advance for any comments. - Hao
Re: FW: GeForce 6600 driver
Hi Dennis, Nick, et al. -On [2906 03:30], Dennis Wong ([EMAIL PROTECTED]) wrote: -Original Message- From:Nick Triantos Sent:Tuesday, September 05, 2000 6:20 PM To: Dennis Wong Subject: RE: GeForce 6600 driver Hi Dennis, Actually, we haven't done it yet. However, all of our major Linux dependencies should be in the 3 source files which ship as part of our kernel module's tarball. If those files were ported to BSD, in theory everything else "should" work, though I'm sure we'd need a bit of testing before that became fully true. We do plan to start on a FreeBSD port soon, we just haven't had time yet. However, if there's someone interested in trying to help do this port, we'd be happy to talk to them. They can email me at [EMAIL PROTECTED] Doug Rabson is the person responsible for the agp miniport driver currently in FreeBSD and I believe he is also a programmer working on the Direct Rendering Infrastructure over at Sourceforge. http://sourceforge.net/projects/dri/ Basically what should require work is probably the detection of your [Nvidia] cards and its subsequent support in DRI. I might be a bit off here, but I am sure one of my more knowledgable committers or fellow BSD users will correct me if wrong. BTW, we did also speak with the FreeBSD guys at linuxworld, I think we have a possible way we could check our code into the FreeBSD tree, which would be great once we do get it working well. There's the opportunity of one or more of your people to become a FreeBSD committer, or you can proxy through a committer, such as Mike Smith is doing for Adaptec's DPT driver. Feel free to post this, btw. I also really like BSD. Nice to see some BSD interest from the major companies aside from all the Linux hype. =) You cannot believe how happy I am to read things like this. Kind regards, -- Jeroen Ruigrok van der Werven Network- and systemadministrator [EMAIL PROTECTED]VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl Lead us not into temptation, but deliver us from evil... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Token Ring ??
-On [2906 15:05], Len Conrad ([EMAIL PROTECTED]) wrote: We deal lot with AS/400 customers with TRN systems. I see 4.1 release still doesn't have a TRN card supported. Anybody got any ideas how to support TRN in FreeBSD? If I am not mistaking Token Ring _is_ supported in FreeBSD. -- Jeroen Ruigrok van der Werven Network- and systemadministrator [EMAIL PROTECTED]VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl There can be no justice so long as laws are absolute... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Token Ring ??
If I am not mistaking Token Ring _is_ supported in FreeBSD. Stealthy support it is, then, as I cannot find it here: http://www.freebsd.org/releases/4.1R/notes.html Len http://BIND8NT.MEIway.com: ISC BIND 8.2.2 p5 installable binary for NT4 http://IMGate.MEIway.com: Build free, hi-perf, anti-spam mail gateways To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: FYI: RSA Donated to the public domain
On Wed, 6 Sep 2000, Jeroen C. van Gelderen wrote: [1] The press release talk about RSADSI "waiving its rights to enforce the RSA patent for any development activities" This is very cunning as the patent never actually covered development. Instead it covers usage and sales of products incorporating RSA, both of which are not explicitly allowed for in the press release. Better be careful, better get written approval! All of the pages they've put up on their website seems to disagree with what you've just said. I think you're confusing use of RSA and use of RSAREF/BSAFE, which they're still maintaining control over (as Warner said.) Somehow I rather doubt they're trying to trick people into using RSA for the next week, and then going on a mass lawsuit spree. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: FYI: RSA Donated to the public domain
On Wed, 6 Sep 2000, Mike Silbersack wrote: Somehow I rather doubt they're trying to trick people into using RSA for the next week, and then going on a mass lawsuit spree. Ugh, please forgive my poor English. It's before noon. Mike "Silby" Silbersack To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: FYI: RSA Donated to the public domain
On Wed, 6 Sep 2000, Warner Losh wrote: http://www.rsasecurity.com/news/pr/000906-1.html RSA Security Releases RSA Encryption Algorithm into Public Domain Ok, now I have a question. Using STARTTLS with sendmail is obviously OK for us, since sendmail got the export liscense. However, AFAIK, qmail and postfix have obtained no such permission. So, can we put in the STARTTLS patches for those two MTAs into the ports tree? Since the actual encryption duties are handled by OpenSSL in both cases, I suspect it's in the same boat as OpenSSH, US export-wise. However, I've never been clear on what boat OpenSSH is actually in. Mike "Silby" Silbersack To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: FYI: RSA Donated to the public domain
Mike Silbersack wrote: On Wed, 6 Sep 2000, Jeroen C. van Gelderen wrote: [1] The press release talk about RSADSI "waiving its rights to enforce the RSA patent for any development activities" This is very cunning as the patent never actually covered development. Instead it covers usage and sales of products incorporating RSA, both of which are not explicitly allowed for in the press release. Better be careful, better get written approval! All of the pages they've put up on their website seems to disagree with what you've just said. I just pointed out that the press release (from which I quoted) doesn't state that use/selling of RSA is allowed now. It seems that the FAQ allows for use and sale. Which document prevails is up in lawyer land... I think you're confusing use of RSA and use of RSAREF/BSAFE, Nope, the press release explicitly (see quote above) talks about the patent (which covers the algorithm, not RSAREF) and I was pointing out just that. which they're still maintaining control over (as Warner said.) Which is not an issue as we don't need RSAREF, not even an international version of RSAREF :-) Somehow I rather doubt they're trying to trick people into using RSA for the next week, and then going on a mass lawsuit spree. You may very well be right but in case you are not, it would be rather nasty if we got harassed, right? RSADSI has not been nice about their IP in the past couple of years and I have no reason to believe they will be now. Cheers, Jeroen -- Jeroen C. van Gelderen o _ _ _ [EMAIL PROTECTED] _o /\_ _ \\o (_)\__/o (_) _ \_ _(_) (_)/_\_| \ _|/' \/ (_)(_) (_)(_) (_)(_)' _\o_ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Need quick help.
In local.freebsd-hackers Doug White wrote: On Tue, 5 Sep 2000, petro wrote: I tried to change smth in my interfaces and now receive such message in /var/log/messages /kernel: arp: IP_number is on rl2 but got reply from MAC_ADDRESS an ed1 Your networks are broken. It appears the two interfaces are plugged into the same physical network. These messages can also occur if one of the interfaces is connected to a "hostile network", such as via a cable-tv modem. How hostile depends on the relative cluelessness of the cable-tv operator/ISP (this particular one [Chello in Stockholm] can be considered "pretty damn clueless"). $.02, /Mikko -- Mikko Työläjä[EMAIL PROTECTED] RSA Security To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: FYI: RSA Donated to the public domain
From the rsa website (the quiz, hey- who can resist a free T-Shirt) there is the following tidbit... With the patent expiration, software developers are now free to develop their own implementation of the RSA algorithm from scratch. However, RSA BSAFE and RSAREF code is still proprietary and subject to licensing. But since there are already other (better?) coded implementations of RSA's algorithms, if those are used we all should be golden. Correct? -=Jim=- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Duplicating packets
Hi! I am doing some testing on FreeBSD 3.3 platform by sending some UDP packets thru FreeBSD routers. It's found that FreeBSD duplicates some packet. That results in that the received packet are more than sent ones. How can I disable the duplication in FreeBSD config. Or did I do some wrong in the FreeBSD config. The FreeBSD 3.3 is running on Pentium III, and NIC is 3C905B-Tx. Could you please inform us about details regarding this problem? Which routing software are you using? natd? routed? Interface Characteristics (output of ifconfig of the interfaces)? netstat -r Best Regards, Freddy -- www.freddym.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: Duplicating packets
Title: RE: Duplicating packets Since the router we are testing is a standalone box, we are not using any routing protocols. The actual testbed is using Gated. Here is the info from the router. Thanks in advance. # ifconfig -au xl0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet 200.1.16.10 netmask 0xf000 broadcast 200.1.31.255 ether 00:50:04:0d:bf:46 media: 10baseT/UTP half-duplex supported media: autoselect 100baseTX full-duplex 100baseTX half-duplex 100 baseTX 10baseT/UTP full-duplex 10baseT/UTP half-duplex 10baseT/UTP xl1: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet 200.2.16.10 netmask 0xf000 broadcast 200.2.31.255 ether 00:50:04:0d:bc:82 media: 10baseT/UTP half-duplex supported media: autoselect 100baseTX full-duplex 100baseTX half-duplex 100 baseTX 10baseT/UTP full-duplex 10baseT/UTP half-duplex 10baseT/UTP xl2: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet 200.3.16.10 netmask 0xf000 broadcast 200.3.31.255 ether 00:b0:d0:2a:79:b2 media: 10baseT/UTP half-duplex supported media: autoselect 100baseTX full-duplex 100baseTX half-duplex 100 baseTX 10baseT/UTP full-duplex 10baseT/UTP half-duplex 10baseT/UTP xl3: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet 200.4.16.10 netmask 0xf000 broadcast 200.4.31.255 ether 00:50:04:71:5a:76 media: 10baseT/UTP half-duplex supported media: autoselect 100baseTX full-duplex 100baseTX half-duplex 100 baseTX 10baseT/UTP full-duplex 10baseT/UTP half-duplex 10baseT/UTP rl0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet 200.5.16.10 netmask 0xf000 broadcast 200.5.31.255 ether 00:48:54:87:9f:de media: autoselect supported media: autoselect 100baseTX full-duplex 100baseTX half-duplex 100 baseTX 10baseT/UTP full-duplex 10baseT/UTP 10baseT/UTP half-duplex rl1: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet 200.6.16.10 netmask 0xf000 broadcast 200.6.31.255 ether 00:48:54:87:e0:3f media: autoselect supported media: autoselect 100baseTX full-duplex 100baseTX half-duplex 100 baseTX 10baseT/UTP full-duplex 10baseT/UTP 10baseT/UTP half-duplex # # netstat -r Routing tables Internet: Destination Gateway Flags Refs Use Netif Expire 200.1.16/20 link#1 UC 0 0 xl0 200.1.16.10 0:50:4:d:bf:46 UHLW 0 432 lo0 200.1.16.100 0:de:bb:1:0:0 UHLW 0 0 xl0 1167 200.2.16/20 link#2 UC 0 0 xl1 200.2.16.100 0:de:bb:1:1:0 UHLW 0 142164 xl1 1167 200.3.16/20 link#3 UC 0 0 xl2 200.3.16.100 0:de:bb:1:2:0 UHLW 0 0 xl2 1167 200.4.16/20 link#4 UC 0 0 xl3 200.4.16.100 0:de:bb:1:3:0 UHLW 0 0 xl3 1167 200.5.16/20 link#5 UC 0 0 rl0 200.5.16.100 0:de:bb:1:10:0 UHLW 0 142243 rl0 1167 200.6.16/20 link#6 UC 0 0 rl1 200.6.16.100 0:de:bb:1:11:0 UHLW 1 9048110 rl1 1167 # --Hao -Original Message- From: Frederik Meerwaldt [mailto:[EMAIL PROTECTED]] Sent: Wednesday, September 06, 2000 2:16 PM To: Zhang, Hao [WDLN2:AN22:EXCH] Cc: freebsd-hackers Subject: Re: Duplicating packets Hi! I am doing some testing on FreeBSD 3.3 platform by sending some UDP packets thru FreeBSD routers. It's found that FreeBSD duplicates some packet. That results in that the received packet are more than sent ones. How can I disable the duplication in FreeBSD config. Or did I do some wrong in the FreeBSD config. The FreeBSD 3.3 is running on Pentium III, and NIC is 3C905B-Tx. Could you please inform us about details regarding this problem? Which routing software are you using? natd? routed? Interface Characteristics (output of ifconfig of the interfaces)? netstat -r Best Regards, Freddy -- www.freddym.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: FYI: RSA Donated to the public domain
On Wed, 6 Sep 2000, Warner Losh wrote: In message [EMAIL PROTECTED] Warner Losh writes: : RSA Security Releases RSA Encryption Algorithm into Public Domain Note that other information at the site says that RSAREF isn't released into the public domain. Its use is still governed by copyright law, so we'll have to use the international version of RSAREF if we want to get RSA into -current. There's no reason why we would want to continue to use RSAREF, except perhaps for source code compatability with something that was written to link against it. The OpenSSL implementation is much better, and basically we just have to build it by default now. I'm not sure whether it's okay to build a shim for OpenSSL which translates the RSAREF API into the native one (the reverse of the OpenSSL - RSAREF code which currently exists), but it would be mildly useful for those legacy apps. Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Promiscuous mode
rl0: promiscuous mode enabled rl0: promiscuous mode disabled What does it mean and how I can set this Thank you very much. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: Promiscuous mode
It means something set your Ethernet interface "rl0" to promiscuous mode, which allows it to receive all Ethernet frames on the wire it's attached to instead of just its own. Common applications that do this are tcpdump, trafshow and ntop. If you've used one of these they will by default try and analyze -all- traffic they can get hold of, instead of just that destined for one of your machines. It is logged because it is a potential security issue. If you have not used any tools like the above, you could have a password sniffer or something like that installed without your knowledge. Jason Young Access US(tm) Chief Network Engineer -Original Message- From: petro [mailto:[EMAIL PROTECTED]] Sent: Wednesday, September 06, 2000 4:33 PM To: [EMAIL PROTECTED] Subject: Promiscuous mode rl0: promiscuous mode enabled rl0: promiscuous mode disabled What does it mean and how I can set this Thank you very much. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Problem!!
* petro [EMAIL PROTECTED] [000906 14:19] wrote: Hi! I have the following problem my local network (192.168.x.x) is connected to server, and use squid on the next server to run Explorer, Nescape. I can run Inetner Explorer and Netscape but when I try to run ping any.hos I receive only it's number arequested timed out . My ipfw is working good, also named works good(I receive IP address of machines) but I can't understand where is problem Thank you very much Unless you're using NAT then your packets are going out onto the internet as 192.168.x.x and the internet has no clue how to get these packets back to you. Solution, install NATd. -- -Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: FYI: RSA Donated to the public domain
Somehow I rather doubt they're trying to trick people into using RSA for the next week, and then going on a mass lawsuit spree. No idea about RSA motives, but "Submarice patents" are a well known strategem. AFAIR owners of compress.c registered it, then published it, only years later tried to extract money for it ( Jean Luc Gailly wrote the more efficient gzip, under GPL, we all abandoned compress :-) Julian - Julian Stacey http://bim.bsn.com/~jhs/ Munich Unix Consultant. Free BSD Unix with 3600 packages sources. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
dc driver issues
With freebsd 4.1, I have 2 "problems" with the dc driver. Im using a 4 port DLINK card in this test: 1) It always give me a "device timeout" on first startup. It seems to work ok though. The de driver (oppositely) gives me an "enabled" on the connected ports on startup. 2). It numbers the ports in the opposite order expected. Bottom to top. Is there a simple patch to correct this...or is this a system or MB issue? the MB is an Intel ATX, pretty standard stuff. any ideas? Dennis To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
What's the best PCMCIA Ethernet card?
Preferably 10/100. This old Megahertz CC10BT doesn't seem to be terribly quick. Stephen -- The views expressed above are not those of PGS Tensor. "We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true."Robert Wilensky, University of California To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
