December 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] UDP Broadcast message

by jannik.laval

Ohhhhhh yessss ! Thank you, It works fine ! No more need of Wireshark. Thank you again. Jannik On Dec 19, 2013, at 4:40 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > You also have to set a port with #setPort: no ? > > On 19 Dec 2013, at 16:39, jannik.laval <jannik.laval(a)gmail.com> wrote: > >> And here is my small example code: >> >> udpSocket := Socket newUDP. >> udpSocket setOption: 'SO_BROADCAST' value: true. >> udpSocket getOption: 'SO_BROADCAST'. >> udpSocket receiveDataTimeout: 15. >> >> >> Jannik >> >> On Dec 19, 2013, at 4:29 PM, jannik.laval <jannik.laval(a)gmail.com> wrote: >> >>> Ok, here is my situation: >>> >>> - I have a Lego Mindstorm that broadcast a UDP message every 10 seconds. >>> - With Wireshark I can see the UDP message, so no problem with that. >>> - I tried to set the option SO_BROADCAST, it does not work anymore. >>> >>> Any other idea ? >>> >>> Jannik >>> >>> On Dec 19, 2013, at 4:14 PM, Stephan Eggermont <stephan(a)stack.nl> wrote: >>> >>>> Norbert wrote: >>>>> To send or receive a broadcast packet you need to put special options on the socket on the native side (setsockopt). You need to >look if the SO_BROADCAST option is mentioned anywhere. If not it wonât work without adding them. And for sending them you >need almost special privileges on the system. This is not a âuser featureâ. >>>> >>>> And even though it is "the right thing" for lots of situations, your network is also very likely to not do the right thing >>>> with broadcast packets. Etsy decided on using bittorrent protocol to update their production servers indexes, because they >>>> found it too difficult to get their network to do the right thing. They found that their switches were basically livelocked >>>> while dealing with broadcast packets. >>>> >>>> http://codeascraft.com/2012/01/23/solr-bittorrent-index-replication/ >>>> >>>> If you want the broadcast to travel a little further, the routers need to be configured not to drop the packets. >>>> >>>> Stephan >>> >> > >

Dec. 19, 2013

Re: [Pharo-dev] UDP Broadcast message

by Norbert Hartl

Am 19.12.2013 um 16:39 schrieb jannik.laval <jannik.laval(a)gmail.com>: > And here is my small example code: > > udpSocket := Socket newUDP. > udpSocket setOption: 'SO_BROADCAST' value: true. > udpSocket getOption: 'SO_BROADCAST'. > udpSocket receiveDataTimeout: 15. > There are operating system specific problems. You need to check if you need specific priviledges even for receiving packets. On linux systems there was once something about the binding interface you use. You need either specific (IP address) or wildcard (0.0.0.0) to make it operate. But can not recall which it was. Norbert > > Jannik > > On Dec 19, 2013, at 4:29 PM, jannik.laval <jannik.laval(a)gmail.com> wrote: > >> Ok, here is my situation: >> >> - I have a Lego Mindstorm that broadcast a UDP message every 10 seconds. >> - With Wireshark I can see the UDP message, so no problem with that. >> - I tried to set the option SO_BROADCAST, it does not work anymore. >> >> Any other idea ? >> >> Jannik >> >> On Dec 19, 2013, at 4:14 PM, Stephan Eggermont <stephan(a)stack.nl> wrote: >> >>> Norbert wrote: >>> >To send or receive a broadcast packet you need to put special options on the socket on the native side (setsockopt). You need to >look if the SO_BROADCAST option is mentioned anywhere. If not it wonât work without adding them. And for sending them you >need almost special privileges on the system. This is not a âuser featureâ. >>> >>> And even though it is "the right thing" for lots of situations, your network is also very likely to not do the right thing >>> with broadcast packets. Etsy decided on using bittorrent protocol to update their production servers indexes, because they >>> found it too difficult to get their network to do the right thing. They found that their switches were basically livelocked >>> while dealing with broadcast packets. >>> >>> http://codeascraft.com/2012/01/23/solr-bittorrent-index-replication/ >>> >>> If you want the broadcast to travel a little further, the routers need to be configured not to drop the packets. >>> >>> Stephan >> >

