LINUX.ORG.RU
ФорумAdmin

Перестает пинговаться интерфейс при обращении к Squid на нём...


0

0

Очень странная ситуация. Есть подсеть. У подсети есть маршрут по умолчаию - ip адрес 192.168.3.1. На интерфейсе поднят прозрачный прокси. Если люди работают на прямую без прокси, то всё хорошо. Если хотя бы один запрос отправляется из этой подсети на прокси, то 192.168.3.1 становится недоступным и не пингуется. Остальные адреса в подсети остаются доступными. Лечится всё просто - ifconfig eth0 down - ifocnfig eth0 up + юзеры перед этим пускаются в обход прокси.

Есть ещё одна подсеть с маршрутом по умолчаю 192.168.2.63. И в ней все ходят в инет через проксю, и проблем не наблюдается, даже когда проблемы есть в соседней подсети.

Маски подсети везде = 24 бита.

Но мне нужно, чтобы обе посдети ходили в инет через один прокси, а не только одна. Помогите пожалуйста! Конфиги фаерволла и сквида прилагаю.

Slackware 12.
2.6.21.5-smp
squid/2.6.STABLE22

RC.FIREWALL:

#!/bin/sh

IPTABLES="/usr/sbin/iptables"
$IPTABLES -F INPUT
$IPTABLES -F OUTPUT
$IPTABLES -F FORWARD
$IPTABLES -t nat -F

INET_IP="10.34.105.30"
INET_IFACE="eth2"
INET_SUBNET="10.34.105.28/30"
INET_BROADCAST="10.34.105.31"


# Specialnie adresnie prostarnstva i adresa //Valya

#SM
RABOCHIE_STANCII="192.168.2.1-192.168.2.30"
TONKIE_CLIENTI="192.168.2.31-192.168.2.100"
TERMINAL_SERVER="192.168.2.171"
ALL_SM_LAN="192.168.2.0/24"

#MD
MD_STANCII="192.168.3.0/24"


LAN_IP="192.168.2.63"
LAN_SUBNET="192.168.2.0/24"
LAN_IFACE_SMS="eth1"
LAN_IFACE_MD="eth0"

LO_IFACE="lo"
LO_IP="127.0.0.1"


IPTABLES="/usr/sbin/iptables"

/sbin/depmod -a

/sbin/modprobe ip_tables
/sbin/modprobe ip_conntrack
/sbin/modprobe iptable_filter
/sbin/modprobe iptable_mangle
/sbin/modprobe iptable_nat
/sbin/modprobe ipt_LOG
/sbin/modprobe ipt_limit
/sbin/modprobe ipt_state


echo "1" > /proc/sys/net/ipv4/ip_forward
#echo "1" > /proc/sys/net/ipv4/conf/all/rp_filter
#echo "1" > /proc/sys/net/ipv4/conf/all/proxy_arp
echo "1" > /proc/sys/net/ipv4/ip_dynaddr


$IPTABLES -P INPUT ACCEPT
$IPTABLES -P OUTPUT ACCEPT
$IPTABLES -P FORWARD ACCEPT


$INET_IFACE -j MASQUERADE

#Çàðåçàåì òðàôèê ñ òîíêèõ êëèåíòîâ â ñåòü èíòåðíåò íàïðÿìóþ
iptables -t filter -A FORWARD -m iprange --src-range $TONKIE_CLIENTI -d ! 192.168.2.63 -p all -j DROP


#########

iptables -t nat -A PREROUTING -m iprange --src-range $RABOCHIE_STANCII -d ! 192.168.2.63 -p tcp -m multiport --dport 80,81,82,83,88,8082,8083,8091,8100,8101,8102,8103,8080,8888,777 -j REDIRECT --to-port 3128
iptables -t nat -A PREROUTING -s $TERMINAL_SERVER -d ! 192.168.2.63 -p tcp -m multiport --dport 80,81,82,83,88,8082,8083,8091,8100,8101,8102,8103,8080,8888,777 -j REDIRECT --to-port 3128
#iptables -t nat -A PREROUTING -s $MD_STANCII -d ! 192.168.3.1 -p tcp -m multiport --dport 80,81,82,83,88,8082,8083,8091,8100,8101,8102,8103,8080,8888,777 -j REDIRECT --to-port 3128


