Networking problem

JD jd1008 at gmail.com
Sun May 15 03:51:57 UTC 2011


On 05/14/11 19:59, James McKenzie wrote:
> On 5/14/11 7:41 PM, Kevin J. Cummings wrote:
>> On 05/14/2011 10:09 PM, JD wrote:
>>> On 05/14/11 18:45, James McKenzie wrote:
>>>> On 5/14/11 6:40 PM, JD wrote:
>>>>> On 05/14/11 18:24, Joe Zeff wrote:
>>>>>> On 05/14/2011 01:27 PM, JD wrote:
>>>>>>> I also brought the fedora firewall down, and retried to ping Fedora
>>>>>>> from Powerbook. No go!!
>>>>>> That means that it's not a firewall issue.  Check your router config to
>>>>>> see if it's set to allow pings inside the LAN.
>>>>> Thanx!
>>>>> I checked. The gateway has a built-in feature (program)
>>>>> to let you ping any client on the lan (or any ip on the public net).
>>>>> The gateway can ping both the powerbook and the fedora pc.
>>>>> no problems there.
>>>>> The fedora pc and the powerbook can ping the gw, and a third machine
>>>>> connected to the GW by ethernet, and can of course ping addresses
>>>>> on the public net.
>>>>> They (fedora pc and powerbook) cannot ping each other!
>>>>> Powerbook firewall is set to promiscuous mode.
>>>>> And as I had stated earlier, I even stopped iptables on the
>>>>> fedora pc, which puts it also in promiscuous mode (I assume).
>>>>> Still these two machines refuse to talk.
>>>>>
>>>> Can you use traceroute to communicate between the two of them?
>>>>
>>>> James McKenzie
>>>>
>>> Tried it.
>>> Tracerout is unable to get to target after 30 tries.
>>> All it shows is asterisks.
>> Sounds to me like traceroute is trying to go "direct" between machines....
>>
> That it is if the two devices exist on the same subnet, which is a bad
> thing for wireless.  Your suggestion on how to solve this is 'spot on'.
> Unless traffic is local, it should go to the gateway on wireless.  Wired
> is much different.
>
> James McKenzie
>
For wired machines, the intelligence is in the switch
which has no firmware, but programmed gate arrays
which make the packets go from one ether port to another
without blasting the packets at all the ports (which is what
hubs do).
Wireless is indeed very different in the sense that the intelligence
is in the software running on the router.
That is why I need to talk to at&t uverse to see what they can do
from remote.


More information about the users mailing list