Re: WiFi Problems (It doesn't work properly)

OK, and your directly connected computer is working?

The central computer is connected to the same wireless router / modem which the laptop is connected to. It works nicely.

Is it running Linux or
Windows?

Windows XP Pro.

If it's working, we know that DHCP is working properly on the DSL
router, and it's correct that it should appear as the DNS IP.

That sounds good to me.

> an Ethernet Cable directly to the Router / Modem. This worked with
> normalcy (id est, every thing was coming in at the normal speed).
>
> Before we try anything else tell us:
>>
>> A) Make & Model of your DSL modem
>
> Siemens SpeedStream 6525 Router / Modem. This is not some thing one can
> buy; it came as a gift from Sympatico.

You're not kidding. Siemens seems to have closed it's whole home networking
line. Are you sure of that model number? Are you sure it's wireless?
(Sorry, but one has to ask!)

Sorry, it's a 6520, not 6525. The rest is correct; even the wireless aspect/

Plug the system you're having trouble with into the router with an ethernet
cable, make sure you have a connection. Then do:

route

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
64.230.197.65   *               255.255.255.255 UH    0      0        0 ppp0
default         64.230.197.65    0.0.0.0         UG    0      0        0 ppp0

cat /etc/resolv.conf

nameserver 206.47.244.12
nameserver 207.47.244.12
search no-domain-set.bellcanada

cat /var/lib/dhcp*/*.leases

lease {
interface "ath0";
fixed-address 192.168.254.2;
option subnet-mask 255.255.255.0 ;
option routers 192.168.254.254;
option domain-name-servers 192.168.254.254;
option domain-name "no-domain-set.bellcanada ";
option dhcp-lease-time -1;
option dhcp-message-type 5;
option dhcp-server-identifier 192.168.254.254;
renew 2 2038/1/19 03:14:07;
rebind 2 2038/1/19 03:14:07;
expire 2 2038/1/19 03:14:07;
}
lease {
interface "ath0";
fixed-address 192.168.2.11;
option subnet-mask 255.255.255.0 ;
option routers 192.168.2.1;
option domain-name-servers 192.168.2.1;
option domain-name "no-domain-set.bellcanada";
option dhcp-lease-time 259200;
option dhcp-message-type 5;
option dhcp-server-identifier 192.168.2.1;
renew 6 2005/10/8 10:11:07;
rebind 0 2005/10/9 13:11:07;
expire 0 2005/10/9 22:11:07;
}
lease {
interface "wlan0";
fixed-address 192.168.2.13;
option subnet-mask 255.255.255.0;
option routers 192.168.2.1;
option domain-name-servers 192.168.2.1;
option host-name "your-8cfb5dbe8b";
option domain-name "no-domain-set.bellcanada";
option dhcp-lease-time 259200;
option dhcp-message-type 5;
option dhcp-server-identifier 192.168.2.1;
renew 2 2005/9/27 03:28:09;
rebind 3 2005/9/28 06:28:09;
expire 3 2005/9/28 15:28:09;
}
lease {
interface "ath0";
fixed-address 192.168.2.11;
option subnet-mask 255.255.255.0;
option routers 192.168.2.1;
option domain-name-servers 192.168.2.1;
option domain-name "no-domain-set.bellcanada";
option dhcp-lease-time 259200;
option dhcp-message-type 5;
option dhcp-server-identifier 192.168.2.1;
renew 0 2005/10/9 05:44:30;
rebind 1 2005/10/10 08:44:30;
expire 1 2005/10/10 17:44:30;
}

Then try to connect wirelessly and do the same.

Compare the results. They
should be exactly the same except for the metric & iface columns in the
"route" output, the actual IP issued in the lease, and the interface the
lease is for.

If you don't get an IP at all wirelessly, then try: "dhclient ath0" (or
whatever the wireless iface is) and report back.

I started to use dhclient ath0. It seems to work, I don't know what else I can do, so I do that.