Re: slow connections to non-bridged hostapd/dnsmasq wireless access point (was pointers to material...)
On Wed, Jun 14, 2017 at 9:39 AM, Dan Ritter wrote: > On Wed, Jun 14, 2017 at 07:40:49AM +0900, Joel Rees wrote: >> (Now that I'm awake...) >> >> On Wed, Jun 14, 2017 at 2:18 AM, Joel Rees wrote: >> > On Tue, Jun 13, 2017 at 9:26 PM, Dan Ritter wrote: >> >> On Tue, Jun 13, 2017 at 11:55:11AM +0900, Joel Rees wrote: >> >>> On Tue, Jun 13, 2017 at 9:30 AM, Dan Ritter >> >>> wrote: >> >>> > On Mon, Jun 12, 2017 at 11:50:00AM +0900, Joel Rees wrote: >> >>> >> (famous last words) >> >>> >> >> >>> >> On Sat, Jun 10, 2017 at 3:53 PM, Joel Rees >> >>> >> wrote: >> >>> >> > I now have connection for both the wireless and the netbook that is >> >>> >> > acting >> >>> >> > as the AP. I took out the bridge entirely, quit trying to play with >> >>> >> > port forwarding, >> >>> >> > just used dead simple setup. dnsmasq was the only missing piece, if >> >>> >> > I had >> >>> >> > not been focusing on bridging. Bridging is probably for the other >> >>> >> > direction. >> >>> >> > >> >>> >> > But the wireless is pretty slow, so I'm not sure I'm finished. >> >>> >> > >> >>> >> > I have to go take care of some family business, when I'm done I'll >> >>> >> > post the details. >> >>> >> > >> >>> >> > But it's really pretty simply. I was just working too hard. >> >>> >> >> >>> >> But it's too slow to maintain a connection. >> >>> >> >> >>> >> After mucking around a bit, I haven't really come up with anything. So >> >>> >> I'll post my >> >>> >> configurations (names changed as usual): >> >>> > >> >>> > You have an eth0 network, a non-overlapping wlan0 network -- can >> >>> > you characterize "too slow"? >> >>> >> >>> Actually, now that I dig in, it only seems to be routing dns traffic. >> >>> >> >>> That is, I tried to ping the wireless interface from my daughter's >> >>> computer >> >>> and got a network not reachable or down result of some sort. (I didn't >> >>> write the exact message down, and my daughter's at school so I can't >> >>> use her computer.) >> >>> >> >>> But my logs on the netbook that is running hostapd and dnsmasq show >> >>> quite a bit of dns traffic, lots of queries returning successful results. >> >>> >> >>> > Things to check: >> >>> > >> >>> > - ping from your netbook to the outside world >> >>> >> >>> No problem there. >> >>> >> >>> > - ping from a wifi client through the netbook to the outside >> >>> > world >> >>> >> >>> That also got network not reachable or down or something. >> >>> >> >>> > if those work, >> >>> > >> >>> > - wget -O /dev/null http://speed.hetzner.de/100MB.bin >> >>> > - and on a wifi client >> >>> >> >>> I tried that in bridge configuration just now and I'm only getting one >> >>> percent every twenty to thirty seconds. The non-bridged configuration >> >>> doesn't even read the mail to look at the url. >> >>> >> >> >> >> Right, that's bad. >> >> Actually, it might be normal for this ancient Android tablet. >> >> >> Try this: >> >> >> >> allow-hotplug eth0 >> >> iface eth0 inet static >> >> >> >> allow-hotplug wlan0 >> >> iface wlan0 inet static >> >> >> >> auto br0 >> >> iface br0 inet static >> >> address 172.28.45.58 >> >> netmask 255.255.255.192 >> >> broadcast 172.28.45.63 >> >> gateway 172.28.45.32 >> >> dns-nameservers 172.28.45.32 208.67.222.222 8.8.4.4 >> >> bridge_ports eth0 wlan0 >> >> bridge_maxwait 1 >> >> >> >> >> >> Note that now both the eth0 and wlan0 interfaces will have the same >> >> 172.28.45.58 address >> >> >> >> But for right now, ignore that: just test connectivity and speed on this >> >> netbook while the bridge is in effect. >> > >> > Interesting. Without the alias on eth0, the netbook is now able to access >> > the internet through the bridged eth0 port. This is beginning to make >> > more sense to me. >> > >> > Speed on your 100Mb blob is reasonable, ETA of about two minutes >> > and 40 seconds, which is close to the limit on my connection. >> > >> > Wireless devices are not able to log in. I'm not sure I got the changes >> > to the dnsmasq and ntp configurations right for doing a subrange of >> > what I have the wall router providing me. >> >> I forgot the most important setting. >> >> Setting hostapd to bridge mode solved the connection problem. >> >> It's still running about 20 seconds per megabyte, which may be all I >> want to expect from this ancient single-processor 32-bit ARM >> Android 2.4 tablet with only 1G RAM and an 80%-90% full 8G internal >> flash. >> >> I'll try a connection on one of my kids' computers later. >> >> >> If you can't get a good approximation of your internet >> >> connection speed from this, there's more to track down. >> >> >> >> -dsr- >> > >> > This is something I can play with after I wake up tomorrow. (It's about >> > two in the morning here and I need to get some sleep.) For the record, the speed problem somehow resolved itself. I don't know how, but I'm guessing that, after a couple of re-boots, networkmanager figured out how to get itself out of the way. Or maybe it was jus
Re: slow connections to non-bridged hostapd/dnsmasq wireless access point (was pointers to material...)
On Wed, Jun 14, 2017 at 07:40:49AM +0900, Joel Rees wrote: > (Now that I'm awake...) > > On Wed, Jun 14, 2017 at 2:18 AM, Joel Rees wrote: > > On Tue, Jun 13, 2017 at 9:26 PM, Dan Ritter wrote: > >> On Tue, Jun 13, 2017 at 11:55:11AM +0900, Joel Rees wrote: > >>> On Tue, Jun 13, 2017 at 9:30 AM, Dan Ritter wrote: > >>> > On Mon, Jun 12, 2017 at 11:50:00AM +0900, Joel Rees wrote: > >>> >> (famous last words) > >>> >> > >>> >> On Sat, Jun 10, 2017 at 3:53 PM, Joel Rees wrote: > >>> >> > I now have connection for both the wireless and the netbook that is > >>> >> > acting > >>> >> > as the AP. I took out the bridge entirely, quit trying to play with > >>> >> > port forwarding, > >>> >> > just used dead simple setup. dnsmasq was the only missing piece, if > >>> >> > I had > >>> >> > not been focusing on bridging. Bridging is probably for the other > >>> >> > direction. > >>> >> > > >>> >> > But the wireless is pretty slow, so I'm not sure I'm finished. > >>> >> > > >>> >> > I have to go take care of some family business, when I'm done I'll > >>> >> > post the details. > >>> >> > > >>> >> > But it's really pretty simply. I was just working too hard. > >>> >> > >>> >> But it's too slow to maintain a connection. > >>> >> > >>> >> After mucking around a bit, I haven't really come up with anything. So > >>> >> I'll post my > >>> >> configurations (names changed as usual): > >>> > > >>> > You have an eth0 network, a non-overlapping wlan0 network -- can > >>> > you characterize "too slow"? > >>> > >>> Actually, now that I dig in, it only seems to be routing dns traffic. > >>> > >>> That is, I tried to ping the wireless interface from my daughter's > >>> computer > >>> and got a network not reachable or down result of some sort. (I didn't > >>> write the exact message down, and my daughter's at school so I can't > >>> use her computer.) > >>> > >>> But my logs on the netbook that is running hostapd and dnsmasq show > >>> quite a bit of dns traffic, lots of queries returning successful results. > >>> > >>> > Things to check: > >>> > > >>> > - ping from your netbook to the outside world > >>> > >>> No problem there. > >>> > >>> > - ping from a wifi client through the netbook to the outside > >>> > world > >>> > >>> That also got network not reachable or down or something. > >>> > >>> > if those work, > >>> > > >>> > - wget -O /dev/null http://speed.hetzner.de/100MB.bin > >>> > - and on a wifi client > >>> > >>> I tried that in bridge configuration just now and I'm only getting one > >>> percent every twenty to thirty seconds. The non-bridged configuration > >>> doesn't even read the mail to look at the url. > >>> > >> > >> Right, that's bad. > > Actually, it might be normal for this ancient Android tablet. > > >> Try this: > >> > >> allow-hotplug eth0 > >> iface eth0 inet static > >> > >> allow-hotplug wlan0 > >> iface wlan0 inet static > >> > >> auto br0 > >> iface br0 inet static > >> address 172.28.45.58 > >> netmask 255.255.255.192 > >> broadcast 172.28.45.63 > >> gateway 172.28.45.32 > >> dns-nameservers 172.28.45.32 208.67.222.222 8.8.4.4 > >> bridge_ports eth0 wlan0 > >> bridge_maxwait 1 > >> > >> > >> Note that now both the eth0 and wlan0 interfaces will have the same > >> 172.28.45.58 address > >> > >> But for right now, ignore that: just test connectivity and speed on this > >> netbook while the bridge is in effect. > > > > Interesting. Without the alias on eth0, the netbook is now able to access > > the internet through the bridged eth0 port. This is beginning to make > > more sense to me. > > > > Speed on your 100Mb blob is reasonable, ETA of about two minutes > > and 40 seconds, which is close to the limit on my connection. > > > > Wireless devices are not able to log in. I'm not sure I got the changes > > to the dnsmasq and ntp configurations right for doing a subrange of > > what I have the wall router providing me. > > I forgot the most important setting. > > Setting hostapd to bridge mode solved the connection problem. > > It's still running about 20 seconds per megabyte, which may be all I > want to expect from this ancient single-processor 32-bit ARM > Android 2.4 tablet with only 1G RAM and an 80%-90% full 8G internal > flash. > > I'll try a connection on one of my kids' computers later. > > >> If you can't get a good approximation of your internet > >> connection speed from this, there's more to track down. > >> > >> -dsr- > > > > This is something I can play with after I wake up tomorrow. (It's about > > two in the morning here and I need to get some sleep.) > > I have a job interview I need to prepare for, so I'll have to save the > playing with the parameters for later. > > Again, thanks. I'll post some of my results so far, maybe today, in case > someone else wants to do this. Good to hear it. Good luck on your job interview, and remind them that you can solve technical problems by asking questions and recognizing good advice. -dsr-
Re: slow connections to non-bridged hostapd/dnsmasq wireless access point (was pointers to material...)
(Now that I'm awake...) On Wed, Jun 14, 2017 at 2:18 AM, Joel Rees wrote: > On Tue, Jun 13, 2017 at 9:26 PM, Dan Ritter wrote: >> On Tue, Jun 13, 2017 at 11:55:11AM +0900, Joel Rees wrote: >>> On Tue, Jun 13, 2017 at 9:30 AM, Dan Ritter wrote: >>> > On Mon, Jun 12, 2017 at 11:50:00AM +0900, Joel Rees wrote: >>> >> (famous last words) >>> >> >>> >> On Sat, Jun 10, 2017 at 3:53 PM, Joel Rees wrote: >>> >> > I now have connection for both the wireless and the netbook that is >>> >> > acting >>> >> > as the AP. I took out the bridge entirely, quit trying to play with >>> >> > port forwarding, >>> >> > just used dead simple setup. dnsmasq was the only missing piece, if I >>> >> > had >>> >> > not been focusing on bridging. Bridging is probably for the other >>> >> > direction. >>> >> > >>> >> > But the wireless is pretty slow, so I'm not sure I'm finished. >>> >> > >>> >> > I have to go take care of some family business, when I'm done I'll >>> >> > post the details. >>> >> > >>> >> > But it's really pretty simply. I was just working too hard. >>> >> >>> >> But it's too slow to maintain a connection. >>> >> >>> >> After mucking around a bit, I haven't really come up with anything. So >>> >> I'll post my >>> >> configurations (names changed as usual): >>> > >>> > You have an eth0 network, a non-overlapping wlan0 network -- can >>> > you characterize "too slow"? >>> >>> Actually, now that I dig in, it only seems to be routing dns traffic. >>> >>> That is, I tried to ping the wireless interface from my daughter's computer >>> and got a network not reachable or down result of some sort. (I didn't >>> write the exact message down, and my daughter's at school so I can't >>> use her computer.) >>> >>> But my logs on the netbook that is running hostapd and dnsmasq show >>> quite a bit of dns traffic, lots of queries returning successful results. >>> >>> > Things to check: >>> > >>> > - ping from your netbook to the outside world >>> >>> No problem there. >>> >>> > - ping from a wifi client through the netbook to the outside >>> > world >>> >>> That also got network not reachable or down or something. >>> >>> > if those work, >>> > >>> > - wget -O /dev/null http://speed.hetzner.de/100MB.bin >>> > - and on a wifi client >>> >>> I tried that in bridge configuration just now and I'm only getting one >>> percent every twenty to thirty seconds. The non-bridged configuration >>> doesn't even read the mail to look at the url. >>> >> >> Right, that's bad. Actually, it might be normal for this ancient Android tablet. >> Try this: >> >> allow-hotplug eth0 >> iface eth0 inet static >> >> allow-hotplug wlan0 >> iface wlan0 inet static >> >> auto br0 >> iface br0 inet static >> address 172.28.45.58 >> netmask 255.255.255.192 >> broadcast 172.28.45.63 >> gateway 172.28.45.32 >> dns-nameservers 172.28.45.32 208.67.222.222 8.8.4.4 >> bridge_ports eth0 wlan0 >> bridge_maxwait 1 >> >> >> Note that now both the eth0 and wlan0 interfaces will have the same >> 172.28.45.58 address >> >> But for right now, ignore that: just test connectivity and speed on this >> netbook while the bridge is in effect. > > Interesting. Without the alias on eth0, the netbook is now able to access > the internet through the bridged eth0 port. This is beginning to make > more sense to me. > > Speed on your 100Mb blob is reasonable, ETA of about two minutes > and 40 seconds, which is close to the limit on my connection. > > Wireless devices are not able to log in. I'm not sure I got the changes > to the dnsmasq and ntp configurations right for doing a subrange of > what I have the wall router providing me. I forgot the most important setting. Setting hostapd to bridge mode solved the connection problem. It's still running about 20 seconds per megabyte, which may be all I want to expect from this ancient single-processor 32-bit ARM Android 2.4 tablet with only 1G RAM and an 80%-90% full 8G internal flash. I'll try a connection on one of my kids' computers later. >> If you can't get a good approximation of your internet >> connection speed from this, there's more to track down. >> >> -dsr- > > This is something I can play with after I wake up tomorrow. (It's about > two in the morning here and I need to get some sleep.) I have a job interview I need to prepare for, so I'll have to save the playing with the parameters for later. Again, thanks. I'll post some of my results so far, maybe today, in case someone else wants to do this. -- Joel Rees One of these days I'll get someone to pay me to design a language that combines the best of Forth and C. Then I'll be able to leap wide instruction sets with a single #ifdef, run faster than a speeding infinite loop with a #define, and stop all integer size bugs with my bare cast. http://defining-computers.blogspot.com/2017/06/reinventing-computers.html More of my delusions: http://reiisi.blogspot.com/2017/05/do-not-pay-modern-danegeld-ransomware.html http://reiisi.blogspot.jp/
Re: slow connections to non-bridged hostapd/dnsmasq wireless access point (was pointers to material...)
On Tue, Jun 13, 2017 at 9:26 PM, Dan Ritter wrote: > On Tue, Jun 13, 2017 at 11:55:11AM +0900, Joel Rees wrote: >> On Tue, Jun 13, 2017 at 9:30 AM, Dan Ritter wrote: >> > On Mon, Jun 12, 2017 at 11:50:00AM +0900, Joel Rees wrote: >> >> (famous last words) >> >> >> >> On Sat, Jun 10, 2017 at 3:53 PM, Joel Rees wrote: >> >> > I now have connection for both the wireless and the netbook that is >> >> > acting >> >> > as the AP. I took out the bridge entirely, quit trying to play with >> >> > port forwarding, >> >> > just used dead simple setup. dnsmasq was the only missing piece, if I >> >> > had >> >> > not been focusing on bridging. Bridging is probably for the other >> >> > direction. >> >> > >> >> > But the wireless is pretty slow, so I'm not sure I'm finished. >> >> > >> >> > I have to go take care of some family business, when I'm done I'll >> >> > post the details. >> >> > >> >> > But it's really pretty simply. I was just working too hard. >> >> >> >> But it's too slow to maintain a connection. >> >> >> >> After mucking around a bit, I haven't really come up with anything. So >> >> I'll post my >> >> configurations (names changed as usual): >> >> >> > >> > >> > You have an eth0 network, a non-overlapping wlan0 network -- can >> > you characterize "too slow"? >> >> Actually, now that I dig in, it only seems to be routing dns traffic. >> >> That is, I tried to ping the wireless interface from my daughter's computer >> and got a network not reachable or down result of some sort. (I didn't >> write the exact message down, and my daughter's at school so I can't >> use her computer.) >> >> But my logs on the netbook that is running hostapd and dnsmasq show >> quite a bit of dns traffic, lots of queries returning successful results. >> >> > Things to check: >> > >> > - ping from your netbook to the outside world >> >> No problem there. >> >> > - ping from a wifi client through the netbook to the outside >> > world >> >> That also got network not reachable or down or something. >> >> > if those work, >> > >> > - wget -O /dev/null http://speed.hetzner.de/100MB.bin >> > - and on a wifi client >> >> I tried that in bridge configuration just now and I'm only getting one >> percent every twenty to thirty seconds. The non-bridged configuration >> doesn't even read the mail to look at the url. >> > > Right, that's bad. > > Try this: > > allow-hotplug eth0 > iface eth0 inet static > > allow-hotplug wlan0 > iface wlan0 inet static > > auto br0 > iface br0 inet static > address 172.28.45.58 > netmask 255.255.255.192 > broadcast 172.28.45.63 > gateway 172.28.45.32 > dns-nameservers 172.28.45.32 208.67.222.222 8.8.4.4 > bridge_ports eth0 wlan0 > bridge_maxwait 1 > > > Note that now both the eth0 and wlan0 interfaces will have the same > 172.28.45.58 address > > But for right now, ignore that: just test connectivity and speed on this > netbook while the bridge is in effect. Interesting. Without the alias on eth0, the netbook is now able to access the internet through the bridged eth0 port. This is beginning to make more sense to me. Speed on your 100Mb blob is reasonable, ETA of about two minutes and 40 seconds, which is close to the limit on my connection. Wireless devices are not able to log in. I'm not sure I got the changes to the dnsmasq and ntp configurations right for doing a subrange of what I have the wall router providing me. > If you can't get a good approximation of your internet > connection speed from this, there's more to track down. > > -dsr- This is something I can play with after I wake up tomorrow. (It's about two in the morning here and I need to get some sleep.) Thanks! -- Joel Rees One of these days I'll get someone to pay me to design a language that combines the best of Forth and C. Then I'll be able to leap wide instruction sets with a single #ifdef, run faster than a speeding infinite loop with a #define, and stop all integer size bugs with my bare cast. http://defining-computers.blogspot.com/2017/06/reinventing-computers.html More of my delusions: http://reiisi.blogspot.com/2017/05/do-not-pay-modern-danegeld-ransomware.html http://reiisi.blogspot.jp/p/novels-i-am-writing.html
Re: slow connections to non-bridged hostapd/dnsmasq wireless access point (was pointers to material...)
On Tue, Jun 13, 2017 at 11:55:11AM +0900, Joel Rees wrote: > On Tue, Jun 13, 2017 at 9:30 AM, Dan Ritter wrote: > > On Mon, Jun 12, 2017 at 11:50:00AM +0900, Joel Rees wrote: > >> (famous last words) > >> > >> On Sat, Jun 10, 2017 at 3:53 PM, Joel Rees wrote: > >> > I now have connection for both the wireless and the netbook that is > >> > acting > >> > as the AP. I took out the bridge entirely, quit trying to play with > >> > port forwarding, > >> > just used dead simple setup. dnsmasq was the only missing piece, if I had > >> > not been focusing on bridging. Bridging is probably for the other > >> > direction. > >> > > >> > But the wireless is pretty slow, so I'm not sure I'm finished. > >> > > >> > I have to go take care of some family business, when I'm done I'll > >> > post the details. > >> > > >> > But it's really pretty simply. I was just working too hard. > >> > >> But it's too slow to maintain a connection. > >> > >> After mucking around a bit, I haven't really come up with anything. So > >> I'll post my > >> configurations (names changed as usual): > >> > > > > > > You have an eth0 network, a non-overlapping wlan0 network -- can > > you characterize "too slow"? > > Actually, now that I dig in, it only seems to be routing dns traffic. > > That is, I tried to ping the wireless interface from my daughter's computer > and got a network not reachable or down result of some sort. (I didn't > write the exact message down, and my daughter's at school so I can't > use her computer.) > > But my logs on the netbook that is running hostapd and dnsmasq show > quite a bit of dns traffic, lots of queries returning successful results. > > > Things to check: > > > > - ping from your netbook to the outside world > > No problem there. > > > - ping from a wifi client through the netbook to the outside > > world > > That also got network not reachable or down or something. > > > if those work, > > > > - wget -O /dev/null http://speed.hetzner.de/100MB.bin > > - and on a wifi client > > I tried that in bridge configuration just now and I'm only getting one > percent every twenty to thirty seconds. The non-bridged configuration > doesn't even read the mail to look at the url. > Right, that's bad. Try this: allow-hotplug eth0 iface eth0 inet static allow-hotplug wlan0 iface wlan0 inet static auto br0 iface br0 inet static address 172.28.45.58 netmask 255.255.255.192 broadcast 172.28.45.63 gateway 172.28.45.32 dns-nameservers 172.28.45.32 208.67.222.222 8.8.4.4 bridge_ports eth0 wlan0 bridge_maxwait 1 Note that now both the eth0 and wlan0 interfaces will have the same 172.28.45.58 address But for right now, ignore that: just test connectivity and speed on this netbook while the bridge is in effect. If you can't get a good approximation of your internet connection speed from this, there's more to track down. -dsr-
Re: slow connections to non-bridged hostapd/dnsmasq wireless access point (was pointers to material...)
On Tue, Jun 13, 2017 at 9:30 AM, Dan Ritter wrote: > On Mon, Jun 12, 2017 at 11:50:00AM +0900, Joel Rees wrote: >> (famous last words) >> >> On Sat, Jun 10, 2017 at 3:53 PM, Joel Rees wrote: >> > I now have connection for both the wireless and the netbook that is acting >> > as the AP. I took out the bridge entirely, quit trying to play with >> > port forwarding, >> > just used dead simple setup. dnsmasq was the only missing piece, if I had >> > not been focusing on bridging. Bridging is probably for the other >> > direction. >> > >> > But the wireless is pretty slow, so I'm not sure I'm finished. >> > >> > I have to go take care of some family business, when I'm done I'll >> > post the details. >> > >> > But it's really pretty simply. I was just working too hard. >> >> But it's too slow to maintain a connection. >> >> After mucking around a bit, I haven't really come up with anything. So >> I'll post my >> configurations (names changed as usual): >> > > > You have an eth0 network, a non-overlapping wlan0 network -- can > you characterize "too slow"? Actually, now that I dig in, it only seems to be routing dns traffic. That is, I tried to ping the wireless interface from my daughter's computer and got a network not reachable or down result of some sort. (I didn't write the exact message down, and my daughter's at school so I can't use her computer.) But my logs on the netbook that is running hostapd and dnsmasq show quite a bit of dns traffic, lots of queries returning successful results. > Things to check: > > - ping from your netbook to the outside world No problem there. > - ping from a wifi client through the netbook to the outside > world That also got network not reachable or down or something. > if those work, > > - wget -O /dev/null http://speed.hetzner.de/100MB.bin > - and on a wifi client I tried that in bridge configuration just now and I'm only getting one percent every twenty to thirty seconds. The non-bridged configuration doesn't even read the mail to look at the url. -- Joel Rees One of these days I'll get someone to pay me to design a language that combines the best of Forth and C. Then I'll be able to leap wide instruction sets with a single #ifdef, run faster than a speeding infinite loop with a #define, and stop all integer size bugs with my bare cast. http://defining-computers.blogspot.com/2017/06/reinventing-computers.html More of my delusions: http://reiisi.blogspot.com/2017/05/do-not-pay-modern-danegeld-ransomware.html http://reiisi.blogspot.jp/p/novels-i-am-writing.html
Re: slow connections to non-bridged hostapd/dnsmasq wireless access point (was pointers to material...)
On Mon, Jun 12, 2017 at 11:50:00AM +0900, Joel Rees wrote: > (famous last words) > > On Sat, Jun 10, 2017 at 3:53 PM, Joel Rees wrote: > > I now have connection for both the wireless and the netbook that is acting > > as the AP. I took out the bridge entirely, quit trying to play with > > port forwarding, > > just used dead simple setup. dnsmasq was the only missing piece, if I had > > not been focusing on bridging. Bridging is probably for the other > > direction. > > > > But the wireless is pretty slow, so I'm not sure I'm finished. > > > > I have to go take care of some family business, when I'm done I'll > > post the details. > > > > But it's really pretty simply. I was just working too hard. > > But it's too slow to maintain a connection. > > After mucking around a bit, I haven't really come up with anything. So > I'll post my > configurations (names changed as usual): > You have an eth0 network, a non-overlapping wlan0 network -- can you characterize "too slow"? Things to check: - ping from your netbook to the outside world - ping from a wifi client through the netbook to the outside world if those work, - wget -O /dev/null http://speed.hetzner.de/100MB.bin - and on a wifi client
slow connections to non-bridged hostapd/dnsmasq wireless access point (was pointers to material...)
(famous last words) On Sat, Jun 10, 2017 at 3:53 PM, Joel Rees wrote: > I now have connection for both the wireless and the netbook that is acting > as the AP. I took out the bridge entirely, quit trying to play with > port forwarding, > just used dead simple setup. dnsmasq was the only missing piece, if I had > not been focusing on bridging. Bridging is probably for the other direction. > > But the wireless is pretty slow, so I'm not sure I'm finished. > > I have to go take care of some family business, when I'm done I'll > post the details. > > But it's really pretty simply. I was just working too hard. But it's too slow to maintain a connection. After mucking around a bit, I haven't really come up with anything. So I'll post my configurations (names changed as usual): /etc/network/interfaces--- # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback # The primary network interface allow-hotplug eth0 #iface eth0 inet dhcp iface eth0 inet static address 172.28.45.58 network 172.28.45.0 netmask 255.255.255.192 broadcast 172.28.45.63 gateway 172.28.45.32 dns-nameservers 172.28.45.32 208.67.222.222 8.8.4.4 # wireless wlan0 allow-hotplug wlan0 #iface wlan0 inet manual iface wlan0 inet static address 172.28.43.168 netmask 255.255.255.192 network 172.28.43.128 broadcast 172.28.43.191 gateway 172.28.45.58 dns-nameservers 172.28.45.58 172.28.45.32 208.67.222.222 8.8.4.4 -- --/etc/hostapd/hostapd.conf ### Wireless network name ### interface=wlan0 ### Driver Name ### driver=nl80211 ### Set your bridge name ### #bridge=br0 ### Country name code in ISO/IEC 3166-1 format. ### # This is used to set regulatory domain. # Set as needed to indicate country in which device is operating. # This can limit available channels and transmit power. ### (IN == INDIA, UK == United Kingdom, US == United Stats and so on ) ### country_code=JP ### SSID: ### ssid=MonkeyMagic ### channel number (some drivers will only accept 0) ### ### (some drivers will not accept 0) ### channel=1,6,10 ### operation mode (a = IEEE 802.11a, b = IEEE 802.11b, g = IEEE 802.11g) ### hw_mode=g ieee80211n=1 ht_capab=[HT40+][SHORT-GI-40][DSSS_CCK-40] ### WPA mode: ### wpa=2 ### passphrase (WiFi password): ### wpa_passphrase=n0+m4REALpa55P#ra$e ## Key management algorithms ## wpa_key_mgmt=WPA-PSK ## Set cipher suites (encryption algorithms) ## ## TKIP = Temporal Key Integrity Protocol ## CCMP = AES in Counter mode with CBC-MAC wpa_pairwise=TKIP rsn_pairwise=CCMP ## Shared Key Authentication ## auth_algs=1 ## Accept all MAC address ### macaddr_acl=0 ## Don't mess with media-specific tuning. ## wme_enabled=0 -- /etc/dnsmasq.conf # Configuration file for dnsmasq. # # Format is one option per line, legal options are the same # as the long options legal on the command line. See # "/usr/sbin/dnsmasq --help" or "man 8 dnsmasq" for details. # Listen on this specific port instead of the standard DNS port # (53). Setting this to zero completely disables DNS function, # leaving only DHCP and/or TFTP. #port=5353 # The following two options make you a better netizen, since they # tell dnsmasq to filter out queries which the public DNS cannot # answer, and which load the servers (especially the root servers) # unnecessarily. If you have a dial-on-demand link they also stop # these requests from bringing up the link unnecessarily. # Never forward plain names (without a dot or domain part) domain-needed # Never forward addresses in the non-routed address spaces. bogus-priv # Uncomment this to filter useless windows-originated DNS requests # which can trigger dial-on-demand links needlessly. # Note that (amongst other things) this blocks all SRV requests, # so don't use it if you use eg Kerberos, SIP, XMMP or Google-talk. # This option only affects forwarding, SRV records originating for # dnsmasq (via srv-host= lines) are not suppressed by it. #filterwin2k # Change this line if you want dns to get its upstream servers from # somewhere other that /etc/resolv.conf #resolv-file= # By default, dnsmasq will send queries to any of the upstream # servers it knows about and tries to favour servers to are known # to be up. Uncommenting this forces dnsmasq to try each query # with each server strictly in the order they appear in # /etc/resolv.conf #strict-order # If you don't want dnsmasq to read /etc/resolv.conf or any other # file, getting its servers from this file instead (see below), then # uncomment this. #no-resolv # If you don't want dnsmasq to poll /etc/resolv.conf or other resolv # files for changes and re-read th
