Hi Rik,
Q1. Thank you for your help. Here are the results. Is it normal to
have so many broadcasts received on Ethernet interface within 30 secs?
samsrt#sh int e0
Ethernet0 is up, line protocol is up
Hardware is PQUICC Ethernet, address is 0005.9a3c.f923 (bia
0005.9a3c.f923)
Internet address is 192.168.0.7/16
MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec,
reliability 255/255, txload 1/255, rxload 5/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full-duplex, 10BaseT
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:00, output 00:00:04, output hang never
Last clearing of "show interface" counters never
Queueing strategy: fifo
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
5 minute input rate 212000 bits/sec, 4 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
999903 packets input, 366262858 bytes, 0 no buffer
Received 815018 broadcasts, 0 runts, 2 giants, 0 throttles
19270 input errors, 19268 CRC, 0 frame, 0 overrun, 0 ignored
0 input packets with dribble condition detected
693690 packets output, 72720727 bytes, 0 underruns
0 output errors, 0 collisions, 2 interface resets
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier
0 output buffer failures, 0 output buffers swapped out
samsrt#sh int f0
FastEthernet0 is up, line protocol is up
Hardware is PQUICC_FEC, address is 0005.9a3c.f922 (bia
0005.9a3c.f922)
Internet address is 10.10.20.1/24
MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full-duplex, 100Mb/s, 100BaseTX/FX
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:04:00, output 00:00:06, output hang never
Last clearing of "show interface" counters never
Queueing strategy: fifo
Output queue 0/40, 0 drops; input queue 0/75, 1 drops
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
657149 packets input, 68749515 bytes
Received 5317 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog
0 input packets with dribble condition detected
226486 packets output, 268732760 bytes, 0 underruns
0 output errors, 0 collisions, 2 interface resets
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier
0 output buffer failures, 0 output buffers swapped out
***************** After 30 secs ***********************
samsrt# sh int e0
Ethernet0 is up, line protocol is up
Hardware is PQUICC Ethernet, address is 0005.9a3c.f923 (bia
0005.9a3c.f923)
Internet address is 192.168.0.7/16
MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec,
reliability 255/255, txload 1/255, rxload 4/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full-duplex, 10BaseT
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:01, output 00:00:09, output hang never
Last clearing of "show interface" counters never
Queueing strategy: fifo
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
5 minute input rate 189000 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
999925 packets input, 366265202 bytes, 0 no buffer
Received 815040 broadcasts, 0 runts, 2 giants, 0 throttles
19270 input errors, 19268 CRC, 0 frame, 0 overrun, 0 ignored
0 input packets with dribble condition detected
693692 packets output, 72720847 bytes, 0 underruns
0 output errors, 0 collisions, 2 interface resets
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier
0 output buffer failures, 0 output buffers swapped out
samsrt#sh int f0
FastEthernet0 is up, line protocol is up
Hardware is PQUICC_FEC, address is 0005.9a3c.f922 (bia
0005.9a3c.f922)
Internet address is 10.10.20.1/24
MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full-duplex, 100Mb/s, 100BaseTX/FX
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:04:18, output 00:00:02, output hang never
Last clearing of "show interface" counters never
Queueing strategy: fifo
Output queue 0/40, 0 drops; input queue 0/75, 1 drops
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
657149 packets input, 68749515 bytes
Received 5317 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog
0 input packets with dribble condition detected
226489 packets output, 268733302 bytes, 0 underruns
0 output errors, 0 collisions, 2 interface resets
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier
0 output buffer failures, 0 output buffers swapped out
Q2. There are many strange accesses from 192.168.0.0/16 like this. Is
it caused by worm or virus on the network?
4d03h: %SEC-6-IPACCESSLOGP: list 101 denied udp 192.168.3.40(13

->
192.168.255.255(13

,
1 packet
4d03h: %SEC-6-IPACCESSLOGP: list 101 denied udp 192.168.3.1(13

->
192.168.255.255(13

,
1 packet
4d03h: %SEC-6-IPACCESSLOGP: list 101 denied udp 192.168.3.89(13

->
192.168.255.255(13

,
1 packet
4d03h: %SEC-6-IPACCESSLOGP: list 101 denied udp 192.168.3.29(13

->
192.168.255.255(13

,
1 packet
4d03h: %SEC-6-IPACCESSLOGP: list 101 denied udp 192.168.3.89(137) ->
192.168.255.255(137),
1 packet
Thank you
Regards
Sam
Rik Bain <> wrote in message news:<pan.2003.12.26.21.18.49.368525.24925@remove. bainz.org>...
> On Fri, 26 Dec 2003 21:00:53 -0600, Sam wrote:
>
> > I brought a new Cisco router 1710 and used it with a PCI broadband
> > router for Internet access. The file download speed from Internet is
> > really slow. When I replace the Cisco router with another broadband
> > router, it is much better.
> >
> > Workstation 10.10.20.2 configs:
> > 1. ip address: 10.10.20.2 netmask 255.255.255.0 2. default gateway:
> > 10.10.20.1
> >
> > Cisco router 1710 major configs:
> > 1. ip route 0.0.0.0 0.0.0.0 192.168.0.3 2. interface Fast Ethernet 0: ip
> > address 10.10.20.1 255.255.255.0
> > ip nat inside
> > 3. interface Ethernet 0: ip address 192.168.0.7 255.255.0.0
> > ip nat outside
> > 4. access-list 7 permit 10.10.20.0 0.0.0.255
> > ip nat inside source list 7 interface Ethernet 0 overload
> >
> > PCI broadband router major configs:
> > 1. interface LAN: ip address 192.168.0.3 2. interface WAN: ip address
> > xxx.xxx.xxx.xxx (ISP assigned) 3. NAT: enabled
> >
> > Thank you in advance
> > Regards
>
>
> First thing /I/ would do is check "show interface" output for errors.