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.
Hello. New to Slackware. Already can tell you that it is definitely much faster on an 800Mhz machine than Debian or Fedora. I have two network interface cards:
1) 3Com 3C905C-TXM
2) Linksys LNE100TX
I have looked in the file /etc/rc.d/rc.modules. I uncommented the
Quote:
/sbin/modprobe 3c59x
and the 3com card is working fine. Can anyone tell me which module needs to be used for the Linksys?
Seems like it is the tulip module that works with the Linksys. If not try via-rhine or the de4x5 module.
If you edit /etc/rc.d/rc.inet1.conf and configure the parameters for both eth0 and eth1 it will probably autodetect it and load the correct modules when you reboot.
do 'dmesg | grep eth0' and 'dmesg | grep eth1' to see what it does.
Note, if you are using a 2.6.x kernel you should be able to specify which card you want to be eth0 and which card you want to be eth1 with aliases in /etc/modprobe.d
root@slacker:~# dmesg|grep eth0
root@slacker:~# dmesg|grep eth1
eth1: ADMtek Comet rev 17 at 0xd800, 00:14:BF:5E:94:50, IRQ 9.
eth1: Setting full-duplex based on MII#1 link partner capability of 41e1.
root@slacker:~#
I have enabled tulip. I can still connect to the internet through eth0 but eth1 in Network Settings-Network Interfaces shows down. I can eit the configuration but when I try to enable it it says
Quote:
There was an error changing the device's state. You will have to do it manually.
I have to confess that I am not a network expert. Is it possible that I am experiencing a mac address conflict since nothing shows for an address for eth0?
I have enabled tulip. I can still connect to the internet through eth0 but eth1 in Network Settings-Network Interfaces shows down. I can eit the configuration but when I try to enable it it says
Try issuing
Code:
ifconfig -a
it should show you all your detected physical and logical interfaces, wether they are up or not.
It could be that the driver isn't printing anything to dmesg (?).
I have enabled tulip. I can still connect to the internet through eth0 but eth1 in Network Settings-Network Interfaces shows down. I can eit the configuration but when I try to enable it it says
I have to confess that I am not a network expert. Is it possible that I am experiencing a mac address conflict since nothing shows for an address for eth0?
Hi,
Please post the output of 'ifconfig -a' and 'lspci -vv'.
Post the /etc/rc.d/rc.inet1.conf file to see the device configurations.
01:0a.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado] (rev 6c)
Subsystem: 3Com Corporation 3C905C-TX Fast Etherlink for PC Management NIC
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 64 (2500ns min, 2500ns max), Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 3
Region 0: I/O ports at dc00 [size=128]
Region 1: Memory at ff8fec00 (32-bit, non-prefetchable) [size=128]
Expansion ROM at ff8a0000 [disabled] [size=128K]
Capabilities: [dc] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=2 PME-
01:0b.0 Ethernet controller: ADMtek NC100 Network Everywhere Fast Ethernet 10/100 (rev 11)
Subsystem: ADMtek Unknown device 0574
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 64 (16000ns min, 32000ns max), Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 9
Region 0: I/O ports at d800 [size=256]
Region 1: Memory at ff8ffc00 (32-bit, non-prefetchable) [size=1K]
Expansion ROM at ff8c0000 [disabled] [size=128K]
Capabilities: [c0] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=100mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Quote:
# /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:
DHCP_HOSTNAME[0]=""
# Config information for eth1:
IPADDR[1]=""
NETMASK[1]=""
USE_DHCP[1]="yes"
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="192.168.1.254"
# 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]="AuthMode=WPAPSK EncrypType=TKIP WPAPSK=7B1ABEEB5D197741923ED26727569C365E31212096A0EAFAD563B268BAD01CAF TxRate=0"
#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]="AuthMode=WPAPSK EncrypType=TKIP WPAPSK=thekey TxRate=0"
# 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 (space-separated, see the
# example).
USE_DHCP[0]="yes"
Your eth0 device is getting assignment from dhcp server. Last command in your /etc/rc.d/rc.inet1.conf file.
Your eth1 uses dhcp and the 'ifconfig -a' shows no assignment because it is not active/up.
BTW, why the need for both NICs up?
Both eth0 and eth1 are recognized with eth0 having an assigned IP.
As for your question about MAC conflict, the devices show the unique MAC address assigned to each. If you were doing MAC filtering and spoof the address then 'yes' there could be a conflict. Only if you enter the wrong data for the MAC addresses.
I was not specific about that I see..
I want to use the box as a internet content filter/proxy server. I have DSL and a wireless router/DSL modem (2Wire) attached to the incoming line. I want to put the Linux with DanGuardian/tiny proxy/firehol between the router and the rest of the boxes in the house (2 XP's, 1 Mac and the Linux).I assumed that you need one card (eth0) for cat5 to the router and one (eth1) for cat5 to a different (Linksys) wireless switch.
The 2 PC's and one Mac would connect to the internet through the Linksys switch on eth1 to the proxy server. The proxy server would connect to the internet through eth0 to the 2Wire modem.
Am I barking up the wrong tree?
I am also learning how to use Linux and experimenting with filters for a church network.
Internet <-> Wirless Router <-> Proxy Server <-> Switch <-> Internal network.
A switch will NOT give out IP addresses. You will have to configure eth1 on the Proxy Server, and either run a DHCP server on eth1, on the Proxy Server to give IPs to the internal network, or more simply, set static IPs on the internal network.
Here's my setup for this:
Code:
# Config information for eth0:
IPADDR[0]=""
NETMASK[0]=""
USE_DHCP[0]="yes"
DHCP_HOSTNAME[0]=""
DHCP_KEEPRESOLV[0]="yes"
# Config information for eth1:
IPADDR[1]="192.168.0.1"
NETMASK[1]="255.255.255.0"
USE_DHCP[1]=""
DHCP_HOSTNAME[1]=""
...
# Default gateway IP address:
GATEWAY=""
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