Dec. 19, 2013

Re: [Pharo-dev] UDP Broadcast message

by Sven Van Caekenberghe

You also have to set a port with #setPort: no ? On 19 Dec 2013, at 16:39, jannik.laval <jannik.laval(a)gmail.com> wrote: > And here is my small example code: > > udpSocket := Socket newUDP. > udpSocket setOption: 'SO_BROADCAST' value: true. > udpSocket getOption: 'SO_BROADCAST'. > udpSocket receiveDataTimeout: 15. > > > Jannik > > On Dec 19, 2013, at 4:29 PM, jannik.laval <jannik.laval(a)gmail.com> wrote: > >> Ok, here is my situation: >> >> - I have a Lego Mindstorm that broadcast a UDP message every 10 seconds. >> - With Wireshark I can see the UDP message, so no problem with that. >> - I tried to set the option SO_BROADCAST, it does not work anymore. >> >> Any other idea ? >> >> Jannik >> >> On Dec 19, 2013, at 4:14 PM, Stephan Eggermont <stephan(a)stack.nl> wrote: >> >>> Norbert wrote: >>> >To send or receive a broadcast packet you need to put special options on the socket on the native side (setsockopt). You need to >look if the SO_BROADCAST option is mentioned anywhere. If not it wonât work without adding them. And for sending them you >need almost special privileges on the system. This is not a âuser featureâ. >>> >>> And even though it is "the right thing" for lots of situations, your network is also very likely to not do the right thing >>> with broadcast packets. Etsy decided on using bittorrent protocol to update their production servers indexes, because they >>> found it too difficult to get their network to do the right thing. They found that their switches were basically livelocked >>> while dealing with broadcast packets. >>> >>> http://codeascraft.com/2012/01/23/solr-bittorrent-index-replication/ >>> >>> If you want the broadcast to travel a little further, the routers need to be configured not to drop the packets. >>> >>> Stephan >> >

Dec. 19, 2013

Re: [Pharo-dev] UDP Broadcast message

by jannik.laval

And here is my small example code: udpSocket := Socket newUDP. udpSocket setOption: 'SO_BROADCAST' value: true. udpSocket getOption: 'SO_BROADCAST'. udpSocket receiveDataTimeout: 15. Jannik On Dec 19, 2013, at 4:29 PM, jannik.laval <jannik.laval(a)gmail.com> wrote: > Ok, here is my situation: > > - I have a Lego Mindstorm that broadcast a UDP message every 10 seconds. > - With Wireshark I can see the UDP message, so no problem with that. > - I tried to set the option SO_BROADCAST, it does not work anymore. > > Any other idea ? > > Jannik > > On Dec 19, 2013, at 4:14 PM, Stephan Eggermont <stephan(a)stack.nl> wrote: > >> Norbert wrote: >> >To send or receive a broadcast packet you need to put special options on the socket on the native side (setsockopt). You need to >look if the SO_BROADCAST option is mentioned anywhere. If not it wonât work without adding them. And for sending them you >need almost special privileges on the system. This is not a âuser featureâ. >> >> And even though it is "the right thing" for lots of situations, your network is also very likely to not do the right thing >> with broadcast packets. Etsy decided on using bittorrent protocol to update their production servers indexes, because they >> found it too difficult to get their network to do the right thing. They found that their switches were basically livelocked >> while dealing with broadcast packets. >> >> http://codeascraft.com/2012/01/23/solr-bittorrent-index-replication/ >> >> If you want the broadcast to travel a little further, the routers need to be configured not to drop the packets. >> >> Stephan >

