Re: Could not find interfaces configuration file /etc/network/interfaces in Debian Linux 11 (bullseye)
On Friday, December 8th, 2023 at 11:23 PM, John Hasler wrote: > Mr. Turritopsis Dohrnii Teo En Ming writes: > > > You managed to install OpenWRT on an Ubiquiti router? > > > Yes. It was quite straightforward. Instructions on the OpenWRT site. > -- > John Hasler > j...@sugarbit.com > Elmwood, WI USA I have seen the web UI of OpenWRT. Quite impressive. Regards, Mr. Turritopsis Dohrnii Teo En Ming Targeted Individual in Singapore
Re: Could not find interfaces configuration file /etc/network/interfaces in Debian Linux 11 (bullseye)
On Friday, December 8th, 2023 at 11:23 PM, John Hasler wrote: > Mr. Turritopsis Dohrnii Teo En Ming writes: > > > You managed to install OpenWRT on an Ubiquiti router? > > > Yes. It was quite straightforward. Instructions on the OpenWRT site. > -- > John Hasler > j...@sugarbit.com > Elmwood, WI USA It's interesting to know. Thank you. Regards, Mr. Turritopsis Dohrnii Teo En Ming Targeted Individual in Singapore
Re: Could not find interfaces configuration file /etc/network/interfaces in Debian Linux 11 (bullseye)
Mr. Turritopsis Dohrnii Teo En Ming writes: > You managed to install OpenWRT on an Ubiquiti router? Yes. It was quite straightforward. Instructions on the OpenWRT site. -- John Hasler j...@sugarbit.com Elmwood, WI USA
Re: Could not find interfaces configuration file /etc/network/interfaces in Debian Linux 11 (bullseye)
On Friday, December 8th, 2023 at 6:15 AM, John Hasler wrote: > Turritopsis Dohrnii Teo En Ming wrote: > > > UDM Pro runs Debian 11 (bullseye) > > > I have a Ubiquiti router. Before I installed OpenWRT I explored the OS. > It uses packages from Bullseye but it is certainly not Debian. You > couldn't find that file because it isn't there. > -- > John Hasler > j...@sugarbit.com > Elmwood, WI USA You managed to install OpenWRT on an Ubiquiti router? Regards, Mr. Turritopsis Dohrnii Teo En Ming Targeted Individual in Singapore
Re: Could not find interfaces configuration file /etc/network/interfaces in Debian Linux 11 (bullseye)
On Friday, December 8th, 2023 at 6:08 AM, jeremy ardley wrote: > On 7/12/23 23:52, Turritopsis Dohrnii Teo En Ming wrote: > > > Subject: Could not find interfaces configuration file > > /etc/network/interfaces in Debian Linux 11 (bullseye) > > > > You should confirm that the device is actually using that file. > > There are at least three different network configuration services in > Debian - which are not completely mutually exclusive > > what is the result of these commands? > > sudo systemctl status networking > > sudo systemctl status systemd-networkd > > sudo systemctl status NetworkManager I will run these commands next week. Thank you for your reply. Regards, Mr. Turritopsis Dohrnii Teo En Ming Targeted Individual in Singapore
Re: Could not find interfaces configuration file /etc/network/interfaces in Debian Linux 11 (bullseye)
On Friday, December 8th, 2023 at 6:05 AM, Andy Smith wrote: > Hello, > > On Thu, Dec 07, 2023 at 03:52:20PM +, Turritopsis Dohrnii Teo En Ming > wrote: > > > UDM Pro runs Debian 11 (bullseye) > > > I don't think it does. Just because you found a file on the > filesystem that says it does, is as trustworthy as the claims in > your email that your client is called Henry Kissinger and your > colleague Edward Snowden. > > It might have started out as Debian 11, but Ubiquiti have made > unknown changes to it. > > > Linux United-States-Space-Command-Secret-Server 4.19.152-ui-alpine > > #4.19.152 SMP Thu Apr 6 21:41:48 CST 2023 aarch64 GNU/Linux > > > This is also not a kernel supplied by Debian. > > > But another problem cropped up. Now we could not access the web UI > > of the UDM Pro. > > > […] > > > We could not putty (ssh) into the UDM Pro too. > > > > May I know what the problem could be? > > > Given that you're running an operating system supplied by Ubiquiti > on hardware supplied by Ubiquiti using a web frontend written by > Ubiquiti on top of a kernel supplied by Ubiquii, I think you need to > ask Ubiquiti. > > > Please advise. > > > I think it's for your vendor to advise. > > Thanks, > Andy > > PS It would also be advisable to get into the habit of using the > "ip" suite of tools instead of deprecated ones like "ifconfig" > and "route". The reason being that tools like ifconfig have not > kept up changes in the Linux kernel and do not actually display > all settings of the system any more. Most of the time the old > ways will still work, but at some point you will encounter a > situation where ifconfig etc is not showing you all of the > settings. The diagnostic output can also be confusing to people > born after the deprecation of ifconfig, for example. > > Your bigger problem though is that Debian didn't supply this > hardware or software. > > -- > https://bitfolk.com/ -- No-nonsense VPS hosting Yes, I am going to ask Ubiquiti. Regards, Mr. Turritopsis Dohrnii Teo En Ming Targeted Individual in Singapore
Re: Could not find interfaces configuration file /etc/network/interfaces in Debian Linux 11 (bullseye)
On Friday, December 8th, 2023 at 12:19 AM, Dan Purgert wrote: > On Dec 07, 2023, to...@tuxteam.de wrote: > > > On Thu, Dec 07, 2023 at 03:52:20PM +, Turritopsis Dohrnii Teo En Ming > > wrote: > > > > [...] > > > > > Problem > > > = > > > > > > On 6 Dec 2023, our client discovered that their UDM Pro could not perform > > > firmware updates automatically. Their UDM Pro was running UniFi OS > > > version 3.0.20. Client wants to upgrade firmware to latest version 3.1.16 > > > but couldn't. > > > > > > UDM Pro runs Debian 11 (bullseye) > > > > > > > Now I don't understand: is it running UniFi OS or Debian bullseye? > > > "UniFi OS" (And EdgeOS on other lineups) is customized Debian Stable of > some flavor or other. > > > Or is Ubiquiti just cheapskating and sending their customers here > > to save on customer support? > > > I've never seen them direct customers anywhere other than their support > forums... > > -- > ||O|| > |||O| Github: https://github.com/dpurgert > |O|O|O| PGP: DDAB 23FB 19FA 7D85 1CC1 E067 6D65 70E5 4CE7 2860 What is EdgeOS? Regards, Mr. Turritopsis Dohrnii Teo En Ming Targeted Individual in Singapore
Re: Could not find interfaces configuration file /etc/network/interfaces in Debian Linux 11 (bullseye)
On Friday, December 8th, 2023 at 12:12 AM, to...@tuxteam.de wrote: > On Thu, Dec 07, 2023 at 03:52:20PM +, Turritopsis Dohrnii Teo En Ming > wrote: > > [...] > > > Problem > > = > > > > On 6 Dec 2023, our client discovered that their UDM Pro could not perform > > firmware updates automatically. Their UDM Pro was running UniFi OS version > > 3.0.20. Client wants to upgrade firmware to latest version 3.1.16 but > > couldn't. > > > > UDM Pro runs Debian 11 (bullseye) > > > > > Now I don't understand: is it running UniFi OS or Debian bullseye? > > Or is Ubiquiti just cheapskating and sending their customers here > to save on customer support? > > Inquiring minds... > > Cheers > -- > t It is an UniFi Dream Machine Pro running Debian 11 bullseye. Regards, Mr. Turritopsis Dohrnii Teo En Ming Targeted Individual in Singapore
Re: Could not find interfaces configuration file /etc/network/interfaces in Debian Linux 11 (bullseye)
Turritopsis Dohrnii Teo En Ming wrote: > UDM Pro runs Debian 11 (bullseye) I have a Ubiquiti router. Before I installed OpenWRT I explored the OS. It uses packages from Bullseye but it is certainly not Debian. You couldn't find that file because it isn't there. -- John Hasler j...@sugarbit.com Elmwood, WI USA
Re: Could not find interfaces configuration file /etc/network/interfaces in Debian Linux 11 (bullseye)
On 7/12/23 23:52, Turritopsis Dohrnii Teo En Ming wrote: Subject: Could not find interfaces configuration file /etc/network/interfaces in Debian Linux 11 (bullseye) You should confirm that the device is actually using that file. There are at least three different network configuration services in Debian - which are not completely mutually exclusive what is the result of these commands? sudo systemctl status networking sudo systemctl status systemd-networkd sudo systemctl status NetworkManager
Re: Could not find interfaces configuration file /etc/network/interfaces in Debian Linux 11 (bullseye)
Hello, On Thu, Dec 07, 2023 at 03:52:20PM +, Turritopsis Dohrnii Teo En Ming wrote: > UDM Pro runs Debian 11 (bullseye) I don't think it does. Just because you found a file on the filesystem that says it does, is as trustworthy as the claims in your email that your client is called Henry Kissinger and your colleague Edward Snowden. It might have started out as Debian 11, but Ubiquiti have made unknown changes to it. > Linux United-States-Space-Command-Secret-Server 4.19.152-ui-alpine #4.19.152 > SMP Thu Apr 6 21:41:48 CST 2023 aarch64 GNU/Linux This is also not a kernel supplied by Debian. > But another problem cropped up. Now we could not access the web UI > of the UDM Pro. […] > We could not putty (ssh) into the UDM Pro too. > > May I know what the problem could be? Given that you're running an operating system supplied by Ubiquiti on hardware supplied by Ubiquiti using a web frontend written by Ubiquiti on top of a kernel supplied by Ubiquii, I think you need to ask Ubiquiti. > Please advise. I think it's for your vendor to advise. Thanks, Andy PS It would also be advisable to get into the habit of using the "ip" suite of tools instead of deprecated ones like "ifconfig" and "route". The reason being that tools like ifconfig have not kept up changes in the Linux kernel and do not actually display all settings of the system any more. Most of the time the old ways will still work, but at some point you will encounter a situation where ifconfig etc is not showing you all of the settings. The diagnostic output can also be confusing to people born after the deprecation of ifconfig, for example. Your bigger problem though is that Debian didn't supply this hardware or software. -- https://bitfolk.com/ -- No-nonsense VPS hosting
Re: Could not find interfaces configuration file /etc/network/interfaces in Debian Linux 11 (bullseye)
On Dec 07, 2023, to...@tuxteam.de wrote: > On Thu, Dec 07, 2023 at 03:52:20PM +, Turritopsis Dohrnii Teo En Ming > wrote: > > [...] > > > Problem > > = > > > > On 6 Dec 2023, our client discovered that their UDM Pro could not perform > > firmware updates automatically. Their UDM Pro was running UniFi OS version > > 3.0.20. Client wants to upgrade firmware to latest version 3.1.16 but > > couldn't. > > > > UDM Pro runs Debian 11 (bullseye) > > > > Now I don't understand: is it running UniFi OS or Debian bullseye? "UniFi OS" (And EdgeOS on other lineups) is customized Debian Stable of some flavor or other. > > Or is Ubiquiti just cheapskating and sending their customers here > to save on customer support? I've never seen them direct customers anywhere other than their support forums... -- |_|O|_| |_|_|O| Github: https://github.com/dpurgert |O|O|O| PGP: DDAB 23FB 19FA 7D85 1CC1 E067 6D65 70E5 4CE7 2860 signature.asc Description: PGP signature
Re: Could not find interfaces configuration file /etc/network/interfaces in Debian Linux 11 (bullseye)
On Thu, Dec 07, 2023 at 03:52:20PM +, Turritopsis Dohrnii Teo En Ming wrote: [...] > Problem > = > > On 6 Dec 2023, our client discovered that their UDM Pro could not perform > firmware updates automatically. Their UDM Pro was running UniFi OS version > 3.0.20. Client wants to upgrade firmware to latest version 3.1.16 but > couldn't. > > UDM Pro runs Debian 11 (bullseye) > Now I don't understand: is it running UniFi OS or Debian bullseye? Or is Ubiquiti just cheapskating and sending their customers here to save on customer support? Inquiring minds... Cheers -- t signature.asc Description: PGP signature
Could not find interfaces configuration file /etc/network/interfaces in Debian Linux 11 (bullseye)
Subject: Could not find interfaces configuration file /etc/network/interfaces in Debian Linux 11 (bullseye) Good day from Singapore, Background Information === Initially our client has a UniFi Dream Machine Pro (UDM Pro) acting as a firewall and router. Port 9 (WAN1) on the UDM Pro was connected to the ONT. Port 1 on the UDM Pro was connected to the LAN switch. Then our client purchased Fortigate 80F firewall from us. The date of the deployment of the Fortigate 80F firewall is 26 May 2023. During the setup and installation, I had connected WAN1 on the Fortigate 80F firewall to the ONT. Then I need to convert UDM Pro to non-routing mode. RJ45 cable to Port 9 (WAN1) on the UDM Pro was removed. I proceeded to connect Port 1 on the UDM Pro to Port 1 on the Fortigate 80F firewall. As the Fortigate 80F firewall already had DHCP server configured, I disabled the DHCP server inside UDM Pro. Everything (the network infrastructure) was working well for 6 months 11 days until 6 Dec 2023. Problem = On 6 Dec 2023, our client discovered that their UDM Pro could not perform firmware updates automatically. Their UDM Pro was running UniFi OS version 3.0.20. Client wants to upgrade firmware to latest version 3.1.16 but couldn't. UDM Pro runs Debian 11 (bullseye) When I putty (SSH) into the UDM Pro machine, I executed the command "cat /etc/os-release". The output is: PRETTY_NAME="Debian GNU/Linux 11 (bullseye)" NAME="Debian GNU/Linux" VERSION_ID="11" VERSION="11 (bullseye)" VERSION_CODENAME=bullseye ID=debian HOME_URL="https://www.debian.org/; SUPPORT_URL="https://www.debian.org/support; BUG_REPORT_URL="https://bugs.debian.org/; The output of the "uname -a" command is: Linux United-States-Space-Command-Secret-Server 4.19.152-ui-alpine #4.19.152 SMP Thu Apr 6 21:41:48 CST 2023 aarch64 GNU/Linux Troubleshooting Troubleshooting date is 6 Dec 2023 Wednesday. When I run "netstat -nr" or "route" commands in UDM Pro, the output shows that the default gateway for the 0.0.0.0/0.0.0.0 destination is 192.168.2.2. 192.168.2.2 is the IP address of the Fortigate 80F firewall. This confirms that the gateway was correctly configured on the UDM Pro. The LAN IP address of the UDM Pro is 192.168.2.1. The UDM Pro could reach the gateway 192.168.2.2, in this case the Fortigate 80F firewall. I could ping the gateway 192.168.2.2 from within the UDM Pro CLI. However, I could not ping 1.2.3.4 or 8.8.8.8. Even with the gateway correctly configured on the UDM Pro, it could not reach the outside world. When I run the command "ifconfig br0", the broadcast shows up as 0.0.0.0. I thought this is wrong. So I ran the following Linux command to correct it. # ifconfig br0 broadcast 192.168.2.255 But it did not solve the problem. My colleague Henry Kissinger told me that Port 9 (WAN1) on the UDM Pro must be connected (seems like a design flaw). I had wanted to configure the network interfaces using the /etc/network/interfaces file. But I could not find it anywhere in the terminal in Debian 11. Where can I find this file in Debian 11? It is missing! I had no choice but to use the web UI of the UDM Pro to configure Port 9 (WAN1). I had asked the client to connect Port 9 (WAN1) on the UDM Pro to Port 5 (LAN) on the Fortigate firewall. Then I configure Port 9 (WAN1) on the UDM Pro with the following network parameters: Static IPv4 address: 192.168.2.254 Subnet mask: 255.255.255.0 Default Gateway: 192.168.2.2 After configuring Port 9 (WAN1) on the UDM Pro, I could ping 8.8.8.8 from inside the UDM Pro already. However, I still could not ping www.google.com. That means DNS name resolution has failed. I had to edit /etc/resolv.conf. # vi /etc/resolv.conf nameserver 8.8.8.8 Now I could ping www.google.com from inside the UDM Pro. Name resolution is working after I have modified the /etc/resolv.conf file by hand. My client Edward Joseph Snowden then initiated the firmware upgrade using the web UI. After the firmware upgrade, the UDM Pro rebooted. Yes, it did reboot. I can confirm. The LCD screen on the UDM Pro shows that the firmware has been successfully upgraded to version 3.1.16. We have the screenshots to show it. Everything is working. All the UniFi wireless access points are working. All the laptops and mobile phones have internet access. But another problem cropped up. Now we could not access the web UI of the UDM Pro. https://192.168.2.1 of the UDM Pro (LAN IP address) is now not accessible. https://192.168.2.254 of the UDM Pro (Port 9 (WAN1)) is also not accessible. We could not putty (ssh) into the UDM Pro too. May I know what the problem could be? I think there's no choice now but to factory reset the UDM Pro and restore configuration from the most recent backup. Our client says their most recent backup
