• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 513
  • Last Modified:

centos wireless NetworkManager

hello there,
I have NetworkManager installed on my laptop running on centos v5.7
I am able to connect with lan and browse websites and connect trough ssh from my win7 machine..
when I connect trough wireless I am only able to browse but no ssh access or http access..
the iptables is not running what could it be?
0
XK8ER
Asked:
XK8ER
  • 7
  • 7
  • 5
2 Solutions
 
PapertripCommented:
When the wireless is connected, run the following commands.
ifconfig -a
netstat -rnv

Open in new window

0
 
XK8ERAuthor Commented:
here's the results.. the address for the router is 6.6.6.6 and the address of the machine that I normally connect to is 6.6.6.122

eth0      Link encap:Ethernet  HWaddr 48:5B:39:81:1D:A8  
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:2028 errors:0 dropped:0 overruns:0 frame:0
          TX packets:790 errors:0 dropped:0 overruns:0 carrier:4
          collisions:0 txqueuelen:1000 
          RX bytes:190529 (186.0 KiB)  TX bytes:228659 (223.2 KiB)
          Interrupt:177 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:5015 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5015 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:5744559 (5.4 MiB)  TX bytes:5744559 (5.4 MiB)

wlan0     Link encap:Ethernet  HWaddr 1C:4B:D6:AE:32:5F  
          inet addr:6.6.6.122  Bcast:6.6.6.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:17753 errors:0 dropped:0 overruns:0 frame:0
          TX packets:9682 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:25275773 (24.1 MiB)  TX bytes:994488 (971.1 KiB)

Open in new window



Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
6.6.6.0         0.0.0.0         255.255.255.0   U         0 0          0 wlan0
0.0.0.0         6.6.6.6         0.0.0.0         UG        0 0          0 wlan0

Open in new window

0
 
PapertripCommented:
OK nothing suspicious there.

In your question you say:
I am able to connect with lan and browse websites and connect trough ssh from my win7 machine..
when I connect trough wireless I am only able to browse but no ssh access or http access..
What do you mean by you are only able to browse, but no http access.  I ask because you use browse in the wired example in relation to websites.  Just need a clarification.

Are you saying that once on the wireless, that you are unable to communicate with other devices on your LAN?
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
XK8ERAuthor Commented:
when its set on wireless..

connecting from win7 to laptop nothing works, port 22 or port 80 or any of that..
0
 
PapertripCommented:
What about connecting from the Linux machine to windows?  Let's see some traceroute output from both sides please.
0
 
XK8ERAuthor Commented:
what command exactly should I use?
0
 
parparovCommented:
What is your windows' IP?
What is your IP when connected via LAN?
0
 
PapertripCommented:
traceroute on Linux
tracert on Windows

Toss some ping outputs in here too.


FYI, all of these thing that parparov and I are asking are thing you should put into your original question.  The less time us experts have to spend prying all the info from you means less time until you get a correct answer :)
0
 
parparovCommented:
I would say address 6.6.6.6 is very strange - it is a real white IP address, and 6.0.0.0/8 address space is allocated to US armed forces.
0
 
XK8ERAuthor Commented:
[(12:16 AM)][(root@alpha)] [(~)] $ traceroute 6.6.6.111
traceroute to 6.6.6.111 (6.6.6.111), 30 hops max, 40 byte packets
 1  * * *
 2  * * *
 3  * * *
 4  * * *
 5  * * *
 6  * * *
 7  * * *
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *
[(12:18 AM)][(root@alpha)] [(~)] $ ping 6.6.6.111
PING 6.6.6.111 (6.6.6.111) 56(84) bytes of data.
64 bytes from 6.6.6.111: icmp_seq=1 ttl=128 time=1.74 ms
64 bytes from 6.6.6.111: icmp_seq=2 ttl=128 time=1.51 ms
64 bytes from 6.6.6.111: icmp_seq=3 ttl=128 time=1.52 ms
64 bytes from 6.6.6.111: icmp_seq=4 ttl=128 time=1.82 ms
64 bytes from 6.6.6.111: icmp_seq=5 ttl=128 time=1.53 ms
64 bytes from 6.6.6.111: icmp_seq=6 ttl=128 time=1.52 ms
64 bytes from 6.6.6.111: icmp_seq=7 ttl=128 time=1.94 ms

[1]+  Stopped                 ping 6.6.6.111
[(12:18 AM)][(root@alpha)] [(~)] $  
0
 
PapertripCommented:
OK now I'm concerned after parparovs last comment and from your last post... are the 6.6.6.x IP's fake addresses you made up just to sanitize your real IP's?
0
 
XK8ERAuthor Commented:
normally Router IP Address: 192.168.1.1 but I canged it to 6.6.6.6 since its faster to access each computer by just connecting to it like 6.6.6.122
thats the local ip address not internet.. and when I access my other windows xp boxes I use 6.6.6.110 etc..
now I have made a shared folder on the win7 and typed this

mount -t cifs //6.6.6.111/test -o username=admin,password=myPassword /mnt/win

now I am able to connect and its working.. weird issue..
0
 
parparovCommented:
You should never use a 6.x.x.x address in your home network. Unlike 192.168.x.x addresses they are not filtered for LAN routing and may cause collisions and drive routers crazy, since another computer in the world may use the same address. And in this specific case, a US Armed Forces computer.

If you want a prettier prefix, switch to 10.x.x.x.
0
 
XK8ERAuthor Commented:
okay, I know what the freaking issue is..
each time the screensaver goes on every minute the wireless goes dead.. any ideas how to disable that?
0
 
parparovCommented:
Or otherwise, in power management, you should notify power manager not to turn off the wifi
0
 
PapertripCommented:
Do NOT use public IP's on private networks!!!

http://en.wikipedia.org/wiki/Private_network

For small home networks just use 192.168.x.x
0
 
XK8ERAuthor Commented:
no, that's not it.. I give up. any other recommendations before I install centos v6?
I used to work fine with centos v6 but I had to install cenos v5.6 due to a software compatibility but if I cant access through ssh there is no hope.
0
 
PapertripCommented:
Before you throw in the towel, setup your network properly using only RFC 1918 addresses for the internal space.  Having it setup like you do WILL cause problems, I promise.
0

Featured Post

Configuration Guide and Best Practices

Read the guide to learn how to orchestrate Data ONTAP, create application-consistent backups and enable fast recovery from NetApp storage snapshots. Version 9.5 also contains performance and scalability enhancements to meet the needs of the largest enterprise environments.

  • 7
  • 7
  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now