| Linux Forum Index » Linux Networking » home network setup: can't ping etc...... |
|
Page 1 of 1 |
|
| Author |
Message |
| John Goche... |
 Posted: Tue Oct 06, 2009 5:13 am |
|
|
|
Guest
|
Hello,
I have the following setup at home:
BelkinWirelessRouter: 192.168.2.1 (internal address)
LaptopSmall WindowsVista: 192.168.2.4
LaptopLarge WindowsVista: 192.168.2.8
PS3 YellowDogLinux: 192.168.2.7
I can browse the web from any laptop or PlayStation3
and each of the three internal computers can ping itself
via its own internal IP address or the default gateway
which is the wireless IP router (which probably also
runs some version of Linux). However while I can
happily browse the web from any of these three
internal computers I am running across the
following problems:
A. No internal computer can ping any other
internal computer other than itself and
the router.
B. No internal computer can ping any other
computer on the internet from the external
interface of the router (which has a proper
IP address as can be seen via traceroute
on Linux or tracert on Windows Vista Home
Premium).
C. I want to shell in from Windows Vista using
putty to my YDL 6.2 Linux PlayStation3
but each time I try the network is
unreachable.
D. I want the PlayStation3 which runs the apache
web server (and during YDL 6.2 installation I
chose not to run the firewall for web requests
to the PS3 so I should be able to use apache
web server on it) to answer HTTP and HTTPS
requests from both the inside (internal network)
and the outside (through the router's external
interface from computers on the network).
What should I do? Should I try and reconfigure
the Belkin Router by connecting to it via
hypertext protocol?
And then I guess I should configure NAT on the
Belkin Wireless router so that any HTTP or
HTTPS requests on it are directed to the PS3?
Thanks,
John Goche |
|
|
| Back to top |
|
|
|
| David Schwartz... |
| Posted: Tue Oct 06, 2009 8:40 am |
|
|
|
Guest
|
On Oct 6, 8:13 am, John Goche <johngoch... at (no spam) googlemail.com> wrote:
Quote: What should I do? Should I try and reconfigure
the Belkin Router by connecting to it via
hypertext protocol?
Yes, you're getting the router's default behavior, which is what most
people want, but not what *you* want.
DS |
|
|
| Back to top |
|
|
|
| John Goche... |
| Posted: Thu Oct 08, 2009 2:42 am |
|
|
|
Guest
|
On Oct 6, 4:13 pm, John Goche <johngoch... at (no spam) googlemail.com> wrote:
Quote:
I have the following setup at home:
BelkinWirelessRouter: 192.168.2.1 (internal address)
LaptopSmall WindowsVista: 192.168.2.4
LaptopLarge WindowsVista: 192.168.2.8
PS3 YellowDogLinux: 192.168.2.7
Thank you all for your replies.Indeed all of the above are wireless
connections.
Since the BelkinWirelessRouter supports both wireless as well as wired
sconnection I have connected LaptopLarge to BelkinWirelesRouter
as suggested and rebooted the laptop. Upon finishing the reboot
the laptop obtained another IP address for the wired connection
so that 192.168.2.8 is the IP address corresponding to the
wireless interface whereas 192.168.2.9 is the IP address
corresponding to the wired interface both on the same
laptop. As a result to this, as suggested, because of
the cable connection being more secure than the
wireless connection from the point of view of the
router manufacturers, I can now establish an
HTTP connection to the router which allows
me to configure it as pleased by just opening
my web browser to:
http://192.168.2.1/
So to summarise I now have:
BelkinWirelessRouter: 192.168.2.1 (internal address)
LaptopSmall WindowsVista: 192.168.2.4 (wireless link)
LaptopLarge WindowsVista: 192.168.2.8 (wireless link)
LaptopLarge WindowsVista: 192.168.2.9 (wired link)
PS3 YellowDogLinux: 192.168.2.7 (wireless link)
Furthermore I can now ping as follows:
LaptopLarge> ping 192.168.2.8 [successful]
LaptopLarge> ping 192.168.2.9 [successful]
LaptopLarge> ping 192.168.2.1 [successful]
LaptopLarge> ping 192.168.2.4 [successful]
LaptopLarge> ping 192.168.2.7 [Reply from localhost: Dst.
unreachable.]
LaptopSmall> ping 192.168.2.8 [Reply from localhost: Dst.
unreachable.]
LaptopSmall> ping 192.168.2.9 [successful]
LaptopSmall> ping 192.168.2.1 [successful]
LaptopSmall> ping 192.168.2.4 [successful]
LaptopSmall> ping 192.168.2.7 [Reply from localhost: Dst.
unreachable.]
PS3> ping 192.168.2.8 [Reply from localhost: Dst. unreachable.]
PS3> ping 192.168.2.9 [Reply from localhost: Dst. unreachable.]
PS3> ping 192.168.2.1 [successful]
PS3> ping 192.168.2.4 [successful]
PS3> ping 192.168.2.7 [Reply from localhost: Dst. unreachable.]
and I can browse the web from any of the three computers.
However what still I cannot understand is:
a) How come LaptopSmall can only ping LaptopLarge on the wired
and not on the wireless interface?
b) How come PS3 cannot be pinged from either laptop computer?
c) How come PS3 cannot ping any laptop computer?
Furthermore as for the suggestion regarding using tcpdump,
on the Linux box I try the following and get the following
response so I am not sure if the syntax is wrong or something:
$ /usr/sbin/tcpdump -n
tcpdump: no suitable device found
$
Thank you for your replies and thanks for all your help,
Best Regards,
John Goche |
|
|
| Back to top |
|
|
|
| David Schwartz... |
| Posted: Thu Oct 08, 2009 1:59 pm |
|
|
|
Guest
|
On Oct 8, 5:42 am, John Goche <johngoch... at (no spam) googlemail.com> wrote:
Quote: LaptopLarge WindowsVista: 192.168.2.8 (wireless link)
LaptopLarge WindowsVista: 192.168.2.9 (wired link)
I think this is an illogical setup. The router likely bridges the
wireless and wired networks, and it makes no sense for a machine with
a weak network model to have two interfaces normally configured in the
same segment.
The problem with tcpdump is that you didn't tell it what interface to
listen on. You need a '-i ethX' parameter.
DS |
|
|
| Back to top |
|
|
|
| terryc... |
| Posted: Thu Oct 08, 2009 5:03 pm |
|
|
|
Guest
|
On Tue, 06 Oct 2009 08:13:26 -0700, John Goche wrote:
Quote: Hello,
I have the following setup at home:
BelkinWirelessRouter: 192.168.2.1 (internal address)
LaptopSmall WindowsVista: 192.168.2.4 LaptopLarge WindowsVista:
192.168.2.8 PS3 YellowDogLinux: 192.168.2.7
I can browse the web from any laptop or PlayStation3 and each of the
three internal computers can ping itself via its own internal IP address
or the default gateway which is the wireless IP router (which probably
also runs some version of Linux). However while I can happily browse the
web from any of these three internal computers I am running across the
following problems:
A. No internal computer can ping any other
internal computer other than itself and the router.
What does netstat -nr show
It should have something like
192.168.2.0 netmask = 255.255.255.0 gw=eth0
as well as
0.0.0.0 netmask= 0.0.0.0 gw = 192.168.2.1
> |
|
|
| Back to top |
|
|
|
| John Goche... |
| Posted: Fri Oct 09, 2009 6:51 am |
|
|
|
Guest
|
On Oct 9, 12:59 am, David Schwartz <dav... at (no spam) webmaster.com> wrote:
Quote: On Oct 8, 5:42 am, John Goche <johngoch... at (no spam) googlemail.com> wrote:
LaptopLarge WindowsVista: 192.168.2.8 (wireless link)
LaptopLarge WindowsVista: 192.168.2.9 (wired link)
I think this is an illogical setup. The router likely bridges the
wireless and wired networks, and it makes no sense for a machine with
a weak network model to have two interfaces normally configured in the
same segment.
Fair enough. Anyways, once I connected LaptopLarge to the BelkinRouter
via an ethernet cable anything that can ping the BelkinRouter can also
ping LaptopLarge on the ethernet interface (but not on the wireless
interface) and conversely LaptopLarge can ping anything that the
BelkinRouter could ping provided it was capable of doing so.
I agree that it is not necessary to have both interfaces on the laptop
connected to the same router but I just wanted to experiment with
my internal local area network configuration.
I also would like to point out that with Windows Vista Home Premium
when a computer is left in such a state where the person in front of
it
does not type anything at the keyboard or move the mouse for some
period of time I think it goes in a state whereby it is said to be
in hybernation or asleep or something like that. In such a case
the computer will not respond to ping requests even when it
receives them until the user in front of it types something or
moves the mouse. OTOH I don't think such behavior would
ever happen on Linux given that it is designed to be
multiuser from the start.
Quote: The problem with tcpdump is that you didn't tell it what interface to
listen on. You need a '-i ethX' parameter.
Thank you, I should have checked the man page. Anyway the PS3
running YDL 6.2 Linux is connected via its wireless interface to the
router so the name of the device is actually wlan0:
Here is what I see with tcpdump when I ping
from LaptopSmall (interface IP address 192.168.2.4 (wireless)):
[root at (no spam) localhost johngoche]# /usr/sbin/tcpdump -i wlan0
tcpdump: verbose output suppressed, use -v or -vv for full protocol
decode
listening on wlan0, link-type EN10MB (Ethernet), capture size 96 bytes
17:37:20.461861 arp who-has 192.168.2.1 tell 192.168.2.9
17:37:20.463226 IP 192.168.2.7.50135 > 192.168.2.1.domain: 57007+
PTR? 1.2.168.192.in-addr.arpa. (42)
17:37:20.493502 IP 192.168.2.1.domain > 192.168.2.7.50135: 57007
NXDomain 0/0/0 (42)
17:37:20.493922 IP 192.168.2.7.47787 > 192.168.2.1.domain: 10187+
PTR? 9.2.168.192.in-addr.arpa. (42)
17:37:20.509480 IP 192.168.2.1.domain > 192.168.2.7.47787: 10187
NXDomain 0/0/0 (42)
17:37:20.509996 IP 192.168.2.7.57222 > 192.168.2.1.domain: 12210+
PTR? 7.2.168.192.in-addr.arpa. (42)
17:37:20.529538 IP 192.168.2.1.domain > 192.168.2.7.57222: 12210
NXDomain 0/0/0 (42)
17:37:25.461798 arp who-has 192.168.2.1 tell 192.168.2.7
17:37:25.463479 arp reply 192.168.2.1 is-at 00:17:3f:de:8b:09 (oui
Unknown)
17:37:29.641111 arp who-has 192.168.2.7 tell 192.168.2.4
17:37:29.641171 arp reply 192.168.2.7 is-at 00:1f:a7:4f:46:88 (oui
Unknown)
17:37:29.641541 IP 192.168.2.7.36325 > 192.168.2.1.domain: 12371+
PTR? 4.2.168.192.in-addr.arpa. (42)
17:37:29.658765 IP 192.168.2.1.domain > 192.168.2.7.36325: 12371
NXDomain 0/0/0 (42)
17:37:30.635525 arp who-has 192.168.2.7 tell 192.168.2.4
17:37:30.635559 arp reply 192.168.2.7 is-at 00:1f:a7:4f:46:88 (oui
Unknown)
17:37:31.667174 arp who-has 192.168.2.7 tell 192.168.2.4
17:37:31.667207 arp reply 192.168.2.7 is-at 00:1f:a7:4f:46:88 (oui
Unknown)
17:37:32.696979 arp who-has 192.168.2.7 tell 192.168.2.4
17:37:32.697014 arp reply 192.168.2.7 is-at 00:1f:a7:4f:46:88 (oui
Unknown)
17:37:33.725119 arp who-has 192.168.2.7 tell 192.168.2.4
17:37:33.725152 arp reply 192.168.2.7 is-at 00:1f:a7:4f:46:88 (oui
Unknown)
17:37:34.753986 arp who-has 192.168.2.7 tell 192.168.2.4
17:37:34.754014 arp reply 192.168.2.7 is-at 00:1f:a7:4f:46:88 (oui
Unknown)
17:37:35.785453 arp who-has 192.168.2.7 tell 192.168.2.4
17:37:35.785488 arp reply 192.168.2.7 is-at 00:1f:a7:4f:46:88 (oui
Unknown)
17:37:36.813395 arp who-has 192.168.2.7 tell 192.168.2.4
17:37:36.813429 arp reply 192.168.2.7 is-at 00:1f:a7:4f:46:88 (oui
Unknown)
17:37:37.842985 arp who-has 192.168.2.7 tell 192.168.2.4
17:37:37.843019 arp reply 192.168.2.7 is-at 00:1f:a7:4f:46:88 (oui
Unknown)
17:37:38.360234 arp who-has 192.168.2.7 tell 192.168.2.4
17:37:38.360268 arp reply 192.168.2.7 is-at 00:1f:a7:4f:46:88 (oui
Unknown)
17:37:39.387589 arp who-has 192.168.2.7 tell 192.168.2.4
17:37:39.387617 arp reply 192.168.2.7 is-at 00:1f:a7:4f:46:88 (oui
Unknown)
17:37:40.417082 arp who-has 192.168.2.7 tell 192.168.2.4
17:37:40.417116 arp reply 192.168.2.7 is-at 00:1f:a7:4f:46:88 (oui
Unknown)
[...snip...]
To me it seems like somehow PS3 is receiving the ARP requests
but the ARP replies do not seem to make it through the router
otherwise the LaptopSmall machine (192.168.2.4) running
Windows Vista would stop sending out ARP requests.
So how can I configure my PlayStation3 running Linux to
respond to ARP requests?
Quote: What does netstat -nr show
It should have something like
192.168.2.0 netmask = 255.255.255.0 gw=eth0
as well as
0.0.0.0 netmask= 0.0.0.0 gw = 192.168.2.1
Indeed here is the output on the PS3 running Linux:
[johngoche at (no spam) localhost ~]$ /bin/netstat -rn
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window
irtt Iface
192.168.2.0 0.0.0.0 255.255.255.0 U 0 0
0 wlan0
0.0.0.0 192.168.2.1 0.0.0.0 UG 0 0
0 wlan0
[johngoche at (no spam) localhost ~]$
Seems OK to me (192.168.2.1 is the router).
Thank you for your replies,
Any ideas of how I could proceed?
Thanks,
John Goche |
|
|
| Back to top |
|
|
|
| Wanna-Be Sys Admin... |
| Posted: Fri Oct 09, 2009 1:17 pm |
|
|
|
Guest
|
John Goche wrote:
Quote: Hello,
I have the following setup at home:
BelkinWirelessRouter: 192.168.2.1 (internal address)
LaptopSmall WindowsVista: 192.168.2.4
LaptopLarge WindowsVista: 192.168.2.8
PS3 YellowDogLinux: 192.168.2.7
....
Why are you posting the same questions on this group as two completely
different posting names and email addresses?
--
Not really a wanna-be, but I don't know everything. |
|
|
| Back to top |
|
|
|
| Allen McIntosh... |
| Posted: Sat Oct 10, 2009 6:56 am |
|
|
|
Guest
|
John Goche wrote:
Quote: Fair enough. Anyways, once I connected LaptopLarge to the BelkinRouter
via an ethernet cable anything that can ping the BelkinRouter can also
ping LaptopLarge on the ethernet interface (but not on the wireless
interface) and conversely LaptopLarge can ping anything that the
BelkinRouter could ping provided it was capable of doing so.
Suggests that the Belkin router has different rules for the wireless
network. Please RTFM.
Quote: [root at (no spam) localhost johngoche]# /usr/sbin/tcpdump -i wlan0
Forgot the -n
Quote: tcpdump: verbose output suppressed, use -v or -vv for full protocol
decode
listening on wlan0, link-type EN10MB (Ethernet), capture size 96 bytes
17:37:20.461861 arp who-has 192.168.2.1 tell 192.168.2.9
17:37:20.463226 IP 192.168.2.7.50135 > 192.168.2.1.domain: 57007+
PTR? 1.2.168.192.in-addr.arpa. (42)
-n would shut these off
Quote: 17:37:20.493502 IP 192.168.2.1.domain > 192.168.2.7.50135: 57007
NXDomain 0/0/0 (42)
17:37:20.493922 IP 192.168.2.7.47787 > 192.168.2.1.domain: 10187+
PTR? 9.2.168.192.in-addr.arpa. (42)
17:37:20.509480 IP 192.168.2.1.domain > 192.168.2.7.47787: 10187
NXDomain 0/0/0 (42)
[snip]
17:37:30.635525 arp who-has 192.168.2.7 tell 192.168.2.4
17:37:30.635559 arp reply 192.168.2.7 is-at 00:1f:a7:4f:46:88 (oui
Unknown)
17:37:31.667174 arp who-has 192.168.2.7 tell 192.168.2.4
17:37:31.667207 arp reply 192.168.2.7 is-at 00:1f:a7:4f:46:88 (oui
Unknown)
17:37:32.696979 arp who-has 192.168.2.7 tell 192.168.2.4
17:37:32.697014 arp reply 192.168.2.7 is-at 00:1f:a7:4f:46:88 (oui
Unknown)
17:37:33.725119 arp who-has 192.168.2.7 tell 192.168.2.4
17:37:33.725152 arp reply 192.168.2.7 is-at 00:1f:a7:4f:46:88 (oui
Unknown)
17:37:34.753986 arp who-has 192.168.2.7 tell 192.168.2.4
17:37:34.754014 arp reply 192.168.2.7 is-at 00:1f:a7:4f:46:88 (oui
Unknown)
17:37:35.785453 arp who-has 192.168.2.7 tell 192.168.2.4
17:37:35.785488 arp reply 192.168.2.7 is-at 00:1f:a7:4f:46:88 (oui
Unknown)
17:37:36.813395 arp who-has 192.168.2.7 tell 192.168.2.4
17:37:36.813429 arp reply 192.168.2.7 is-at 00:1f:a7:4f:46:88 (oui
Unknown)
17:37:37.842985 arp who-has 192.168.2.7 tell 192.168.2.4
17:37:37.843019 arp reply 192.168.2.7 is-at 00:1f:a7:4f:46:88 (oui
Unknown)
17:37:38.360234 arp who-has 192.168.2.7 tell 192.168.2.4
17:37:38.360268 arp reply 192.168.2.7 is-at 00:1f:a7:4f:46:88 (oui
Unknown)
17:37:39.387589 arp who-has 192.168.2.7 tell 192.168.2.4
17:37:39.387617 arp reply 192.168.2.7 is-at 00:1f:a7:4f:46:88 (oui
Unknown)
17:37:40.417082 arp who-has 192.168.2.7 tell 192.168.2.4
17:37:40.417116 arp reply 192.168.2.7 is-at 00:1f:a7:4f:46:88 (oui
Unknown)
[...snip...]
To me it seems like somehow PS3 is receiving the ARP requests
but the ARP replies do not seem to make it through the router
otherwise the LaptopSmall machine (192.168.2.4) running
Windows Vista would stop sending out ARP requests.
So how can I configure my PlayStation3 running Linux to
respond to ARP requests?
It **is** responding. Tcpdump is showing you that. In fact, given that
there is no second ARP following immediately after the first one, I
would guess that the reply gets back to the windows machine. This is
only a supposition however, and is not based on any facts.
Notice that the ARP requests are spaced approximately one second apart.
This might be consistent with the Belkin router dropping PINGs, not
ARPs. Again, this is based on supposition, not fact.
So what you are seeing is not inconsistent with the Belkin router
dropping PINGs on the wireless side. If you want to get facts to prove
or disprove this, you will have to install wireshark or something
similar on your Windows machines. (You could install on your Linux box
too if it's not already there.) Then you can watch both side of
attempts at pinging and server connection.
I would suggest
0) RTFM to see what the default router behavior is supposed to be
1) Connect everything up wired, with no wireless adapters turned on
2) RTFM
3) Install wireshark everywhere and use it to watch anything you try to do.
4) RTFM
(In your shoes I would not want to be running a server on the back side
of a wireless connection.) |
|
|
| Back to top |
|
|
|
| Pascal Hambourg... |
| Posted: Sat Oct 10, 2009 7:24 am |
|
|
|
Guest
|
Allen McIntosh a écrit :
Quote:
It **is** responding. Tcpdump is showing you that.
I agree.
Quote: In fact, given that
there is no second ARP following immediately after the first one, I
would guess that the reply gets back to the windows machine.
I disagree here. Why would there be a second ARP (request ?) following
immediately if the reply gets back to the Windows machine ?
Quote: Notice that the ARP requests are spaced approximately one second apart.
This might be consistent with the Belkin router dropping PINGs, not
ARPs.
I disagree again. The ARP reply is normally stored in the ARP cache for
several minutes, so there is no reason to send a new ARP request for
every IP packet to the same destination.
IMO the behaviour is consistent with the Windows machine not receiving
the ARP replies.
Quote: If you want to get facts to prove
or disprove this, you will have to install wireshark or something
similar on your Windows machines.
Before that, you can just check the ARP cache with arp -a. |
|
|
| Back to top |
|
|
|
| Allen McIntosh... |
| Posted: Sat Oct 10, 2009 9:52 am |
|
|
|
Guest
|
Pascal Hambourg wrote:
Quote: IMO the behaviour is consistent with the Windows machine not receiving
the ARP replies.
And with it sending one ARP per ping. You are correct. I had thought
that it would be more aggressive about ARPing, but that seems not to be
the case. |
|
|
| Back to top |
|
|
|
| John Goche... |
| Posted: Sun Oct 11, 2009 2:06 am |
|
|
|
Guest
|
On 10 Oct, 13:56, Allen McIntosh <nos... at (no spam) mouse-potato.com> wrote:
Quote: (In your shoes I would not want to be running a server on the back side
of a wireless connection.)
Well, the router is using WPA1/2 encryption rather than the flawed WEP
protocol so security should not be a problem. However I would agree
that
using an ethernet cable to connect the PS3 to the router would make it
a faster server.
Furthermore I have recently rebooted the router via the web interface
which I can access by connecting to http://192.168.2.1/ via a direct
wired connection. Once the reboot was complete for whatever reason
my Linux box was not able to receive its IP address, netmask address,
and default gateway address via DHCP. I cannot understand why this
would be the case. In fact from my PS3 with the Wicd 1.5.3 program
I just cannot see it any more and the ESSID does not seem to be
hidden either because I have tried searching for it as though it
were hidden and this did not work. I tried rebooting into the
PS3 GameOS with the command ps3-boot-game-os to see
if the GameOS could see the Belkin Router's signal or not
and the result was that when on the PS3 GameOS I went
to Settings -> System Settings -> System Information
there was no IP address (a dash appeared in its place).
But the Windows Vista computers are still connecting
to the Belkin Router so there seems to be a signal
problem which I find somewhat strange as I have
not really moved anything around. So now I have
this new problem which seems to be associated
with the wireless signal not getting through.
So I ordered an ethernet cable online (not sure if it makes
a difference but I got a CAT 6 FTP rather than UTP and
hopefully the extra shielding will keep interference from
Bluetooth devices down. I am going to use the cable
to go by the suggestion posted here that things be
made to work with cables first and only once this
is successful with wireless likns. Seems like it
could be a good approach to me.
As with regards to the Belkin Router, the worse part for
me is that I cannot shell into it to check the routing table
and must mess around with the web interface instead.
Is there a way I can retrieve the routing table of my
router in some nonobvious way?
Well, thanks for all your help,
John Goche |
|
|
| Back to top |
|
|
|
| John Goche... |
| Posted: Fri Oct 16, 2009 7:26 am |
|
|
|
Guest
|
On Oct 11, 1:06 pm, John Goche <johngoch... at (no spam) googlemail.com> wrote:
Hello,
I just wanted to post an update to the problems I was experiencing.
Basically I RTFM'd and my Belkin G Router does not seem to have
a setting that allows any computer to be pinged, ssh'd into, or http'd
for as long as the computer is connected wirelessly to the router. It
is a shame that I cannot change this setting as I am using WPA2
for authentication which is supposed to be cryptographically very
strong. Oh well, when I connect the computer to the router with
the cable I don't have this problem.
Furthermore upon rebooting my router I could not see any SSID
other than my neighbour's, but I figured out that this was because
the setting on the router for changing the channel was set to Auto
and unfortunately it was defaulting to channel 13 which could have
been the one corresponding to the same microwave EM frequency
as that used by my neighbour's router. When I changed the channel
number to a different number it all worked once again.
Regards,
John Goche |
|
|
| Back to top |
|
|
|
| Pascal Hambourg... |
| Posted: Fri Oct 16, 2009 2:25 pm |
|
|
|
Guest
|
John Goche a écrit :
Quote: Basically I RTFM'd and my Belkin G Router does not seem to have
a setting that allows any computer to be pinged, ssh'd into, or http'd
for as long as the computer is connected wirelessly to the router. It
is a shame that I cannot change this setting as I am using WPA2
for authentication which is supposed to be cryptographically very
strong.
So what ? IIUC, this feature is designed to protect wireless hosts
against attacks from other hosts on the network. WPA2 has nothing to do
with this, it would not protect from other authenticated hosts. |
|
|
| Back to top |
|
|
|
| John Goche... |
| Posted: Sun Oct 18, 2009 2:40 am |
|
|
|
Guest
|
On Oct 16, 9:25 pm, Pascal Hambourg <boite-a-s... at (no spam) plouf.fr.eu.org>
wrote:
Quote: John Goche a écrit :
Basically I RTFM'd and my Belkin G Router does not seem to have
a setting that allows any computer to be pinged, ssh'd into, or http'd
for as long as the computer is connected wirelessly to the router. It
is a shame that I cannot change this setting as I am using WPA2
for authentication which is supposed to be cryptographically very
strong.
So what ? IIUC, this feature is designed to protect wireless hosts
against attacks from other hosts on the network. WPA2 has nothing to do
with this, it would not protect from other authenticated hosts.
Well, the fact of it is that only hosts that have the WPA2 passphrase
which I have set up on the router via an ethernet cable (so nobody
could
sniff it) can connect to my wireless router. Since I am using the
access
point for home use, only people within my household know the WPA2
and thus are the only ones that can authenticate. Since I trust the
people in my household I should not have to be concerned.
Unfortunately, the Belkin G Router does not allow a wireless computer
whom has successfully authenticated with the router ping anohter
computer
on the private network of computers in my household internal to the
router.
Thanks,
John Goche |
|
|
| Back to top |
|
|
|
|
