Re: wifi network connection
Hello Good Day My name is sandra i saw your profile today at (nabble.com) and became intrested in you,i will also like to know you the more, and i want you to send an email to my email address, so i can give you my picture for you to know whom i believe we can move from here to next level I am waiting for your mail to my maill address ([EMAIL PROTECTED] ) Remeber the distance or colour does not matter but love matters alot in life with love sandra please reply to my email, ([EMAIL PROTECTED]) so i can give you my picture and will can move from here to next love. my lovely one, Remeber love and understading matters alot in life one love; Awaiting to hear from you soonest, Thanks and God bless you, Form sandra -- View this message in context: http://www.nabble.com/wifi-network-connection-tp14484085p18020709.html Sent from the Debian User mailing list archive at Nabble.com. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: wifi network connection
On 12/25/07, wanderlust <[EMAIL PROTECTED]> wrote: > У пн, 2007-12-24 у 13:43 +1100, hce пише: > > Hi, > > > > I am doing an experiment to set up a home wifi network. The setup is > > descripbed as follows: > > > > I have a laptop running Debian connected to the ISP via phone line > > (ppp), the laptop has also an ethernet port, I set it to 192.168.5.1 > > which connectes to a wifi router at Internet port. The wifi local LAN > > IP address to 192.168.2.1. The nameserver in laptop is assigned by > > ISP 139.134.2.190 and the default gw in laptop does not have an IP > > address, but the iface = ppp0. > > > > I have another desktop connect tot he wifi LAN via udhcpc, it gets the > > ip address 192.168.0.252 from DHCP server of wifi route. On the > > desktop, the nameserver in resolv.conf sets to 192.168.0.1 and default > > gw sets to 192.168.0.1. But, the desktop could not connect to the > > internet. Any help what I was missing? > > > > Thank you. > > > > Jim > > > > > > Here is an iptables config from my wifi-network: > > # Generated by iptables-save v1.3.8 on Tue Dec 25 13:24:19 2007 > *nat > :PREROUTING ACCEPT [63410:4479749] > :POSTROUTING ACCEPT [39259:2493913] > :OUTPUT ACCEPT [39199:2418755] > -A POSTROUTING -s 192.168.0.0/255.255.255.0 -o ppp0 -j MASQUERADE > -A POSTROUTING -s 192.168.1.0/255.255.255.0 -o ppp0 -j MASQUERADE > COMMIT > # Completed on Tue Dec 25 13:24:20 2007 > # Generated by iptables-save v1.3.8 on Tue Dec 25 13:24:20 2007 > *filter > :INPUT ACCEPT [4558907:4280157754] > :FORWARD ACCEPT [592010:86851941] > :OUTPUT ACCEPT [4204932:1208883656] > COMMIT > # Completed on Tue Dec 25 13:24:20 2007 > # Generated by iptables-save v1.3.8 on Tue Dec 25 13:24:20 2007 > *mangle > :PREROUTING ACCEPT [5151583:4367072131] > :INPUT ACCEPT [4558907:4280157754] > :FORWARD ACCEPT [592010:86851941] > :OUTPUT ACCEPT [4204932:1208883656] > :POSTROUTING ACCEPT [4797376:1295842013] > -A FORWARD -o ppp0 -p tcp -m tcp --tcp-flags SYN,RST SYN -m tcpmss --mss > 1400:1536 -j TCPMSS --clamp-mss-to-pmtu > COMMIT > # Completed on Tue Dec 25 13:24:20 2007 > > My configuration is: LAN (192.168.2.0) -> (192.168.2.254) wifi-router > (192.168.1.18) -> (192.168.1.1) InetServer (PPPoE connection) -> DSL > modem -> Provider > > Router is taking IP address via DHCP from InetServer, and InetServer is > taking DNS and etc from provider. > > Sincerely, > wanderlust Thanks wanderlust, it is really good reference of iptable set up. I'll change my iptables according to it. Thank you. Kind Regards, Jim
Re: wifi network connection
У пн, 2007-12-24 у 13:43 +1100, hce пише: > Hi, > > I am doing an experiment to set up a home wifi network. The setup is > descripbed as follows: > > I have a laptop running Debian connected to the ISP via phone line > (ppp), the laptop has also an ethernet port, I set it to 192.168.5.1 > which connectes to a wifi router at Internet port. The wifi local LAN > IP address to 192.168.2.1. The nameserver in laptop is assigned by > ISP 139.134.2.190 and the default gw in laptop does not have an IP > address, but the iface = ppp0. > > I have another desktop connect tot he wifi LAN via udhcpc, it gets the > ip address 192.168.0.252 from DHCP server of wifi route. On the > desktop, the nameserver in resolv.conf sets to 192.168.0.1 and default > gw sets to 192.168.0.1. But, the desktop could not connect to the > internet. Any help what I was missing? > > Thank you. > > Jim > > Here is an iptables config from my wifi-network: # Generated by iptables-save v1.3.8 on Tue Dec 25 13:24:19 2007 *nat :PREROUTING ACCEPT [63410:4479749] :POSTROUTING ACCEPT [39259:2493913] :OUTPUT ACCEPT [39199:2418755] -A POSTROUTING -s 192.168.0.0/255.255.255.0 -o ppp0 -j MASQUERADE -A POSTROUTING -s 192.168.1.0/255.255.255.0 -o ppp0 -j MASQUERADE COMMIT # Completed on Tue Dec 25 13:24:20 2007 # Generated by iptables-save v1.3.8 on Tue Dec 25 13:24:20 2007 *filter :INPUT ACCEPT [4558907:4280157754] :FORWARD ACCEPT [592010:86851941] :OUTPUT ACCEPT [4204932:1208883656] COMMIT # Completed on Tue Dec 25 13:24:20 2007 # Generated by iptables-save v1.3.8 on Tue Dec 25 13:24:20 2007 *mangle :PREROUTING ACCEPT [5151583:4367072131] :INPUT ACCEPT [4558907:4280157754] :FORWARD ACCEPT [592010:86851941] :OUTPUT ACCEPT [4204932:1208883656] :POSTROUTING ACCEPT [4797376:1295842013] -A FORWARD -o ppp0 -p tcp -m tcp --tcp-flags SYN,RST SYN -m tcpmss --mss 1400:1536 -j TCPMSS --clamp-mss-to-pmtu COMMIT # Completed on Tue Dec 25 13:24:20 2007 My configuration is: LAN (192.168.2.0) -> (192.168.2.254) wifi-router (192.168.1.18) -> (192.168.1.1) InetServer (PPPoE connection) -> DSL modem -> Provider Router is taking IP address via DHCP from InetServer, and InetServer is taking DNS and etc from provider. Sincerely, wanderlust -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: wifi network connection
Thanks Mihira, it works after I rebooted the wifi router. Thank you for your patient helps. Kind Regards, Jim On 12/25/07, hce <[EMAIL PROTECTED]> wrote: > On 12/26/07, Mihira Fernando <[EMAIL PROTECTED]> wrote: > > On Tue December 25 2007, hce wrote: > > > > > > Yes, I run the ppp manually. I did run iptable manually, but did not > > > seems anything added to the list? > > > > > > ~$ sudo /sbin/iptables -t nat -A POSTROUTING -o ppp0 -j MASQUERADE > > > > > > ~$ sudo /sbin/iptables -L > > > Chain INPUT (policy ACCEPT) > > > target prot opt source destination > > > > > > Chain FORWARD (policy ACCEPT) > > > target prot opt source destination > > > > > > Chain OUTPUT (policy ACCEPT) > > > target prot opt source destination > > > > > > > the ip forwarding is still enabled right ? > > > > > > Yes, I added net.ipv4.conf.default.forwarding=1 in /etc/sysctl.conf > > > > > > I also tried ifconfig eth1 down and run eth1 by udhcpc, but failed. > > > > > > $ sudo /sbin/udhcpc -i eth1 > > > udhcpc (v0.9.9-pre) started > > > Sending discover... > > > Sending discover... > > > Sending discover... > > > Lease failed: > > Why are you running dhcp client on eth1 ? its configured with a static IP. > > I tried to set static IP down and using dhcp client to test dhcp > server. But, does not make sense. > > > > ~$ cat /etc/resolv.conf > > > nameserver 203.49.70.20 > > > nameserver 139.134.2.190 > > > > > > Did that mean? Why ISP dhcp server did not respose? If that does not > > > work on my laptop, the wifi router won't get it work either? > > > > ISP dhcp server is not likely to respond to dhcp requests from eth1. your > > ppp > > is getting IPs from your ISP. Not eth1. > > Understand. > > > when both ppp0 and eth1 is up, run the following commands as root: > > > > These commands flushes out any iptables rules: > > #iptables --flush > > #iptables --table nat --flush > > #iptables --delete-chain > > #iptables --table nat --delete-chain > > > > These 2 commands gets NAT and forwarding on: > > #iptables --table nat --append POSTROUTING --out-interface ppp0 -j > > MASQUERADE > > #iptables --append FORWARD --in-interface eth1 -j ACCEPT > > I did those two commands, but still not working. > > ~$ sudo /sbin/iptables -L Chain INPUT (policy ACCEPT) > target prot opt source destination > > Chain FORWARD (policy ACCEPT) > target prot opt source destination > ACCEPT 0-- anywhere anywhere > > Chain OUTPUT (policy ACCEPT) > target prot opt source destination > > Should I make eth1 accept for both INPUT and OUTPUT as well? > > Thank you. > > Jim > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: wifi network connection
On 12/26/07, Mihira Fernando <[EMAIL PROTECTED]> wrote: > On Tue December 25 2007, hce wrote: > > > > Yes, I run the ppp manually. I did run iptable manually, but did not > > seems anything added to the list? > > > > ~$ sudo /sbin/iptables -t nat -A POSTROUTING -o ppp0 -j MASQUERADE > > > > ~$ sudo /sbin/iptables -L > > Chain INPUT (policy ACCEPT) > > target prot opt source destination > > > > Chain FORWARD (policy ACCEPT) > > target prot opt source destination > > > > Chain OUTPUT (policy ACCEPT) > > target prot opt source destination > > > > > the ip forwarding is still enabled right ? > > > > Yes, I added net.ipv4.conf.default.forwarding=1 in /etc/sysctl.conf > > > > I also tried ifconfig eth1 down and run eth1 by udhcpc, but failed. > > > > $ sudo /sbin/udhcpc -i eth1 > > udhcpc (v0.9.9-pre) started > > Sending discover... > > Sending discover... > > Sending discover... > > Lease failed: > Why are you running dhcp client on eth1 ? its configured with a static IP. I tried to set static IP down and using dhcp client to test dhcp server. But, does not make sense. > > ~$ cat /etc/resolv.conf > > nameserver 203.49.70.20 > > nameserver 139.134.2.190 > > > > Did that mean? Why ISP dhcp server did not respose? If that does not > > work on my laptop, the wifi router won't get it work either? > > ISP dhcp server is not likely to respond to dhcp requests from eth1. your ppp > is getting IPs from your ISP. Not eth1. Understand. > when both ppp0 and eth1 is up, run the following commands as root: > > These commands flushes out any iptables rules: > #iptables --flush > #iptables --table nat --flush > #iptables --delete-chain > #iptables --table nat --delete-chain > > These 2 commands gets NAT and forwarding on: > #iptables --table nat --append POSTROUTING --out-interface ppp0 -j MASQUERADE > #iptables --append FORWARD --in-interface eth1 -j ACCEPT I did those two commands, but still not working. ~$ sudo /sbin/iptables -L Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source destination ACCEPT 0-- anywhere anywhere Chain OUTPUT (policy ACCEPT) target prot opt source destination Should I make eth1 accept for both INPUT and OUTPUT as well? Thank you. Jim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: wifi network connection
On Tue December 25 2007, hce wrote: > > Yes, I run the ppp manually. I did run iptable manually, but did not > seems anything added to the list? > > ~$ sudo /sbin/iptables -t nat -A POSTROUTING -o ppp0 -j MASQUERADE > > ~$ sudo /sbin/iptables -L > Chain INPUT (policy ACCEPT) > target prot opt source destination > > Chain FORWARD (policy ACCEPT) > target prot opt source destination > > Chain OUTPUT (policy ACCEPT) > target prot opt source destination > > > the ip forwarding is still enabled right ? > > Yes, I added net.ipv4.conf.default.forwarding=1 in /etc/sysctl.conf > > I also tried ifconfig eth1 down and run eth1 by udhcpc, but failed. > > $ sudo /sbin/udhcpc -i eth1 > udhcpc (v0.9.9-pre) started > Sending discover... > Sending discover... > Sending discover... > Lease failed: Why are you running dhcp client on eth1 ? its configured with a static IP. > > ~$ cat /etc/resolv.conf > nameserver 203.49.70.20 > nameserver 139.134.2.190 > > Did that mean? Why ISP dhcp server did not respose? If that does not > work on my laptop, the wifi router won't get it work either? ISP dhcp server is not likely to respond to dhcp requests from eth1. your ppp is getting IPs from your ISP. Not eth1. when both ppp0 and eth1 is up, run the following commands as root: These commands flushes out any iptables rules: #iptables --flush #iptables --table nat --flush #iptables --delete-chain #iptables --table nat --delete-chain These 2 commands gets NAT and forwarding on: #iptables --table nat --append POSTROUTING --out-interface ppp0 -j MASQUERADE #iptables --append FORWARD --in-interface eth1 -j ACCEPT This has to get the ball rolling. Mihira. -- Random Quotes From Megas XLR Coop: You see? The mysteries of the Universe are revealed when you break stuff. Jamie: When in doubt, blow up a planet. Kiva: It's an 80 foot robot, if we can't see it, absolutely it's not here. Glorft Technician: Unnecessary use of force in capturing the Earthers has been approved. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: wifi network connection
On 12/26/07, Mihira Fernando <[EMAIL PROTECTED]> wrote: > On Tue December 25 2007, hce wrote: > > > > auto lo > > iface lo inet loopback > > > > # The primary network interface > > allow-hotplug eth1 > > iface eth1 inet static > > address 192.168.5.1 > > netmask 255.255.255.0 > > network 192.168.5.0 > > > > Thank you. > > > > Jim > You have no lines defining your ppp connection ? no matter, > Remove the up iptables line from /etc/network/interfaces and after the ppp is > up try running it from the command line to test if NAT is working. Yes, I run the ppp manually. I did run iptable manually, but did not seems anything added to the list? ~$ sudo /sbin/iptables -t nat -A POSTROUTING -o ppp0 -j MASQUERADE ~$ sudo /sbin/iptables -L Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination > the ip forwarding is still enabled right ? Yes, I added net.ipv4.conf.default.forwarding=1 in /etc/sysctl.conf I also tried ifconfig eth1 down and run eth1 by udhcpc, but failed. $ sudo /sbin/udhcpc -i eth1 udhcpc (v0.9.9-pre) started Sending discover... Sending discover... Sending discover... Lease failed: ~$ cat /etc/resolv.conf nameserver 203.49.70.20 nameserver 139.134.2.190 Did that mean? Why ISP dhcp server did not respose? If that does not work on my laptop, the wifi router won't get it work either? Thank you. Jim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: wifi network connection
On Tue December 25 2007, hce wrote: > > auto lo > iface lo inet loopback > > # The primary network interface > allow-hotplug eth1 > iface eth1 inet static > address 192.168.5.1 > netmask 255.255.255.0 > network 192.168.5.0 > > Thank you. > > Jim You have no lines defining your ppp connection ? no matter, Remove the up iptables line from /etc/network/interfaces and after the ppp is up try running it from the command line to test if NAT is working. the ip forwarding is still enabled right ? Mihira. -- Random Quotes From Megas XLR Coop: You see? The mysteries of the Universe are revealed when you break stuff. Jamie: When in doubt, blow up a planet. Kiva: It's an 80 foot robot, if we can't see it, absolutely it's not here. Glorft Technician: Unnecessary use of force in capturing the Earthers has been approved. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: wifi network connection
On 12/25/07, Mihira Fernando <[EMAIL PROTECTED]> wrote: > On Tue December 25 2007, hce wrote: > > > The iptables has already been installed. I added "up iptables -t nat > > -A POSTROUTING -o ppp0 -j MASQUERADE" to the /etc/network/interfaces > > and restarted networking, it did not work. I then rebooted the laptop, > > it still did not work. Now, ping from the desktop on wifi local > > network got backward, please see following result: > > > > # ping -c 2 www.google.com > > ping: www.google.com: Host name lookup failure > > > > > > Thank you. > > > > Jim > > Can you post your unedited /etc/network/interfaces here ? auto lo iface lo inet loopback # The primary network interface allow-hotplug eth1 iface eth1 inet static address 192.168.5.1 netmask 255.255.255.0 network 192.168.5.0 Thank you. Jim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: wifi network connection
On Tue December 25 2007, hce wrote: > The iptables has already been installed. I added "up iptables -t nat > -A POSTROUTING -o ppp0 -j MASQUERADE" to the /etc/network/interfaces > and restarted networking, it did not work. I then rebooted the laptop, > it still did not work. Now, ping from the desktop on wifi local > network got backward, please see following result: > > # ping -c 2 www.google.com > ping: www.google.com: Host name lookup failure > > > Thank you. > > Jim Can you post your unedited /etc/network/interfaces here ? Mihira. -- Random Quotes From Megas XLR Coop: You see? The mysteries of the Universe are revealed when you break stuff. Jamie: When in doubt, blow up a planet. Kiva: It's an 80 foot robot, if we can't see it, absolutely it's not here. Glorft Technician: Unnecessary use of force in capturing the Earthers has been approved. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: wifi network connection
On 12/25/07, Mihira Fernando <[EMAIL PROTECTED]> wrote: > On Mon December 24 2007, hce wrote: > > I did as per above, then did a reboot on my Debian laptop and ping > > from my desktop in wifi local network: > > > > # ping -c 2 www.google.com > > PING www.l.google.com (209.85.175.147): 56 data bytes > > > > --- www.l.google.com ping statistics --- > > 2 packets transmitted, 0 packets received, 100% packet loss > > > > It seems that the DNS works, but still could not get through the > > Internet via my laptop. The laptop does not formward packges to ppp0, > > something seems still missing in my loptop? > NAT on eth1. I though that was already understood. > You need iptables package to be installed (chances are its already installed). > Several ways to enable it but easiest would be to add a line to > the /etc/network/interfaces > > find the lines that configures eth1 and add this line at the bottom : > up iptables -t nat -A POSTROUTING -o ppp0 -j MASQUERADE > > then restart networking : > # /etc/init.d/networking restart The iptables has already been installed. I added "up iptables -t nat -A POSTROUTING -o ppp0 -j MASQUERADE" to the /etc/network/interfaces and restarted networking, it did not work. I then rebooted the laptop, it still did not work. Now, ping from the desktop on wifi local network got backward, please see following result: # ping -c 2 www.google.com ping: www.google.com: Host name lookup failure Thank you. Jim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: wifi network connection
On Mon December 24 2007, hce wrote: > I did as per above, then did a reboot on my Debian laptop and ping > from my desktop in wifi local network: > > # ping -c 2 www.google.com > PING www.l.google.com (209.85.175.147): 56 data bytes > > --- www.l.google.com ping statistics --- > 2 packets transmitted, 0 packets received, 100% packet loss > > It seems that the DNS works, but still could not get through the > Internet via my laptop. The laptop does not formward packges to ppp0, > something seems still missing in my loptop? NAT on eth1. I though that was already understood. You need iptables package to be installed (chances are its already installed). Several ways to enable it but easiest would be to add a line to the /etc/network/interfaces find the lines that configures eth1 and add this line at the bottom : up iptables -t nat -A POSTROUTING -o ppp0 -j MASQUERADE then restart networking : # /etc/init.d/networking restart Mihira. -- Random Quotes From Megas XLR Coop: You see? The mysteries of the Universe are revealed when you break stuff. Jamie: When in doubt, blow up a planet. Kiva: It's an 80 foot robot, if we can't see it, absolutely it's not here. Glorft Technician: Unnecessary use of force in capturing the Earthers has been approved. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: wifi network connection
On Tue, Dec 25, 2007 at 10:56:50AM +1100, hce wrote: > ... > > It seems that the DNS works, but still could not get through the > Internet via my laptop. The laptop does not formward packges to ppp0, > something seems still missing in my loptop? > > If I plug an Ethernet port from an ADSL modem to the wifi router, that > works. So, Iit seems to me that the wifi local network setting is > fine, the problem of setting is still in the debian laptop. Please see > following informaiton of my laptop status: > > $ /sbin/route > Kernel IP routing table > Destination Gateway Genmask Flags Metric RefUse Iface > 139.134.108.242 * 255.255.255.255 UH0 00 ppp0 > 192.168.5.0 * 255.255.255.0 U 0 00 eth1 > default * 0.0.0.0 U 0 00 ppp0 > > $ /sbin/ifconfig > eth1 Link encap:Ethernet HWaddr 00:20:E0:64:6E:0A > inet addr:192.168.5.1 Bcast:192.168.5.255 Mask:255.255.255.0 > inet6 addr: fe80::220:e0ff:fe64:6e0a/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:12 errors:0 dropped:0 overruns:0 frame:0 > TX packets:12 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:1110 (1.0 KiB) TX bytes:1040 (1.0 KiB) > > ppp0 Link encap:Point-to-Point Protocol > inet addr:144.139.45.157 P-t-P:139.134.108.242 > Mask:255.255.255.255 > UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1 > RX packets:3872 errors:0 dropped:0 overruns:0 frame:0 > TX packets:3609 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:3 > RX bytes:1058759 (1.0 MiB) TX bytes:460017 (449.2 KiB) > > Is there any debug messages can see on the debian laptop when I ping > from wifi local network? There was noting shown from dmesg from the > laptop when I ping from the wifi local network. > > Thanks all responses. > > Jim Maybe check the MTU setting. It can cause odd symptoms, with some things working (probably those with small packets) and some not. Ken -- Ken Irving, [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: wifi network connection
On 12/25/07, Mihira Fernando <[EMAIL PROTECTED]> wrote: > On Mon December 24 2007 11:02 am, hce wrote: > > > > Right, that was missing on my laptop. Could you please explain more > > how to enable the IP formward on my laptop (an example of commands > > will be better). > > > To enable IP Forwarding, run (as root) > # echo "1" > /proc/sys/net/ipv4/ip_forward > > (you need to run this everytime the system reboots ) > > [snip] > > > > I'll use the wifi router's DHCP server. > Then in the wifi router's DHCP configuration, set the Gateway and name server > to Laptop's ethernet IP address. > > > > > Goes withut saying that laptop must have a caching dns service such as > > > dnsmasq for this to work. > > > > Right, please also explain more, or an example of commands. > install dnsmasq. its a lightweight dns caching server. > > # aptitude install dnsmasq > > in its default config, it will take name servers as given in resolv.conf so it > should just work 'out of the box' in your case. > > That should get things going. I did as per above, then did a reboot on my Debian laptop and ping from my desktop in wifi local network: # ping -c 2 www.google.com PING www.l.google.com (209.85.175.147): 56 data bytes --- www.l.google.com ping statistics --- 2 packets transmitted, 0 packets received, 100% packet loss It seems that the DNS works, but still could not get through the Internet via my laptop. The laptop does not formward packges to ppp0, something seems still missing in my loptop? If I plug an Ethernet port from an ADSL modem to the wifi router, that works. So, Iit seems to me that the wifi local network setting is fine, the problem of setting is still in the debian laptop. Please see following informaiton of my laptop status: $ /sbin/route Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 139.134.108.242 * 255.255.255.255 UH0 00 ppp0 192.168.5.0 * 255.255.255.0 U 0 00 eth1 default * 0.0.0.0 U 0 00 ppp0 $ /sbin/ifconfig eth1 Link encap:Ethernet HWaddr 00:20:E0:64:6E:0A inet addr:192.168.5.1 Bcast:192.168.5.255 Mask:255.255.255.0 inet6 addr: fe80::220:e0ff:fe64:6e0a/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:12 errors:0 dropped:0 overruns:0 frame:0 TX packets:12 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1110 (1.0 KiB) TX bytes:1040 (1.0 KiB) ppp0 Link encap:Point-to-Point Protocol inet addr:144.139.45.157 P-t-P:139.134.108.242 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1 RX packets:3872 errors:0 dropped:0 overruns:0 frame:0 TX packets:3609 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:3 RX bytes:1058759 (1.0 MiB) TX bytes:460017 (449.2 KiB) Is there any debug messages can see on the debian laptop when I ping from wifi local network? There was noting shown from dmesg from the laptop when I ping from the wifi local network. Thanks all responses. Jim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: wifi network connection
On Monday 24 December 2007 20:16:19 Mihira Fernando wrote: > On Mon December 24 2007 11:02 am, hce wrote: > > Right, that was missing on my laptop. Could you please explain more > > how to enable the IP formward on my laptop (an example of commands > > will be better). > > To enable IP Forwarding, run (as root) > # echo "1" > /proc/sys/net/ipv4/ip_forward > > (you need to run this everytime the system reboots ) > keep in mind that you can change the option in /etc/sysctl.conf so that you don't have to run it everytime you reboot. If you change it in the config file then it stays forever. All changes you apply to the /proc filesystem will be lost after a reboot. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: wifi network connection
On Mon, Dec 24, 2007 at 19:16:19 +, Mihira Fernando wrote:
> On Mon December 24 2007 11:02 am, hce wrote:
> >
> > Right, that was missing on my laptop. Could you please explain more
> > how to enable the IP formward on my laptop (an example of commands
> > will be better).
> >
> To enable IP Forwarding, run (as root)
> # echo "1" > /proc/sys/net/ipv4/ip_forward
>
> (you need to run this everytime the system reboots )
A convenient way to make this permanent is putting
net.ipv4.ip_forward=1
into /etc/sysctl.conf. This line is probably already there and just
needs to be uncommented to become active (at least on Lenny and Sid; I
am not sure about Etch).
This works for all settings accessible via /proc/sys/, for example
vm.swappiness=10
will set /proc/sys/vm/swappiness to 10 at every boot. /etc/sysctl.conf
contains a number of commented examples for commonly used parameters.
You can restart procps ("invoke-rc.d procps restart") or use "sysctl -q
-p" to make changes to /etc/sysctl.conf effective without a reboot (or
use echo commands for each individual setting as Mihira has shown
above.)
--
Regards,| http://users.icfo.es/Florian.Kulzer
Florian |
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: wifi network connection
On Mon December 24 2007 11:02 am, hce wrote: > > Right, that was missing on my laptop. Could you please explain more > how to enable the IP formward on my laptop (an example of commands > will be better). > To enable IP Forwarding, run (as root) # echo "1" > /proc/sys/net/ipv4/ip_forward (you need to run this everytime the system reboots ) [snip] > > I'll use the wifi router's DHCP server. Then in the wifi router's DHCP configuration, set the Gateway and name server to Laptop's ethernet IP address. > > > Goes withut saying that laptop must have a caching dns service such as > > dnsmasq for this to work. > > Right, please also explain more, or an example of commands. install dnsmasq. its a lightweight dns caching server. # aptitude install dnsmasq in its default config, it will take name servers as given in resolv.conf so it should just work 'out of the box' in your case. That should get things going. Mihira. -- Random Quotes From Megas XLR Coop: You see? The mysteries of the Universe are revealed when you break stuff. Jamie: When in doubt, blow up a planet. Kiva: It's an 80 foot robot, if we can't see it, absolutely it's not here. Glorft Technician: Unnecessary use of force in capturing the Earthers has been approved. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: wifi network connection
On 12/24/07, Jesus Arocho <[EMAIL PROTECTED]> wrote: > should not resolv.conf and gw point to the address of the router? I would set > up the interface on the desktop manually just to test the connection. > You can enter the DNS provided by the ISP into resolv.conf or use the router > as the DNS. > > Something along the lines of: > > # The primary network interface > auto eth0 > iface eth0 inet static > address 192.168.2.x > netmask 255.255.255.0 > gateway 192.168.2.1 I guess you were talking about set up for my desktop which connected to the wifi router as a local lan. If so, it was all done. The missing parts were actually on my debian laptop as Mihira indicated such as ip forwarding. Thanks. Kind Regards, Jim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: wifi network connection
should not resolv.conf and gw point to the address of the router? I would set up the interface on the desktop manually just to test the connection. You can enter the DNS provided by the ISP into resolv.conf or use the router as the DNS. Something along the lines of: # The primary network interface auto eth0 iface eth0 inet static address 192.168.2.x netmask 255.255.255.0 gateway 192.168.2.1 On Sunday 23 December 2007 21:43:16 hce wrote: > Hi, > > I am doing an experiment to set up a home wifi network. The setup is > descripbed as follows: > > I have a laptop running Debian connected to the ISP via phone line > (ppp), the laptop has also an ethernet port, I set it to 192.168.5.1 > which connectes to a wifi router at Internet port. The wifi local LAN > IP address to 192.168.2.1. The nameserver in laptop is assigned by > ISP 139.134.2.190 and the default gw in laptop does not have an IP > address, but the iface = ppp0. > > I have another desktop connect tot he wifi LAN via udhcpc, it gets the > ip address 192.168.0.252 from DHCP server of wifi route. On the > desktop, the nameserver in resolv.conf sets to 192.168.0.1 and default > gw sets to 192.168.0.1. But, the desktop could not connect to the > internet. Any help what I was missing? > > Thank you. > > Jim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: wifi network connection
On 12/25/07, Mihira Fernando <[EMAIL PROTECTED]> wrote: > On Mon December 24 2007 9:02 am, hce wrote: > > > > Sorry, it was my mistake, the local wifi route IP addres = > > 192.168.0.1. I guess, the problem may be due to missing some services > > in my Debian laptop, should I run the DHCP server on the Debian > > laptop? > > > > I actually tried to connect the local wifi route (with same set up > > above) to a friend's ADSL modem which also sets the local LAN address > > to 192.168.5.1. And, it works fine. It seems that the ADSL modem has > > more proper setting than my Debian laptop. > > > > Thank you. > > > > Jim > > What are you trying to do ? share your Dial up internet connection via the > WIFI router ? > or does the WIFI Router has its own connection to the internet ? It is the former. The laptop Ethernet connects to the wifi Internet port. > If its the former, you will need to enable IP forwarding in your laptop's > interface that connects to the wifi router. Right, that was missing on my laptop. Could you please explain more how to enable the IP formward on my laptop (an example of commands will be better). > Also, If you plan to setup dhcp on this interface, then your dhcp options > must be configured so that > 1. dhcp clients gets an IP address in the same subnet as your interface > laptop's ethernet. > 2. the WIFI router must NOT be doing dhcp (2 dhcp servers are not necessary ) > 3. the dhcp clients must get your laptop's ethernet IP as both gateway and > nameserver. > > Alternatively you can use WIFI router's DHCP server but configure it so that : > 1. Laptop ethernet, WIF Router and dhcp clients are all on the same ip network > 2. Laptop ethernet has ip forwarding enabled > 3. dhcp clients get laptop ethernet ip address as both gateway and nameserver. I'll use the wifi router's DHCP server. > Goes withut saying that laptop must have a caching dns service such as dnsmasq > for this to work. Right, please also explain more, or an example of commands. Thank you. Kind Regards, Jim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: wifi network connection
On Mon December 24 2007 9:02 am, hce wrote: > > Sorry, it was my mistake, the local wifi route IP addres = > 192.168.0.1. I guess, the problem may be due to missing some services > in my Debian laptop, should I run the DHCP server on the Debian > laptop? > > I actually tried to connect the local wifi route (with same set up > above) to a friend's ADSL modem which also sets the local LAN address > to 192.168.5.1. And, it works fine. It seems that the ADSL modem has > more proper setting than my Debian laptop. > > Thank you. > > Jim What are you trying to do ? share your Dial up internet connection via the WIFI router ? or does the WIFI Router has its own connection to the internet ? If its the former, you will need to enable IP forwarding in your laptop's interface that connects to the wifi router. Also, If you plan to setup dhcp on this interface, then your dhcp options must be configured so that 1. dhcp clients gets an IP address in the same subnet as your interface laptop's ethernet. 2. the WIFI router must NOT be doing dhcp (2 dhcp servers are not necessary ) 3. the dhcp clients must get your laptop's ethernet IP as both gateway and nameserver. Alternatively you can use WIFI router's DHCP server but configure it so that : 1. Laptop ethernet, WIF Router and dhcp clients are all on the same ip network 2. Laptop ethernet has ip forwarding enabled 3. dhcp clients get laptop ethernet ip address as both gateway and nameserver. Goes withut saying that laptop must have a caching dns service such as dnsmasq for this to work. If its the later, suggestion in my earlier mail has to work. Mihira. PS. Replies only to the list please. -- Random Quotes From Megas XLR Coop: You see? The mysteries of the Universe are revealed when you break stuff. Jamie: When in doubt, blow up a planet. Kiva: It's an 80 foot robot, if we can't see it, absolutely it's not here. Glorft Technician: Unnecessary use of force in capturing the Earthers has been approved. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: wifi network connection
On 12/25/07, Mihira Fernando <[EMAIL PROTECTED]> wrote: > On Mon December 24 2007 2:43 am, hce wrote: > > Hi, > > > > I am doing an experiment to set up a home wifi network. The setup is > > descripbed as follows: > [snip] > > The wifi local LAN IP address to 192.168.2.1. > [snip] > > I have another desktop connect tot he wifi LAN via udhcpc, it gets the > > ip address 192.168.0.252 from DHCP server of wifi route. On the > > desktop, the nameserver in resolv.conf sets to 192.168.0.1 and default > > gw sets to 192.168.0.1. But, the desktop could not connect to the > > internet. Any help what I was missing? > > Since the wifi router is on 192.168.2.0/24 shouldn't the DHCP network be on > the same IP range and the DHCP clients getting IP : 192.168.2.1 as both > gateway and nameserver ? Sorry, it was my mistake, the local wifi route IP addres = 192.168.0.1. I guess, the problem may be due to missing some services in my Debian laptop, should I run the DHCP server on the Debian laptop? I actually tried to connect the local wifi route (with same set up above) to a friend's ADSL modem which also sets the local LAN address to 192.168.5.1. And, it works fine. It seems that the ADSL modem has more proper setting than my Debian laptop. Thank you. Jim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: wifi network connection
On Mon December 24 2007 2:43 am, hce wrote: > Hi, > > I am doing an experiment to set up a home wifi network. The setup is > descripbed as follows: [snip] > The wifi local LAN IP address to 192.168.2.1. [snip] > I have another desktop connect tot he wifi LAN via udhcpc, it gets the > ip address 192.168.0.252 from DHCP server of wifi route. On the > desktop, the nameserver in resolv.conf sets to 192.168.0.1 and default > gw sets to 192.168.0.1. But, the desktop could not connect to the > internet. Any help what I was missing? Since the wifi router is on 192.168.2.0/24 shouldn't the DHCP network be on the same IP range and the DHCP clients getting IP : 192.168.2.1 as both gateway and nameserver ? Mihira. -- Random Quotes From Megas XLR Coop: You see? The mysteries of the Universe are revealed when you break stuff. Jamie: When in doubt, blow up a planet. Kiva: It's an 80 foot robot, if we can't see it, absolutely it's not here. Glorft Technician: Unnecessary use of force in capturing the Earthers has been approved. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
wifi network connection
Hi, I am doing an experiment to set up a home wifi network. The setup is descripbed as follows: I have a laptop running Debian connected to the ISP via phone line (ppp), the laptop has also an ethernet port, I set it to 192.168.5.1 which connectes to a wifi router at Internet port. The wifi local LAN IP address to 192.168.2.1. The nameserver in laptop is assigned by ISP 139.134.2.190 and the default gw in laptop does not have an IP address, but the iface = ppp0. I have another desktop connect tot he wifi LAN via udhcpc, it gets the ip address 192.168.0.252 from DHCP server of wifi route. On the desktop, the nameserver in resolv.conf sets to 192.168.0.1 and default gw sets to 192.168.0.1. But, the desktop could not connect to the internet. Any help what I was missing? Thank you. Jim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
