- server with wireless NIC not accessible outside of LAN

PDA

View Full Version : server with wireless NIC not accessible outside of LAN


John Lukar
07-24-2004, 11:20 PM
Hi,

I have a linux RH9.0 with a wireless TEW-223PI(admtek) with their
8211 driver which I compile from source.


I have a linksys hub(not wireless) connected to cable modem which acts
as my internal DHCP server. I have another linksys hub(DHCP turned
OFF) connected to the wired HUB providing AP to all my wireless
desktops(XP) and this linux server with the TEW-223PI card.

like so.

-- cable modem ---> LAN HUB(dhcp)---->pc1 (LAN card)
|
|----->pc2 (LAN card)
|
|--->Wireless HUB (AP)---> pc3(wireless card)
|
|---------> laptop4 (wireless card)
|
|---------> linux RH9.0(wireless card)



The linux RH9.0 I setup initialy with a LAN connection(i.e. RJ45) to
the accesspont HUB so was not using the wireless card. I had setup
port forwarding on my LAN HUB(dhcp) and I could access the linux box
services from outside. DHCP assinged 192.168.1.104 to this linux
server.

This worked fine untill I switched the linux box to use the wireless
card(eth1) by loading the driver. It picked up the AP HUB signal
without a problem. The DHCP assigned 192.168.1.103 to this wireless
card. I of course had unplugged the LAN card eth0.

Now, from inside my LAN from laptop4 I can only access ssh ports and
ssh into my linux RH9.0. I can no longer access the webserver which I
used to be able to do. I can no longer access port 2401 which is my
CVS server port on linux RH9.0. From outside LAN I can not even ssh
any longer into my server. I get "connection to xxxx port 22,
permission denied" from outside of LAN.


I made sure I changed the IP address for port forwarding in my LAN HUB
that acts as the dhcp server and point of entry. (from 192.168.1.104
to newly assigned 192.168.1.103).

from inside LAN accessing the linux server, I can only access using
ssh port 22. No longer can I hit the web server. I can also not access
CVS server on port 2401.


Any ideas what is going on ?


the wireless card is TEW-223PI from trendnet with 8211 driver compiled
from source without problems.


thanks much as this thing is driving me crazy.

John Lukar.

David Cutting
07-24-2004, 11:20 PM
"John Lukar" <johnlukar@yahoo.com> wrote in message
news:e5815a1b.0402140048.7bddb000@posting.google.com...
> Hi,
>
> I have a linux RH9.0 with a wireless TEW-223PI(admtek) with their
> 8211 driver which I compile from source.
>
>
> I have a linksys hub(not wireless) connected to cable modem which acts
> as my internal DHCP server. I have another linksys hub(DHCP turned
> OFF) connected to the wired HUB providing AP to all my wireless
> desktops(XP) and this linux server with the TEW-223PI card.
[snip diagram etc...]

Indeed it is very strange. Can you connect to the remote interface
locally eg ssh into 192.168.whatever from the machine in question?

It /could/ be a listening problem.

Also; can you ping the machine from inside the LAN?

Cheers,

Dave.

David Efflandt
07-24-2004, 11:20 PM
On 14 Feb 2004 00:48:20 -0800, John Lukar <johnlukar@yahoo.com> wrote:
> Hi,
>
> I have a linux RH9.0 with a wireless TEW-223PI(admtek) with their
> 8211 driver which I compile from source.
>
>
> I have a linksys hub(not wireless) connected to cable modem which acts
> as my internal DHCP server. I have another linksys hub(DHCP turned
> OFF) connected to the wired HUB providing AP to all my wireless
> desktops(XP) and this linux server with the TEW-223PI card.
>
> like so.
>
> -- cable modem ---> LAN HUB(dhcp)---->pc1 (LAN card)
> |
> |----->pc2 (LAN card)
> |
> |--->Wireless HUB (AP)---> pc3(wireless card)
> |
> |---------> laptop4 (wireless card)
> |
> |---------> linux RH9.0(wireless card)
>
>
>
> The linux RH9.0 I setup initialy with a LAN connection(i.e. RJ45) to
> the accesspont HUB so was not using the wireless card. I had setup
> port forwarding on my LAN HUB(dhcp) and I could access the linux box
> services from outside. DHCP assinged 192.168.1.104 to this linux
> server.
>
> This worked fine untill I switched the linux box to use the wireless
> card(eth1) by loading the driver. It picked up the AP HUB signal
> without a problem. The DHCP assigned 192.168.1.103 to this wireless
> card. I of course had unplugged the LAN card eth0.
>
> Now, from inside my LAN from laptop4 I can only access ssh ports and
> ssh into my linux RH9.0. I can no longer access the webserver which I
> used to be able to do. I can no longer access port 2401 which is my
> CVS server port on linux RH9.0. From outside LAN I can not even ssh
> any longer into my server. I get "connection to xxxx port 22,
> permission denied" from outside of LAN.

