I am having a bizarre problem and I'm not real sure where the problem exist. I have my linux box on a wireless network with a D-link DI-624 wireless router.

I have tried to set up telnet, ssh, and postfix however I cannot get a connection from either my LAN or WAN. When I try to connect via telnet or ssh to this machine from another machine I get "no route to host". I could never get postfix up and running (for what I believe is the same reason).

The wireless router does have a firewall and I have set it up to allow these connections through the LAN and WAN. Now here is the bizarre thing, the web server work on both the WAN and LAN using Apache.

I think the problem exists with the router but I not sure if it is not in my linux box configuration. Any help or suggestions, thanks.


Milton Griggs

Have you tried to ping your router from this troublesome linux box?

what does the following commands have to say

#dmesg|grep eth
#/sbin/ifconfig -a
#netstat -r

1) I have ping the router and it responds back.

2) Output of dmeg |grep eth
(nothing...there is no entry for eth)
Here is the output of dmeg |grep ath (My wireless card is using ath0 as the interface)
ath_hal: 0.9.8.6
ath_pci: 0.8.5.5 BETA
ath_pci: 0.8.5.5 BETA
divert: allocating divert_blk for ath0
ath0: mac 5.6 phy 4.1 5ghz radio 4.6
ath0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
ath0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
ath0: 802.11 address: 00:0d:88:64:49:dd
ath0: Atheros 5212: mem=0xd4000000, irq=10
divert: freeing divert_blk for ath0
ath_pci: driver unloaded
ath_hal: driver unloaded
ath_hal: 0.9.8.6
ath_pci: 0.8.5.5 BETA
ath_pci: 0.8.5.5 BETA
divert: allocating divert_blk for ath0
ath0: mac 5.6 phy 4.1 5ghz radio 4.6
ath0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
ath0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
ath0: 802.11 address: 00:0d:88:64:49:dd
ath0: Atheros 5212: mem=0xd4000000, irq=10

3) Output of /sbin/ifconfig -a

ath0 Link encap:Ethernet HWaddr 00:0D:88:64:49D
inet addr:192.168.0.100 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:128450 errors:2459818 dropped:0 overruns:0 frame:2456242
TX packets:11167 errors:82 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:199
RX bytes:23356231 (22.2 Mb) TX bytes:2574060 (2.4 Mb)
Interrupt:10 Memory:d0960000-d0970000

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:2430 errors:0 dropped:0 overruns:0 frame:0
TX packets:2430 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1876967 (1.7 Mb) TX bytes:1876967 (1.7 Mb)

4)Output of netstat -r

kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
192.168.0.0 * 255.255.255.0 U 0 0 0 ath0
169.254.0.0 * 255.255.0.0 U 0 0 0 lo
127.0.0.0 * 255.0.0.0 U 0 0 0 lo
default 192.168.0.1 0.0.0.0 UG 0 0 0 ath0

thanks again
Milton

Ensure sshd and postfix services are running

#service sshd status
#service postfix status

shut down iptables

#service iptables stop

and check whether you can connect to your linux box

Also make sure /etc/hosts.allow and /etc/hosts.deny do not have any restrictive entries.

Flusing the iptables work. Now, the question is having the tables flushed a good idea...I would like to edit these tables if possible.


Thanks again
Milton

It is a very bad idea not to have iptables running. I just wanted to make sure it is not iptables that is filtering the connections.

If you allowed RedHat installation to configure your iptables, you will need to flush those rules and write a customised iptables script.

The Security sectionl of LQ will have a lot of stuff to read and a lot of sample scripts that will help you setup your customized iptables.