On 04/09/2014 08:06 AM, heinzchr wrote:
>
> today I was able to produce the some more output (and copied it - no
> typing…)
Thank-you; it is appreciated.
> Code:
> --------------------
> sr1111:/home/christoph # ip addr
> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> inet 127.0.0.1/8 scope host lo
> valid_lft forever preferred_lft forever
> inet6 ::1/128 scope host
> valid_lft forever preferred_lft forever
> 2: enp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
> link/ether 00:22:19:28:1a:cb brd ff:ff:ff:ff:ff:ff
> inet 10.122.114.111/23 brd 10.122.115.255 scope global enp4s0
> valid_lft forever preferred_lft forever
> inet6 fe80::222:19ff:fe28:1acb/64 scope link
> valid_lft forever preferred_lft forever
> --------------------
This is probably nothing, but just to be sure…
All of the first lines in your code blocks have a couple of leading
spaces. You wrote ‘no typing’ but maybe you didn’t count that as typing.
Still, did you indent those on puropse? I ask because otherwise is it
possible your hostname actually has a couple of spaces at the beginning?
This is all probably nothing, but if that’s actually there it’s probably
not good.
> Code:
> --------------------
> sr1111:/home/christoph # ip route
> default via 10.122.114.1 dev enp4s0 proto static
> 10.122.114.0/23 dev enp4s0 proto kernel scope link src 10.122.114.111 metric 1
> --------------------
You mentioned originally that DHCP does not work, so you’re setting the
network stuff manually. I assume you have confirmed that all IPs are
correct, and that the netmask is also correct (/23, or 255.255.254.0
instead of /24, or 255.255.255.0). If you haven’t checked a dozen times
before, now’s a good time to verify.
> Code:
> --------------------
> sr1111:/home/christoph # ip -s link
> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT
> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> RX: bytes packets errors dropped overrun mcast
> 33440 351 0 0 0 0
> TX: bytes packets errors dropped carrier collsns
> 33440 351 0 0 0 0
> 2: enp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT qlen 1000
> link/ether 00:22:19:28:1a:cb brd ff:ff:ff:ff:ff:ff
> RX: bytes packets errors dropped overrun mcast
> 66729 1029 0 0 0 0
> TX: bytes packets errors dropped carrier collsns
> 19746 201 0 0 0 0
> --------------------
>
>
> Code:
> --------------------
> sr1111:/home/christoph # dmesg | grep enp4s0
> 5.869096] systemd-udevd[318]: renamed network interface eth0 to enp4s0
> 18.666098] IPv6: ADDRCONF(NETDEV_UP): enp4s0: link is not ready
> 20.340766] tg3 0000:04:00.0 enp4s0: Link is up at 100 Mbps, full duplex
> 20.340774] tg3 0000:04:00.0 enp4s0: Flow control is off for TX and off for RX
> 20.340789] IPv6: ADDRCONF(NETDEV_CHANGE): enp4s0: link becomes ready
> --------------------
>
>
> Code:
> --------------------
> sr1111:/home/christoph # /sbin/ifconfig
> enp4s0 Link encap:Ethernet Hardware Adresse 00:22:19:28:1A:CB
> inet Adresse:10.122.114.111 Bcast:10.122.115.255 Maske:255.255.254.0
> inet6 Adresse: fe80::222:19ff:fe28:1acb/64 Gültigkeitsbereich:Verbindung
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:1866 errors:0 dropped:0 overruns:0 frame:0
> TX packets:356 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 Sendewarteschlangenlänge:1000
> RX bytes:120927 (118.0 Kb) TX bytes:29722 (29.0 Kb)
> Interrupt:17
> lo Link encap:Lokale Schleife
> inet Adresse:127.0.0.1 Maske:255.0.0.0
> inet6 Adresse: ::1/128 Gültigkeitsbereich:Maschine
> UP LOOPBACK RUNNING MTU:65536 Metric:1
> RX packets:563 errors:0 dropped:0 overruns:0 frame:0
> TX packets:563 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 Sendewarteschlangenlänge:0
> RX bytes:53556 (52.3 Kb) TX bytes:53556 (52.3 Kb)
> --------------------
You have traffic going both ways. I’m starting to wonder if this is more
of a network issue than a computer issue. Did you try this?
Code:
ping -c 4 10.122.114.1
> I really get frustrated here… :X
Have you tried another computer, with any OS, at this same spot in your
“factory”? It is possible that the port you’re using requires a certain
MAC address (thus the DHCP failure), or uses some 801.1x (I forget which
ones… too many of them) technologies to limit systems that authenticate
(you’re not authenticating per your report). You could also be having a
VLAN issue, where you are using settings from a working system (on one
VLAN) but then are somehow getting plugged into another.
Have you checked with, or are you yourself, the local network administrator?
–
Good luck.
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below…