SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
my slackware computer (fresh setup from current iso Jun 23 ) will not use the route to default gateway provided by dhcp.
i am on a wireless network configured in rc.inet1.conf:
i also have an eth0 device that is not in use so it is not configured here.
Code:
# Config information for eth0:
IPADDR[0]=""
NETMASK[0]=""
USE_DHCP[0]=""
DHCP_HOSTNAME[0]=""
# Config information for eth1:
IPADDR[1]=""
NETMASK[1]=""
USE_DHCP[1]=""
DHCP_HOSTNAME[1]=""
# Config information for eth2:
IPADDR[2]=""
NETMASK[2]=""
USE_DHCP[2]=""
DHCP_HOSTNAME[2]=""
# Config information for eth3:
IPADDR[3]=""
NETMASK[3]=""
USE_DHCP[3]=""
DHCP_HOSTNAME[3]=""
# Default gateway IP address:
#GATEWAY=""
# Change this to "yes" for debugging output to stdout. Unfortunately,
# /sbin/hotplug seems to disable stdout so you'll only see debugging output
# when rc.inet1 is called directly.
DEBUG_ETH_UP="no"
# Example of how to configure a bridge:
# Note the added "BRNICS" variable which contains a space-separated list
# of the physical network interfaces you want to add to the bridge.
#IFNAME[0]="br0"
#BRNICS[0]="eth0"
#IPADDR[0]="192.168.0.1"
#NETMASK[0]="255.255.255.0"
#USE_DHCP[0]=""
#DHCP_HOSTNAME[0]=""
## Example config information for wlan0. Uncomment the lines you need and fill
## in your info. (You may not need all of these for your wireless network)
IFNAME[4]="wlan0"
#IPADDR[4]=""
#NETMASK[4]=""
USE_DHCP[4]="yes"
DHCP_HOSTNAME[4]="acer"
#DHCP_KEEPRESOLV[4]="yes"
#DHCP_KEEPNTP[4]="yes"
#DHCP_KEEPGW[4]="yes"
#DHCP_IPADDR[4]=""
WLAN_ESSID[4]=R279
WLAN_MODE[4]=Managed
##WLAN_RATE[4]="54M auto"
##WLAN_CHANNEL[4]="auto"
##WLAN_KEY[4]="D5AD1F04ACF048EC2D0B1C80C7"
WLAN_IWPRIV[4]="set AuthMode=WPAPSK | set EncrypType=TKIP | set WPAPSK=hemligthe
mligt"
WLAN_WPA[4]="wpa_supplicant"
#WLAN_WPADRIVER[4]="ndiswrapper"
Well I tried briefly with Kde but it was way too slow for that computer. Could not get wireless working at all with NM anyway so I uninstalled Kde. I will mostly play around with this computer for web related stuff, so I really don't need a gui.
BTW, blanking the gateway line did not help me either.
You can easily generate your wpa_supplicant.conf using wpa_passphrase by doing wpa_passphrase SSIDpassword >> /etc/wpa_supplicant.conf
For the info you provided in your rc.inet1.conf, I went ahead and ran the command for you. It should add something like the following to your /etc/wpa_supplicant.conf (first line is the command I ran)
If you continue to run into issues after that, I'd recommend trying to just use wpa_supplicant to connect, as it should help by providing output on what errors it is running into.
Connecting is fine, I get a connection by wpa-supplicant somehow. Probably made a mess of it but it works...
I want all routes handled by dhcp. I get all routes but one...
root@acer:~# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
10.8.0.0 plutten 255.255.255.0 UG 303 0 0 wlan0
loopback * 255.0.0.0 U 0 0 0 lo
192.168.35.0 * 255.255.255.0 U 303 0 0 wlan0
root@acer:~#
As you see there is no default (Internet) route in there.
yep, gotta look exactly at what dnsmasq is serving. i see no delault route in the debug output.
one thing that does work is the reverse route to openvpn ;-)
yep, gotta look exactly at what dnsmasq is serving. i see no delault route in the debug output.
one thing that does work is the reverse route to openvpn ;-)
Are other machines on your network having difficulty getting the default route? Have you tried switching out dhcpcd for dhclient?
If you scroll down in these docs to the bottom of the "Manual Configuration" section, you will note the following:
Quote:
Why does Slackware include two DHCP clients? Sometimes a particular DHCP server may be broken and not respond well to either dhcpcd or dhclient. In those cases, you can fall back to the other DHCP client in hopes of getting a valid response from the server. Traditionally, Slackware uses dhcpcd, and this works in the vast majority of cases, but it may become necessary at some point for you to use dhclient instead. Both are excellent DHCP clients, so use whichever you prefer.
I can attest to this being accurate with some routers that serve DHCP addresses. In most cases a firmware update on the router is necessary. I did not experience this with Slackware, but I have with Debian in the past.
Stop all networking...
Code:
# sh /etc/rc.d/rc.inet1 stop && sh /etc/rc.d/rc.wireless stop
....and restart it manually as suggested in this documentation. Then when you bring up the NIC, run dhclient for wlan0.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.