LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking
User Name
Password
Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.

Notices


Reply
  Search this Thread
Old 10-22-2014, 10:06 PM   #1
tentativeOrch
LQ Newbie
 
Registered: Nov 2013
Posts: 10

Rep: Reputation: Disabled
Slackware 14 Internet issues


I can access the machine over the local network and access services on the machine, but I cannot get online with the server. Every other device on the network can get online.

I'm stumped. Where can I start on this or should I just rewrite the OS?
 
Old 10-22-2014, 10:18 PM   #2
frankbell
LQ Guru
 
Registered: Jan 2006
Location: Virginia, USA
Distribution: Slackware, Ubuntu MATE, Mageia, and whatever VMs I happen to be playing with
Posts: 19,580
Blog Entries: 28

Rep: Reputation: 6219Reputation: 6219Reputation: 6219Reputation: 6219Reputation: 6219Reputation: 6219Reputation: 6219Reputation: 6219Reputation: 6219Reputation: 6219Reputation: 6219
What is the output of ifconfig -a, cat /etc/networks, and cat /etc/rc.d/rc.inet1.conf.
 
Old 10-22-2014, 10:48 PM   #3
tentativeOrch
LQ Newbie
 
Registered: Nov 2013
Posts: 10

Original Poster
Rep: Reputation: Disabled
ifconfig -a results:

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.105 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::fa0f:41ff:fe37:a8b prefixlen 64 scopeid 0x20<link>
ether f8:0f:41:37:0a:8b txqueuelen 1000 (Ethernet)
RX packets 4821 bytes 462639 (451.7 KiB)
RX errors 1 dropped 0 overruns 1 frame 0
TX packets 3465 bytes 425805 (415.8 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 0 (Local Loopback)
RX packets 100 bytes 6568 (6.4 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 100 bytes 6568 (6.4 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0


results of cat /etc/networks

#
# networks This file describes a number of netname-to-address
# mappings for the TCP/IP subsystem. It is mostly
# used at boot time, when no name servers are running.
#

loopback 127.0.0.0
localnet 127.0.0.0

# End of networks.


results of cat /etc/rc.d/rc.inet1.conf:

# /etc/rc.d/rc.inet1.conf
#
# This file contains the configuration settings for network interfaces.
# If USE_DHCP[interface] is set to "yes", this overrides any other settings.
# If you don't have an interface, leave the settings null ("").

# You can configure network interfaces other than eth0,eth1... by setting
# IFNAME[interface] to the interface's name. If IFNAME[interface] is unset
# or empty, it is assumed you're configuring eth<interface>.

# Several other parameters are available, the end of this file contains a
# comprehensive set of examples.

# =============================================================================

# Config information for eth0:
IPADDR[0]="192.168.1.105"
NETMASK[0]="255.255.255.0"
USE_DHCP[0]="no"
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]="icculus-wireless"
#DHCP_KEEPRESOLV[4]="yes"
#DHCP_KEEPNTP[4]="yes"
#DHCP_KEEPGW[4]="yes"
#DHCP_IPADDR[4]=""
#WLAN_ESSID[4]=BARRIER05
#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=96389dc66eaf7e6efd5b5523ae43c7925ff4df2f8b7099495192d44a774fda16"
#WLAN_WPA[4]="wpa_supplicant"
#WLAN_WPADRIVER[4]="ndiswrapper"

## Some examples of additional network parameters that you can use.
## Config information for wlan0:
#IFNAME[4]="wlan0" # Use a different interface name instead of
# the default 'eth4'
#HWADDR[4]="00:01:23:45:67:89" # Overrule the card's hardware MAC address
#MTU[4]="" # The default MTU is 1500, but you might need
# 1360 when you use NAT'ed IPSec traffic.
#DHCP_KEEPRESOLV[4]="yes" # If you don't want /etc/resolv.conf overwritten
#DHCP_KEEPNTP[4]="yes" # If you don't want ntp.conf overwritten
#DHCP_KEEPGW[4]="yes" # If you don't want the DHCP server to change
# your default gateway
#DHCP_IPADDR[4]="" # Request a specific IP address from the DHCP
# server
#WLAN_ESSID[4]=DARKSTAR # Here, you can override _any_ parameter
# defined in rc.wireless.conf, by prepending
# 'WLAN_' to the parameter's name. Useful for
# those with multiple wireless interfaces.
#WLAN_IWPRIV[4]="set AuthMode=WPAPSK | set EncrypType=TKIP | set WPAPSK=thekey"
# Some drivers require a private ioctl to be
# set through the iwpriv command. If more than
# one is required, you can place them in the
# IWPRIV parameter (separated with the pipe (|)
# character, see the example).
 
Old 10-23-2014, 08:18 PM   #4
frankbell
LQ Guru
 
Registered: Jan 2006
Location: Virginia, USA
Distribution: Slackware, Ubuntu MATE, Mageia, and whatever VMs I happen to be playing with
Posts: 19,580
Blog Entries: 28

Rep: Reputation: 6219Reputation: 6219Reputation: 6219Reputation: 6219Reputation: 6219Reputation: 6219Reputation: 6219Reputation: 6219Reputation: 6219Reputation: 6219Reputation: 6219
Code:
loopback 127.0.0.0
localnet 127.0.0.0
In /etc/networks, try changing local net to "192.168.1.0" and let me know what happens. Right now, the localnet setting is pointing to the loopback address.

I checked my localnet setting and it points to 192.168.x.0.

Last edited by frankbell; 10-23-2014 at 08:20 PM.
 
Old 10-24-2014, 08:34 AM   #5
hua
Member
 
Registered: Oct 2006
Location: Slovak Republic
Distribution: Slackware 14.2, current
Posts: 463

Rep: Reputation: 79
You are missing the GATEWAY in /etc/rc.d/rc.inet1.conf. And check /etc/reslov.conf too - your resolver DNS servers should be there (sometimes its the same as the GW).

Another question is whether you use NetworkManager or not.
 
  


Reply

Tags
internet connection, network activity, networking


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Slackware Internet Issues? aquamongoose Linux - Newbie 23 04-24-2011 07:06 PM
Internet issues! danielakkerman Linux - Networking 10 02-03-2008 09:34 AM
Slackware 11 and Internet issues w0lv3rin3 Linux - Newbie 16 07-11-2007 09:53 AM
internet issues dbinc Ubuntu 1 03-05-2006 10:24 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Networking

All times are GMT -5. The time now is 03:46 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration