Re: Check Update, Update and Port Blocking

2014-03-11 Thread Bill Wood
On Wed, 2014-03-05 at 18:53 +, Joe wrote: . . . > From your last post: > > Failed to fetch > ftp://ftp.us.debian.org/debian/dists/squeeze/contrib/i18n/Translation-en.bz2 > Could not connect passive socket. [IP: 64.50.233.100 21] Failed to fetch > ftp://ftp.us.debian.org/debian/dists/squeeze

Re: Check Update, Update and Port Blocking

2014-03-05 Thread Joe
On Wed, 05 Mar 2014 10:49:27 -0600 Bill Wood wrote: > On Thu, 2014-02-20 at 07:09 -0500, PaulNM wrote: >. . . > > On second though, I just re-read the OP's message. He's talking > > about the firewall on the Comcast modem/router. It's really rare > > for those types of devices to have outgo

Re: Check Update, Update and Port Blocking

2014-03-05 Thread Bill Wood
On Thu, 2014-02-20 at 07:09 -0500, PaulNM wrote: . . . > On second though, I just re-read the OP's message. He's talking about > the firewall on the Comcast modem/router. It's really rare for those > types of devices to have outgoing filtering. > > However, according to: > http://media2.comca

Re: Check Update, Update and Port Blocking

2014-03-02 Thread Bill Wood
This is an update on my post on 02/20. I got the "yellow triangle" icon again so I went into admin for my Wireless Gateway and reset the security level to intermediate or "typical". I then clicked on the icon and selected "check updates". The usual dialog box appeared and it started checking for

Re: Check Update, Update and Port Blocking

2014-02-20 Thread Andrei POPESCU
On Jo, 20 feb 14, 07:09:27, PaulNM wrote: > On 02/20/2014 03:50 AM, Andrei POPESCU wrote: > > On Lu, 17 feb 14, 22:30:31, PaulNM wrote: > >> > >> I could be wrong, but my understanding is that apt uses standard http, > >> so port 80 outgoing. > > > > Just because port 80 is used for listening for

Re: Check Update, Update and Port Blocking

2014-02-20 Thread PaulNM
On 02/20/2014 03:50 AM, Andrei POPESCU wrote: > On Lu, 17 feb 14, 22:30:31, PaulNM wrote: >> >> I could be wrong, but my understanding is that apt uses standard http, >> so port 80 outgoing. > > Just because port 80 is used for listening for http requests doesn't > meant the client is using the s

Re: Check Update, Update and Port Blocking

2014-02-20 Thread Andrei POPESCU
On Lu, 17 feb 14, 22:30:31, PaulNM wrote: > > I could be wrong, but my understanding is that apt uses standard http, > so port 80 outgoing. Just because port 80 is used for listening for http requests doesn't meant the client is using the same outgoing port ;) Kind regards, Andrei -- http://wi

Re: Check Update, Update and Port Blocking

2014-02-17 Thread PaulNM
On 02/17/2014 09:28 PM, Bill Wood wrote: > Do the protocols used for automatic check for updates and for updates > require specific ports to be available? I recently switched my cable > modem to a Comcast Internet Gateway 1with the firewall set to high > security and subsequently a couple of upd

Check Update, Update and Port Blocking

2014-02-17 Thread Bill Wood
Do the protocols used for automatic check for updates and for updates require specific ports to be available? I recently switched my cable modem to a Comcast Internet Gateway 1with the firewall set to high security and subsequently a couple of update check icons appeared indicating an error condit