Freek de Kruijf wrote:

Op maandag 9 oktober 2017 07:42:30 CEST schreef Per Jessen:

...

Dave Smith wrote:

...

I recently installed 42.3 on a second computer. This computer has 2 disks. One disk for Leap 42.3 and the other for Windows 10. The install went very smooth (as usual) and I use grub to boot into my disks. I was able to update 42.3 and noticed no issues. Today I went to use the machine and discovered I have no internet. Ifconfig shows I have no address assigned via dhcp. To eliminate a hardware issue I booted into Windows. Windows had internet connectivity. The motherboard is an ASRock H97 Pro4 which uses the Intel gigabyte ethernet chip, the same one used by the machine I am typing from now (leap 42.2).

I then switched to a static ip to see if it is a dhcp issue. I used YAST to configure the static ip. Using wicked I was able to start and stop the network successfully. Ifconfig showed my static ip address assigned to eth0. Still no internet. lsmod shows e1000e is loaded.

To have internet, you need a default route - with the static config, can you ping the router or any other machine on your network?

...

My system consists of a NETGEAR ProSafe™ Gigabit 8 Port VPN Firewall FVS318G router attached to a cable modem. All devices are plugged into the router which assigns ip addresses via dhcp during boot. I have the two computers, a ps3, and a cisco wifi plugged into the router. All are visible to the router and have internet access. On the machine in question when I boot into windows the router shows the computer and assigned ip address(dhcp). When I boot into 42.3 nothing shows up on the router, dhcp or static ip.

That sounds like a config problem on your Leap423. Maybe post the config here. /etc/sysconfig/network/ifcfg-eth0 ?

When you configure a static IP address, you also need to define the route and the DNS servers in YaST.

