On Tue, Jun 13, 2017 at 11:55:11AM +0900, Joel Rees wrote:
> On Tue, Jun 13, 2017 at 9:30 AM, Dan Ritter <d...@randomstring.org> 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 <joel.r...@gmail.com> 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-
