slyon | Hey cyphermox! We've recently been wondering about the status of https://snapcraft.io/netplan as we got some bug reports about it (e.g. https://pad.lv/1896354). Do you have any plans for that snap, or would you mind unpublishing it from the store to avoid people using the old version? | 09:30 |
---|---|---|
BeRoots | Hello. | 12:33 |
BeRoots | I tried to use netplan instead of networkd to configure a adhoc network between 2 ubuntu machines. I follow the third example from https://raspberrypi.stackexchange.com/questions/94047/how-to-setup-an-unprotected-ad-hoc-ibss-network-and-if-possible-with-wpa-encry/94048#94048 (the "Only with suitable (RSN-IBSS capable) USB dongle" bullet point). | 12:33 |
BeRoots | So, I added a netplan config file named /etc/netplan/40-wlan1.yaml like this: | 12:33 |
BeRoots | ```network: | 12:33 |
BeRoots | version: 2 | 12:33 |
BeRoots | renderer: networkd | 12:33 |
BeRoots | wifis: | 12:33 |
BeRoots | wlan1: | 12:33 |
BeRoots | access-points: | 12:33 |
BeRoots | "My adhoc": | 12:33 |
BeRoots | mode: adhoc | 12:33 |
BeRoots | password: "s3kr1t"``` | 12:33 |
BeRoots | I added and apply an /etc/wpa_supplicant/wpa_supplicant-wlan1.conf like this: | 12:42 |
BeRoots | ```ctrl_interface=DIR=/run/wpa_supplicant GROUP=netdev | 12:42 |
BeRoots | update_config=1 | 12:42 |
BeRoots | p2p_disabled=1 | 12:42 |
BeRoots | country=DE | 12:42 |
BeRoots | network={ | 12:42 |
BeRoots | ssid="My adhoc" | 12:42 |
BeRoots | key_mgmt=WPA-PSK | 12:42 |
BeRoots | proto=RSN | 12:42 |
BeRoots | psk="s3kr1t" | 12:42 |
BeRoots | mode=1 | 12:42 |
BeRoots | frequency=2412 | 12:42 |
BeRoots | }``` | 12:42 |
BeRoots | My problem is I'm not sure if I have to add this wpa_supplicant fille too. | 12:42 |
BeRoots | I tested with netplan+wpa_supplicant files and with only the netplan file but I don't have an ipv4 address at all | 12:43 |
BeRoots | `ip a` return: | 12:52 |
BeRoots | 4: wlan1: <NO-CARRIER,BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state DORMANT group default qlen 1000 | 12:53 |
BeRoots | link/ether ab:54:b4:ba 46:55 brd ff:ff:ff:ff:ff:ff | 12:53 |
BeRoots | inet6 fe78:d237:45ff:fee2:918/64 scope link | 12:53 |
BeRoots | valid_lft forever preferred_lft forever | 12:53 |
BeRoots | If someone have an idea why I don't have my IPv4 ? What's the problem with my configuration? | 12:54 |
cyphermox | slyon: sure, I'll go unpublish it | 12:58 |
cyphermox | slyon: tbf, if you think about it you'll notice why that never took off... kinda chicken and egg thing | 12:59 |
cyphermox | BeRoots: NO-CARRIER, it's not finding the wireless config most likely | 13:00 |
cyphermox | BeRoots: you shouldn't have to add a wpa-supplicant file, it should be generated for you | 13:00 |
slyon | thanks cyphermox. This is a chicken-egg situation indeed, but we also have netplan as part of the core snap and want to avoid version conflicts with snaps installed on top of that | 13:09 |
slyon | BeRoots: as mentioned above, netplan will generate the wpa_supplicant config for you, no need to specify it manually | 13:10 |
cyphermox | slyon: yup | 13:10 |
cyphermox | anyway, it's done | 13:10 |
BeRoots | Ok. I going to remove the wpa_supplicant file. Is it a good solution finded here: https://makerforce.io/setting-up-a-ad-hoc-network/ ? And if Yes, do I have to apply iw command too ? | 13:24 |
slyon | BeRoots: hmm.. I did not use ad-hoc mode in a very long time. I usually use AP/hotspot mode instead. But this guide looks rather up-to-date, so you should give it a try, incl. applying the iw commands | 13:31 |
slyon | And you probably also need to statically assign an IP address to your device, using the "addresses: []" setting in your netplan config. | 13:34 |
slyon | unless there is a DHCP server running on one of the other devices? | 13:34 |
BeRoots | slyon. Ok. Thanks for the feedback. I going to test that.... | 13:37 |
BeRoots | No I haven't any DHCP at this time. I have chosen an adhoc with 2 devices allowed in my case... | 13:37 |
slyon | BeRoots: okay. what system are you using on the other devices (netplan as well)? Just make sure they are all on the same IP network, so they can communicate with each other | 13:38 |
BeRoots | I have two ubuntu devices. | 13:39 |
slyon | that's good. Try to add "addresses: [192.168.0.1/24]" to one and "addresses: [192.168.0.2/24]" to the other | 13:40 |
=== akp55_ is now known as akp55__ |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!