6:49 p.m.
My main box is an FC3 linux box wire coupled to a Linksys router WRT54G.
I have two laptops wireless coupled to the router. One laptop runs
Windows 2000 the other Windows XP. The laptops can ping all boxes but
the linux box can't ping the laptops. All boxes access the internet
through the router without any problem whatsoever. In addition I have
two printers wire coupled to the router and all boxes can print on any
printer.
The routing table on the linux box is:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
192.168.1.0 * 255.255.255.0 U 0 0 0 eth0
169.254.0.0 * 255.255.0.0 U 0 0 0 eth0
default 192.168.1.1 0.0.0.0 UG 0 0 0 eth0
It looks quite primitive to me compared to what I see on the windows
boxes, so I assume something is wrong with - but what? How can I
customise the routing table so that I can ping the laptops?
Also it contains a destination address of 169.254.0.0 which I don't know
and which I have not added to the table myself. What could it be and who
has put it into my routing table?
Thanks in advance for any help that might bring me closer to a solution
to this "mysterious" problem.
--
Regards,
Erik P. Olsen
7:01 p.m.
On Mon, 2006-03-13 at 01:49 +0100, Erik P. Olsen wrote:
My main box is an FC3 linux box wire coupled to a Linksys router
WRT54G.
I have two laptops wireless coupled to the router. One laptop runs
Windows 2000 the other Windows XP. The laptops can ping all boxes but
the linux box can't ping the laptops. All boxes access the internet
through the router without any problem whatsoever. In addition I have
two printers wire coupled to the router and all boxes can print on any
printer.
The routing table on the linux box is:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
192.168.1.0 * 255.255.255.0 U 0 0 0 eth0
169.254.0.0 * 255.255.0.0 U 0 0 0 eth0
default 192.168.1.1 0.0.0.0 UG 0 0 0 eth0
It looks quite primitive to me compared to what I see on the windows
boxes, so I assume something is wrong with - but what? How can I
customise the routing table so that I can ping the laptops?
Also it contains a destination address of 169.254.0.0 which I don't know
and which I have not added to the table myself. What could it be and who
has put it into my routing table?
You can ignore the 169.254 address. That is there due to the zeroconf
being enabled by default. You can disable this if you like.
You don't provide details on how you are trying to ping the other
systems from the linux box. Are you using their IP addresses or trying
to use their host names? You should be able to ping them using IP
addresses. Unless you are using DNS that contains all of your local
machines host names or have put those names in your /etc/hosts file.
Windows systems can utilize info collected using WINS and Netbios to
determine hostnames.
3:14 a.m.
Scot L. Harris wrote:
On Mon, 2006-03-13 at 01:49 +0100, Erik P. Olsen wrote:
>My main box is an FC3 linux box wire coupled to a Linksys router WRT54G.
>I have two laptops wireless coupled to the router. One laptop runs
>Windows 2000 the other Windows XP. The laptops can ping all boxes but
>the linux box can't ping the laptops. All boxes access the internet
>through the router without any problem whatsoever. In addition I have
>two printers wire coupled to the router and all boxes can print on any
>printer.
>
>The routing table on the linux box is:
>
>Kernel IP routing table
>Destination Gateway Genmask Flags Metric Ref Use
>Iface
>192.168.1.0 * 255.255.255.0 U 0 0 0 eth0
>169.254.0.0 * 255.255.0.0 U 0 0 0 eth0
>default 192.168.1.1 0.0.0.0 UG 0 0 0 eth0
>
>It looks quite primitive to me compared to what I see on the windows
>boxes, so I assume something is wrong with - but what? How can I
>customise the routing table so that I can ping the laptops?
>
>Also it contains a destination address of 169.254.0.0 which I don't know
>and which I have not added to the table myself. What could it be and who
>has put it into my routing table?
You can ignore the 169.254 address. That is there due to the zeroconf
being enabled by default. You can disable this if you like.
You don't provide details on how you are trying to ping the other
systems from the linux box. Are you using their IP addresses or trying
to use their host names? You should be able to ping them using IP
addresses. Unless you are using DNS that contains all of your local
machines host names or have put those names in your /etc/hosts file.
Windows systems can utilize info collected using WINS and Netbios to
determine hostnames.
I have been using both IP-addresses and host names and the host names are
correctly substituted by the corresponding IP-addresses.
Since you believe I should be able to ping them I'll leave the routing table
issue and look for inhibitors outside the linux box. Perhaps it's in the router?
I'll concentrate on that.
--
Regards,
Erik P. Olsen
7 a.m.
On Mon, 2006-03-13 at 10:14 +0100, Erik P. Olsen wrote:
I have been using both IP-addresses and host names and the host names
are
correctly substituted by the corresponding IP-addresses.
Since you believe I should be able to ping them I'll leave the routing table
issue and look for inhibitors outside the linux box. Perhaps it's in the router?
I'll concentrate on that.
One other thing to check is to make sure you don't have a firewall on
one or more of the boxes blocking communications.
10:06 a.m.
Scot L. Harris wrote:
On Mon, 2006-03-13 at 10:14 +0100, Erik P. Olsen wrote:
>I have been using both IP-addresses and host names and the host names are
>correctly substituted by the corresponding IP-addresses.
>
>Since you believe I should be able to ping them I'll leave the routing table
>issue and look for inhibitors outside the linux box. Perhaps it's in the router?
>I'll concentrate on that.
One other thing to check is to make sure you don't have a firewall on
one or more of the boxes blocking communications.
Yes, there is a firewall in the router and the XP box but since I have the same
problem with both W2K and XP I suspect the router.
--
Regards,
Erik P. Olsen
3 a.m.
On 3/13/06, Erik P. Olsen <erik(a)epo.dk> wrote:
Scot L. Harris wrote:
> On Mon, 2006-03-13 at 10:14 +0100, Erik P. Olsen wrote:
>
>
>>I have been using both IP-addresses and host names and the host names are
>>correctly substituted by the corresponding IP-addresses.
>>
>>Since you believe I should be able to ping them I'll leave the routing table
>>issue and look for inhibitors outside the linux box. Perhaps it's in the
router?
>>I'll concentrate on that.
>
>
> One other thing to check is to make sure you don't have a firewall on
> one or more of the boxes blocking communications.
>
Yes, there is a firewall in the router and the XP box but since I have the same
problem with both W2K and XP I suspect the router.
I think the IP is coming from the router, did you enable dhcp? Also
configure the firewall to allow you ping the box..
Do you have firewall configured on the Linux? you would need to check that...
--
Regards,
Erik P. Olsen
--
fedora-list mailing list
fedora-list(a)redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
4:36 p.m.
Erik P. Olsen wrote:
My main box is an FC3 linux box wire coupled to a Linksys router
WRT54G.
I have two laptops wireless coupled to the router. One laptop runs
Windows 2000 the other Windows XP. The laptops can ping all boxes but
the linux box can't ping the laptops.
Is your router assigning IPs from the same network to both the Linux
host and the wireless-attached hosts? If so, you can use tcpdump
(install it if you need to) and make sure that the Windows hosts are
responding to ARP requests.
As an example, if I want to observe the arp and ping to 172.20.111.6
from my workstation (wanderlust), I might use this command:
# tcpdump arp or host 172.20.111.6
I could be more specific, but that will work. Now, if I ping that host
in another terminal, I see these three lines printed from tcpdump:
14:29:47.317821 arp who-has 172.20.111.6 tell wanderlust
14:29:47.317975 arp reply 172.20.111.6 is-at 00:11:11:74:ca:7b
14:29:47.317986 IP wanderlust > 172.20.111.6: icmp 64: echo request seq 0
The first two are examples of what you should see. If you ping another
host in the same IP network, your workstation should request the MAC
address of the remote host. If it doesn't reply, it's possible that
your router isn't bridging broadcast traffic between the wired and
wireless attached networks. If *that* is the case, the best solution is
to configure the router to assign different IP networks to hosts in each
of the wired and wireless attached nets.
2:50 p.m.
New subject: Strange routing table (solved).
Gordon Messmer wrote:
Erik P. Olsen wrote:
> My main box is an FC3 linux box wire coupled to a Linksys router
> WRT54G. I have two laptops wireless coupled to the router. One laptop
> runs Windows 2000 the other Windows XP. The laptops can ping all boxes
> but the linux box can't ping the laptops.
Is your router assigning IPs from the same network to both the Linux
host and the wireless-attached hosts? If so, you can use tcpdump
(install it if you need to) and make sure that the Windows hosts are
responding to ARP requests.
As an example, if I want to observe the arp and ping to 172.20.111.6
from my workstation (wanderlust), I might use this command:
# tcpdump arp or host 172.20.111.6
I could be more specific, but that will work. Now, if I ping that host
in another terminal, I see these three lines printed from tcpdump:
14:29:47.317821 arp who-has 172.20.111.6 tell wanderlust
14:29:47.317975 arp reply 172.20.111.6 is-at 00:11:11:74:ca:7b
14:29:47.317986 IP wanderlust > 172.20.111.6: icmp 64: echo request seq 0
The first two are examples of what you should see. If you ping another
host in the same IP network, your workstation should request the MAC
address of the remote host. If it doesn't reply, it's possible that
your router isn't bridging broadcast traffic between the wired and
wireless attached networks. If *that* is the case, the best solution is
to configure the router to assign different IP networks to hosts in each
of the wired and wireless attached nets.
Thanks for all your help. I have now found the reason to my problems. Being a
newbie I wasn't aware that the iptables running on my linux box actually IS a
firewall and that it blocked any connect attempt from outside (blush). When I
opened for the port in question to tcp everything performed normally. It took me
many days of agony before I realised what it was, sigh.
Again, thanks a lot.
--
Regards,
Erik P. Olsen
6609
days inactive
6612
days old
7 comments
4 participants
participants (4)
-
Erik P. Olsen -
Gordon Messmer -
Oluwagbenga Shobowale -
Scot L. Harris