Your terminology is confusing. What you refer to as a hub in this case is
more likely a broadband NAT gateway or router (most of which have switch
ports rather than hub ports). It is always best to use static IPs for
servers on a LAN (in same network, but outside of dhcp assigned range).

Your problem could be any number of problems. Maybe your PC can no longer
find an IP on itself for its own hostname. Maybe your servers are
configured for a hostname that no longer points to your IP. Maybe you
have other DNS, port forwarding. or firewall configuration issues. Check
the logs for your gateway/routers and Linux and apache to see if they give
any clue.

--
David Efflandt - All spam ignored http://www.de-srv.com/

John Lukar
07-24-2004, 11:21 PM
"David Cutting" <dcutting@spambuster.purplepixie.org> wrote in message news:
> > I have a linksys hub(not wireless) connected to cable modem which acts
> > as my internal DHCP server. I have another linksys hub(DHCP turned
> > OFF) connected to the wired HUB providing AP to all my wireless
> > desktops(XP) and this linux server with the TEW-223PI card.
> [snip diagram etc...]
>
> Indeed it is very strange. Can you connect to the remote interface
> locally eg ssh into 192.168.whatever from the machine in question?

yes. I can ssh localy and I found out remotely as well.

I can ssh from outside of my LAN passed the cable mode and router into
linux server which means the port forwarding I setup on my router,
works fine for port 22(ssh).


>
> It /could/ be a listening problem.
>
> Also; can you ping the machine from inside the LAN?

yes I can.


John.

John Lukar
07-24-2004, 11:21 PM
efflandt@xnet.com (David Efflandt) wrote in message news:<slrnc2spb0.o90.e
>
> Your terminology is confusing. What you refer to as a hub in this case is
> more likely a broadband NAT gateway or router (most of which have switch
> ports rather than hub ports). It is always best to use static IPs for
> servers on a LAN (in same network, but outside of dhcp assigned range).
>

probably because I am a little confused between the two.

One is a Linksys Etherfast router(BEFSR41) with 4 port connecters and
build in firewall administered through a web interface which is
connected to cable modem and is the DHCP server.


The other is a Wireless linksys router with 4 port switch that
provides the AP and connects using a cable directly to the router
above.


> Your problem could be any number of problems. Maybe your PC can no longer
> find an IP on itself for its own hostname. Maybe your servers are
> configured for a hostname that no longer points to your IP. Maybe you
> have other DNS, port forwarding. or firewall configuration issues. Check
> the logs for your gateway/routers and Linux and apache to see if they give
> any clue.

I use the Dynamically assigned IP address in the configuration of the
firewall for port forwarding. At no point do I use the hostname of
the linux server.

I know this is not very good to do as internal dynamicaly assigned
IP's are bound to change but I just wanted to get it up and running
quickly.


I'll check the logs to get a clue.

btw. I can ssh from outside and inside into my linux box using the
wireless LAN card. so this means that port forwarding on port 22 is
working at least. But just can get the webserver or CVS traffic
forwarded for some reason.


thanks much
John.

David Cutting
07-24-2004, 11:21 PM
"John Lukar" <johnlukar@yahoo.com> wrote in message
news:e5815a1b.0402151244.3a9a32fe@posting.google.com...
> "David Cutting" <dcutting@spambuster.purplepixie.org> wrote in message
news:
> > > I have a linksys hub(not wireless) connected to cable modem which acts
> > > as my internal DHCP server. I have another linksys hub(DHCP turned
> > > OFF) connected to the wired HUB providing AP to all my wireless
> > > desktops(XP) and this linux server with the TEW-223PI card.
> > [snip diagram etc...]
> >
> > Indeed it is very strange. Can you connect to the remote interface
> > locally eg ssh into 192.168.whatever from the machine in question?
> yes. I can ssh localy and I found out remotely as well.
>
> I can ssh from outside of my LAN passed the cable mode and router into
> linux server which means the port forwarding I setup on my router,
> works fine for port 22(ssh).
[snip]
> > Also; can you ping the machine from inside the LAN?
>
> yes I can.

Hi,

Erm - the only thing I can think of (and it is probably not
it) is that it is a interface listening problem and the Apache
etc... are not bound for the eth1 interface.

From the local machine can you telnet into (a) 127.0.0.1
and (b) 192.168.X the IP address of the eth1 card on
port 80?

I can't recall a specific bind-to-interface option in Apache
which makes is even more bizzare if it is.

Cheers,

Dave.