Voyager can't get through Firewall

We’ve just installed 6.1.0 from a downloaded CD and are having problems
getting Voyager to work through our Firewall. We have the proper proxy
and port entered, but that doesn’t seem to matter. We never get
prompted for a Firewall ID and password. I’ve seen several other
threads here that sound like other users may also be experiencing this
problem, but I haven’t seen a posted solution.

Here are two screen shots of a sniffer examining packets between two
different hosts and our firewall. The first host (failhost) is running
RTP 6.1.0 / Voyager. The firewall’s IP address ends in .15. The second
screen shot (succeed) is from a machine running Windows 95 / Netscape
4.51.

Anyone seen anything like this? Why is Voyager trying to do an HTTP
Continuation instead of a GET?

\

Phil Kelly
Delphi Delco Electronic Systems
Embedded Computing Technologies Phone (765) 451-7743
Internet: pwkelly@eng.delcoelect.com Kokomo, Indiana, USA

We now have more information on this problem.

There appear to be 2 different bugs that are causing problems:

First, In the Proxy Overrides section of the Edit->Preferences
(Connections Tab),
it appears that pure domain name overrides don’t work.

That is if you have:

qnx.com, foo.com, somewhere.com

in this section, voyager will ignore this and still hit the proxy server
for hosts in these domains! i.e. If you try to go to www.foo.com, then
voyager will try to go through the proxy to reach it! You can confirm
this by running netstat.

Alternatively, if you specify a hostname, host ip, or
wildcarded domain, then it seems to work: i.e.

*.qnx.com, www.foo.com, 192.168.1.15

would allow “internal” connections to all of qnx.com, as well as the
machines www.foo.com and 192.168.1.15.


The second issue is a bit more esoteric, but Laxman Kapaleshwari
remembered something similar when we were playing with Voyager on QNX4.

If you are running an http proxy, be sure to leave the SOCKS proxy field
blank or things don’t seem to work. Once we erased the entry in the
SOCKS field, everything started to work.



Phil Kelly wrote:

We’ve just installed 6.1.0 from a downloaded CD and are having problems
getting Voyager to work through our Firewall. We have the proper proxy
and port entered, but that doesn’t seem to matter. We never get
prompted for a Firewall ID and password. I’ve seen several other
threads here that sound like other users may also be experiencing this
problem, but I haven’t seen a posted solution.

Here are two screen shots of a sniffer examining packets between two
different hosts and our firewall. The first host (failhost) is running
RTP 6.1.0 / Voyager. The firewall’s IP address ends in .15. The second
screen shot (succeed) is from a machine running Windows 95 / Netscape
4.51.

Anyone seen anything like this? Why is Voyager trying to do an HTTP
Continuation instead of a GET?


Phil Kelly
Delphi Delco Electronic Systems
Embedded Computing Technologies Phone (765) 451-7743
Internet: > pwkelly@eng.delcoelect.com > Kokomo, Indiana, USA


[Image] [Image]


Phil Kelly
Delphi Delco Electronic Systems
Embedded Computing Technologies Phone (765) 451-7743
Internet: pwkelly@eng.delcoelect.com Kokomo, Indiana, USA

Hello Phil,

Your first issue was a known issue and your second has been added to our
bug tracking system; Therefore, both these issues will be dealt with in
the future.

Thank you,
Dave B.




Phil Kelly wrote:

We now have more information on this problem.

There appear to be 2 different bugs that are causing problems:

First, In the Proxy Overrides section of the Edit->Preferences
(Connections Tab),
it appears that pure domain name overrides don’t work.

That is if you have:

qnx.com, foo.com, somewhere.com

in this section, voyager will ignore this and still hit the proxy server
for hosts in these domains! i.e. If you try to go to > www.foo.com> , then
voyager will try to go through the proxy to reach it! You can confirm
this by running netstat.

Alternatively, if you specify a hostname, host ip, or
wildcarded domain, then it seems to work: i.e.

*.qnx.com, > www.foo.com> , 192.168.1.15

would allow “internal” connections to all of qnx.com, as well as the
machines > www.foo.com > and 192.168.1.15.


The second issue is a bit more esoteric, but Laxman Kapaleshwari
remembered something similar when we were playing with Voyager on QNX4.

If you are running an http proxy, be sure to leave the SOCKS proxy field
blank or things don’t seem to work. Once we erased the entry in the
SOCKS field, everything started to work.



Phil Kelly wrote:

We’ve just installed 6.1.0 from a downloaded CD and are having problems
getting Voyager to work through our Firewall. We have the proper proxy
and port entered, but that doesn’t seem to matter. We never get
prompted for a Firewall ID and password. I’ve seen several other
threads here that sound like other users may also be experiencing this
problem, but I haven’t seen a posted solution.

Here are two screen shots of a sniffer examining packets between two
different hosts and our firewall. The first host (failhost) is running
RTP 6.1.0 / Voyager. The firewall’s IP address ends in .15. The second
screen shot (succeed) is from a machine running Windows 95 / Netscape
4.51.

Anyone seen anything like this? Why is Voyager trying to do an HTTP
Continuation instead of a GET?


Phil Kelly
Delphi Delco Electronic Systems
Embedded Computing Technologies Phone (765) 451-7743
Internet: > pwkelly@eng.delcoelect.com > Kokomo, Indiana, USA


[Image] [Image]