route flush and sh /etc/netstart not enough?

[Neal Hogan]

Hello misc@,

I'm having an issue with my wifi AP after I reconnect to my ISP. That
is, when my internet connection is broken, for whatever reason, and
then reconnected, my wireless machines see that the AP is available,
but fail to connect to it. My hard connection works just fine.

I flush all the routes (ie., # route flush) and then sh /etc/netstart,
but that does not work. At this point, rebooting the AP machine is the
only thing that I've been able to do to rectify the situation. From
the research that I've done, it doesn't look as though I should have
to reboot. Any suggestions?

Thanks!
-Neal

P.S. -- I'm not sure what would be appropriate for you to look at, if
anything. So, I offer a few things below. Let me know if something
else would help.


lambdahogan cat /etc/hostname.ral0
inet 192.168.3.1 255.255.255.0 NONE media autoselect \
        mediaopt hostap nwid lambdaserver nwkey xxxxxxxxxxxxxx



lambdahogan cat /etc/dhcpd.conf
#       $OpenBSD: dhcpd.conf,v 1.1 1998/08/19 04:25:45 form Exp $
#
# DHCP server options.
# See dhcpd.conf(5) and dhcpd(8) for more information.
#

# Network:              192.168.1.0/255.255.255.0
# Domain name:          my.domain
# Name servers:         192.168.1.3 and 192.168.1.5
# Default router:       192.168.1.1
# Addresses:            192.168.1.32 - 192.168.1.127
#
shared-network ETHERNET  {
        option  domain-name "lambdaserver";
        option  domain-name-servers 64.233.207.8, 64.233.207.9;
        #internal ethernet
        subnet 192.168.2.0 netmask 255.255.255.0 {
                option routers 192.168.2.1;

                range 192.168.2.32 192.168.2.127;
        }
}

shared-network WIRELESS  {
        option domain-name "lambdaserver";
        option domain-name-servers 64.233.207.8, 64.233.207.9;
        #internal wireless
        subnet 192.168.3.0 netmask 255.255.255.0 {
                option routers 192.168.3.1;

                range 192.168.3.32 192.168.3.127;
        }
}