152 reputation
27
bio website
location
age
visits member for 4 years, 7 months
seen Nov 29 '13 at 8:52

Dec
19
awarded  Nice Question
Jun
18
awarded  Popular Question
Feb
12
awarded  Notable Question
Oct
8
awarded  Notable Question
Jan
25
awarded  Popular Question
Oct
21
awarded  Popular Question
Jun
2
asked How much does 24 hours of a large instance on ec2 cost?
Jan
24
awarded  Scholar
Jan
24
accepted lvs vs haproxy vs ? for hostname based forwarding
Jan
24
asked lvs vs haproxy vs ? for hostname based forwarding
Jan
24
asked How to divert traffic based on hostname using HAProxy?
Jan
23
awarded  Student
Jan
23
answered apache listening on 80, but not on any other port
Jan
22
revised apache listening on 80, but not on any other port
deleted 33 characters in body; edited title
Jan
22
revised apache listening on 80, but not on any other port
added 163 characters in body
Jan
22
revised apache listening on 80, but not on any other port
added 908 characters in body
Jan
22
comment apache listening on 80, but not on any other port
will try this. but why my current config's as ^ work for port 80, and not any other port
Jan
22
revised apache listening on 80, but not on any other port
deleted 579 characters in body
Jan
22
comment apache listening on 80, but not on any other port
unforunately this did not make a difference. i dont have tshark on the machine, but tcpdump that effectively does the same thing did not detect anything. NOTE: i do have some added information in UPDATE 2 about some promiscuous mode
Jan
22
revised apache listening on 80, but not on any other port
added UPDATE 1 & UPDATE 2