Yes, that's why I asked about it above, but it seems more important to figure out why dhcp isn't working. -- Per Jessen, Zürich (14.0°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

* Carlos E. R. [10-09-17 10:25]:

On 2017-10-09 13:03, Per Jessen wrote:

...

Freek de Kruijf wrote:

...

Op maandag 9 oktober 2017 07:42:30 CEST schreef Per Jessen:

...

...

...

That sounds like a config problem on your Leap423. Maybe post the config here. /etc/sysconfig/network/ifcfg-eth0 ?

The log could have some clue.

...

...

When you configure a static IP address, you also need to define the route and the DNS servers in YaST.

Yes, that's why I asked about it above, but it seems more important to figure out why dhcp isn't working.

Notice that when he configures dhcp, the router does not see the Linux machine:

...

...

...

...

On the machine in question when I boot into windows the router shows the computer and assigned ip address(dhcp). When I boot into 42.3 nothing shows up on the router, dhcp or static ip.

But maybe the router can not display a machine that has no IP address.

how can one have a networked machine w/o an ip address? shouldn't the OP assign/reserve the machine an address in the router config? -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Patrick Shanahan wrote:

* Carlos E. R. [10-09-17 10:25]:

...

On 2017-10-09 13:03, Per Jessen wrote:

...

Freek de Kruijf wrote:

...

Op maandag 9 oktober 2017 07:42:30 CEST schreef Per Jessen:

...

...

...

That sounds like a config problem on your Leap423. Maybe post the config here. /etc/sysconfig/network/ifcfg-eth0 ?

The log could have some clue.

...

...

When you configure a static IP address, you also need to define the route and the DNS servers in YaST.

Yes, that's why I asked about it above, but it seems more important to figure out why dhcp isn't working.

Notice that when he configures dhcp, the router does not see the Linux machine:

...

...

...

...

On the machine in question when I boot into windows the router shows the computer and assigned ip address(dhcp). When I boot into 42.3 nothing shows up on the router, dhcp or static ip.

But maybe the router can not display a machine that has no IP address.

how can one have a networked machine w/o an ip address?

shouldn't the OP assign/reserve the machine an address in the router config?

It works with Windows, so it sounds much like the problem is in his Linux config. -- Per Jessen, Zürich (13.8°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Le 09/10/2017 à 16:29, Patrick Shanahan a écrit :

shouldn't the OP assign/reserve the machine an address in the router config?

I don't know for wifi (because authentication), but on a threaded network, a machine can run the IP it wants without advertising it, at least at start. It can even be on the dhcp reserved part, and the machine can work and go to internet. Of course the router know it as soon as traffic is made on the net. of course if an other machine have the same IP, there are problems. It depends also of the router to store (or not) the IP not covered by it's dhcp. simpler ones don't seems to care. jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Op maandag 9 oktober 2017 17:02:14 CEST schreef Patrick Shanahan:

* jdd@dodin.org [10-09-17 10:55]:

...

Le 09/10/2017 à 16:29, Patrick Shanahan a écrit :

...

shouldn't the OP assign/reserve the machine an address in the router config?

I don't know for wifi (because authentication), but on a threaded network, a machine can run the IP it wants without advertising it, at least at start.

I assign ip's to expected instruments, phone, tablet, laptops, and allow the router to assign addresses to "other" machines. wifi is just another connection different than wire.

Indeed and functions exactly the same re. networking. Just enter the proper data IP ( in the range your router provides, 192.168.1.*, 10.10.138.*) DNS 8.8.8.8, 8.8.4.4 Gateway: the internal IP address of your router. Mostly easy to pick up from a device that does work -- Gertjan Lettink, a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 2017-10-09 17:45, Anton Aylward wrote:

It can also simplify ACLs. Personally I hate the idea of early binding ACLs but sometimes it is very useful.

I can tell my printer to refuse any device on the network that isn't my PC, my phone or or my laptop or my tablet. It is a simple security hack.

This could be interesting to force anybody in a network going to print to do it via the cups server instead of directly to the printer. How do you do that? Maybe on a different thread. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)

Here is the ifconfig-eth0 file. The only thing I find odd is the name given in the file. Not sure what the (2) is in there for, it would suggest there is a 1 somewhere but I have never found it. This system was literally a straight install with no glitches, a couple of updates, and then a network failure. I did not even look at the network until I no longer had it. Has me stumped. On Mon, Oct 9, 2017 at 1:13 PM, Dave Smith wrote:

I have read all of your comments and here are a couple of things that I did not mention in my first post. Both the default gateway and nameserver are set to the router ip address. I am not even able to ping the router or any other device on the lan. With a static ip address ifconfig shows eth0 with the correct ip address. Using dhcp ifconfig shows eht0 with no ip address. While using dhcp it always times out and I get the message 'setup in progress'. I believe there was a kernel update in the last batch of updates. Could the e1000e module be broken. The computer acts like everything is okay with the network and is just waiting for a response from the router. The router on the other hand never receives any data from the computer. I will get the ifconif-eth0 file posted as soon as I can get it over to this computer. I have looked it over and see nothing different from the same file on the machine I am using now.

On Mon, Oct 9, 2017 at 11:45 AM, Anton Aylward wrote:

...

On 09/10/17 11:02 AM, Patrick Shanahan wrote:

...

I assign ip's to expected instruments, phone, tablet, laptops, and allow the router to assign addresses to "other" machines. wifi is just another connection different than wire.

While a good DHCP + DNS set-up can handle the dhcp telling the dns about devices, having static, predefined addresses for key devices like the printer, the router/gateway can simplify a lot of things about configuration and debugging.

It can also simplify ACLs. Personally I hate the idea of early binding ACLs but sometimes it is very useful.

I can tell my printer to refuse any device on the network that isn't my PC, my phone or or my laptop or my tablet. It is a simple security hack.

I'm sure Patrick can give other illustrations.

-- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon?

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 10/09/2017 01:45 PM, Dave Smith wrote:

I fired up wireshark. Wireshark is able to capture all of the network chatter occurring on my lan from the other devices. There is a repeating dhcp discover associated with ip 0.0.0.0 which I assume to be the 42.3 machine. Still no address assigned to the 42.3 machine.

The discover should have a source MAC that matches the Linux box. The 0.0.0.0 or unspecified source IP address is used until an address has been received from the DHCP server. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Dave Smith wrote:

I believe there was a kernel update in the last batch of updates. Could the e1000e module be broken.

It could. Do you see anything unusual in the 'dmesg' output, specifically related to that driver?

The computer acts like everything is okay with the I will get the ifconif-eth0 file posted as soon as I can get it over to this computer. I have looked it over and see nothing different from the same file on the machine I am using now.

Yep, I agree, looks good. /Per -- Per Jessen, Zürich (12.0°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

A lot of responses with a ton of ideas. There also seems to be some confusion about my setup which I will try to clarify. It is a very basic home configuration, nothing fancy. The lan consists of a cable modem and router. The router connects to the cable model using dhcp and does indeed have an ip address different from my lan ip. The router also gets ip addresses for the name servers from my isp and stores them. Connected to the router are 2 computers, 1 wifi router, 1 printer, 1 nas, and 1 ps3. The router acts as the dhcp server for everything connected to it using the address 192.168.133.x. 192.168.133.2 through 192.168.133.9 are reserved for a static ip. The printer and nas have static ip's everything else connects to the router via dhcp. All devices attached to the router use the routers ip of 192.168.133.1 for both the default gateway and nameserver. No other device on the lan has difficulty connecting to the router or getting to the internet. The 42.3 box did not have any problems connecting either until the last update. I cannot connect to the router using either dhcp or setting a static ip nor does the router see the 42.3 machine when using a static ip. Using a static ip the 42.3 machine cannot get to the router or internet nor ping the router or any device connected to the router. Truthfully, I was surprised that wireshark was able to receive packets from the network. I use 192.168.133.2 for the nas and 192.168.133.8 for the printer. I used 192.168.133.3 for the 42.3 machine and set the default gateway and nameserver to 192.168.133.1. Yast was used for all of the configurations I have done thus far. Didn't realize there was no live version for 42.3 so am downloading knoppix 8.1 now. I am beginning to believe if I did a reinstall of 42.3 I would again have no problem with the network. Will let you know, Dave On Mon, Oct 9, 2017 at 2:15 PM, Carlos E. R. wrote:

On 2017-10-09 20:11, Per Jessen wrote:

...

Dave Smith wrote:

...

I believe there was a kernel update in the last batch of updates. Could the e1000e module be broken.

It could. Do you see anything unusual in the 'dmesg' output, specifically related to that driver?

Can't be, as it works with fixed IP address.

-- Cheers / Saludos,

Carlos E. R.

(from 42.2 x86_64 "Malachite" (Minas Tirith))

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 2017-10-09 21:49, Dave Smith wrote: ...

I cannot connect to the router using either dhcp or setting a static ip nor does the router see the 42.3 machine when using a static ip. Using a static ip the 42.3 machine cannot get to the router or internet nor ping the router or any device connected to the router. Truthfully, I was surprised that wireshark was able to receive packets from the network. I use 192.168.133.2 for the nas and 192.168.133.8 for the printer. I used 192.168.133.3 for the 42.3 machine and set the default gateway and nameserver to 192.168.133.1. Yast was used for all of the configurations I have done thus far.

Ok, then open two terminals as root. In one, run "journalctl --follow" and let it there. In another, try "rcnetwork restart", then "ifconfig" and report back all the text that you get on both terminals. You can pipe all that to a file in order to send from another computer: whatever command | tee -a somefile.txt -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith))