#çàðåçàåì óòå÷êè brodcast-òðàôèêà èç âñåõ ëîêàëüíûõ ñåòåé
$IPTABLES -A INPUT -i $LAN_IFACE_SMS -s 255.255.255.255 -j DROP
$IPTABLES -A INPUT -i $LAN_IFACE_SMS -d 0.0.0.0 -j DROP

#$IPTABLES -A INPUT -i $LAN_IFACE_MD -s 255.255.255.255 -j DROP
#$IPTABLES -A INPUT -i $LAN_IFACE_MD -d 0.0.0.0 -j DROP


#######################################################

$IPTABLES -A FORWARD -p tcp --dport 25 -d ! 62.113.86.197 -j ULOG --ulog-nlgroup 1 --ulog-prefix "(b25-tcp): "
$IPTABLES -A FORWARD -p tcp --dport 25 -d ! 62.113.86.197 -j REJECT
$IPTABLES -A FORWARD -p udp --dport 25 -d ! 62.113.86.197 -j ULOG --ulog-nlgroup 1 --ulog-prefix "(b25-udp): "
$IPTABLES -A FORWARD -p udp --dport 25 -d ! 62.113.86.197 -j REJECT

$IPTABLES -A FORWARD -d 81.176.226.166 -j REJECT --reject-with icmp-host-prohibited
$IPTABLES -A FORWARD -d 87.242.91.47 -j REJECT --reject-with icmp-host-prohibited
$IPTABLES -A FORWARD -d 195.2.91.115 -j REJECT --reject-with icmp-host-prohibited
$IPTABLES -A FORWARD -d 195.2.91.116 -j REJECT --reject-with icmp-host-prohibited
$IPTABLES -A FORWARD -d 195.190.105.0/24 -j REJECT --reject-with icmp-host-prohibited

$IPTABLES -t nat -A POSTROUTING -o $INET_IFACE -j SNAT --to-source $INET_IP


SQUD.CONF :

##################################### ACL ######################################
#You can disable allowing only SM packets here, but I recommend to pass only them //V

acl manager proto cache_object
acl all src 0.0.0.0/0.0.0.0
acl root_host src 192.168.2.199
acl localhost src 127.0.0.1/255.255.255.255
acl bad_sites url_regex -i "/usr/local/squid/etc/bw.regex"
acl good_sites url_regex -i "/usr/local/squid/etc/gw.regex"

http_access allow manager localhost
http_access deny manager

acl sm src 192.168.2.0/24
acl md src 192.168.3.0/24

http_access deny bad_sites
http_access allow good_sites
http_access allow sm
http_access allow md
http_access deny all

acl to_localhost dst 127.0.0.0/8
acl SSL_ports port 443 9443 9080 563 15100 11001 11002
acl Safe_ports port 80 # http
acl Safe_ports port 21 # ftp
acl Safe_ports port 443 9443 9080 563 11001 11002 # https
acl Safe_ports port 70 # gopher
acl Safe_ports port 210 # wais
acl Safe_ports port 1025-65535 # unregistered ports
acl Safe_ports port 280 # http-mgmt
acl Safe_ports port 488 # gss-http
acl Safe_ports port 591 # filemaker
acl Safe_ports port 777 # multiling http
acl CONNECT method CONNECT

#acl sm proxy_auth REQUIRED
http_access deny all

############# CACHE #############
hierarchy_stoplist cgi-bin ?
acl QUERY urlpath_regex cgi-bin \?
cache deny QUERY
cache allow all

cache_mem 60 MB

####DNS


##################################

############# PATHS #################################
cache_dir ufs /usr/local/squid/var/cache 7000 16 256
access_log /usr/local/squid/var/logs/access.log squid
####################################################

acl apache rep_header Server ^Apache
broken_vary_encoding allow apache

cache_effective_user squid
cache_effective_group squid
log_access allow all

tcp_outgoing_address 10.34.105.30 sm
tcp_outgoing_address 10.34.105.30 md
http_port 3128 transparent

