ftp dir fails with ipfw fwd
I get this when I try to ftp dir: Can't create data socket (n.n.n.n,20) : Can't assign requested address. I'm using ipfw fwd. Do I need a rule? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: SMP + fxp0 wierdness
According to Doug: > Heh... well I've already enabled flags 0xb0ff, which has improved things Speaking of flags for ATA disks, I'm using 0xa0ff for my laptop drive and wonders if there a better setting...? found-> vendor=0x8086, dev=0x7111, revid=0x01 class=01-01-80, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 map[0]: type 4, range 32, base fcb0, size 4 ide_pci0: rev 0x01 on pci0.7.1 intel_piix_status: primary master/slave sample = 3, master/slave recovery = 1 intel_piix_status: primary master fastDMAonly disabled, pre/post enabled, intel_piix_status: IORDY sampling enabled, intel_piix_status: fast PIO enabled intel_piix_status: primary master/slave sample = 3, master/slave recovery = 1 intel_piix_status: primary slave fastDMAonly disabled, pre/post disabled, intel_piix_status: IORDY sampling disabled, intel_piix_status: fast PIO disabled ide_pci: busmaster 0 status: 24 from port: fcb2 ide_pci: ide0:0 has been configured for DMA by BIOS intel_piix_status: secondary master/slave sample = 5, master/slave recovery = 4 intel_piix_status: secondary master fastDMAonly disabled, pre/post disabled, intel_piix_status: IORDY sampling disabled, intel_piix_status: fast PIO disabled intel_piix_status: secondary master/slave sample = 5, master/slave recovery = 4 intel_piix_status: secondary slave fastDMAonly disabled, pre/post disabled, intel_piix_status: IORDY sampling disabled, intel_piix_status: fast PIO disabled ide_pci: busmaster 1 status: 04 from port: fcba ... wdc0 at 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa wdc0: unit 0 (wd0): , DMA, 32-bit, multi-block-16 wd0: 6194MB (12685680 sectors), 13424 cyls, 15 heads, 63 S/T, 512 B/S wd0: ATA INQUIRE valid = 0007, dmamword = 0007, apio = 0003, udma = 0407 -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- [EMAIL PROTECTED] FreeBSD keltia.freenix.fr 4.0-CURRENT #74: Thu Sep 9 00:20:51 CEST 1999 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: module names
This kind of stuff is better suited to the arch mailing list..cross-posting. Kris On Tue, 26 Oct 1999, Pascal Hofstee wrote: > Hi, > > With the recent addition of more and more KLDs to the /modules directory i > was wondering if perhaps it would be a good idea to name these modules > more consistantly: > > if_*: For all network modules (done already) > ng_*: For all netgraph related modules (done already) > fs_*: For all filesystem modules > saver_* : For all screensavers (probably would prefer a shorter prefix) > emu_* : For binary compatibilty modules like linux/ibcs2/svr4 > > of course this is just a suggestion ... just thought i would voice it > here. > > > Pascal Hofstee - [EMAIL PROTECTED] > > -BEGIN GEEK CODE BLOCK- > Version: 3.1 > GCS d- s+: a-- C++ UB P+ L- E--- W- N+ o? K- w--- O? M V? PS+ PE Y-- PGP-- > t+ 5 X-- R tv+ b+ DI D- G e* h+ r- y+ > --END GEEK CODE BLOCK-- > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message > XOR for AES -- join the campaign! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: module names
On Mon, 25 Oct 1999, Chris Costello wrote: >I agree with the idea but some of the name ideas are a little > off. What would Vinum go under? > >I also disagree with your usage of ``emu_''. I would prefer > ``compat_''. I agree the names were not choosen perfectly ... I agree on compat_ the suggestions i provided were just to illustrate the idea ... in the hopes to get some discussion and attention on the whole idea. Pascal Hofstee - [EMAIL PROTECTED] -BEGIN GEEK CODE BLOCK- Version: 3.1 GCS d- s+: a-- C++ UB P+ L- E--- W- N+ o? K- w--- O? M V? PS+ PE Y-- PGP-- t+ 5 X-- R tv+ b+ DI D- G e* h+ r- y+ --END GEEK CODE BLOCK-- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: vaio z505sx and fxp suspend/resume problem
According to Guido van Rooij: > When I suspend and later resume a VAIO z505sx, the fxp interface seems > not to be able to send out packets. Receiving goes okay (as tcpdump -n > will actually dump all packets on the wire). I've seen that when this happen (it doesn't happen every resume), running "tcpdump" seems to wake the interface up. Nice to see you've installed your VAIO now :-) Mine made a buildworld for 3.3-RELEASE in 3422s... Way faster than my K6/200 (around 2 hours) and my dual PPro/200 (4915 s). 3422.40 real 2227.82 user 460.99 sys This laptop is now my fastest machine, wow! :-) -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- [EMAIL PROTECTED] FreeBSD keltia.freenix.fr 4.0-CURRENT #74: Thu Sep 9 00:20:51 CEST 1999 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: module names
On Tue, Oct 26, 1999, Pascal Hofstee wrote: > Hi, > > With the recent addition of more and more KLDs to the /modules directory i > was wondering if perhaps it would be a good idea to name these modules > more consistantly: > > if_*: For all network modules (done already) > ng_*: For all netgraph related modules (done already) > fs_*: For all filesystem modules > saver_* : For all screensavers (probably would prefer a shorter prefix) > emu_* : For binary compatibilty modules like linux/ibcs2/svr4 I agree with the idea but some of the name ideas are a little off. What would Vinum go under? I also disagree with your usage of ``emu_''. I would prefer ``compat_''. -- |Chris Costello <[EMAIL PROTECTED]> |If at first you don't succeed, you must be a programmer. ` To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
module names
Hi, With the recent addition of more and more KLDs to the /modules directory i was wondering if perhaps it would be a good idea to name these modules more consistantly: if_*: For all network modules (done already) ng_*: For all netgraph related modules (done already) fs_*: For all filesystem modules saver_* : For all screensavers (probably would prefer a shorter prefix) emu_* : For binary compatibilty modules like linux/ibcs2/svr4 of course this is just a suggestion ... just thought i would voice it here. Pascal Hofstee - [EMAIL PROTECTED] -BEGIN GEEK CODE BLOCK- Version: 3.1 GCS d- s+: a-- C++ UB P+ L- E--- W- N+ o? K- w--- O? M V? PS+ PE Y-- PGP-- t+ 5 X-- R tv+ b+ DI D- G e* h+ r- y+ --END GEEK CODE BLOCK-- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: FreeBSDCon pictures
On Sun, Oct 24, 1999 at 03:59:00PM -0700, John Polstra wrote: > I put a few pictures from FreeBSDCon here for your enjoyment: > > http://www.freebsd.org/~jdp/freebsdcon1999/ Ugh! That's a horrible picture of me on there. Similarly, http://www.freebsd.org/~nik/freebsdcon-1999/pictures/ No captions yet though. Of those, http://www.freebsd.org/~nik/freebsdcon-1999/pictures/Tuesday/P118.JPG is really quite amusing. . . More pics to follow. N To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
vaio z505sx and fxp suspend/resume problem
When I suspend and later resume a VAIO z505sx, the fxp interface seems not to be able to send out packets. Receiving goes okay (as tcpdump -n will actually dump all packets on the wire). No errors are reporteed on the interface (kernel or netstat -ni). Ifconfig-ing the interface down and up again does not seem to make a difference. It seems after 1-2 minutes the interface is okay again. The interface was both tried with mdia selection to auto and to UTP (both worked in the same way) Have others seen the same and is thyere a known fix? -Guido To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: FreeBSD reboots
why do you have a lot of connections in 'fin-wait-2 state?
do you have windows clients? how many is 'a lot'
if you leave the console on and so NOT have X11 runjing you may see
mesages on the console.
(possibly install DDB so that it doesn't fully reboot, but stops in the
debugger)
I have a patch to fix the fin-wait-2 problem..
I have included it. (It was last tested in 3.2)
What it does is allow probing of the client so that the client will send
an RST if the session is really closed, and if no response for a while,
it will time out. You need to enable it in the config file too
julian
On Mon, 25 Oct 1999, Min Wei (Exchange) wrote:
> Hi. I have a situation where FreeBSD 3.2 reboots once a while (less than
> every
> 12 hours). My net environment is, FreeBSD 3.2 sits behind a Cisco
> LocalDirector.
> The FreeBSD machine is a Dell dual-proc with 512M RAM. I recompiled the
> kernel
> with SMP options and set MAXMEM to 512M (since by default FreeBSD thinks it
> only
> has 64M). I have apache installed as the Web server.
>
> However during our Web stress run, FreeBSD reboots periodically. I wonder
> if it's because a lot of TCP connections at FIN_WAIT_2 state, which causes
> the kernel crash. The load on the machine is not high (CPU is about 90% idle
> from
> top). I could only guess Cisco LD might not be configured properly which
> causes
> a lot of open connections.
>
> Anyone sees this kind of problem before? Any advice would be greatly
> appreciated.
>
> Thanks,
> --min
>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-net" in the body of the message
>
Index: netinet/tcp_input.c
===
RCS file: /home/ncvs/src/sys/netinet/tcp_input.c,v
retrieving revision 1.84
diff -c -r1.84 netinet/tcp_input.c
*** netinet/tcp_input.c 1999/02/06 00:47:45 1.84
--- netinet/tcp_input.c 1999/04/08 00:45:54
***
*** 88,93
--- 88,99
SYSCTL_INT(_net_inet_tcp, OID_AUTO, delayed_ack, CTLFLAG_RW,
&tcp_delack_enabled, 0, "");
+ #ifdefTCP_USOFT_BUG
+ int tcp_fin_retry_enable = 0;
+ SYSCTL_INT(_net_inet_tcp, OID_AUTO, fin_retry, CTLFLAG_RW,
+ &tcp_fin_retry_enable, 0, "");
+ #endif/* TCP_USOFT_BUG */
+
u_longtcp_now;
struct inpcbhead tcb;
struct inpcbinfo tcbinfo;
***
*** 1495,1504
--- 1501,1540
* specification, but if we don't get a FIN
* we'll hang forever.
*/
+ #ifdef TCP_USOFT_BUG
+ /*
+* Wait longer and longer for the other
+* end to respond with something.
+* Eventually they should either
+* RST or FIN. If they are still alive
+* and actually want us to remain in this
+* state, they will keep ACKing and
+* we'll stay here indefinitly.
+* If they don't respond at all, we will
+* revert to FIN_WAIT_1 and eventually
+* time out as it would. How to cope with
+* the case of broken clients who are still
+* alive but never FIN is arguable. Certainly
+* if we've closed our end entirely, we
+* might as well just close the connection.
+*/
+ if (tcp_fin_retry_enable) {
+ tp->t_timer[TCPT_2MSL] =
+ ((tp->t_idle > TCPTV_MSL) ?
+ tp->t_idle : TCPTV_MSL);
+ } else {
+ if (so->so_state & SS_CANTRCVMORE) {
+ soisdisconnected(so);
+ tp->t_timer[TCPT_2MSL]
+ = tcp_maxidle;
+ }
+ }
+ #else /* TCP_USOFT_BUG */
if (so->so_state & SS_CANTRCVMORE) {
soisdisconnected(so);
tp->t_timer[TCPT_2MSL] = tcp_maxidle;
}
+ #endif/* TCP_USOFT_BUG */
tp->t_state = TCPS_FIN_WAIT_2;
}
break;
Index: netinet/tcp_timer.c
===
RCS file: /home/ncvs/src/sys/netinet/tcp_timer.c,v
FreeBSD reboots
Hi. I have a situation where FreeBSD 3.2 reboots once a while (less than every 12 hours). My net environment is, FreeBSD 3.2 sits behind a Cisco LocalDirector. The FreeBSD machine is a Dell dual-proc with 512M RAM. I recompiled the kernel with SMP options and set MAXMEM to 512M (since by default FreeBSD thinks it only has 64M). I have apache installed as the Web server. However during our Web stress run, FreeBSD reboots periodically. I wonder if it's because a lot of TCP connections at FIN_WAIT_2 state, which causes the kernel crash. The load on the machine is not high (CPU is about 90% idle from top). I could only guess Cisco LD might not be configured properly which causes a lot of open connections. Anyone sees this kind of problem before? Any advice would be greatly appreciated. Thanks, --min To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: replacing grep (again) and regex speed ups
On 25 Oct 1999, Dag-Erling Smorgrav wrote: > James Howard <[EMAIL PROTECTED]> writes: > > I submitted a PR (bin/14342) which adds a lot of speed to mismatches in > > Henry Spencer's regex code. Who knows a lot about regex whom I can bug? > > Umm, how about Henry Spencer <[EMAIL PROTECTED]>? :) That does little to help FreeBSD's regex. I'll email him though, that seems like a pretty good idea. BTW, this is the Boyer-Moore code pulled from grep so now grep behaves itself. Jamie To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: replacing grep (again) and regex speed ups
James Howard <[EMAIL PROTECTED]> writes: > I submitted a PR (bin/14342) which adds a lot of speed to mismatches in > Henry Spencer's regex code. Who knows a lot about regex whom I can bug? Umm, how about Henry Spencer <[EMAIL PROTECTED]>? :) DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
