I have been getting a probe on port 1080 from time to time.
No sniffing with a sniffer.
I'm planning up adding to my ipchain rules.
Could it be (is it likely to be) a physical thing (bad cable/hub/card) or
does something stink around here?
----- Original Message -----
From: Furmanek, Greg <
Greg.Furmanek@hit.cendant.com>
To: <
plug-discuss@lists.PLUG.phoenix.az.us>
Sent: Tuesday, March 21, 2000 8:52 AM
Subject: RE: Network Errors
> Have you noticed any unusual scans on the portsentry??
> Since you running firewall do you have antispoofing
> enabled??
>
> Do you deny any source 127.0.0.0 on you external interface??
> Have you tried to analyze the traffic with a sniffer??
>
> The Wolf
>
>
> -----Original Message-----
> From: Amir Aliabadi [mailto:amir@aliabadi.com]
> Sent: Monday, March 20, 2000 7:33 PM
> To: plug-discuss@lists.PLUG.phoenix.az.us
> Subject: Re: Network Errors
>
>
> > Are you offering services to the Internet??
> Yes, ye basic www, telnet, ftp, mail
>
> > Are you running a firewall??
> Yes, ipchains
>
> > Are you logging the connections??
> No.
>
> > Do you run Scan sensing software??
> Portsentry
>
> >
> > This looks disturbing when your loopback interface has tcp errors on it.
> That is what i don't understand...
>
> > -----Original Message-----
> > From: Amir Aliabadi [mailto:amir@aliabadi.com]
> > Sent: Sunday, March 19, 2000 11:03 AM
> > To: plug-discuss@lists.PLUG.phoenix.az.us
> > Subject: Network Errors
> >
> >
> > I recently noticed I was having a bunch of errors on my ethernet
> interfaces.
> > Any suggestions on where to start looking?
> >
> > eth0 is an internal network
> > eth1 is plugged into the internet
> > and lo is lo (why would I be getting errors on a loop back is kinda
> > confusing)
> >
> > It seems like I started seeing this when I upgraded to 2.2.13 kernal. I
> > should probably bump up to the latest....
> >
> > lo Link encap:Local Loopback
> > inet addr:127.0.0.1 Bcast:127.255.255.255 Mask:255.0.0.0
> > UP LOOPBACK RUNNING MTU:3924 Metric:1
> > RX packets:389518 errors:0 dropped:0 overruns:0
> > TX packets:0 errors:118988302 dropped:389518 overruns:0
> >
> > eth0 Link encap:Ethernet HWaddr 00:10:5B:27:08:62
> > inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
> > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> > RX packets:1272091 errors:267 dropped:0 overruns:288
> > TX packets:0 errors:1232085057 dropped:1423974 overruns:0
> > Interrupt:10 Base address:0x300
> >
> > eth1 Link encap:Ethernet HWaddr 00:4F:4A:05:68:16
> > inet addr:209.141.132.195 Bcast:209.141.132.255
> > Mask:255.255.255.0
> > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> > RX packets:1677197 errors:0 dropped:0 overruns:0
> > TX packets:42 errors:182048567 dropped:1355452 overruns:62
> > Interrupt:11 Base address:0x280
> >
> >
> >
> >
> > _______________________________________________
> > Plug-discuss mailing list - Plug-discuss@lists.PLUG.phoenix.az.us
> > http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
> >
> > _______________________________________________
> > Plug-discuss mailing list - Plug-discuss@lists.PLUG.phoenix.az.us
> > http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
>
>
> _______________________________________________
> Plug-discuss mailing list - Plug-discuss@lists.PLUG.phoenix.az.us
> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
>
> _______________________________________________
> Plug-discuss mailing list - Plug-discuss@lists.PLUG.phoenix.az.us
> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss