Network issues with Samba Share

Jack128 · 06-28-2009, 04:39 AM

Good Morning,

I trying to install Slackware(64) current.
But with both versions 32 and 64 Bit the
setup utility configure my network wrong.
A DHCP Server is running in this network,
so it should receive a answer, but it didn't.

After set the interface manually up to the
right configuration, nothing changed. I
cant reach another pc with ping.

The drivers seems to be loaded right,
its the r8169 and the mii.

Can someone give me a advice?

Regards, Jack.
Cheers

onebuck · 06-28-2009, 06:25 AM

Hi,

You could run the 'netconfig' again. You could look at 'Configuring your network in Slackware'.

This link and others are available from 'Slackware-Links'. More than just Slackware® links!

Jack128 · 06-29-2009, 04:07 AM

Hello Gary,
'netconfig' isn't available in the setup
environment. The pkgtool don't list any
scripts, and the directory /var/log/scripts
is empty.

After testing my nic with the current Slackware
kernel (2.6.29.5) and the Slackware 12.2 kernel (2.6.27.7)
I found the issue with the r8169 module only in
the current kernel (2.6.29.5). Both versions, 32
and 64 Bit got this issue.

Slackware 12.2 kernel works just fine.

Maybe I'm find some new info's about
that issue with the kernel 2.6.29.5.

[EDIT]:
http://www.kernel.org/pub/linux/kern...geLog-2.6.29.5
r8169: avoid losing MSI interrupts

Maybe this fix broke the connectivity of
the module.

Regards, Jack.
Cheers

onebuck · 06-29-2009, 06:52 AM

Hi,

'Netconfig' is what you are running when you do your network configuration within the setup.

If you use 'pkgtool' to rerun scripts you will need to scroll down to get 'netconfig'. You can run 'netconfig' from the cli as root.

Jack128 · 06-29-2009, 08:42 AM

I've found the 'netconfig', but I only
can use it to reconfigure an existing
Slackware installation. But I want to
configure the nic on the fly, for using
my network to install Slackware from my
Server who's offers a Samba-Share with the
Slackware-Resources. And it looks like the
module is broken, because I haven't Any
traffic on the nic, Nothing. But with the
Slackware 12.2 kernel (2.6.27.7) no problems.

Regards, Jack.
Cheers

onebuck · 06-29-2009, 01:21 PM

Hi,

What do you mean on the fly?

Exactly what are you attempting?

Jack128 · 06-30-2009, 05:31 AM

Ok, here is the whole way I want to go:

Boot my PC over PXE
Load the Slackware Current Kernel, and the initrd.img
(from Current Resource isolinux/initrd.img) from the PXE Server
Kernel Boots, I set the Keyboard-Layout,
I login as root and run the 'setup' utility
I follow the setup, add swap, choice the partition for
installation, format the partition, and Then, I should choice
the "Source Media", my selection is "Install from Samba share".
I tried both, automatic and manually configuration.
I go on, set the server and the paths, and here I am.
Network is not reachable.
I leave the setup, run ifconfig and lsmod, checked both.
lsmod shows my nic module is loaded, ifconfig shows, if
I went automatic config a private ip address, and if I
went manually config the ip I set.
After that I run ping, and I can't receive any packet.
The module won't working.

And exactly the same way works with the Slackware 12.2
Kernel. But the Current one didn't.

Can you follow me?

Regrads, Jack.
Cheers

Jack128 · 07-09-2009, 08:04 AM

Hello,

I've got new info's about my problem.
I've updated my slackware-current copy,
but my problem is still there. So I booted
again the current kernel and the 12.2 kernel,
and I made a dmesg output. Here they are:

dmesg | grep r8169: (On Slackware-Current Kernel)

Code:

r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
r8169 0000:02:00.0: PCI INT A -> GSI 35 (level, low) -> IRQ 35
r8169 0000:02:00.0: setting latency timer to 64
r8169 0000:02:00.0: irq 43 for MSI/MSI-X
r8169: eth0: link down

dmesg | grep r8169: (On Slackware 12.2 Kernel)

Code:

r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
r8169 0000:02:00.0: PCI INT A -> GSI 35 (level, low) -> IRQ 35
r8169 0000:02:00.0: setting latency timer to 64
r8169 0000:02:00.0: no MSI. Back to INTx.
r8169: eth0: link down
r8169: eth0: link down
r8169: eth0: link up

The Slackware 12.2 Kernel works just great,
the Current one doesn't.

Regrads, Jack.
Cheers

onebuck · 07-09-2009, 09:02 AM

Hi,

With the 'Slackware -current' system do a 'ifconfig -a', 'route -n'. Post the output.

Your dmesg output states the device is recognized but the link is down.

zhjim · 07-09-2009, 09:59 AM

I had a similar issue with a NIC with the realteak chip. It just would not get any IP over DHCP also another card in the same box with the same cable did fine. I remember to read something about the MAC not gettin read propably from the nic. Solution to my problem was to change the mac addr of the nic like this.

Code:

ip addr set hwaddr 00:01:02:03:04:05

After that dhclient just worked fine.
This all happend on a freshly installed system of debian 5.0 (lenny).

To be sure its the same error. Can you print the output of

Code:

dhclient eth0

Pretenting the nic is also eth0.

What module does your card use?

Jack128 · 07-10-2009, 01:48 PM

Here are the outputs:

ifconfig -a:

Code:

eth0      Link encap:Ethernet  HWaddr 00:19:66:54:9D:61  
          inet addr:169.254.46.207  Bcast:169.254.255.255  Mask:255.255.0.0
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:43 Base address:0x4000 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

route -n:

Code:

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
169.254.0.0     0.0.0.0         255.255.0.0     U     0      0        0 eth0
127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0 lo

ip addr set hwaddr 00:01:02:03:04:05:

Code:

ip: unknown command set

dhclient eth0:

Code:

dhclient is not available in the setup environment.

Regards, Jack.
Cheers

onebuck · 07-10-2009, 04:15 PM

Hi,

What do you have in your '/etc/rc.d/rc.inet1.conf'?

Your eth device is recognized and has a IP 169.254.46.207. How are you getting that IP? You can setup with that IP or I would setup a static IP first within your assignment, 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

Be sure to use your assigned IP information within the above example.

You should have your '/etc/resolv.conf' setup with your 'ISP DNS' nameservers.

Code:

 sample '/etc/resolv.conf';

search 192.168.0.1           #setup to your gateway

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

zhjim · 07-14-2009, 05:31 PM

Not ment to be rude. But ifconfig is somewhat outdated. I guess even on Slackware. (Consider that the last version was 11.0 I used). The new tool is ip so (better) stick with this.

The 169.254.*.* is a adress you get when dhcp does not have a ip for you. A.K.A. the machines does not get a valid dhcp-lease.

You're sure that the dchp-server is on the same physical network like your machine? physical here means on the same switch (hub if anymore in use).

Get the network settings and a free ip and set it by hand and see if you can ping any machine. If not do the usual physical replacemants. Change cable. Change nic. Change switch.

(by mind. Some of the stuff I mentioned before might not have the right syntax)

Code:

ip addr add 192.168.0.23/24 dev eth0

Should get an IP on the 255.255.255.0 network with an ip of 192.168.0.23.

give us some information about the ip settings in the network and i provide you with some working options.

Another thing, please do a whereis ip to verify that the ip command is installed.

onebuck · 07-14-2009, 06:20 PM

Hi,

Maybe you feel 'ifconfig' is outdated but you will find it installed on most GNU/Linux.

Why do you issue the hint to 'whereis ip'?

Jack128 · 07-15-2009, 11:16 AM

I said post's ago, the Hardware is working.
The Cable, the nic, the switch, all is up
and running. The problem is the connectivity
of the nic-module in case of Slackware Current.
All is fine on Slackware 12.2.

And I said too, both ways, set the ip address
manually to static and/or automatic over dhcp
give's no solution. I can't ping any host in
my network.

The dhcp-Server is configured correctly,
its up and running. I can get a ip over dhcp
with Slackware 12.2. No problem with this
kernel version.

But with the new kernel version 2.6.29.X.
X is the Slackware Current case 5.

So, my nic configuration is the same as
the the configuration on 12.2.

It could only be a kernel version issue.

Regards Jack.
Cheers