visible_hostname squid


Re: Перестает пинговаться интерфейс при обращении к Squid на нём...

в логах что есть? (dmesg, /var/log/messages, /var/log/syslog)

samson ★★ ()

Re: Перестает пинговаться интерфейс при обращении к Squid на нём...

покажите таблицу маршрутизации до и после "192.168.3.1 становится недоступным и не пингуется."

Так мне не понятно назначение правил:
$IPTABLES -A INPUT -i $LAN_IFACE_SMS -s 255.255.255.255 -j DROP
$IPTABLES -A INPUT -i $LAN_IFACE_SMS -d 0.0.0.0 -j DROP

И не понятно зачем нужно:
echo "1" > /proc/sys/net/ipv4/ip_dynaddr

mky ★★★★★ ()

Re: Перестает пинговаться интерфейс при обращении к Squid на нём...

Вот вся диагностика, которую вы спрпашивали, простите, что припозднился. Не нужные правила, смысл которых непонятен, убрал, не помогло. вывод dmesg в следующем сообщении (не влезает)

до

root:/etc# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
10.34.105.28    0.0.0.0         255.255.255.252 U     0      0        0 eth2
192.168.3.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0
192.168.2.0     0.0.0.0         255.255.255.0   U     0      0        0 eth1
127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0 lo
0.0.0.0         10.34.105.29    0.0.0.0         UG    1      0        0 eth2

после

root:/etc/rc.d# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
10.34.105.28    0.0.0.0         255.255.255.252 U     0      0        0 eth2
192.168.3.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0
192.168.2.0     0.0.0.0         255.255.255.0   U     0      0        0 eth1
127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0 lo
0.0.0.0         10.34.105.29    0.0.0.0         UG    1      0        0 eth2

tail /var/log/syslog
Feb 25 08:17:25 mainrouter smbd[4915]: [2009/02/25 08:17:25, 0] smbd/service.c:make_connection(1191)
Feb 25 08:17:25 mainrouter smbd[4915]:   lom (192.168.2.18) couldn't find service netlogo
Feb 25 08:21:42 mainrouter smbd[4915]: [2009/02/25 08:21:42, 0] smbd/service.c:make_connection(1191)
Feb 25 08:21:42 mainrouter smbd[4915]:   lom (192.168.2.18) couldn't find service netlogo
Feb 25 08:21:42 mainrouter smbd[4915]: [2009/02/25 08:21:42, 0] smbd/service.c:make_connection(1191)
Feb 25 08:21:42 mainrouter smbd[4915]:   lom (192.168.2.18) couldn't find service netlogo
Feb 25 08:21:45 mainrouter smbd[4915]: [2009/02/25 08:21:45, 0] smbd/service.c:make_connection(1191)
Feb 25 08:21:45 mainrouter smbd[4915]:   lom (192.168.2.18) couldn't find service netlogo
Feb 25 08:21:45 mainrouter smbd[4915]: [2009/02/25 08:21:45, 0] smbd/service.c:make_connection(1191)
Feb 25 08:21:45 mainrouter smbd[4915]:   lom (192.168.2.18) couldn't find service netlogo


tail /var/log/messages
Feb 25 08:01:16 mainrouter -- MARK --
Feb 25 08:07:13 mainrouter dhcpd: DHCPINFORM from 192.168.2.15 via eth1
Feb 25 08:07:13 mainrouter dhcpd: DHCPACK to 192.168.2.15 (00:c0:ca:17:69:54) via eth1
Feb 25 08:07:18 mainrouter dhcpd: DHCPINFORM from 192.168.2.15 via eth1
Feb 25 08:07:18 mainrouter dhcpd: DHCPACK to 192.168.2.15 (00:c0:ca:17:69:54) via eth1
Feb 25 08:16:01 mainrouter dhcpd: Wrote 0 deleted host decls to leases file.
Feb 25 08:16:01 mainrouter dhcpd: Wrote 0 new dynamic host decls to leases file.
Feb 25 08:16:01 mainrouter dhcpd: Wrote 71 leases to leases file.
Feb 25 08:16:01 mainrouter dhcpd: DHCPREQUEST for 192.168.3.97 from 00:15:af:c7:61:7c (valentin) via eth0
Feb 25 08:16:01 mainrouter dhcpd: DHCPACK on 192.168.3.97 to 00:15:af:c7:61:7c (valentin) via eth0

