On Fri, Oct 23, 2026 at 05:16:26PM +0200, [email protected] wrote: > Hello,
hello > I "inherited" a nat server which wouldnt boot. Actually not that relevant, see below, but you mean a NAS server (NAS == "network attached storage")? > I installed a fresh debian on it, but I can't figure out to set up an > ethernet connection. The above question not that relevant, because it now is a Debian box :-) > I'm still figuring things out, but here is my knowledge so far: > There are two interfaces eno2np1 and eno1np0. Those look like Ethernet. Are they connected to something? What does "ip addr show" say? > I set the my /etc/hosts, domain name and /etc/network/interfaces as before: > Say the address is 123.123.123.123 with a gateway of 123.123.134.254 and a > nameserver somewhere else: 123.123.100.100. Are those IP addresses for real, or are you keeping back the "real" ones for privacy reasons? (That would be *perfectly fine*, but we might come up with more intelligent ideas when we know that this is the case). > I don't have full access to the network, someone just gave this ip address > to the server. Can you ping your name server? If not: how do the error messages look? > I tried doing dhcpcd on both networks, and it works, but it gives me some > random address like 165.255.255.3. Aha. That answers (partially) some of the questions above. There is a net "out there" (what you mean with "both networks". And: you are doing "dhcpd" or rather "dhclient"? (the second command is to request an IP address -- and possibly other network config, like DNS, etc. -- from a running DHCP server (for example dhcpd) out there. > And ping says the temporar failure in name resolution. > I also can't ping any nameserver, not 8.8.8.8, not 123.123.100.100. Assuming you actually did "dhclient" above: what is in your /etc/resolv.conf after this step? (again, it is OK to hide your "real" IP addresses, but then you better choose a consistent renaming, so we can make intelligent guesses :-) > Could the issue be, that I have to change my MAC address, because it will be > blocked somehow if its not the original? That depends on the network your box lives in. Some do restrict the MAC addresses allowed to connect to ports (this will be typical in a bigger corporate or uni network). This is intended to enhance security. Ask your sysadmins. > Physical access to the server is difficult at the moment. That makes things ever more interesting :-) Cheers & good luck -- tomás
signature.asc
Description: PGP signature
