Hi,
I've been playing with twisted msn implementation but failed to figure out
how to send/recv message to another msn user ? I understand that i need to
use msn.SwitchboardClient but am confused as to how and where to connect it
? what factory to use etc.
any hint/example shall be appreciated.
To all those whose email I have (and still am) filling:
Yers - it was a network problem on my part. The two NIC's were causing
the problems. The example code is now working fine. Thanks all:-)
On Wed, Mar 10, 2010 at 2:43 PM, Ben Barker wrote:
> Ah - I have now sorted the interface problem.
>
>
Ah - I have now sorted the interface problem.
I run the code I listed earlier, but it sites at the command line
saying "listening" without every dumping anything to screen.
/sbin/ip maddr now shows:
eth1
link 01:00:5e:00:00:04
link 33:33:ff:7a:7e:4e
link 01:00:5e:00:00
On 10/03/10 13:18, Ben Barker wrote:
> Well that's odd...
>
> I changed the interfaces over - used eth1 for the connection to the
> network I need to sniff...
>
> and now /sbin/ip maddr tells me I have joined 224.0.0.4 on eth0 !
>
> Whichever interface is live, the join seems to happen on the other
On Wed, 2010-03-10 at 10:35 +, Ben Barker wrote:
> I have been looking at the examples here:
>
> http://code.activestate.com/recipes/425975-simple-udp-multicast-client-server-using-twisted/
>
> But I seem to have trouble getting them to receive anything at all.
Did you do the joinGroup()? O
Well that's odd...
I changed the interfaces over - used eth1 for the connection to the
network I need to sniff...
and now /sbin/ip maddr tells me I have joined 224.0.0.4 on eth0 !
Whichever interface is live, the join seems to happen on the other :-p
What could there be about my network config
On 10/03/10 13:03, Ben Barker wrote:
>>> But I seem to have trouble getting them to receive anything at all.
>>
>> That's a little vague. Does "trouble" mean "it sometimes works" or
>> "never works"?
>>
>
> Sorry - yes, it was very vague! Never works. If I run wiresahrk I can
> see udp packets addr
>> But I seem to have trouble getting them to receive anything at all.
>
> That's a little vague. Does "trouble" mean "it sometimes works" or
> "never works"?
>
Sorry - yes, it was very vague! Never works. If I run wiresahrk I can
see udp packets addressed to 224.0.0.4, port 901, flying past, howe
On 10/03/10 10:35, Ben Barker wrote:
> Hello - I wonder if someone can help:
>
> We have some status info being sent by various machines using
> multicast addressed udp packets. I have been attempting to use twisted
> to write a python script that will passively monitor on the relevant
> port for a
Thanks Lars - yes, I am not adamant about using twisted, although it
seemed initially to be the best place to stary. I have also been
looking at the pcapy module, which I think may do what I want, but
also seems very low level.
On Wed, Mar 10, 2010 at 10:48 AM, Lars Ivar Igesund wrote:
> Hi Ben,
Hi Ben,
my experience (not with Twisted, but with multicast), is that
multicast often fail to be properly routed (this may be a restriction
on OS, switch, etc). That you see the multicasts on using tshark is no
indication on the routing working properly, as it will catch all
information in promisc
Hello - I wonder if someone can help:
We have some status info being sent by various machines using
multicast addressed udp packets. I have been attempting to use twisted
to write a python script that will passively monitor on the relevant
port for any udp packets with the specified multicast addr
12 matches
Mail list logo