Dec. 19, 2013

Re: [Pharo-dev] UDP Broadcast message

by Norbert Hartl

Am 19.12.2013 um 16:29 schrieb jannik.laval <jannik.laval(a)gmail.com>: > Ok, here is my situation: > > - I have a Lego Mindstorm that broadcast a UDP message every 10 seconds. > - With Wireshark I can see the UDP message, so no problem with that. > - I tried to set the option SO_BROADCAST, it does not work anymore. > > Any other idea ? > What operating system are you using? Norbert > Jannik > > On Dec 19, 2013, at 4:14 PM, Stephan Eggermont <stephan(a)stack.nl> wrote: > >> Norbert wrote: >> >To send or receive a broadcast packet you need to put special options on the socket on the native side (setsockopt). You need to >look if the SO_BROADCAST option is mentioned anywhere. If not it wonât work without adding them. And for sending them you >need almost special privileges on the system. This is not a âuser featureâ. >> >> And even though it is "the right thing" for lots of situations, your network is also very likely to not do the right thing >> with broadcast packets. Etsy decided on using bittorrent protocol to update their production servers indexes, because they >> found it too difficult to get their network to do the right thing. They found that their switches were basically livelocked >> while dealing with broadcast packets. >> >> http://codeascraft.com/2012/01/23/solr-bittorrent-index-replication/ >> >> If you want the broadcast to travel a little further, the routers need to be configured not to drop the packets. >> >> Stephan >

Dec. 19, 2013

Re: [Pharo-dev] UDP Broadcast message

by Norbert Hartl

Am 19.12.2013 um 16:14 schrieb Stephan Eggermont <stephan(a)stack.nl>: > Norbert wrote: > >To send or receive a broadcast packet you need to put special options on the socket on the native side (setsockopt). You need to >look if the SO_BROADCAST option is mentioned anywhere. If not it wonât work without adding them. And for sending them you >need almost special privileges on the system. This is not a âuser featureâ. > > And even though it is "the right thing" for lots of situations, your network is also very likely to not do the right thing > with broadcast packets. Etsy decided on using bittorrent protocol to update their production servers indexes, because they > found it too difficult to get their network to do the right thing. They found that their switches were basically livelocked > while dealing with broadcast packets. > > http://codeascraft.com/2012/01/23/solr-bittorrent-index-replication/ > > If you want the broadcast to travel a little further, the routers need to be configured not to drop the packets. > > Stephan I donât think broadcast is âthe right thingâ in most use cases. It is just a lot less cumbersome to use instead of multicast which is supposed to be the right thing for a broader use. So you can overuse broadcast very easy. In an environment with a lot of cascaded switches broadcast is something that makes the whole thing inoperable. A switch tries to use the smallest number of physical ports to route packets. It decides that based on internal tables recorded from MAC addresses and such. Broadcast is a brute force attempt where every address bit is set to reach every participant in the local hardware segment. So you might see that a switch has basically no other option then to open all ports to send a broadcast packet. So having a prevent-broadcast-packets option is a last ressort option. Norbert

Dec. 19, 2013

Re: [Pharo-dev] UDP Broadcast message

by jannik.laval

Ok, here is my situation: - I have a Lego Mindstorm that broadcast a UDP message every 10 seconds. - With Wireshark I can see the UDP message, so no problem with that. - I tried to set the option SO_BROADCAST, it does not work anymore. Any other idea ? Jannik On Dec 19, 2013, at 4:14 PM, Stephan Eggermont <stephan(a)stack.nl> wrote: > Norbert wrote: > >To send or receive a broadcast packet you need to put special options on the socket on the native side (setsockopt). You need to >look if the SO_BROADCAST option is mentioned anywhere. If not it wonât work without adding them. And for sending them you >need almost special privileges on the system. This is not a âuser featureâ. > > And even though it is "the right thing" for lots of situations, your network is also very likely to not do the right thing > with broadcast packets. Etsy decided on using bittorrent protocol to update their production servers indexes, because they > found it too difficult to get their network to do the right thing. They found that their switches were basically livelocked > while dealing with broadcast packets. > > http://codeascraft.com/2012/01/23/solr-bittorrent-index-replication/ > > If you want the broadcast to travel a little further, the routers need to be configured not to drop the packets. > > Stephan

