Re: Virtual network interface
On 11/09/2014 12:20 PM, Peter Robinson wrote: There is means of doing this. For Wired - Wireless there's relatively straight forward ways to deal with it but you need to have support for the handover across the entire network infrastructure, it's not really something the host does on it's own. Well. There is MultiPathTCP http://www.multipath-tcp.org/ but it is not in stock kernel yet. In the mean time you can try Copr build: https://copr.fedoraproject.org/coprs/fulltext/?fulltext=mptcp -- Miroslav Suchy, RHCE, RHCDS Red Hat, Senior Software Engineer, #brno, #devexp, #fedora-buildsys -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Virtual network interface
Dne 12.11.2014 v 13:40 Miroslav Suchý napsal(a): On 11/09/2014 12:20 PM, Peter Robinson wrote: There is means of doing this. For Wired - Wireless there's relatively straight forward ways to deal with it but you need to have support for the handover across the entire network infrastructure, it's not really something the host does on it's own. Well. There is MultiPathTCP http://www.multipath-tcp.org/ but it is not in stock kernel yet. In the mean time you can try Copr build: https://copr.fedoraproject.org/coprs/fulltext/?fulltext=mptcp Interesting. Thanks for the tip! Have to give it a try ... Vít -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Virtual network interface
Dne 8.11.2014 v 14:23 Björn Persson napsal(a): Tomasz Torcz wrote: On Fri, Nov 07, 2014 at 03:37:53PM +0100, Björn Persson wrote: Vít Ondruch vondr...@redhat.com wrote: * I don't understand why my Xchat should loose connection, when I am switching from ethernet to WiFi (and they are both available during interim period). For this use case you want to run IRC over SCTP, so that you can keep the connection open when you change IP addresses. The best that can be done with TCP is to automatically reconnect from the new IP address when the old TCP connection breaks. Why different address? If this the same machine, it would be much easier just to configure DHCP to give the same IPv4 for both wifi and wired interface. That works only for the special case where you're moving around inside an office (or a geek's home) where the wired and wireless networks share an IP address range. This would be good start from my POV. IP address should identify machine, network interfaces are identified by their MAC addresses ... Vít If you're moving between your home, your office, public hotspots, trains and whatnot, then there's no way you'll be able to keep the same IP address without workarounds like tunneling. (Well I suppose you could just use an LTE connection all the time, but Vít's question was about switching network connections.) IPv6 stateless configured addresses are problematic, of course. If you have DHCP then you can have DHCPv6 too. IPv6 has the potential to be less problematic than IPv4 because it doesn't need address translation. I just hope people aren't so accustomed to being crippled by address translation that they start translating IPv6 addresses everywhere by habit. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Virtual network interface
Is there way how to setup some virtual network inteface, which would always work, no matter if I use ethernet, wireles, VPN or whatever else network connection on background? * It is pretty annoying that every time I change my location, I have to change configuration of my virtual machines, just because now I am not connected via ethernet, but via WiFi. * I don't understand why my Xchat should loose connection, when I am switching from ethernet to WiFi (and they are both available during interim period). The type of network connection is just implementation detail, so why this does not work? If there is possible to create some virtual network interface, which would take all the real network connection under one umbrella, this should be default for Fedora Workstation. Additional feature could be that WiFi goes down when Ethernet is available etc. This functionality has been available in Lenovo's Access Connection tools at least 8 years ago as far as I remember and I greatly missing it. There is means of doing this. For Wired - Wireless there's relatively straight forward ways to deal with it but you need to have support for the handover across the entire network infrastructure, it's not really something the host does on it's own. There's also 802.21 which in theory could make this work for most comms media wired/wireless/bluetooth/WWAN etc but even though it's been about since 2008 I'm not aware of a complete implementation of it and again it needs infrastructure support. [1] https://en.wikipedia.org/wiki/IEEE_802.21 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Virtual network interface
On Fri, Nov 07, 2014 at 03:37:53PM +0100, Björn Persson wrote: Vít Ondruch vondr...@redhat.com wrote: * I don't understand why my Xchat should loose connection, when I am switching from ethernet to WiFi (and they are both available during interim period). For this use case you want to run IRC over SCTP, so that you can keep the connection open when you change IP addresses. The best that can be done with TCP is to automatically reconnect from the new IP address when the old TCP connection breaks. Why different address? If this the same machine, it would be much easier just to configure DHCP to give the same IPv4 for both wifi and wired interface. IPv6 stateless configured addresses are problematic, of course. -- Tomasz Torcz Never underestimate the bandwidth of a station xmpp: zdzich...@chrome.plwagon filled with backup tapes. -- Jim Gray -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Virtual network interface
Tomasz Torcz wrote: On Fri, Nov 07, 2014 at 03:37:53PM +0100, Björn Persson wrote: Vít Ondruch vondr...@redhat.com wrote: * I don't understand why my Xchat should loose connection, when I am switching from ethernet to WiFi (and they are both available during interim period). For this use case you want to run IRC over SCTP, so that you can keep the connection open when you change IP addresses. The best that can be done with TCP is to automatically reconnect from the new IP address when the old TCP connection breaks. Why different address? If this the same machine, it would be much easier just to configure DHCP to give the same IPv4 for both wifi and wired interface. That works only for the special case where you're moving around inside an office (or a geek's home) where the wired and wireless networks share an IP address range. If you're moving between your home, your office, public hotspots, trains and whatnot, then there's no way you'll be able to keep the same IP address without workarounds like tunneling. (Well I suppose you could just use an LTE connection all the time, but Vít's question was about switching network connections.) IPv6 stateless configured addresses are problematic, of course. If you have DHCP then you can have DHCPv6 too. IPv6 has the potential to be less problematic than IPv4 because it doesn't need address translation. I just hope people aren't so accustomed to being crippled by address translation that they start translating IPv6 addresses everywhere by habit. -- Björn Persson signature.asc Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Virtual network interface
Hi everybody, Is there way how to setup some virtual network inteface, which would always work, no matter if I use ethernet, wireles, VPN or whatever else network connection on background? * It is pretty annoying that every time I change my location, I have to change configuration of my virtual machines, just because now I am not connected via ethernet, but via WiFi. * I don't understand why my Xchat should loose connection, when I am switching from ethernet to WiFi (and they are both available during interim period). The type of network connection is just implementation detail, so why this does not work? If there is possible to create some virtual network interface, which would take all the real network connection under one umbrella, this should be default for Fedora Workstation. Additional feature could be that WiFi goes down when Ethernet is available etc. This functionality has been available in Lenovo's Access Connection tools at least 8 years ago as far as I remember and I greatly missing it. Vít -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Virtual network interface
On Fri, Nov 07, 2014 at 10:56:19AM +0100, Vít Ondruch wrote: Hi everybody, Is there way how to setup some virtual network inteface, which would always work, no matter if I use ethernet, wireles, VPN or whatever else network connection on background? * It is pretty annoying that every time I change my location, I have to change configuration of my virtual machines, just because now I am not connected via ethernet, but via WiFi. * I don't understand why my Xchat should loose connection, when I am switching from ethernet to WiFi (and they are both available during interim period). The type of network connection is just implementation detail, so why this does not work? If there is possible to create some virtual network interface, which would take all the real network connection under one umbrella, this should be default for Fedora Workstation. I think bridged networking should just be the default. In this day and age, multiple processes inside the OS should be able to acquire an IP address from the ethernet interface (whether wired or wireless). http://wiki.libvirt.org/page/Networking#Bridged_networking_.28aka_.22shared_physical_device.22.29 Note not just VMs: There's a lot of theoretical work around having ordinary processes have their own IPv6 address. Additional feature could be that WiFi goes down when Ethernet is available etc. This functionality has been available in Lenovo's Access Connection tools at least 8 years ago as far as I remember and I greatly missing it. Agreed. This is particularly annoying when I use my laptop docking station (which has wired gigE) but basically am forced to stick with slow wifi because otherwise everything breaks. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-p2v converts physical machines to virtual machines. Boot with a live CD or over the network (PXE) and turn machines into KVM guests. http://libguestfs.org/virt-v2v -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Virtual network interface
On 2014-11-07, Vít Ondruch vondr...@redhat.com wrote: Is there way how to setup some virtual network inteface, which would always work, no matter if I use ethernet, wireles, VPN or whatever else network connection on background? Your question contains the answer: You need to create a tunnel to an always reachable node and use the tunneled IP address. This way you will have always a static IP address on your mobile host. There are other posibilities like mobile IP extension or multipath TCP or even some experiments splitting node's IP address into location and identifier halves. (In order of number of deployments :) * It is pretty annoying that every time I change my location, I have to change configuration of my virtual machines, just because now I am not connected via ethernet, but via WiFi. You assign your own private addresses to them and use them in scope of your host and virtual machines running in it. * I don't understand why my Xchat should loose connection, when I am switching from ethernet to WiFi (and they are both available during interim period). The reason is that processes usually work with transport adresses (e.g. a TCP) and these include network address (e.g. an IP). And network addresses in the current Internet are used as locators, thus they depend on the network topology. The type of network connection is just implementation detail, so why this does not work? If there is possible to create some virtual network interface, which would take all the real network connection under one umbrella, this should be default for Fedora Workstation. Well, it is possible. But any site operator would shot you because you would break his precious one-way firewall. -- Petr -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Virtual network interface
Vít Ondruch vondr...@redhat.com wrote: * I don't understand why my Xchat should loose connection, when I am switching from ethernet to WiFi (and they are both available during interim period). For this use case you want to run IRC over SCTP, so that you can keep the connection open when you change IP addresses. The best that can be done with TCP is to automatically reconnect from the new IP address when the old TCP connection breaks. Using SCTP requires of course that the IRC server listens for SCTP connections. There must also not be any overzealous firewalls that block SCTP just because they don't know what it is. Björn Persson signature.asc Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
