Re: Support for direct connection without cross cable / Run Avahi Zeroconfig Services
Hi Daniel, On 10/11/2011 03:35 PM, Daniel Yek wrote: +ACs-AD4 I noticed that windows can setup networking +ACs-AD4 to a direct-connected ... device +ACs-AD4 (tested ... with network-drives, such as WD MyBook World) +ACs-AD4 with ... straight ... ethernet cable. Hi, Could you make sure that you installed and ran Avahi? I think Avahi could enable this same easy, direct, connection with your WD MyBook World. I don't have a way to test it now, but I am interested to find out if you have luck with Avahi. I have Avahi installed and it's not working with it, but I didn't do any configuration (it should not need any, right?) +AKA- WD MyBook World and Windows implemented zeroconfig networking (with address range: 169.254.x.x/255.255.0.0), which make the direct connection works. Yep, on Windows I can confirm they always setup with 169.254.+ACo- addresses. Without Avahi, it is possible that a Linux command such as this: +ACs-ACM ifconfig address 169.254.1.23 eth0 could enable HTTP connection to WD MyBook World. What I just did is setting up a Wired connection with Method: Shared to other computers in NM, and it's working. Thanks for the reply and the clues, appreciated. All the best. -arief ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Support for direct connection without cross cable / Run Avahi Zeroconfig Services
Hi Sven, On 10/11/2011 07:26 PM, Sven Nielsen wrote: I am not actually sure where the problem is here? My NM can do this without any problems (0.8.1 on Ubuntu Maverick), and I use it all the time. In the nm applet just go to the tab for wired connections, edit your eth0 (or whatever connection), ipv4 settings, and choose shared with other machines (my ui is german, so cannot state the exact name of that option). Thanks for this clue, I was wondering about that option, but thought it was for internet connection sharing, so I didn't tried it. Now that I tried it (It's called Shared to other computers in the method option), it's working. Yay! :) All the best. -arief ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Support for direct connection without cross cable / Run Avahi Zeroconfig Services
I noticed that windows can setup networking to a direct-connected ... device (tested ... with network-drives, such as WD MyBook World) with ... straight ... ethernet cable. Hi, Could you make sure that you installed and ran Avahi? I think Avahi could enable this same easy, direct, connection with your WD MyBook World. I don't have a way to test it now, but I am interested to find out if you have luck with Avahi. WD MyBook World and Windows implemented zeroconfig networking (with address range: 169.254.x.x/255.255.0.0), which make the direct connection works. (I think not needing the cross cable is the Ethernet support/chipset thing, not software.) Without Avahi, it is possible that a Linux command such as this: # ifconfig address 169.254.1.23 eth0 could enable HTTP connection to WD MyBook World. Tips: These might work (and should work with Avahi running): $ ping mybookworld http://mybookworld/ (Zeroconfig hostname resolution.) Not sure what support should be added to NM here, but there might be work to do to add missing browsing support in toolkits/apps that can use devices services. Resources: Dr. Stuart Cheshire gives a Zeroconf talk to the Google engineers: http://video.google.com/videoplay?docid=-7398680103951126462 Zero Configuration Networking (Zeroconf) IETF Working Group: http://www.zeroconf.org/ zcip: http://linux.kernel.org/mailman/listinfo/zcip = ZeroConfig IP package. Regards, -- Daniel Yek On Sat, 2011-10-08 at 21:18 +0700, Arief M Utama wrote: Hi all, I'm just wondering, and might as well send the message on the list, in case someone has more ideas. On recent windows, with recent network cards, I noticed (on a couple laptops) that windows can setup networking to a direct-connected to another device (tested couple of times with network-drives, such as WD MyBook World) with simple straight forward ethernet cable. No crossing needed. I'm wondering if NM (or linux?) can support this as well? I'd appreciate any pointers on this issue. Thanks for your time :) All the best. -arief ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: new avahi autoip stuff not working for me
On Wed, 2008-07-09 at 19:18 +0200, Björn Martensen wrote:
hi,
not sure what's wrong here, but after todays change to the autoip code
(now using avahi-autoipd), nm just gives me a disconnected
notification immediately when i try to activate an autoip connection.
so i tried running avahi-autoipd in a terminal, which gives me this
weird error:
$ sudo avahi-autoipd eth0
Failed to find user 'avahi-autoipd'.
what's with the user thing? is my distro doing stuff wrong and if so,
what's that? or is avahi broken?
That's probably the issue; avahi-autoipd usually tries to use it's own
user and drop privileges after launch. Fedora avahi-autoipd package
does:
/usr/sbin/groupadd -f -r avahi-autoipd
/usr/bin/id avahi-autoipd /dev/null 21 || \
/usr/sbin/useradd -r -g avahi-autoipd -c 'avahi-autoipd' -s
/sbin/nologin -d %{_localstatedir}/lib/avahi-autoipd avahi-autoipd
Dan
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
new avahi autoip stuff not working for me
hi, not sure what's wrong here, but after todays change to the autoip code (now using avahi-autoipd), nm just gives me a disconnected notification immediately when i try to activate an autoip connection. so i tried running avahi-autoipd in a terminal, which gives me this weird error: $ sudo avahi-autoipd eth0 Failed to find user 'avahi-autoipd'. what's with the user thing? is my distro doing stuff wrong and if so, what's that? or is avahi broken? greetz, björn signature.asc Description: This is a digitally signed message part ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: avahi ip even if the network cable is unplugged
On 7/12/07, yelo_3 [EMAIL PROTECTED] wrote: That is likely be fixed by recent commits to stable branch. But when this happens, can you check the value of /sys/class/net/eth0/carrier? Thanks, Dan The carrier is well detected. Let's hope that ubuntu will include the new stable branch! Do you think that it will be out before the upstream version freeze in ubuntu ( August 16th)? thank you Since the patch was applied to stable then you should be able to pull the patch via the svn changelog and open a ticket on Launchpad to have it included with the Ubuntu Package. Thanks! ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
avahi ip even if the network cable is unplugged
Hello, this is a bug I have now with nm 0.6.5-0ubuntu6 when I load the ethernet card module (tg3) and if the cable is unplugged, network manager thinks that the cable is plugged and the applet icon changes into the acquiring address and when the dhcp timeout triggers, avahi-autoip gives me an ip, and creates the interface eth0:avah. Now the icon is changed to the normal one, as if I'm connected via the cable. Connection information is showing that everything is 0.0.0.0. when I plug the cable I get Jul 10 10:24:13 yelo3-laptop kernel: [ 1460.812000] tg3: eth0: Link is up at 100 Mbps, full duplex. Jul 10 10:24:13 yelo3-laptop kernel: [ 1460.812000] tg3: eth0: Flow control is off for TX and off for RX. Jul 10 10:24:13 yelo3-laptop kernel: [ 1460.816000] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Jul 10 10:24:14 yelo3-laptop avahi-daemon[7003]: Registering new address record for fe80::211:2fff:feb5:41dd on eth0.*. the interface eth0:avah will remain up, until I unplug the cable: Jul 10 10:25:39 yelo3-laptop NetworkManager: info SWITCH: terminating current connection 'eth0' because it's no longer valid. Jul 10 10:25:39 yelo3-laptop NetworkManager: info Deactivating device eth0. Jul 10 10:25:39 yelo3-laptop NetworkManager: nm_device_is_802_3_ethernet: assertion `dev != NULL' failed Jul 10 10:25:39 yelo3-laptop NetworkManager: nm_device_is_802_11_wireless: assertion `dev != NULL' failed Jul 10 10:25:39 yelo3-laptop avahi-daemon[7003]: Withdrawing address record for 169.254.7.228 on eth0. Jul 10 10:25:39 yelo3-laptop avahi-daemon[7003]: Leaving mDNS multicast group on interface eth0.IPv4 with address 169.254.7.228. Jul 10 10:25:39 yelo3-laptop avahi-daemon[7003]: Interface eth0.IPv4 no longer relevant for mDNS. Jul 10 10:25:39 yelo3-laptop avahi-daemon[7003]: Withdrawing address record for fe80::211:2fff:feb5:41dd on eth0. If I plug in the cable again I finally get my normal connection up and running I don't know if this bug is only of my distribution, which is ubuntu gutsy, or if it is a kernel module bug and I would like to know if any of you has it too. ___ L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail: http://it.docs.yahoo.com/nowyoucan.html ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Avahi
I just spotted something that might be of interest turning up on planet.debian.org. Avahi is a DNS-SD implementation for freedesktop.org using DBUS to communicate. May well be of interest for future it just works stuff, and possible integration (esp. for things like virtual network devices and figuring out what's possible on the local network) http://www.freedesktop.org/Software/Avahi Tom ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