Dec. 19, 2013

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/30653 Home: https://github.com/pharo-project/pharo-core

Dec. 19, 2013

[pharo-project/pharo-core] 9822a6: 30653

by GitHub

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: 9822a65fdf5c0fe4ef9c41887245533dd31334ba https://github.com/pharo-project/pharo-core/commit/9822a65fdf5c0fe4ef9c4188… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2013-12-19 (Thu, 19 Dec 2013) Changed paths: M Manifest-CriticBrowser.package/CriticBrowser.class/instance/private/browseRule.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script306.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30653.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Slot.package/MethodRecompileStrategy.class/instance/updating/transform_to_using_.st M Slot.package/MethodRecompileStrategy.class/instance/updating/updateClassLiteralKeysIn_.st A Slot.package/PharoClassInstaller.class/instance/migrating/fixClassBindings_.st M Slot.package/PharoClassInstaller.class/instance/notifications/classDefinitionChangedFrom_to_by_.st M Slot.package/SlotClassBuilder.class/instance/initialize-release/buildNewClass.st A SlotTests.package/SlotMethodRecompilationTest.class/README.md A SlotTests.package/SlotMethodRecompilationTest.class/definition.st A SlotTests.package/SlotMethodRecompilationTest.class/instance/accessing/method.st A SlotTests.package/SlotMethodRecompilationTest.class/instance/accessing/methodBinding.st A SlotTests.package/SlotMethodRecompilationTest.class/instance/accessing/traitMethod.st A SlotTests.package/SlotMethodRecompilationTest.class/instance/accessing/traitMethodBinding.st A SlotTests.package/SlotMethodRecompilationTest.class/instance/running/setUp.st A SlotTests.package/SlotMethodRecompilationTest.class/instance/tests/reshapeClass.st A SlotTests.package/SlotMethodRecompilationTest.class/instance/tests/testClassReshapeShouldKeepClassBinding.st A SlotTests.package/SlotMethodRecompilationTest.class/instance/tests/testClassReshapeShouldKeepClassBindingForTraitMethods.st A SlotTests.package/SlotMethodRecompilationTest.class/instance/tests/testMethodClassBindingShouldBeClassBinding.st A SlotTests.package/SlotMethodRecompilationTest.class/instance/tests/testTraitMethodClassBindingShouldBeClassBinding.st Log Message: ----------- 30653 11756 Reshaping a class breaks classBinding identity https://pharo.fogbugz.com/f/cases/11756 12450 CriticBrowser Browss Rule opens SystemBrowser on TreeNodeModel https://pharo.fogbugz.com/f/cases/12450 http://files.pharo.org/image/30/30653.zip

Dec. 19, 2013

Re: [Pharo-dev] UDP Broadcast message

by Stephan Eggermont

Norbert wrote: >To send or receive a broadcast packet you need to put special options on the socket on the native side (setsockopt). You need to >look if the SO_BROADCAST option is mentioned anywhere. If not it wonât work without adding them. And for sending them you >need almost special privileges on the system. This is not a âuser featureâ. And even though it is "the right thing" for lots of situations, your network is also very likely to not do the right thing with broadcast packets. Etsy decided on using bittorrent protocol to update their production servers indexes, because they found it too difficult to get their network to do the right thing. They found that their switches were basically livelocked while dealing with broadcast packets. http://codeascraft.com/2012/01/23/solr-bittorrent-index-replication/ If you want the broadcast to travel a little further, the routers need to be configured not to drop the packets. Stephan

Dec. 19, 2013