Featured post

c# - Usage of Server Side Controls in MVC Frame work -

i using asp.net 4.0 , mvc 2.0 web application. project requiremrnt have use server side control in application not possibl in noraml case. ideally want use adrotator control , datalist control. i saw few samples , references in codepleax mvc controllib howwver found less useful. can tell how utilize theese controls in asp.net application along mvc. note: please provide functionalities related adrotator , datalist controls not equivalent functionalities thanks in advace. mvc pages not use normal .net solution makes use of normal .net components impossible. a normal .net page use event driven solution call different methods service side mvc use actions , view completly different way handle things. also, mvc not use viewstate normal .net controlls require. found article discussing mixing of normal .net , mvc.

c# - UDP hole-punching: testability on single machine -


i'm writing simple p2p application test feasibilty of using udp hole-punching in larger project.

i tried test apps home yesterday , worked.

however, @ work , same code no longer job. sender sending appropriate port on external ip address of our router here, receiver isn't getting of them.

prior calling udpclient.receive(), receiving app sends packet ip:port listening on. again, works on home setup, not here. outcome same regardless of whether windows firewall on or off, that's not issue.

could routers handling situation differently?

edit1: both apps run on same machine.

in answer own question:

the routers indeed exhibiting different behavior.

my home router hooked laptop. assume why when send out udp packet port n leaves router on port n.

however, work network consists of several computers , router randomizes port on end, means packet sent port y leave router on port x.

i have gotten home , work machines communicate through nat without using port forwarding in following way:

h - sends packet port w:b, thereby opening port incoming connections

w - sends packet h:a , switches receive mode. has open port.

h - receives packet w , instead of presuming know port reply to, checks packet source port , uses instead.

h - sends packet w:source port

w - receives packet.

voila.

in practice, tho, h , w contact server exchange connection details, simplifies matters because server knows ports h , w sending from.


Comments

Popular posts from this blog

c# - Usage of Server Side Controls in MVC Frame work -

cocoa - Nesting arrays into NSDictionary object (Objective-C) -

ios - Very simple iPhone App crashes on UILabel settext -