Russell Senior
2007-10-08 01:23:46 UTC
David> I'm attempting to connect to the personal telco node at the
David> Hawthorne Hostel (NodeDB: 143) from my house about a block away
David> using a Linksys WET11 802.11b Wireless Ethernet Bridge because
David> it has a better antennae than my laptop. I've used the bridge
David> successfully before to get other signals, and when I bring my
David> laptop to within range of the hostel signal I can get internet
David> directly, but when I try to use the bridge it recognizes that
David> it is receiving the hawthorne node's signal but doesn't get an
David> IP address from the DCHP server. I've used it before
David> successfully with other wi-fi signals and didn't have this
David> problem. Any suggestions? Thanks in advance for your help.
I am cc'ing the general list in case someone knows the answer.
Generally speaking, I've seen all kinds of weirdness, including DHCP
failures, when using client bridges. The most direct solution is
probably to just statically configure your ip, netmask, gateway and
nameserver.
ipaddr: 10.11.100.x (pick an x where x > 5 and < 50)
netmask: 255.255.252.0 (yeah, that's a /22 network, not a /24)
gateway: 10.11.100.1
nameserver: 10.11.100.1
--
Russell Senior, Secretary
russell-LS+HbC+***@public.gmane.org
David> Hawthorne Hostel (NodeDB: 143) from my house about a block away
David> using a Linksys WET11 802.11b Wireless Ethernet Bridge because
David> it has a better antennae than my laptop. I've used the bridge
David> successfully before to get other signals, and when I bring my
David> laptop to within range of the hostel signal I can get internet
David> directly, but when I try to use the bridge it recognizes that
David> it is receiving the hawthorne node's signal but doesn't get an
David> IP address from the DCHP server. I've used it before
David> successfully with other wi-fi signals and didn't have this
David> problem. Any suggestions? Thanks in advance for your help.
I am cc'ing the general list in case someone knows the answer.
Generally speaking, I've seen all kinds of weirdness, including DHCP
failures, when using client bridges. The most direct solution is
probably to just statically configure your ip, netmask, gateway and
nameserver.
ipaddr: 10.11.100.x (pick an x where x > 5 and < 50)
netmask: 255.255.252.0 (yeah, that's a /22 network, not a /24)
gateway: 10.11.100.1
nameserver: 10.11.100.1
--
Russell Senior, Secretary
russell-LS+HbC+***@public.gmane.org
--
The Personal Telco Project - http://www.personaltelco.net/
Donate to PTP: http://www.personaltelco.net/donate
Un/Subscribe: http://lists.personaltelco.net/mailman/listinfo/general/
Archives: http://news.gmane.org/gmane.network.wireless.portland.general/
Etiquette: http://www.personaltelco.net/index.cgi/MailingListEtiquette
The Personal Telco Project - http://www.personaltelco.net/
Donate to PTP: http://www.personaltelco.net/donate
Un/Subscribe: http://lists.personaltelco.net/mailman/listinfo/general/
Archives: http://news.gmane.org/gmane.network.wireless.portland.general/
Etiquette: http://www.personaltelco.net/index.cgi/MailingListEtiquette