Linux Debian support - Sudden networking problem - clients behind a firewall cannot connect

This is Interesting: Free IT Magazines  
Home > Archive > Linux Debian support > October 2004 > Sudden networking problem - clients behind a firewall cannot connect





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author Sudden networking problem - clients behind a firewall cannot connect
Madhusudan Singh

2004-10-22, 2:45 am

Hi

I run a home network with a Desktop (Slack 10) acting as the router. It has
two network interfaces - eth0 and wlan0. The wired interface eth0 is
connected to an ADSL network (runs dhclient). The wireless interface wlan0
is the local network.

This evening, after a long day at work, I shut down both machines. About an
hour ago, I switched on the system again and found to my horror that my
laptop (192.168.1.2, Debian Sarge) could not connect to anythin on the
internet.

Then I logged on to the desktop and found the same state of affairs. So,
thinking that DSL provider had shut things down, I rebooted the machine.
This time, it came up fine. However, my laptop still cannot get through (it
can ssh to the desktop just fine - so there is no problem with the wireless
network).

On the desktop, /sbin/route -n :

# /sbin/route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0
wlan0
141.213.240.0 0.0.0.0 255.255.248.0 U 0 0 0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 141.213.240.1 0.0.0.0 UG 0 0 0 eth0


Please help me debug what is going on. My /etc/dhcpd.conf :

# dhcpd.conf
#
# Configuration file for ISC dhcpd (see 'man dhcpd.conf')
#
default-lease-time 28800;
max-lease-time 86400;
option domain-name "msingh.org";
option domain-name-servers 192.168.1.1;
ddns-update-style ad-hoc;

subnet 192.168.1.0 netmask 255.255.255.0
{
option broadcast-address 192.168.1.255;
option routers 192.168.1.1;
range 192.168.1.3 192.168.1.3;
}
# I just restricted this because I was getting some wierd DHCP offers from
192.168.1.6 - I know this probably has nothing to do with it.

host host2
{
hardware ethernet xx:xx:xx:xx:xx:xx; # MAC address of my
laptop, suitably obfuscated
fixed-address 192.168.1.2;
}

Thanks.
Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com