Downloaded knoppix 8.1 live cd. Ran it. It make a dhcp connection without any problems. Anton I will try all of your suggestions and report back in the morning. I don't know what happened to 42.3. I did nothing to this install except a couple of prompted updates. On Mon, Oct 9, 2017 at 7:34 PM, Anton Aylward wrote:

On 09/10/17 03:49 PM, Dave Smith wrote:

...

The 42.3 box did not have any problems connecting either until the last update.

If you are sure of that then check your logs to see what was updated then.

-- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon?

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 2017-10-10 03:37, Anton Aylward wrote:

On 09/10/17 08:12 PM, Dave Smith wrote:

...

I don't know what happened to 42.3. I did nothing to this install except a couple of prompted updates.

What were those updates? When you determine what was updated you can use the 'rpm' tool to list the files updated.

Run this: rpm -q -a --queryformat "%{INSTALLTIME}\t%{INSTALLTIME:day} \ %{BUILDTIME:day} %-30{NAME}\t%15{VERSION}-%-7{RELEASE}\t%{arch} \ %25{VENDOR}%25{PACKAGER} == %{DISTRIBUTION} %{DISTTAG}\n" \ | sort | cut --fields="2-" | tee rpmlist | less -S It displays and saves a list of all installed rpms sorted by date. Dave has to look at the last ones. Also knowing the repo mix would be interesting: zypper lr --details > repolist and attach "repolist" to an email here. It is plain text. And, what command and options were used for the update? -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)

On 10/09/2017 10:55 AM, jdd@dodin.org wrote:

Le 09/10/2017 à 16:29, Patrick Shanahan a écrit :

...

shouldn't the OP assign/reserve the machine an address in the router config?

I don't know for wifi (because authentication), but on a threaded network, a machine can run the IP it wants without advertising it, at least at start. It can even be on the dhcp reserved part, and the machine can work and go to internet. Of course the router know it as soon as traffic is made on the net.

of course if an other machine have the same IP, there are problems.

It depends also of the router to store (or not) the IP not covered by it's dhcp. simpler ones don't seems to care.

Actually, there's more to it than that. Duplicate Address Detection (DAD) is often used now, to see if an address is in use. Even without DAD, a device will often do a gratuitous ARP, to let other devices know it's on the network. It will also ARP requests to determine the MAC address for the gateway etc.. So, there are lots of things that "advertise" an IP address by an interface that's starting up, even when DHCP is not used. Fire up Wireshark and filter on ARP, to see what actually happens. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 2017-10-09 15:27, Anton Aylward wrote:

On 08/10/17 02:26 PM, Dave Smith wrote:

...

To eliminate a hardware issue I booted into Windows. Windows had internet connectivity.

Well, yes there is that ... for those that have Windows to hand.

I don't, so I solve Linux problems with Linux.

I keep, to hand, a few generations of Knoppix. Weird to say, but Knoppix, for all its other limitation, seems to be great in addressing issues to do with configuration. It runs remarkably well on anything, provided you match architecture (don't run x86 on IBM AIX). It seems to have no problems repairing damaged file system that I've met on my own and other machines. Yes, you may have to add to the book CLI, turn off USB or other 'distractions'.

I don't recommend Knoppix as a running system, just as a maintenance tool for extreme cases.

My point here is that if you have a Linux class problem then I'm not sure how reassuring a Windows verification is going to be.

In this case it is, because it shows that the hardware works. And he also setup up a static configuration in Linux, and it worked. It is dhcp which does not. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)