images.linuxquestions.org port #?

Aeiri · 06-01-2004, 02:15 PM

My firewall is blocking the port images.linuxquestions.org uses, is there any way to determine WHICH port it is so I can open it up?

It's kinda annoying seeing the alt attributes showing up all the time :/

david_ross · 06-01-2004, 02:36 PM

I doubt it is your firewall - it uses the standard http port (80). Are you sure that you did not block images on this site with a browser configuration.

Aeiri · 06-01-2004, 02:47 PM

Quote:

Originally posted by david_ross
I doubt it is your firewall - it uses the standard http port (80). Are you sure that you did not block images on this site with a browser configuration.

When I stop the firewall the images work fine... I'm sure its the firewall. Can't even ping it when the firewall is on. All browsers are this way.

What port does it send to then?

XavierP · 06-01-2004, 02:50 PM

Moved: This thread is more suitable in Website Questions and Suggestions and has been moved accordingly to help your thread/question get the exposure it deserves.

jeremy · 06-01-2004, 04:06 PM

All images are served on the standard port 80.

--jeremy

trickykid · 06-01-2004, 05:02 PM

Perform a trace route to images.linuxquestions.org so you can tell where its dropping your connection/route off at. Most likely that is the problem, could be your ISP or a few hops down the pipe..

Aeiri · 06-01-2004, 09:13 PM

I try traceroute'ing before firewall is set up, works fine, after the firewall is on:

Quote:

aeiri@localhost:~$ traceroute images.linuxquestions.org
traceroute to images.linuxquestions.org (207.44.183.182), 30 hops max, 38 byte packets
traceroute: sendto: Operation not permitted

Same for ping images.linuxquestions.org after firewall is up......

Weird, everything else ping's and traceroute's fine after firewall is setup.... even www.linuxquestions.org:

Quote:

aeiri@localhost:~$ traceroute www.linuxquestions.org
traceroute to www.linuxquestions.org (64.179.4.149), 30 hops max, 38 byte packet s
1 wbar1.sea1-4-5-240-001.sea1.elnk.dsl.genuity.net (4.5.240.1) 27.204 ms 27. 333 ms 63.576 ms
2 4.9.10.161 (4.9.10.161) 27.290 ms 48.509 ms 31.205 ms
3 so-4-0-0.bbr1.Chicago1.Level3.net (4.68.112.189) 27.457 ms 31.148 ms 27.3 28 ms
4 so-0-0-0.bbr2.NewYork1.Level3.net (64.159.0.238) 59.113 ms 67.468 ms 103. 542 ms
5 ge-7-0-0.edge1.NewYork1.Level3.net (64.159.4.150) 62.682 ms 58.897 ms 59. 047 ms
6 ewr-brdr-02.inet.qwest.net (205.171.1.97) 97.229 ms 59.358 ms 89.546 ms
7 ewr-core-02.inet.qwest.net (205.171.17.129) 63.350 ms 86.351 ms 60.254 ms
8 chi-core-01.inet.qwest.net (205.171.8.229) 79.959 ms 113.692 ms 101.228 m s
9 chi-edge-09.inet.qwest.net (205.171.20.122) 111.638 ms 79.942 ms 80.085 m s
10 63.149.3.230 (63.149.3.230) 95.102 ms 91.476 ms 91.172 ms
11 atm6-5-978-pitb-isp-cisco.choiceone.net (66.202.102.254) 101.101 ms 107.236 ms 107.527 ms
12 web1.linuxquestions.org (64.179.4.149) 107.943 ms 99.438 ms 101.790 ms

david_ross · 06-02-2004, 01:58 PM

Perhaps you could post a copy of your firewall rules so we can see what they are doing.

Aeiri · 06-04-2004, 01:44 AM

It was a bad Firewall Rule

It fixed itself with auto update...