root@mainrouter:/etc/rc.d# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:1E:8C:E0:DC:9D
          inet addr:192.168.3.1  Bcast:192.168.3.255  Mask:255.255.255.0
          inet6 addr: fe80::21e:8cff:fee0:dc9d/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:10417950 errors:5 dropped:0 overruns:0 frame:5
          TX packets:10211711 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:2985638657 (2.7 GiB)  TX bytes:1950298493 (1.8 GiB)
          Interrupt:17

eth1      Link encap:Ethernet  HWaddr 00:1C:F0:0E:80:3C
          inet addr:192.168.2.63  Bcast:192.168.2.255  Mask:255.255.255.0
          inet6 addr: fe80::21c:f0ff:fe0e:803c/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:20410562 errors:0 dropped:0 overruns:0 frame:0
          TX packets:23001420 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1559984244 (1.4 GiB)  TX bytes:1261640972 (1.1 GiB)
          Interrupt:16 Base address:0x2c00

eth2      Link encap:Ethernet  HWaddr 00:19:5B:70:4B:F2
          inet addr:10.34.105.30  Bcast:10.34.105.31  Mask:255.255.255.252
          inet6 addr: fe80::219:5bff:fe70:4bf2/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:22929628 errors:0 dropped:0 overruns:0 frame:0
          TX packets:19388848 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:744454375 (709.9 MiB)  TX bytes:3342085690 (3.1 GiB)
          Interrupt:17 Base address:0x4800

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:130823 errors:0 dropped:0 overruns:0 frame:0
          TX packets:130823 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:12092307 (11.5 MiB)  TX bytes:12092307 (11.5 MiB)

mora ()

Re: Перестает пинговаться интерфейс при обращении к Squid на нём...

кусок последних строк dmesg 

