Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #165270 > unrolled thread
| Started by | supersonicsnow <supersonicsnow@gmail.com> |
|---|---|
| First post | 2016-03-12 12:10 +0100 |
| Last post | 2016-03-12 12:20 +0100 |
| Articles | 3 — 3 participants |
Back to article view | Back to linux.debian.user
WPA supplicant configured with static IP inside /etc/network/interfaces invokes dhcpcd supersonicsnow <supersonicsnow@gmail.com> - 2016-03-12 12:10 +0100
Re: WPA supplicant configured with static IP inside /etc/network/interfaces invokes dhcpcd deloptes <deloptes@gmail.com> - 2016-03-12 12:10 +0100
Re: WPA supplicant configured with static IP inside /etc/network/interfaces invokes dhcpcd Pascal Hambourg <pascal@plouf.fr.eu.org> - 2016-03-12 12:20 +0100
| From | supersonicsnow <supersonicsnow@gmail.com> |
|---|---|
| Date | 2016-03-12 12:10 +0100 |
| Subject | WPA supplicant configured with static IP inside /etc/network/interfaces invokes dhcpcd |
| Message-ID | <rbPAJ-51S-5@gated-at.bofh.it> |
[Multipart message — attachments visible in raw view] — view raw
When I try this: /etc/network/interfaces auto wlan0 allow-hotplug wlan0 iface wlan0 inet static address 192.168.0.123 netmask 255.255.255.0 gateway 192.168.0.1 dns-nameservers 8.8.8.8 8.8.4.4 *resolvconf makes 2 entries as expected inside the resolv.conf**file* nameserver 8.8.8.8 nameserver 8.8.4.4 *Alright, but I still need to connect to a network. So I add this stuff underneath:* wpa-scan-ssid 1 wpa-ap-scan 1 wpa-key-mgmt WPA-PSK wpa-proto RSN WPA wpa-pairwise CCMP TKIP wpa-group CCMP TKIP wpa-ssid "blah" wpa-psk blahblah *I get a static IP on the network and connect successfully, but now resolv.conf file is polluted with junk created by dhcpcd* _$ resolvconf -l_ # resolv.conf from wlan0 # Generated by dhcpcd from wlan0 nameserver 192.168.0.1 # resolv.conf from wlan0:ra # Generated by dhcpcd from wlan0:ra nameserver fe80::1%wlan0 # resolv.conf from wlan0.inet # Generated by ifup for wlan0.inet nameserver 8.8.8.8 nameserver 8.8.4.4 *I expect that dhcpcd should not be involved at all with**my STATIC wlan0, is that correct?* 1. Can you please confirm this behavior is a bug. 2. Do you know what package is responsible for the faulty behavior? My best guess would be: ifupdown? Thanks
[toc] | [next] | [standalone]
| From | deloptes <deloptes@gmail.com> |
|---|---|
| Date | 2016-03-12 12:10 +0100 |
| Subject | Re: WPA supplicant configured with static IP inside /etc/network/interfaces invokes dhcpcd |
| Message-ID | <rbPAK-51S-7@gated-at.bofh.it> |
| In reply to | #165270 |
supersonicsnow wrote: > *I expect that dhcpcd should not be involved at all with**my STATIC > wlan0, is that correct?* > 1. Can you please confirm this behavior is a bug. > 2. Do you know what package is responsible for the faulty behavior? My > best guess would be: ifupdown? you might have some network manager running - at least in my case. I solved all similar issue by disabling all setup in interfaces and using the manager to handle all of it. regards
[toc] | [prev] | [next] | [standalone]
| From | Pascal Hambourg <pascal@plouf.fr.eu.org> |
|---|---|
| Date | 2016-03-12 12:20 +0100 |
| Subject | Re: WPA supplicant configured with static IP inside /etc/network/interfaces invokes dhcpcd |
| Message-ID | <rbPKp-568-5@gated-at.bofh.it> |
| In reply to | #165270 |
supersonicsnow a écrit : > > *I expect that dhcpcd should not be involved at all with**my STATIC > wlan0, is that correct?* IIUC, not any more if you have dhcpcd5 (the only version available in the current stable Jessie). It is an autonomous daemon which detects when an interface is up and tries to configure it, unless configured otherwise.
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.user
csiph-web