You are not logged in.
Hello
My desktop which is running arch linux, can't be found by other devices on the network, it is connected by cable to my router, neither my sonos media player which also connected by cable to my router and my android phone which is connected through wireless to my router, but the phone and the sonos mediaplayer finds each other.
I've tried pinging my computer both through my hostname and the ip adress, but "unknown host" is only what I get.
Any suggestions?
EDIT: I do not use any firewalls on the computer, dynamic ip v4 adresses. Was no problem with Windows 7.
Last edited by Roberth (2013-05-19 17:21:58)
Use the Source, Luke!
Offline
Oh my, this could be anything, from wrongly addressed clients to broken cables!
'Unknown host' means the host your pinging, can't be found.
Check your dns and gateway!
Offline
Well, I need help to look for whats wrong so:)
And not to mention, I have fully working internet on all devices. And it's ip v6 I use.
I seem to not understand much of the new tools yet:
magda /home/roberth :( # 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 pfifo_fast state UP qlen 1000
link/ether 50:e5:49:3d:21:67 brd ff:ff:ff:ff:ff:ff
inet 10.0.1.6/24 brd 10.0.1.255 scope global enp4s0
valid_lft forever preferred_lft forever
inet6 fe80::52e5:49ff:fe3d:2167/64 scope link
valid_lft forever preferred_lft forever
Use the Source, Luke!
Offline
Oh, in that case I ain't gonna be of much help, only running IPv4, but still the rules are the same!
But I don't know how to 'address' in IPv6
Offline
I don't really know why I use ip v6, that was default, when I installed....
Use the Source, Luke!
Offline
You both have an IPv4 and an IPv6 address. If you want to ping an IPv6 connection, use ping6 with the IPv6 IP in brackets, in this case ping6 [fe80::52e5:49ff:fe3d:2167] will do the trick.
Otherwise, your IPv4 address is 10.0.1.6
since 2009
Offline
well it pings fine when pinging 10.0.1.6, I don't have ping6 on android.
Maybe the issue lies with having both ipv4 and ipv6?
Use the Source, Luke!
Offline
Well I disabled ipv6, and added samba share to sonos, but didn't work with hostname, so I added through ip adress and it worked, so then I was setting static ip, but when I start the network daemon, this comes up when I check the status, and when I start it, but I still have internet:
magda /home/roberth :( # systemctl status network.service
network.service - Wireless Static IP Connectivity
Loaded: loaded (/etc/systemd/system/network.service; disabled)
Active: failed (Result: exit-code) since Sun 2013-05-19 22:09:11 CEST; 5s ago
Process: 1002 ExecStart=/sbin/ip addr add 10.0.1.6/24 dev enp4s0 (code=exited, status=2)
Process: 1000 ExecStart=/sbin/ip link set dev enp4s0 up (code=exited, status=0/SUCCESS)
May 19 22:09:11 magda systemd[1]: network.service: main process exited, code=exited, status=2/INVALIDARGUMENT
May 19 22:09:11 magda systemd[1]: Failed to start Wireless Static IP Connectivity.
May 19 22:09:11 magda systemd[1]: Unit network.service entered failed state.
/etc/systemd/system/network.service:
[Unit]
Description=Wireless Static IP Connectivity
Wants=network.target
Before=network.target
BindsTo=sys-subsystem-net-devices-enp4s0.device
After=sys-subsystem-net-devices-enp4s0.device
[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/sbin/ip link set dev enp4s0 up
ExecStart=/sbin/ip addr add 10.0.1.6/24 dev enp4s0
ExecStart=/sbin/ip route add default via 10.0.1.1
ExecStop=/sbin/ip addr flush dev enp4s0
ExecStop=/sbin/ip link set dev enp4s0 down
[Install]
WantedBy=multi-user.target
What am I doing wrong?
Use the Source, Luke!
Offline
May 19 22:09:11 magda systemd[1]: network.service: main process exited, code=exited, status=2/INVALIDARGUMENT
I think this is the relevant part, but looking at the wiki, your config seems to be right, although mine looks very different, without all the variables!
I use networkmanager by the way!! Like this,
[Unit]
Description=Network Connectivity
Wants=network.target
Before=network.target
[Service]
Type=oneshot
RemainAfterExit=yes
EnvironmentFile=/etc/conf.d/network
ExecStart=/sbin/ip link set dev ${interface} up
ExecStart=/sbin/ip addr add ${address}/${netmask} broadcast ${broadcast} dev ${interface}
ExecStart=/sbin/ip route add default via ${gateway}
ExecStop=/sbin/ip addr flush dev ${interface}
ExecStop=/sbin/ip link set dev ${interface} down
[Install]
WantedBy=multi-user.target
Offline
Isn't the point of using networkmanager to avoid that?
Anyway, I installed networkmanager, but it is also behavin odd, I have internet etc, but networkmanager shows the same:
magda /home/roberth # nm-tool
NetworkManager Tool
State: disconnected
- Device: enp4s0 ---------------------------------------------------------------
Type: Wired
Driver: r8169
State: disconnected
Default: no
HW Address: 50:E5:49:3D:21:67
Capabilities:
Carrier Detect: yes
Speed: 1000 Mb/s
Wired Properties
Carrier: on
magda /home/roberth :( # nmcli nm
RUNNING STATE WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN
running disconnected enabled enabled enabled disabled
Use the Source, Luke!
Offline
Well I enabled static ip adresses, and it worked normally, but suddenly I lost all internet to the computer. So I disabled networkmanager, and used the regular network service, networkmanager seemed very buggy may that be the case?
Use the Source, Luke!
Offline
Well since you were not using NM before, I don't think thats the issue;)
Now if U use static addresses and everything behaves normal after removing NM, it's solved than?
Yes , I use NM myself, and it's a little buggy, a little sometimes , but mostly it behaves well!
Offline
Well after restarting it does:
magda /home/roberth # systemctl status network.service
network.service - Wireless Static IP Connectivity
Loaded: loaded (/etc/systemd/system/network.service; enabled)
Active: active (exited) since Mon 2013-05-20 20:49:06 CEST
Process: 214 ExecStart=/sbin/ip route add default via 10.0.1.1 (code=exited, status=0/SUCCESS)
Process: 211 ExecStart=/sbin/ip addr add 10.0.1.6/24 dev enp4s0 (code=exited, status=0/SUCCESS)
Process: 199 ExecStart=/sbin/ip link set dev enp4s0 up (code=exited, status=0/SUCCESS)
Buggy systemd I guess?
Use the Source, Luke!
Offline
I really hate it when people can't figure out their issue so they just say "Oh well it must be systemd." In some cases, things might very well be attributed to systemd. But this is not often the case, and more often it just means that the accusing party just doens't really know what is going on.
About your issue though. I see you have the r8169 module in use for your card. Might I ask what kind of ethernet card you have? Can you give the output of "lspci -nn | grep Ether"?
The reason I ask is because I have a machine that has this:
$ lspci -nn | grep Ether
0c:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168 PCI Express Gigabit Ethernet controller [10ec:8168] (rev 07)
So although I have seen just about everyone say that they are able to use the r8169 module just fine, when I first got this machine I had the hardest time installing the base group. It took nearly two hours to download the packages. But once I realized that there is an r8168 package in the repos, I installed that unloaded r8169 and loaded r8168, and it worked amazingly. Since then, I have gotten a new motherboard, which means that I also have a "new" ethernet card. I put that in quites beacuse it should be exactly the same, but the one I have now works just fine with r8169...
So if you have similar hardware, I might say that it might be buggy hardware, and not buggy systemd.
Offline
04:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168 PCI Express Gigabit Ethernet controller [10ec:8168] (rev 06)
Maybe we are in the same boat...
Use the Source, Luke!
Offline
Ha Woofy, glad you jumped in, I didn't know that card had problems!
Well, good luck solving it Roberth
Offline
04:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168 PCI Express Gigabit Ethernet controller [10ec:8168] (rev 06)
Maybe we are in the same boat...
Its a crapshoot, but try installing community/r8168 (assuming you are not using [testing]). Then unload r8169 with "modprobe -r r8169" and load r1868 with "modprobe r8168". If all goes well, you should have an interface back up.
If it turns out to work better, blacklist r8169 so it won't load at boot. It willl then load r8168 automatically.
Offline
Ha Woofy, glad you jumped in, I didn't know that card had problems!
Well, good luck solving it Roberth
From all the experiences I have read, and from what other people have told me when I ask, typically this card doesn't have problems. But I know that a two hour download of the base group wasn't something I could have imagined, and when I tried with r8168, it took the <5min to download and install those packages like it should.
Offline
Yes, clear! than it doesn't hurt to try and will hopefully solve it
Offline
Well loading the r8168 module made my system unstable, it froze during startup and shutdown, alsa wasn't being properly loaded etc.
Use the Source, Luke!
Offline
Interesting... it should certainly not do that. Did you remember to blacklist r8169?
Offline
Yep, the real trouble started when I blacklisted it, when just removing it and loading r8168 made just modprobe freeze.
Use the Source, Luke!
Offline
I have never experienced such a thing with the r8168 module. Not with linux-pf, not with linux-ck, linux-mainline, linux-lts, nor linux-lts34. This is both with self compilation and the use of modules from the repos. I kind of suspect that soemthing went awry during compilation.
Offline
Is /etc/modprobe.d/modprobe.conf the right place to blacklist it?
Use the Source, Luke!
Offline
Yes it is. I just stick all blacklists in a single file of /etc/modprobe.d/blacklist.conf.
Offline