Re: Something wrong with TCP connections in recent -current

2010-04-27 Thread Alex Keda

27.04.2010 16:54, Alex Keda пишет:

27.04.2010 16:35, Andrey Chernov пишет:

See subj.
They appears to work for ~10 minutes then all hangs deadly. No one TCP
service responds, but ICMP and UDP goes normally.
The machine is x86 Pentium 4 IPv4-only, IPv6 is turned off in every 
place.

Last kernel I have that works nice compiled at Mar 19.

Ethernet info:
fxp0:  port 0xc000-0xc03f mem
0xed10-0xed100fff,0xed00-0xed0f irq 11 at device 11.0 on 
pci1

miibus0:  on fxp0
inphy0:  PHY 1 on miibus0
inphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto

This is remote machine, so I don't have console access.


I too have it bug
but, time > 2-3 hours.
lissyara$ ifconfig
bge0: flags=8943 
metric 0 mtu 1500

options=c0098
ether 00:1c:c4:98:77:a8
inet 172.17.4.127 netmask 0xff00 broadcast 172.17.4.255
media: Ethernet autoselect (100baseTX )
status: active
lo0: flags=8049 metric 0 mtu 16384
options=3
inet 127.0.0.1 netmask 0xff00
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2
nd6 options=21
tap0: flags=8902 metric 0 mtu 1500
options=8
ether 00:bd:3c:81:00:00
bridge0: flags=8843 metric 0 
mtu 1500

ether 42:16:df:e5:3c:68
id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
maxage 20 holdcnt 6 proto rstp maxaddr 100 timeout 1200
root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
member: tap0 flags=143
ifmaxaddr 0 port 3 priority 128 path cost 200
member: bge0 flags=143
ifmaxaddr 0 port 1 priority 128 path cost 55
gif0: flags=8051 metric 0 mtu 1280
tunnel inet 172.17.4.127 --> 172.29.200.25
inet 10.10.20.26 --> 10.10.10.16 netmask 0x
options=1
lissyara$

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to 
"freebsd-current-unsubscr...@freebsd.org"


forget. if I attempt local login to machine, I can type "root", Enter - 
and finish - cursor get to line down and nothing. (root without password)

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Re: Something wrong with TCP connections in recent -current

2010-04-27 Thread Alex Keda

27.04.2010 16:35, Andrey Chernov пишет:

See subj.
They appears to work for ~10 minutes then all hangs deadly. No one TCP
service responds, but ICMP and UDP goes normally.
The machine is x86 Pentium 4 IPv4-only, IPv6 is turned off in every place.
Last kernel I have that works nice compiled at Mar 19.

Ethernet info:
fxp0:  port 0xc000-0xc03f mem
0xed10-0xed100fff,0xed00-0xed0f irq 11 at device 11.0 on pci1
miibus0:  on fxp0
inphy0:  PHY 1 on miibus0
inphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto

This is remote machine, so I don't have console access.

   

I too have it bug
but, time > 2-3 hours.
lissyara$ ifconfig
bge0: flags=8943 metric 
0 mtu 1500

options=c0098
ether 00:1c:c4:98:77:a8
inet 172.17.4.127 netmask 0xff00 broadcast 172.17.4.255
media: Ethernet autoselect (100baseTX )
status: active
lo0: flags=8049 metric 0 mtu 16384
options=3
inet 127.0.0.1 netmask 0xff00
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2
nd6 options=21
tap0: flags=8902 metric 0 mtu 1500
options=8
ether 00:bd:3c:81:00:00
bridge0: flags=8843 metric 0 mtu 
1500

ether 42:16:df:e5:3c:68
id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
maxage 20 holdcnt 6 proto rstp maxaddr 100 timeout 1200
root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
member: tap0 flags=143
ifmaxaddr 0 port 3 priority 128 path cost 200
member: bge0 flags=143
ifmaxaddr 0 port 1 priority 128 path cost 55
gif0: flags=8051 metric 0 mtu 1280
tunnel inet 172.17.4.127 --> 172.29.200.25
inet 10.10.20.26 --> 10.10.10.16 netmask 0x
options=1
lissyara$

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"