Tell me what you want, What you really, really want.

Moderator: Mmiscool

User avatar
By forlotto
#54920 Have you tried to check firewall rules or have you tried to use packet sender?
User avatar
By Oldbod
#54927 I guess for now if i want it available it will be create a setting variable for it. Tbh, that it's never come up before probably shows that the default 255 approach works fine for home setups. The esp must iuse the default gateway info from dhcp even though espbasic ( and the sdk?) don't have a way to display it.

Forlotto - i kmow what you mean about sometimes being led astray by an understanding based on experience. I've designed or approved a few addressing schemes over the years but tbh for small private networks using a home router to connect a single site to the outside world .......

You're right, all a subnet mask really does is allow you to override the default split in an ip address between the network portion and the device portion. That's only really useful when you have a limited address range or a lot of networks. With ip4, the chances of getting a 'real' ip4 address allocation big enough to cover every device in a large network were close to zeo 20 years ago, a lot less now, and nobody wants that many points of of entry to police. So you choose your own internal addresses, and most people would pick one that was easily human readable, that is using byte boundaries....its just easier. So as long as you pick an address range that is in the right class, the default mask is fine. Easier still, most home routers don't allow global broadcssts outside the private/local side of the network (commercial routers may allow some specific purpose broadcasts out, usually with contrained delivery to help avoid broadcast storms - eg a bootp 'helper' - hence you could use 255.255.255.255 inside a local network. But specifically targeted is much more elegant...
User avatar
By picstart
#54949 Still no further ahead. The esp8266 Iot UDP broadcasts are being received by the other esp8266's. The goal was to have a win10 PC receive the UDP broadcast packet on xxx,xxx,xxx,255 port yyyy.
I believe the issue is with WIN10.
WIN 10 has buried security that I believe will not allow the broadcast packet to pass through the socket. It is a home wired network with an access point. I so far have found little information about Microsoft filtering in WIN10. A UDP packet targeted to send to a specific esp's IP and port will go through.
Others believe WIN10 has been altered w.r.t UDP since WIN7 or since the introduction of WIN10 IoT.
Again receiving a UDP broad cast packet doesn't appear to work with a WIN10 pro PC with a subnet mask of 255.255.255.0