Re: Broken Network
Erich Titl <[email protected]>
| Newsgroups | gmane.linux.leaf.user |
|---|---|
| Message-ID | <[email protected]> |
Am 11.09.2020 um 17:25 schrieb Robert K Coffman Jr. -Info From Data Corp.:
>
>
> On 9/11/2020 10:44 AM, Erich Titl wrote:
>> Hi Bob
>>
>> Am 11.09.2020 um 15:07 schrieb Robert K Coffman Jr. -Info From Data
>> Corp.:
>>> Not an emergency.
>>>
>>> I built a machine yesterday to allow me to replace a "normal" internet
>>> firewall with one that connects to a hotspot.
>>
>> I typically do that to extend WiFi reception aboard. I have an old ALIX
>> sitting at my desk which exactly does that, only it has wlan1 and eth0
>> bridged as the internal network :-).
>>
>>>
>>> I have it mostly configured, but I created a problem and I don't know if
>>> it is solvable or if I should just restart.
>>
>> Mabe restarting is not so much of an issue. First find out if you get a
>> wlan0 interface up without wpa_supplicant.
>>
>>>
>
> Restarting, especially since I am not under any pressure to get it
> working (I was yesterday as we had a line cut) is definitely an option.
>
> I tried - but wpa_supplicant seemed to be the closest I got to a working
> configuration.
>
> This is similar to what I originally tried:
>
> auto wlan0
> iface wlan0 inet dhcp
> wpa-ssid ESSID
> wpa-psk PASSWORD
Here is my interfaces file, it is generated by webconf.
SALT# cat /etc/network/interfaces
################################################################
# /etc/network/interfaces -- configuration file for LEAF network
# this file was generated by interfaces.cgi
#
# Loopback interface.
auto lo
iface lo inet loopback
################################################################
# configure wlan0 interface
# wlan0 / dynamic IP from pump/dhclient
#
auto wlan0
iface wlan0 inet dhcp
wpa_supplicant_control 1
################################################################
#
# br0 / Fixed IP
#
auto br0
iface br0 inet static
address 192.168.217.1
netmask 255.255.255.0
bridge_ports eth0 wlan1
################################################################
# end of generated interface file
################################################################
The wpa_supplicant control is actually redundant as wpa_supplicant is
started by init.
You should set the wifi config stuff in wpasupplicant.conf and not in
the interface file. I recommend to use the wpasupp.lwp webconf plugin to
handle the WiFi stuff.
>
>
>>> The wlan0 interface, when being brought up, hangs the boot process
>>> because it never connects. So I have a "pre" up executable that
>>> launches wpa_supplicant, and that is where it hangs.
Get rid of that stuff.
>>
>> You don't need a pre-up for wpa_supplicant. It will happily run without
>> an interface.
>
> Ok! My main problem is not understanding wireless config.
See above for an easy way.
>
>>> I cannot break out of it or reach another desktop - and the internal
>>> interface isn't "up" so I can't remote to it.
>>
>> Do you have physical access to the box?
>
> I do. But the console doesn't allow me to do anything - it is busy
> showing my pre-up command.
Get rid of the pre-up stuff.
>
>>> Any options? I guess I could pull the drive and remove wpa_supplicant
>>> from leaf.cfg - just not sure if there was another way to break out of
>>> this.
>>
>> Couldn't you just access the 'internal' interface or, if worst comes to
>> worst, the console?
>
> Internal interface is not up ("interfaces" is still processing).
See above ;-)
cheers
ET
--
Diese E-Mail wurde von AVG auf Viren geprüft.
http://www.avg.com
------------------------------------------------------------------------
leaf-user mailing list: [email protected]
https://lists.sourceforge.net/lists/listinfo/leaf-user
Support Request -- http://leaf-project.org/