Network Manager 1.0 Released after 10 years of development
mail.gnome.org
mail.gnome.org
This is huge news. systemd-networkd's DHCP client, thanks to Tom Gundersen's work, can successfully get an address in milliseconds, rather than the many seconds required by dhclient. See https://plus.google.com/+TomGundersen/posts/eztZWbwmxM8 for some of the details.
I eagerly await wireless networking support in systemd-networkd, but in the interim, this will drastically improve network setup time on the average Linux system.
Does it now work wireless though ? From the link you shared :
Using networkd together with wpa_supplicant on my laptop on my crappy home wifi, the time from link-sense to fully configured network is roughly 50msSo really, it seems to me that the only reason networkd's DHCP is fast is because it's bare bones (and also skips a few sections of RFC 1531, according to Jayson Vantuyl... which doesn't sound good). Only dealing with lease negotiation, if Gundersen's statement near the end is still true.
I'm not an expert on the implementation of mac/windows/linux so maybe someone who knows can chip in.
Works OK in small domestic networks but can cause some issues in big uni and corporate nets with frequent address churn.
My favourite one to watch was the roguelike ADoM, which went through 0.1 - 0.9, then 0.91 - 0.99, then .99alpha - .99gamma, then got up to .99gamma16 before it finally hit 1.0.
What issues have you had?
i've built scripts that serve ics but only under shamanic preconditions that elude me
network manager is supposed to allow for it with their 'share this connection' but getting it to work has also eluded me
on a windows7 boot everything just works with ics, but then i'm booted into windows
gramm`err : /allude/elude/
you are fine to point out when sumone errs without associating yourself with a genocidal political movement
still.. any thoughts on linux ics?
I was unoffended by the parent referring to thaemself as a grammar Nazi, my message latent in my response was a genuine appreciation for bringing my error to my attention, and my lament that so much culture is afraid to make a mistake that we shame people who explain correct usage to the point that as a defense people preemptively shame themselves
Like I said,'its fine to correct sumone[sic]'
Also, sumone was an international mistake intended to make people smile and remind us of our humanity:'to err is to be humen'
echo 1 > /proc/sys/net/ipv4/ip_forward
iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
Ta-da, basic internet connection sharing is working. (If you want automatic network configuration for the devices that are connecting to your machine, you'll need to install and configure a dhcp server e.g. dhcpd)Edit: oh, no, that won't work, your network device is no longer eth0 because the distros have been messing around with it again. Sorry, I can't help, I moved to FreeBSD years ago to get away from this crap.
Sometimes using those two lines would work alone, sometimes they would only work in conjunction with more lines with different flags.. This is why I said reliable and shamanic
I run ubuntu 1404 server, slack on my notebook, debian on my home box.. Those two lines all do something different on each at different times of day under different moons, or alike when they all fail to do anything at all
I chalked it up to some kind of collision with how nm or wicd, machine respective, were trying to run their show
its been years since i tried a *BSD back in my greener days when i was trying every alt os around before i settled on linux by way of slack, but itd be interesting to look at it now with more knowledge of the whys and wherefores