You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Dave Pawson <da...@gmail.com> on 2013/11/27 17:18:40 UTC
wifi access to tomcat on wired mc
Scenario.
Tomcat install on Linux, wired to router.
Windows 7 connected to router via wifi.
from windows.
>ping ip.address no problem
http access to tomcat from windows. Nothing
telnet access to tomcat ip port Nothing
wired access to tomcat from a.n.other no problem
I've got Zone alarm on the windows box.
I think I have set it to pass through for 'trusted' zone on my local net.
Can anyone think of more 'blocks' to seeing the server please?
TiA
--
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.
http://www.dpawson.co.uk
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: wifi access to tomcat on wired mc
Posted by Dave Pawson <da...@gmail.com>.
basic is.... from wifi mc
>ping 192.168.1.65
no problem
My local net is that, 192.168.1.*
putting that in the window(Chrome) browser says no.
http://192.168.1.65:8081
Just times out.
regards
On 27 November 2013 16:37, Leo Donahue - OETX
<Le...@mail.maricopa.gov> wrote:
>>-----Original Message-----
>>From: Dave Pawson [mailto:dave.pawson@gmail.com]
>>Subject: wifi access to tomcat on wired mc
>>
>>http access to tomcat from windows. Nothing
>
> Can you elaborate on this? What url did you try?
--
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.
http://www.dpawson.co.uk
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: wifi access to tomcat on wired mc
Posted by Leo Donahue - OETX <Le...@mail.maricopa.gov>.
>-----Original Message-----
>From: Dave Pawson [mailto:dave.pawson@gmail.com]
>Subject: wifi access to tomcat on wired mc
>
>http access to tomcat from windows. Nothing
Can you elaborate on this? What url did you try?
Re: wifi access to tomcat on wired mc
Posted by Dave Pawson <da...@gmail.com>.
On 27 November 2013 18:24, Christopher Schultz
<ch...@christopherschultz.net> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> Dave,
>
> On 11/27/13, 12:39 PM, Dave Pawson wrote:
>> On 27 November 2013 17:10, Christopher Schultz
>>> You mean when you try to reach Tomcat's HTTP port from a machine
>>> hard-wired on the network using the local IP, it works fine?
>>
>> No, sorry , I lie Oops, Google chrom could not connect to
>> 192.168.65:8081
>
> You mean 192.168.1.65:8081 right?
Yes. that's right.
>
>>> To summarize, you can ping from anywhere but HTTP only works when
>>> you use a hard-wired client? Odd.
>>
>> ping works from both wired/wireless to the 'main' wired machine
>> containing the tomcat server
>>
>>>
>>> What if you hard-wire the Windows box?
>>
>> I have both... neither works (sorry)
>
> Okay, that suggests that the problem is on the Windows box.
Noted.
>
> You said that "wires access to tomcat from a.n.other no problem".
> What other client did you use and what was its setup?
No, I was wrong. I have a full windows box, wired to the router.
A laptop, wifi connected to the router.
Both report Connecting to (ip ads) Could not open connection to the
host, on port 8081
Both ping the (ip ads) works fine.
>
>>>> I've got Zone alarm on the windows box.
>>>
>>> Does it have any rules concerning outbound traffic? It might be
>>> blocking lots of stuff to the local network.
>>
>> Outbound? I presumed the block (if there was one) was inbound,
>> http from 'trusted zone'
>
> Your Windows box can be configured to refuse to transmit traffic out
> to certain places. It seems that is the likely problem, here. Check
> both firewalls for any such rules.
Will do. Zonealarm seems v.complex to set up.
I think I need both incoming and outgoing
'mycomputer' to trusted zone :8081
and vice versa
>> IMHO I can ping it... does that necessarily mean I can get http
>> connections?
>
> No. ping sends ICMP packets which are in a special category and do not
> use a port number. They can be allowed or rejected by firewalls. HTTP
> is TCP/IP and uses whatever port number you want (8081 in your case).
>
>>>> Can anyone think of more 'blocks' to seeing the server please?
>>>
>>> As far as the Linux machine is concerned, there is no difference
>>> between a WiFi and hard-wired client, as long as they are in the
>>> same IP range. I'm not sure you could configure iptables to
>>> restrict based upon that criteria alone. Is iptables running?
>>> What rules does it have?
>>
>> Sorry.. excuse my ignorance, but how to check?
>
> As root, type "iptables -L" and it will list all the firewall rules on
> the server. I suspect the server is not a problem, though.
Heck of a list?
is there a gui I could use to add one ... or leave that till I
have tried the Windows end more thoroughly perhaps.
Nothing obvious showing currently.
>
>>> Windows has a built-in firewall, but I believe it's configured
>>> out of the box to allow anything to call-out to port 80. I'm not
>>> sure about 8080. If you have ZoneAlarm, does that mean you have 2
>>> software firewalls in the mix on that machine? You may want to
>>> check *both* their settings.
>>
>> I believe I have switched off the M$ firewall, since I have
>> zonealarm running?
>
> Only you can answer that.
Windows firewall shows
Home or work(private) networks 'Connected'
Beneath that
Public networks, Not connected.
Between them
Windows firewall state 'Off'
which is what I wanted.
v.complex i/face though.
>
>>> Finally, the router can do weird things, too. Check your settings
>>> for anything "restriction-related".
>>
>> It's a BT (our national phone company) router+wifi I haven't found
>> anything strictly ip to ip mapping related.
>>
>> That is one of the potential blockers.
>
> That the Windows machine cannot connect regardless of
> WiFi-versus-Ethernet suggests that the problem is with the Windows
> box, not the network.
>
> - -chris
Again, thanks Chris.
I'll play (on the windows side) tomorrow.
regards
--
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.
http://www.dpawson.co.uk
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: wifi access to tomcat on wired mc
Posted by Dave Pawson <da...@gmail.com>.
Yes, 192.168,1.xxx
http://dpawson.co.uk
xslt xsl-fo docbook FAQ
On 3 Dec 2013, at 19:29, Leo Donahue - OETX <Le...@mail.maricopa.gov> wrote:
>> -----Original Message-----
>> From: Dave Pawson [mailto:dave.pawson@gmail.com]
>> Subject: Re: wifi access to tomcat on wired mc
>>>
>>> But you can't use the IP of your wired Tomcat box in a URL with port 8081 to get Tomcat to respond from your Windows 7 wireless laptop? It just times out?
>>
>> ....Not that it times out, just that I can't get any data back using http, from browser.
>> telnet ipAddress port also reports 'could not open connection'
>>
>>
>>> But if you make the same request from the other wired computer, that same URL works fine?
>>
>> No. I believe I corrected myself. From the wired windows box I cannot get access.
>
> This is where the Linux people step in. I'm assuming that all three of your computers are on the same domain/workgroup?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: wifi access to tomcat on wired mc
Posted by Leo Donahue - OETX <Le...@mail.maricopa.gov>.
>-----Original Message-----
>From: Dave Pawson [mailto:dave.pawson@gmail.com]
>Subject: Re: wifi access to tomcat on wired mc
>>
>> But you can't use the IP of your wired Tomcat box in a URL with port 8081 to get Tomcat to respond from your Windows 7 wireless laptop? It just times out?
>
>....Not that it times out, just that I can't get any data back using http, from browser.
> telnet ipAddress port also reports 'could not open connection'
>
>
>> But if you make the same request from the other wired computer, that same URL works fine?
>
>No. I believe I corrected myself. From the wired windows box I cannot get access.
This is where the Linux people step in. I'm assuming that all three of your computers are on the same domain/workgroup?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: wifi access to tomcat on wired mc
Posted by Dave Pawson <da...@gmail.com>.
On 3 December 2013 17:48, Leo Donahue - OETX
<Le...@mail.maricopa.gov> wrote:
> Reading back over your previous posts, you said you can ping the Linux box from Windows 7 (aka your wireless laptop?):
> " ...ping works from both wired/wireless to the 'main' wired machine containing the tomcat server"
Yes
>
> But you can't use the IP of your wired Tomcat box in a URL with port 8081 to get Tomcat to respond from your Windows 7 wireless laptop? It just times out?
.... Not that it times out, just that I can't get any data back using
http, from browser.
telnet ipAddress port also reports 'could not open connection'
> But if you make the same request from the other wired computer, that same URL works fine?
No. I believe I corrected myself. From the wired windows box I cannot get
access.
[May be of use. I can 'share' a directory, using Samba. No idea what
protocol that uses. ]
>
> Sorry for making you repeat all of this. One of your previous posts confused me as to whether you could or could not do this.
My apologies. I profess mostly ignorance of internet protocols.
>
> From your wireless Windows 7 laptop, can you see a file share on the other wired (non-Linux) box? I'm just trying to rule out your network and/or your vendor provided hardware.
OK. More trial (and learning).
>From the laptop I can 'share' (windows wise) with the wired windows box.
ditto I can 'see' the shared (samba) directory on the linux box.
HTH
--
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.
http://www.dpawson.co.uk
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: wifi access to tomcat on wired mc
Posted by Leo Donahue - OETX <Le...@mail.maricopa.gov>.
>-----Original Message-----
>From: Dave Pawson [mailto:dave.pawson@gmail.com]
>Subject: Re: wifi access to tomcat on wired mc
>>
>> ISP ----> | inside your house | ----> your ISP provided wifi /router ----> your
>computers?
>
>The latter.
>
>router to linux (tomcat) is wired.
>router to windows laptop box is wifi
>router to windows box also wired.
>
Reading back over your previous posts, you said you can ping the Linux box from Windows 7 (aka your wireless laptop?):
" ...ping works from both wired/wireless to the 'main' wired machine containing the tomcat server"
But you can't use the IP of your wired Tomcat box in a URL with port 8081 to get Tomcat to respond from your Windows 7 wireless laptop? It just times out?
But if you make the same request from the other wired computer, that same URL works fine?
Sorry for making you repeat all of this. One of your previous posts confused me as to whether you could or could not do this.
From your wireless Windows 7 laptop, can you see a file share on the other wired (non-Linux) box? I'm just trying to rule out your network and/or your vendor provided hardware.
Re: wifi access to tomcat on wired mc
Posted by Dave Pawson <da...@gmail.com>.
On 3 December 2013 17:18, Leo Donahue - OETX
<Le...@mail.maricopa.gov> wrote:
> Would it maybe be possible to give us a line diagram of your request from your windows box through your hardware to your Tomcat on Linux?
>
> For example, you are using a vendor supplied wireless router? I am sure my ISP blocks all 8080 type traffic to my cable modem and I wouldn't put it past them to enable something like that in the hardware I would rent from them (which I don't).
>
> Is your diagram something like this:
> Or is it this:
>
> ISP ----> | inside your house | ----> your ISP provided wifi /router ----> your computers?
The latter.
router to linux (tomcat) is wired.
router to windows laptop box is wifi
router to windows box also wired.
HTH
--
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.
http://www.dpawson.co.uk
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: wifi access to tomcat on wired mc
Posted by Leo Donahue - OETX <Le...@mail.maricopa.gov>.
>-----Original Message-----
>From: Dave Pawson [mailto:dave.pawson@gmail.com]
>Subject: Re: wifi access to tomcat on wired mc
>
>Yes... (as far as I know - unloaded Zonealarm altogether. Still nothing).
>I have a wifi / router in the game too. It's not a commercial one, it was provided
>by the ISP, so no passthrough ip lists...
>I am suspicious of that.
>
Would it maybe be possible to give us a line diagram of your request from your windows box through your hardware to your Tomcat on Linux?
For example, you are using a vendor supplied wireless router? I am sure my ISP blocks all 8080 type traffic to my cable modem and I wouldn't put it past them to enable something like that in the hardware I would rent from them (which I don't).
Is your diagram something like this:
ISP ----> | inside your house | ----> your ISP provided wifi /router ----> switch maybe or other router of your own (?) ----> your computers?
Or is it this:
ISP ----> | inside your house | ----> your ISP provided wifi /router ----> your computers?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: wifi access to tomcat on wired mc
Posted by Dave Pawson <da...@gmail.com>.
On 3 December 2013 14:21, Leo Donahue - OETX
<Le...@mail.maricopa.gov> wrote:
>>-----Original Message-----
>>From: Dave Pawson [mailto:dave.pawson@gmail.com]
>>Subject: Re: wifi access to tomcat on wired mc
>>
>>Thanks Chuck.
>>Back to playing with Windows firewalls.
>>
>
> Have you tried disabling the windows firewall altogether to rule it out as the problem?
>
> Leo
Hi Leo
Yes... (as far as I know - unloaded Zonealarm altogether. Still nothing).
I have a wifi / router in the game too. It's not a commercial one,
it was provided by the ISP, so no passthrough ip lists...
I am suspicious of that.
regards
--
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.
http://www.dpawson.co.uk
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: wifi access to tomcat on wired mc
Posted by Dave Pawson <da...@gmail.com>.
On 3 December 2013 14:46, Christopher Schultz
<ch...@christopherschultz.net> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> Chuck,
>
> On 12/3/13, 9:39 AM, Caldarale, Charles R wrote:
>>> From: Leo Donahue - OETX [mailto:LeoDonahue@mail.maricopa.gov]
>>> Subject: RE: wifi access to tomcat on wired mc
>>
>>> Have you tried disabling the windows firewall altogether to rule
>>> it out as the problem?
>>
>> The OP may well have more than one firewall active on the Windows
>> box, if I interpreted his previous postings correctly.
>
> +1
>
> Also iptables on the Linux box, but I'm still confused as to what
> exactly does and does not work. It seems the OP gives conflicting
> information with every additional post.
Confusion leading to conflicting?
I.e. I don't know what is / isn't getting in the way.
Window to Linux (tomcat)
1. I believe windows firewall is switched off (Zonealarm does that
on request)
2. Zonealarm firewall. Not exactly clear how to get that to pass through
... AFAIK that just needs incoming ip:8080 ( main tc port) - no others.
outgoing 'this machine' to ip address
3. British Telecom router (unable to find anything to set)
4. Fedora Linux. There is a firewall. No ideas on iptables.
Hence my confusion?
regards
--
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.
http://www.dpawson.co.uk
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: wifi access to tomcat on wired mc
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Chuck,
On 12/3/13, 9:39 AM, Caldarale, Charles R wrote:
>> From: Leo Donahue - OETX [mailto:LeoDonahue@mail.maricopa.gov]
>> Subject: RE: wifi access to tomcat on wired mc
>
>> Have you tried disabling the windows firewall altogether to rule
>> it out as the problem?
>
> The OP may well have more than one firewall active on the Windows
> box, if I interpreted his previous postings correctly.
+1
Also iptables on the Linux box, but I'm still confused as to what
exactly does and does not work. It seems the OP gives conflicting
information with every additional post.
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.15 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBCAAGBQJSne7VAAoJEBzwKT+lPKRYcNgP/3VIIKUphETcF5Y3qm0XHv1C
cryHusGuj1Dsn9vtC44MFoPUjNXrIVb3igaZztD/PrB+tur6kqcnN6n9ILQgRbxn
athEuiSJtFY+CKzf57aUKyraoYmqXbyFDTeXlpG/amyfXzGpbe2Hr849TdFE0RE6
NrpawNf2du8adNxUzy2jUwQpAOxBsrn5UENrr6EB4AzQEGRSEVFM1My0HKIth6dK
c4fe2hF7TbwBJQezXdaQ1OrbgT/wy2Fn9WzGGdQdkkwb09KhF7Ry1YJQYxDHMS5E
X+D81bZ3eVkEVDDLF2i2MX/IVMZBn0X1oiF8b8rWnG6T66UZCkMAaxDpo/JHgGoF
6qowtgpC4RQBJUIi7CPDy/lMhaAYDXQ1qyPClINuT7z1OUbPnOW3/hhgXvFwNVK+
jtDlmofqRMsqc/kSxAUhSrvVEsqACHDfq/GmVFoTPCkm/53IKcATBF2J2cLWVT0X
b+2ojJf6IdUJ0xow3wFEveHA+YCncVlvoqM5wbb3mveFz4qsZOCdvv94ou9Rilua
bmrz62HlUBALQAjUu+h3Ol/3gnnfrGc0DF67cfat5yptoEOdLuNQpC7IN6wK1I/a
e1M9t4K6m6Oj6Wo6yMepsqUfjwXwRYSD7RvabtR20depRnkQ6Ks4TCJSHCdfOosk
CtYRYuqTmqa/9Cp9I8BA
=otwK
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: wifi access to tomcat on wired mc
Posted by Leo Donahue - OETX <Le...@mail.maricopa.gov>.
>-----Original Message-----
>From: Caldarale, Charles R [mailto:Chuck.Caldarale@unisys.com]
>Subject: RE: wifi access to tomcat on wired mc
>
>> From: Leo Donahue - OETX [mailto:LeoDonahue@mail.maricopa.gov]
>> Subject: RE: wifi access to tomcat on wired mc
>
>> Have you tried disabling the windows firewall altogether to rule it out as the
>problem?
>
>The OP may well have more than one firewall active on the Windows box, if I
>interpreted his previous postings correctly.
>
> - Chuck
Yes, I forgot to mention also disabling his "zone alarm" product.
Leo
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: wifi access to tomcat on wired mc
Posted by "Caldarale, Charles R" <Ch...@unisys.com>.
> From: Leo Donahue - OETX [mailto:LeoDonahue@mail.maricopa.gov]
> Subject: RE: wifi access to tomcat on wired mc
> Have you tried disabling the windows firewall altogether to rule it out as the problem?
The OP may well have more than one firewall active on the Windows box, if I interpreted his previous postings correctly.
- Chuck
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: wifi access to tomcat on wired mc
Posted by Leo Donahue - OETX <Le...@mail.maricopa.gov>.
>-----Original Message-----
>From: Dave Pawson [mailto:dave.pawson@gmail.com]
>Subject: Re: wifi access to tomcat on wired mc
>
>Thanks Chuck.
>Back to playing with Windows firewalls.
>
Have you tried disabling the windows firewall altogether to rule it out as the problem?
Leo
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: wifi access to tomcat on wired mc
Posted by Dave Pawson <da...@gmail.com>.
Thanks Chuck.
Back to playing with Windows firewalls.
DaveP
On 30 November 2013 14:49, Caldarale, Charles R
<Ch...@unisys.com> wrote:
>> From: Dave Pawson [mailto:dave.pawson@gmail.com]
>> Subject: Re: wifi access to tomcat on wired mc
>
>> Am I right in thinking that tomcat (as installed) only allows access
>> to localhost,
>> using server.xml / <Valve /> options?
>
> No, you are incorrect. Out of the box, Tomcat allows access from any client, anywhere. Your platform, router, or ISP might not.
>
> - Chuck
>
>
> THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
--
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.
http://www.dpawson.co.uk
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: wifi access to tomcat on wired mc
Posted by "Caldarale, Charles R" <Ch...@unisys.com>.
> From: Dave Pawson [mailto:dave.pawson@gmail.com]
> Subject: Re: wifi access to tomcat on wired mc
> Am I right in thinking that tomcat (as installed) only allows access
> to localhost,
> using server.xml / <Valve /> options?
No, you are incorrect. Out of the box, Tomcat allows access from any client, anywhere. Your platform, router, or ISP might not.
- Chuck
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: wifi access to tomcat on wired mc
Posted by Dave Pawson <da...@gmail.com>.
On 27 November 2013 18:24, Christopher Schultz
<ch...@christopherschultz.net> wrote:
...
A little progress.
Clarification please.
Am I right in thinking that tomcat (as installed) only allows access
to localhost,
using server.xml / <Valve /> options?
http://tomcat.apache.org/tomcat-7.0-doc/config/valve.html#Remote_Address_Filter
My local network on 192.168.1.xxx
I want to give access to other mc's on this net.
<Valve className="org.apache.catalina.valves.RemoteAddrValve"
allow="192\.168\.1\.66" />
Isn't working - Is that the right attribute value for @allow please
(I'll change it to a range if this is the right regex syntax)
TiA
--
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.
http://www.dpawson.co.uk
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: wifi access to tomcat on wired mc
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Dave,
On 11/27/13, 12:39 PM, Dave Pawson wrote:
> On 27 November 2013 17:10, Christopher Schultz
>> You mean when you try to reach Tomcat's HTTP port from a machine
>> hard-wired on the network using the local IP, it works fine?
>
> No, sorry , I lie Oops, Google chrom could not connect to
> 192.168.65:8081
You mean 192.168.1.65:8081 right?
>> To summarize, you can ping from anywhere but HTTP only works when
>> you use a hard-wired client? Odd.
>
> ping works from both wired/wireless to the 'main' wired machine
> containing the tomcat server
>
>>
>> What if you hard-wire the Windows box?
>
> I have both... neither works (sorry)
Okay, that suggests that the problem is on the Windows box.
You said that "wires access to tomcat from a.n.other no problem".
What other client did you use and what was its setup?
>>> I've got Zone alarm on the windows box.
>>
>> Does it have any rules concerning outbound traffic? It might be
>> blocking lots of stuff to the local network.
>
> Outbound? I presumed the block (if there was one) was inbound,
> http from 'trusted zone'
Your Windows box can be configured to refuse to transmit traffic out
to certain places. It seems that is the likely problem, here. Check
both firewalls for any such rules.
>>> I think I have set it to pass through for 'trusted' zone on my
>>> local net.
>>
>> Okay, maybe not.
>>
>> Some routers have AP-isolation features where the WiFi clients
>> can only get to the "outside" of the network, and can't contact
>> local machines. But since you can ping the local machine that
>> seems to rule that out.
>
> IMHO I can ping it... does that necessarily mean I can get http
> connections?
No. ping sends ICMP packets which are in a special category and do not
use a port number. They can be allowed or rejected by firewalls. HTTP
is TCP/IP and uses whatever port number you want (8081 in your case).
>>> Can anyone think of more 'blocks' to seeing the server please?
>>
>> As far as the Linux machine is concerned, there is no difference
>> between a WiFi and hard-wired client, as long as they are in the
>> same IP range. I'm not sure you could configure iptables to
>> restrict based upon that criteria alone. Is iptables running?
>> What rules does it have?
>
> Sorry.. excuse my ignorance, but how to check?
As root, type "iptables -L" and it will list all the firewall rules on
the server. I suspect the server is not a problem, though.
>> Windows has a built-in firewall, but I believe it's configured
>> out of the box to allow anything to call-out to port 80. I'm not
>> sure about 8080. If you have ZoneAlarm, does that mean you have 2
>> software firewalls in the mix on that machine? You may want to
>> check *both* their settings.
>
> I believe I have switched off the M$ firewall, since I have
> zonealarm running?
Only you can answer that.
>> Finally, the router can do weird things, too. Check your settings
>> for anything "restriction-related".
>
> It's a BT (our national phone company) router+wifi I haven't found
> anything strictly ip to ip mapping related.
>
> That is one of the potential blockers.
That the Windows machine cannot connect regardless of
WiFi-versus-Ethernet suggests that the problem is with the Windows
box, not the network.
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.15 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBCAAGBQJSljjuAAoJEBzwKT+lPKRYXhYP/1Cz5cV1snXcxcH2QzKYGnXw
G1s+++EiuEdoCB8cJpTBJhzPzZhlcfoKeTIJv7aHLpQ1zg0aD21Oj52TFok6pRTS
HYa4AIossZ87Oh2ePZHpYXzxMbSFgERtMHNNttbd24bcEsimpWZ8RF0NHnQZa0nG
7xfkoQDtMjXsvGQHuoEwLmV96WclOarFyvVO9ZKVRvCNeybI+5Sr0C/zZdCSWBoo
t+4vDg2gPfHmwWAbYpsLA1L2PC7oAzhvEtrepilm12GXYWLcM228is9au2RDQgEB
YbSEkyzFLx+xv1fF8M2+/YysmhDYt/jYJq+jE8xr52f6JRNbshAt3cnJIKFI2nsu
HsfwrfWFbOz6cwxb1oO5UnzBh/VjhpIMOUVQz6G1vpsIb8DZKct+lttYv1vGDnBj
DbTBkiVkXSa2J4jfW0dlP6ausrmrYbWRXH2hS7QGR5acXN8alyXw5aGtJ7KJ+Sy9
RVNtdiP2KvH9wLI0CH7oNJn/3C0p7ZyEc/7fqxp0r/oWHB94eqv0Jf5pfxQhMxKP
9d31Z2tHwYgIX90ntuteg62aT742Q8GYRiA1GH71r1rOmYz0OP9j3psHbLLDMOm6
q8Ldx0FmMC37UeKPZNyZTdRu5+L8s33/5r3fq0JCdcvNucrnaV7jQH0G86DQFmpc
3ES9nIoA1/rde+IrnCYu
=PeJI
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: wifi access to tomcat on wired mc
Posted by Dave Pawson <da...@gmail.com>.
On 27 November 2013 17:10, Christopher Schultz
<ch...@christopherschultz.net> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> Dave,
>
> On 11/27/13, 11:18 AM, Dave Pawson wrote:
>> Scenario. Tomcat install on Linux, wired to router. Windows 7
>> connected to router via wifi.
>>
>> from windows.
>>> ping ip.address no problem
>
> Which IP address? The local one or the public one of the router? I
> suspect the former.
the ip of the tomcat server.... i.e.
192.168.1.254
from which
.....65:8081 should be visible.
>
>> http access to tomcat from windows. Nothing telnet access to tomcat
>> ip port Nothing
>>
>> wired access to tomcat from a.n.other no problem
>
> You mean when you try to reach Tomcat's HTTP port from a machine
> hard-wired on the network using the local IP, it works fine?
No, sorry , I lie
Oops, Google chrom could not connect to
192.168.65:8081
>
> To summarize, you can ping from anywhere but HTTP only works when you
> use a hard-wired client? Odd.
ping works from both wired/wireless to the 'main' wired machine
containing the tomcat server
>
> What if you hard-wire the Windows box?
I have both... neither works (sorry)
>
>> I've got Zone alarm on the windows box.
>
> Does it have any rules concerning outbound traffic? It might be
> blocking lots of stuff to the local network.
Outbound?
I presumed the block (if there was one) was inbound, http
from 'trusted zone'
>
>> I think I have set it to pass through for 'trusted' zone on my
>> local net.
>
> Okay, maybe not.
>
> Some routers have AP-isolation features where the WiFi clients can
> only get to the "outside" of the network, and can't contact local
> machines. But since you can ping the local machine that seems to rule
> that out.
IMHO
I can ping it... does that necessarily mean I can get http connections?
>
>> Can anyone think of more 'blocks' to seeing the server please?
>
> As far as the Linux machine is concerned, there is no difference
> between a WiFi and hard-wired client, as long as they are in the same
> IP range. I'm not sure you could configure iptables to restrict based
> upon that criteria alone. Is iptables running? What rules does it have?
Sorry.. excuse my ignorance, but how to check?
>
> Windows has a built-in firewall, but I believe it's configured out of
> the box to allow anything to call-out to port 80. I'm not sure about
> 8080. If you have ZoneAlarm, does that mean you have 2 software
> firewalls in the mix on that machine? You may want to check *both*
> their settings.
I believe I have switched off the M$ firewall, since I have zonealarm running?
>
> Finally, the router can do weird things, too. Check your settings for
> anything "restriction-related".
It's a BT (our national phone company) router+wifi
I haven't found anything strictly ip to ip mapping related.
That is one of the potential blockers.
regards
--
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.
http://www.dpawson.co.uk
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: wifi access to tomcat on wired mc
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Dave,
On 11/27/13, 11:18 AM, Dave Pawson wrote:
> Scenario. Tomcat install on Linux, wired to router. Windows 7
> connected to router via wifi.
>
> from windows.
>> ping ip.address no problem
Which IP address? The local one or the public one of the router? I
suspect the former.
> http access to tomcat from windows. Nothing telnet access to tomcat
> ip port Nothing
>
> wired access to tomcat from a.n.other no problem
You mean when you try to reach Tomcat's HTTP port from a machine
hard-wired on the network using the local IP, it works fine?
To summarize, you can ping from anywhere but HTTP only works when you
use a hard-wired client? Odd.
What if you hard-wire the Windows box?
> I've got Zone alarm on the windows box.
Does it have any rules concerning outbound traffic? It might be
blocking lots of stuff to the local network.
> I think I have set it to pass through for 'trusted' zone on my
> local net.
Okay, maybe not.
Some routers have AP-isolation features where the WiFi clients can
only get to the "outside" of the network, and can't contact local
machines. But since you can ping the local machine that seems to rule
that out.
> Can anyone think of more 'blocks' to seeing the server please?
As far as the Linux machine is concerned, there is no difference
between a WiFi and hard-wired client, as long as they are in the same
IP range. I'm not sure you could configure iptables to restrict based
upon that criteria alone. Is iptables running? What rules does it have?
Windows has a built-in firewall, but I believe it's configured out of
the box to allow anything to call-out to port 80. I'm not sure about
8080. If you have ZoneAlarm, does that mean you have 2 software
firewalls in the mix on that machine? You may want to check *both*
their settings.
Finally, the router can do weird things, too. Check your settings for
anything "restriction-related".
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.15 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBCAAGBQJSliecAAoJEBzwKT+lPKRY7W4P/Atx3bCLTPtUbE24oQS80jqf
YrPQd7aX62ewJ3IzkSEV6XFsAih98S8fCPcrCw0zwDqCWnb72At5oiu5ovtGjKVd
fJM/2CO1Vu4P3Zq8C8X/J7Iq9E7SsY7b9GyikUzE85PBpU3QLBsGkGxv5Io7EtJO
qVJse4CtgO1UHu6/HOGlPspFwz+NA0HQIOUVSSI7XDqlr10ZlryhSzN4mgvy5DvH
fYzZ5UFdw8gHPcKLakwOjK6wtdUcFyzq5QjaIJU3XdLAAqRKAn8/nNTZu8Olo8Xw
UZL5LYt5CChmAvpC5NouKyVEBtJMB1gxvD43uZoG659Bf9nBeL9aemWdID1u7tyb
nsaeFMQW984Rg3HytWoG4xcChawslbfvkCYM9eDnO0QH/92WqhM3I4djuSj+VDqu
b7BZd0UjWTFcxRfKOV+pbx/v99s5io4rngvIjORfF7HEYCFXg5HV0Uh/PgfxwOSy
HD54YErNTWY6q/xZNMRUFb4R6ZTQ2O9kCsu4tjsJALkjCJdIAMRRdwNeIS1AOMdM
+9lRoYzfGSwu4JInBDnHrp+utEpsyKl//Lo2HEcCKB7Xwh7ATGnkzveM/jkfzG6G
RzQDvj9lvglBBNcXVC6j0ZoRUEhlvmEp2bLSH+eJmCr98exBHn51Ua/f1IzJXPBL
/26EhxvYurCpmdMlMrqi
=89WD
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org