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.
What is the problem with posting the file '/etc/udev/rules.d/70-persistent-net.rules'? It's not golden.
You are not helping us by not posting the requested information to help you!
The first line removes the tg3 module.
Second line adds the broadcom (Broadcom PHY driver).
Third line adds the tg3 (Broadcom Tigon3 ethernet driver)
After that post the 'lsmod' and 'ifconfig -a'.
If you have a 'eth0' device then I would setup a static IP first, do as root from cli;
Code:
~#ifconfig -a #get recognized devices
~#ifconfig eth0 192.168.0.10 #set to a available IP
~#route add default gw 192.168.0.1 #set to your gateway
~#route -n #show the route table
~#ifconfig eth0 up #should be up already
~#ping 192.168.0.1 #ping your gateway
~#ping 208.69.32.130 #google.com IP
~#ping google.com #test DNS, if fail then
#check /etc/resolv.conf
Post the '/etc/rc.d/rc.inet1.conf' file & '/etc/resolv.conf' so we can see if things are setup properly.
You should have your '/etc/resolv.conf' setup with your 'ISP DNS' nameservers.
Code:
sample '/etc/resolv.conf';
#search 192.168.x.xyou could set this to the router IP
nameserver xxx.xxx.xxx.xxx #ISP DSN 'replace xxx.xxx.xxx.xxx
#with IP from your ISP
nameserver 4.2.2.1 #Verizon third level DNS
nameserver 4.2.2.2
nameserver 4.2.2.3
nameserver 4.2.2.4
You should have your '/etc/resolv.conf' setup with your 'ISP DNS' nameservers. After you find that the static works then use the information to edit or generate a new /etc/rc.d/rc.inet1.conf.
You can restart init via the '/etc/rc.d/rc.inet1.conf restart' issue.
If the static works then we'll attempt to work up the correct configuration(s) .
I could not give all the results asked for by this
because my message exceeded the size limits to post,
so this is part one and part two will follow, maybe
part three also, who knows?
results of modinfo broadcom
Code:
filename: /lib/modules/2.6.33.4/kernel/drivers/net/phy/broadcom.ko
license: GPL
author: Maciej W. Rozycki
description: Broadcom PHY driver
depends: libphy
vermagic: 2.6.33.4 SMP mod_unload
Now where is the 'lsmod' ,'ifconfig -a' and the ''/etc/udev/rules.d/70-persistent-net.rules'?
Your device is now shown as eth1. I bet you could setup static by the above suggested procedure. You will have Internet. The problem still is the udev rules we've been requesting you to show for a too long.
BTW, You could place in a paste.bin to show large outputs. We'll show you later.
edit: look at the output below and see the device & module
Your device is now shown as eth1. I bet you could setup static by the above suggested procedure. You will have Internet. The problem still is the udev rules we've been requesting you to show for a too long.
You were right, I did the specified things changing eth0 to
eth1 and I could ping the addresses you gave, first time that
has happened.
I thought I posted those rules, but I must have missed it.
I will post them shortly, next post.
Here is contents of the file /etc/udev/rules.d/70-persistent-net-rules:
# This file was automatically generated by the /lib/udev/write_net_rules
# program, run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single
# line, and change only the value of the NAME= key.
I have not quite got on the internet yet. I can
ping the addresses, including google, but I can't
get them on a web browser. I tried putting in
the address, 203.69.32.130 on the url line,for example,
and I get the error message "can't find server at
block.opendns.com".
My brain is fried right now, so I'll take another
look at this tomorrow and see if I can figure out
how to proceed from what you said.
How do you have the system setup now? How do you have the '/etc/rc.d/rc.inet1.conf' setup?
Don't forget, Configuring your network in Slackware is Alien_Bob's excellent article on the way network cards are configured in Slackware. Plus there are Loads of internal reference links. Help getting Ethernet or Wireless working.
As to long list of data or whatever, you can use a PasteBin . It's pretty self explanatory at the PasteBin, plus it's FREE.
Since you must unload tg3 and load broadcom before tg3 loads, it may be helpful to throw this in /etc/rc.d/rc.netdevice:
Code:
rmmod tg3
modprobe broadcom
modprobe tg3
Make rc.netdevice executable with
Code:
# chmod +x /etc/rc.d/rc.netdevice
Then remove /etc/udev/rules.d/70-persistent-net.rules and let it regenerate upon restart. Hopefully it will get an eth0 name; if not you will have to edit 70-persistent-net.rules and rename the device to eth0 instead of eth1. I believe netconfig only configures the eth0 device (though you can configure eth1 in /etc/rc.d/rc.inet1.conf if you know what you're doing), so it would be easier to get the device to be eth0 instead of eth1 (especially since you do not have another device taking up the eth0 slot).
The adapter still
works, obviously, because I can still get on the internet
in Windows.
It's funny how often that is the way that people know that something is amiss in Linux and not with hardware ... Windows is still working trouble-free!!
Well, its another day, and I can think again. I am going to the
gym in a few minutes, and after I will try to put all this guidance
together and see how far I can get. It has to be very close right
now, with actually being able to use the network hardware and
actually ping things on the network, so it can't be that much
more difficult to get browsers cooperating again. I was really
surprised when I could not get anything on any of the browsers,
like google, yahoo, etc., but yet I could ping google with no
problems in a terminal window. Until later, thanks for all
the time, effort and education you have provided, I will report
back as I progress.
Well, its another day, and I can think again. I am going to the
gym in a few minutes, and after I will try to put all this guidance
together and see how far I can get. It has to be very close right
now, with actually being able to use the network hardware and
actually ping things on the network, so it can't be that much
more difficult to get browsers cooperating again. I was really
surprised when I could not get anything on any of the browsers,
like google, yahoo, etc., but yet I could ping google with no
problems in a terminal window. Until later, thanks for all
the time, effort and education you have provided, I will report
back as I progress.
I would look at the 'route' assignments. Show the 'route -n' results. But my bet is on DNS, how do you have the DNS setup in '/etc/resolv.conf'? Plus, please show us the '/etc/rc.d/rc.inet1.conf' file. You can XXX out any security information within.
Now that we know the 'udev' rules are setting up the device, even if it's 'eth1' instead of your desired 'eth0'. You can edit the '/etc/udev/rules.d/70-persistent-net.rules' or as T3slider suggests to work via 'netdevice'.
We could continue to trouble shoot and find how/why things are being setup in this manner.
checked /etc/udev/rules.d/70-persistent-net.rules file
and there was no entry concerning eth0 or eth1.
Then I executed manually rc.netdevice above.
checked /etc/udev/rules.d/70-persistent-net.rules file
and there was entry for eth0. yep, looks good so far.
Then I did netconfig, asking for DHCP.
Checked file rc.inet1.conf and it showed that eth0
USE_DHCP[0]="yes"
Now my network is configured, my drivers loaded, I think.
Run lsmod and yes, tg3 and broadcom both loaded.
Now I ping 192.168.0.1
Network is unreachable.
By the way I originally used DHCP when I ran netconfig
at original installation and everything worked.
So now lets try setting the IP.
~#ifconfig -a
showed eth0 was there.
~#ifconfig eth0 192.168.0.101
~#route add default gw 192.168.0.1
~#route -n
showed I had gateway setup Using eth0
~#ifconfig eth0 up
~#ping 192.168.0.1
worked
~#ping 208.69.32.130
worked on google using address
~#ping google.com
unknown host
I guess DNS failed. I check /ect/resolv.conf
and it is empty file.
Tried setting up /etc/resolv.conf with various
entries like:
nameserver 192.168.0.1
nameserver 4.2.2.1
nameserver 4.2.2.2
nameserver 4.2.2.3
Tried several changes to 192.168.0.1 like
192.168.0.101
192.168.x.x
Always got unknown host google.com
Here is my rc.inet1.conf
Code:
# /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]=""
NETMASK[0]=""
USE_DHCP[0]="yes"
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 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 nstead 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 dont 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).
Setup the 'gateway=' to your gateway in the '/etc/rc.d/rc.inet1.conf'. Then do a '/etc/rc.d/rc.inet1 restart'.
As to the DNS, set the first entry to your ISP provided IP for DNS. You could have a router setup error and the '192.168.0.1'(router) is not setting up the DNS properly or passing. Just comment out the 'search 192.168.0.1'. The Verizon (4.2.2.x)third level DNS should respond & reply but slower.
Post the output for 'route -n', so we can see the kernel route table.
Your continued filtering of requested information just causes poor diagnosis since we cannot discern. I request the outputs so I can SEE and possibly provide the correct methodology for a solution.
If you are going the 'netdevice' method then you must initialize this, since Slackware doesn't use the '/etc/rc.d/rc.netdevice' methods any longer. You could execute 'netdevice' from '/etc/rc.d/rc.local'. But to do it right we need to find out why it's not being setup through the scheduler(kernel).
The second removal of '/etc/udev/rules.d/70-persistent-net.rules' should not have been performed. You had the device setup and the rules set. Your arbitrary hit and miss is just creating issues and is a poor method of trouble shooting.
Back out to where things were working. I think the kernel route table was the problem but since you seem to think our requests for your active feedback of information is not important.
Self diagnosis is fine but your history shows that you don't understand how to set things up properly. We will just keep spinning and spinning without get things correct.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