sky2 eth0: tx timeout
sky2 eth0: transmit ring 429 .. 406 report=429 done=429
sky2 eth0: disabling interface
sky2 eth0: enabling interface
sky2 eth0: ram buffer 0K
sky2 eth0: Link is up at 100 Mbps, full duplex, flow control both
NETDEV WATCHDOG: eth0: transmit timed out
sky2 eth0: tx timeout
sky2 eth0: transmit ring 255 .. 232 report=255 done=255
sky2 eth0: disabling interface
sky2 eth0: enabling interface
sky2 eth0: ram buffer 0K
sky2 eth0: Link is up at 100 Mbps, full duplex, flow control both
NETDEV WATCHDOG: eth0: transmit timed out
sky2 eth0: tx timeout
sky2 eth0: transmit ring 116 .. 93 report=116 done=116
sky2 eth0: disabling interface
sky2 eth0: enabling interface
sky2 eth0: ram buffer 0K
sky2 eth0: Link is up at 100 Mbps, full duplex, flow control both
sky2 eth0: disabling interface
sky2 eth0: enabling interface
sky2 eth0: ram buffer 0K
ADDRCONF(NETDEV_UP): eth0: link is not ready
eth1: link up, 100Mbps, full-duplex, lpa 0x45E1
eth2: link up, 100Mbps, full-duplex, lpa 0x41E1
sky2 eth0: Link is up at 100 Mbps, full duplex, flow control both
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
eth1: no IPv6 routers present
eth2: no IPv6 routers present
eth0: no IPv6 routers present
NETDEV WATCHDOG: eth0: transmit timed out
sky2 eth0: tx timeout
sky2 eth0: transmit ring 72 .. 49 report=72 done=72
sky2 eth0: disabling interface
sky2 eth0: enabling interface
sky2 eth0: ram buffer 0K
sky2 eth0: Link is up at 100 Mbps, full duplex, flow control both
NETDEV WATCHDOG: eth0: transmit timed out
sky2 eth0: tx timeout
sky2 eth0: transmit ring 43 .. 20 report=43 done=43
sky2 eth0: disabling interface
sky2 eth0: enabling interface
sky2 eth0: ram buffer 0K
sky2 eth0: Link is up at 100 Mbps, full duplex, flow control both
NETDEV WATCHDOG: eth0: transmit timed out
sky2 eth0: tx timeout
sky2 eth0: transmit ring 223 .. 200 report=223 done=223
sky2 eth0: disabling interface
sky2 eth0: enabling interface
sky2 eth0: ram buffer 0K
sky2 eth0: Link is up at 100 Mbps, full duplex, flow control both
sky2 eth0: disabling interface
sky2 eth0: enabling interface
sky2 eth0: ram buffer 0K
ADDRCONF(NETDEV_UP): eth0: link is not ready
sky2 eth0: Link is up at 100 Mbps, full duplex, flow control both
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
eth0: no IPv6 routers present
sky2 eth0: disabling interface
sky2 eth0: enabling interface
sky2 eth0: ram buffer 0K
ADDRCONF(NETDEV_UP): eth0: link is not ready
eth1: link up, 100Mbps, full-duplex, lpa 0x45E1
eth2: link up, 100Mbps, full-duplex, lpa 0x41E1
sky2 eth0: Link is up at 100 Mbps, full duplex, flow control both
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
eth2: no IPv6 routers present
eth1: no IPv6 routers present
eth0: no IPv6 routers present
NETDEV WATCHDOG: eth0: transmit timed out
sky2 eth0: tx timeout
sky2 eth0: transmit ring 411 .. 388 report=411 done=411
sky2 eth0: disabling interface
sky2 eth0: enabling interface
sky2 eth0: ram buffer 0K
sky2 eth0: Link is up at 100 Mbps, full duplex, flow control both
NETDEV WATCHDOG: eth0: transmit timed out
sky2 eth0: tx timeout
sky2 eth0: transmit ring 110 .. 87 report=110 done=110
sky2 eth0: disabling interface
sky2 eth0: enabling interface
sky2 eth0: ram buffer 0K
sky2 eth0: Link is up at 100 Mbps, full duplex, flow control both
NETDEV WATCHDOG: eth0: transmit timed out
sky2 eth0: tx timeout
sky2 eth0: transmit ring 326 .. 303 report=326 done=326
sky2 eth0: disabling interface
sky2 eth0: enabling interface
sky2 eth0: ram buffer 0K
sky2 eth0: Link is up at 100 Mbps, full duplex, flow control both
NETDEV WATCHDOG: eth0: transmit timed out
sky2 eth0: tx timeout
sky2 eth0: transmit ring 273 .. 250 report=273 done=273
sky2 eth0: disabling interface
sky2 eth0: enabling interface
sky2 eth0: ram buffer 0K
sky2 eth0: Link is up at 100 Mbps, full duplex, flow control both
sky2 eth0: Link is down.
sky2 eth0: Link is up at 100 Mbps, full duplex, flow control both
NETDEV WATCHDOG: eth0: transmit timed out
sky2 eth0: tx timeout
sky2 eth0: transmit ring 77 .. 54 report=77 done=77
sky2 eth0: disabling interface
sky2 eth0: enabling interface
sky2 eth0: ram buffer 0K
sky2 eth0: Link is up at 100 Mbps, full duplex, flow control both
NETDEV WATCHDOG: eth0: transmit timed out
sky2 eth0: tx timeout
sky2 eth0: transmit ring 3 .. 492 report=3 done=3
sky2 eth0: disabling interface
sky2 eth0: enabling interface
sky2 eth0: ram buffer 0K
sky2 eth0: Link is up at 100 Mbps, full duplex, flow control both
sky2 eth0: Link is down.
sky2 eth0: Link is up at 100 Mbps, full duplex, flow control both
NETDEV WATCHDOG: eth0: transmit timed out
sky2 eth0: tx timeout
sky2 eth0: transmit ring 349 .. 326 report=349 done=349
sky2 eth0: disabling interface
sky2 eth0: enabling interface
sky2 eth0: ram buffer 0K
sky2 eth0: Link is up at 100 Mbps, full duplex, flow control both
NETDEV WATCHDOG: eth0: transmit timed out
sky2 eth0: tx timeout
sky2 eth0: transmit ring 339 .. 316 report=339 done=339
sky2 eth0: disabling interface
sky2 eth0: enabling interface
sky2 eth0: ram buffer 0K
sky2 eth0: Link is up at 100 Mbps, full duplex, flow control both
NETDEV WATCHDOG: eth0: transmit timed out
sky2 eth0: tx timeout
sky2 eth0: transmit ring 309 .. 286 report=309 done=309
sky2 eth0: disabling interface
sky2 eth0: enabling interface
sky2 eth0: ram buffer 0K
sky2 eth0: Link is up at 100 Mbps, full duplex, flow control both
NETDEV WATCHDOG: eth0: transmit timed out
sky2 eth0: tx timeout
sky2 eth0: transmit ring 148 .. 125 report=148 done=148
sky2 eth0: disabling interface
sky2 eth0: enabling interface
sky2 eth0: ram buffer 0K
sky2 eth0: Link is up at 100 Mbps, full duplex, flow control both
sky2 eth0: Link is down.
sky2 eth0: Link is up at 100 Mbps, full duplex, flow control both
sky2 eth0: Link is down.
sky2 eth0: Link is up at 100 Mbps, full duplex, flow control both
NETDEV WATCHDOG: eth0: transmit timed out
sky2 eth0: tx timeout
sky2 eth0: transmit ring 143 .. 120 report=143 done=143
sky2 eth0: disabling interface
sky2 eth0: enabling interface
sky2 eth0: ram buffer 0K
sky2 eth0: Link is up at 100 Mbps, full duplex, flow control both
sky2 eth0: Link is down.
sky2 eth0: Link is up at 100 Mbps, full duplex, flow control both
sky2 eth0: disabling interface
sky2 eth0: enabling interface
sky2 eth0: ram buffer 0K
ADDRCONF(NETDEV_UP): eth0: link is not ready
sky2 eth0: Link is up at 100 Mbps, full duplex, flow control both
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
eth0: no IPv6 routers present
sky2 eth0: disabling interface
sky2 eth0: enabling interface
sky2 eth0: ram buffer 0K
ADDRCONF(NETDEV_UP): eth0: link is not ready
sky2 eth0: Link is up at 100 Mbps, full duplex, flow control both
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
eth0: no IPv6 routers present
sky2 eth0: Link is down.
sky2 eth0: Link is up at 100 Mbps, full duplex, flow control both
sky2 eth0: Link is down.
sky2 eth0: Link is up at 100 Mbps, full duplex, flow control both
sky2 eth0: disabling interface
sky2 eth0: enabling interface
sky2 eth0: ram buffer 0K
ADDRCONF(NETDEV_UP): eth0: link is not ready

mora ()

Re: Перестает пинговаться интерфейс при обращении к Squid на нём...

продолжение dmesg

sky2 eth0: Link is up at 100 Mbps, full duplex, flow control both
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
eth0: no IPv6 routers present
NETDEV WATCHDOG: eth0: transmit timed out
sky2 eth0: tx timeout
sky2 eth0: transmit ring 163 .. 140 report=163 done=163
sky2 eth0: disabling interface
sky2 eth0: enabling interface
sky2 eth0: ram buffer 0K
sky2 eth0: Link is up at 100 Mbps, full duplex, flow control both
sky2 eth0: disabling interface
sky2 eth0: enabling interface
sky2 eth0: ram buffer 0K
ADDRCONF(NETDEV_UP): eth0: link is not ready
sky2 eth0: Link is up at 100 Mbps, full duplex, flow control both
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
eth0: no IPv6 routers present
sky2 eth0: disabling interface
sky2 eth0: enabling interface
sky2 eth0: ram buffer 0K
ADDRCONF(NETDEV_UP): eth0: link is not ready
sky2 eth0: Link is up at 100 Mbps, full duplex, flow control both
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
eth0: no IPv6 routers present
sky2 eth0: disabling interface
sky2 eth0: enabling interface
sky2 eth0: ram buffer 0K
ADDRCONF(NETDEV_UP): eth0: link is not ready
sky2 eth0: Link is up at 100 Mbps, full duplex, flow control both
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
eth0: no IPv6 routers present
NETDEV WATCHDOG: eth0: transmit timed out
sky2 eth0: tx timeout
sky2 eth0: transmit ring 254 .. 231 report=254 done=254
sky2 eth0: disabling interface
sky2 eth0: enabling interface
sky2 eth0: ram buffer 0K
sky2 eth0: Link is up at 100 Mbps, full duplex, flow control both
sky2 eth0: disabling interface
sky2 eth0: enabling interface
sky2 eth0: ram buffer 0K
ADDRCONF(NETDEV_UP): eth0: link is not ready
sky2 eth0: Link is up at 100 Mbps, full duplex, flow control both
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
eth0: no IPv6 routers present
sky2 eth0: disabling interface
sky2 eth0: enabling interface
sky2 eth0: ram buffer 0K
ADDRCONF(NETDEV_UP): eth0: link is not ready
sky2 eth0: Link is up at 100 Mbps, full duplex, flow control both
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
eth0: no IPv6 routers present
sky2 eth0: rx error, status 0x5f20010 length 1518
sky2 eth0: rx error, status 0x5f20010 length 1518
sky2 eth0: rx error, status 0x5f20010 length 1518
sky2 eth0: rx error, status 0x5f20010 length 1518
sky2 eth0: disabling interface
sky2 eth0: enabling interface
sky2 eth0: ram buffer 0K
ADDRCONF(NETDEV_UP): eth0: link is not ready
sky2 eth0: Link is up at 100 Mbps, full duplex, flow control both
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
eth0: no IPv6 routers present
sky2 eth0: disabling interface
sky2 eth0: enabling interface
sky2 eth0: ram buffer 0K
ADDRCONF(NETDEV_UP): eth0: link is not ready
sky2 eth0: Link is up at 100 Mbps, full duplex, flow control both
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
eth0: no IPv6 routers present
sky2 eth0: disabling interface
sky2 eth0: enabling interface
sky2 eth0: ram buffer 0K
ADDRCONF(NETDEV_UP): eth0: link is not ready
sky2 eth0: Link is up at 100 Mbps, full duplex, flow control both
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
eth0: no IPv6 routers present
sky2 eth0: rx error, status 0x5f20010 length 1518

mora ()

Re: Перестает пинговаться интерфейс при обращении к Squid на нём...

TO edigaryev:

Совет хороший по поводу подсветки, но...

"GTFO" - давайте без оскорблений, то, что вас не видно по ту сторону провода, не означает, что можно безнаказанно материться.


mora ()

Re: Перестает пинговаться интерфейс при обращении к Squid на нём...

>Если хотя бы один запрос отправляется из этой подсети на прокси, то 192.168.3.1 становится недоступным и не пингуется.

192.168.3.1 -- если пропинговать хост до того как кто-либо пытается сделать коннект на порт прокси сервера? Ну или скажем, зайти по ssh?

Были ли раньше подобные проблемы?

edigaryev ★★★★★ ()

Re: Перестает пинговаться интерфейс при обращении к Squid на нём...

Если пропинговать до того, как кто-либо попытается соединиться с прокси - всё пингуется великолепно...

Была раньше эта проблема, думал, дело в acpi, сделал acpi=off в lilo.conf, вроде бы даже это помогло на время. Но теперь опять всё падает...

меня смущают watchdog - записи в dmesg... Может, стоит копать туда?

mora ()

Re: Перестает пинговаться интерфейс при обращении к Squid на нём...

Вот, нашел: http://www.ambience.sk/azureus-transmit-timed-out

Sometimes network connection on Linux goes down with short message in syslog saying: "[localhost kernel] NETDEV WATCHDOG: eth0: transmit timed out" (or similar).

Some network-heavy programs or the buggy driver/kernel handling of traffic could cause this error. Azureus (torrents downloading software), for example, is often guilty for this.

Solution is to offload the network card - run the following command in the console: ethtool -K сетевой_интерфейс tso off

edigaryev ★★★★★ ()
Вы не можете добавлять комментарии в эту тему. Тема перемещена в архив.