DHCP failure: NACK
I set up a local DHCP server at home and disabled the DHCP running on my internet provider modem. My laptop, phone & tablet are working fine and are able to get an IP however I have troubles with my sonos wifi speaker: it keeps sending DHCP requests like this:
192.168.1.62 is the DHCP server. 192.168.1.254 is the modem. I guess the problem is the NACK request sent by the modem (the DHCP server is disabled on it though)... The pcap file is available here: https://ufile.io/vaubc Any idea about what's wrong here?
See also questions close to this topic
Ethernet connection using PRO/1000 GT Desktop Adapter and Beckhoff
Using openSUSE 11 (i586) installed on a PC used for an old project.
I have a problem with the network card (Intel PRO/1000 GT Desktop Adapter). Connecting the ethernet cable to a Beckhoff module (EK1100), the light on the PC-Port lights up, while nothing happens on the module. This happens even if connected to a switch instead of the Beckhoff module. The Beckhoff module has been tested with an another PC and it works.
I have already done several tests, but without positive results:
- changed the cable
- changed network card slot in the PCI
- reinstalled the network card driver (e1000)
Someone with more experience knows by chance what could be the problem?
Thanks to anyone who decides to help me!
Add printer that connect to router wireless from pc that connect to LAN
My PC connect to LAN network, say it PC1.
PC1 config is: - IP 172.16.160.203 netmask 255.255.255.0 broadcast 172.16.160.255.
There is a wireless router that connect to the same LAN network, say it WR. WR config is: - IP 172.16.160.183 netmask 255.255.255.0 broadcast 172.16.160.255.
WR setup is: - subnet mask: 255.255.255.0
There is a printer that connect to the wireless. It IP is 192.168.1.2
I try to ping 192.168.1.2 from PC1 and it tells Destination Host Unreachable. How can I add printer to PC1?
Nb: I use Linux Mint
Can't create network bridge on Ubuntu server 18.04
I'm trying to expose my KVM/libvirt guests to my home network with a bridge interface. I have disabled network-manager and configured br0 in my /etc/network/interfaces as below:
# /etc/network/interfaces -- configuration file for ifup(8), ifdown(8) # Generated by debian-installer. # The loopback interface auto lo iface lo inet loopback # The bridge interface for KVM/qemu auto br0 iface br0 inet static address 192.168.1.25 network 192.168.1.0 netmask 255.255.255.0 broadcast 192.168.1.255 gateway 192.168.1.1 dns-nameservers 192.168.1.5 22.214.171.124 dns-search example.com bridge_ports eno1 bridge_stp off bridge_fd 0 bridge_maxwait 0
Despite this, before and after rebooting, the interface is not available to my KVM guests. It is also not listed in the output of ip link, even though virbr0 is there.
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000 link/ether 90:b1:1c:00:22:9d brd ff:ff:ff:ff:ff:ff 3: eno2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 90:b1:1c:00:22:9e brd ff:ff:ff:ff:ff:ff 4: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default qlen 1000 link/ether 52:54:00:ac:13:93 brd ff:ff:ff:ff:ff:ff 5: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc fq_codel master virbr0 state DOWN mode DEFAULT group default qlen 1000 link/ether 52:54:00:ac:13:93 brd ff:ff:ff:ff:ff:ff 6: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default link/ether 02:42:5c:bc:08:32 brd ff:ff:ff:ff:ff:ff
I am connected to the network on eno1:
eno1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.1.25 netmask 255.255.255.0 broadcast 192.168.1.255 inet6 fe80::92b1:1cff:fe00:229d prefixlen 64 scopeid 0x20<link> ether 90:b1:1c:00:22:9d txqueuelen 1000 (Ethernet) RX packets 3689 bytes 559475 (559.4 KB) RX errors 0 dropped 10 overruns 0 frame 0 TX packets 1749 bytes 769715 (769.7 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
I've been fiddling with this for hours and gotten nowhere. Can anyone spot an issue with my setup?
Thoughts on needed subnet expansions
I work for a non-profit with some slightly more antiquated hardware. We have 3 locations, about 700 devices across them. Right now our locations are set up as:
Location 1 (Main) - /23 with a DHCP server. Range is 10.0.0.0 - 10.0.1.254
Location 2 - /24 with a DHCP server. Range is 192.168.0.0 - 192.168.0.254
Location 3 - /24 without a DHCP server. This location has the subnet issued by our ISP and all devices are pointed back to our primary and secondary DNS servers via adapter management (often via scripts).
We are rolling out VoIP at the end of the month and I'm not confident we have the necessary IPs to handle the incoming hardware at Location 1 and Location 2. I'm looking for thoughts on the following:
Moving Location 1 to a /22. This location has a ton of static devices (DVRs, Routers, Printers, reserved leases, most of our servers, etc). This would be quite a bit of work.
Moving Location 2 to a /23. This has fewer static devices and probably wouldn't be as difficult.
Here are my questions / issues that are causing me to be conflicted:
I actually don't know how many open IP addresses we have at Location 1. Unfortunately, my predecessor didn't use reservations, so I have no way to see all of the static devices on the network outside of just..knowing. In addition, the scope was set to only 150 addresses of the potential 512, but it was set in the middle of the subnet and I can't figure out why.
I think it would be nice to have all of the VoIP phones on their own cluster of 256, even if I don't NEED the addresses, maybe I should expand and scope it anyway?
I know that /24 has always been the ideal scenario for a network, but anymore is this really necessary? Does anyone see any issues with /22?
We don't have vLANs and our switches are dummy switches. I've been pushing for managed (or partially managed) switches at the minimum, but they aren't approved yet, so vLANs aren't really an option right now.
A final note, all of our servers are physical devices and not virtualized. Again, working on approval, but hard to come by with tight budget constraints. This means that changes are not easily snapshotted or restored from backup.
Anyone have some thoughts or suggestions on what you would recommend?
How do I send a UDP hardware unicast on Windows?
I am developing a DHCP server in Rust.
The DHCP server must be able to send hardware unicasts to clients with unconfigured interfaces using their MAC address and the newly assigned (but not configured yet) IP address.
I have solved it on Linux by injecting an ARP entry before sending a packet, and on FreeBSD and Mac OS with BPF.
As long as there are few open-source DHCP servers for Windows, I cannot know how to send a hardware unicast properly.
I have tried the
CreateIpNetEntryWinAPI function, but for some reason it blocks for 3 seconds exactly and then returns the success code with no effect (I do not see the anticipated entry neither with
For now it is solved by calling subprocess
netsh ip interface set neighbors ..., but such a solution does not fit my project will.
How do I send a UDP hardware unicast on Windows properly?
DHCP network settings
I have a Synology NAS box (IP 192.168.8.104). I cannot seem to access it. I used to be able to access it from my Xbox connected to the same T Link router. Now, since I got a new router, the Xbox cannot see it.
Also, when I use my MacBook, in Finder I can see the Nas box, and can connect to it with the username and password.
However when entering 192.168.8.104:5000 in a browser, the response times out.
Looking at my DHCP settings in the router, the start IP is 126.96.36.199 and end 192.168.0.199. The range is outside the NAS IP. I cannot change there to a range fitting the NAS IP.
Any ideas please? How can I get a browser and/or Xbox to connect.