Re: Access limitation on wap gateway side.

2003-06-08 Thread Stipe Tolj
Vjacheslav Chekushin wrote: > > Hi, Angus and Andreas. > Ok. After discussion I must agree with you that forcing HTTP request to go > from specific interface is good way to solve my problem. > > So go to solution: > http.c function get_connection has hardcoded our_host = NULL, binding > not forc

Re: Access limitation on wap gateway side.

2003-06-06 Thread Steve Kennedy
On Thu, Jun 05, 2003 at 04:38:46PM +0100, Angus M Wood wrote: > On Thu, 05 Jun 2003 13:55:03 +0300, Vjacheslav Chekushin <[EMAIL PROTECTED]> > wrote: > >Yes, it is possible. But in some cases it is not so easy. > >I don't want to maintain several proxies for simple tasks. > >And we loose pool of

Re: Access limitation on wap gateway side.

2003-06-06 Thread Vjacheslav Chekushin
Hi, Angus and Andreas. Ok. After discussion I must agree with you that forcing HTTP request to go from specific interface is good way to solve my problem. So go to solution: http.c function get_connection has hardcoded our_host = NULL, binding not forced now. I propose add configuration variable (

Re: Access limitation on wap gateway side.

2003-06-06 Thread Angus M Wood
On Thu, 05 Jun 2003 13:55:03 +0300, Vjacheslav Chekushin <[EMAIL PROTECTED]> wrote: Yes, it is possible. But in some cases it is not so easy. I don't want to maintain several proxies for simple tasks. And we loose pool of open connections functionality for example. I think that to implement simpl

Re: Access limitation on wap gateway side.

2003-06-06 Thread Angus M Wood
On Fri, 06 Jun 2003 08:24:37 +0300, Vjacheslav Chekushin <[EMAIL PROTECTED]> wrote: Hi, Angus. Yes, it is simple solution, if I have one WAP gateway on host. But once more: I talking about MANY gateways bound to different external interfaces on ONE host. For routing to private network I use only

Re: Access limitation on wap gateway side.

2003-06-05 Thread Andreas Fink
On Freitag, Juni 6, 2003, at 07:24 Uhr, Vjacheslav Chekushin wrote: Hi, Angus. Yes, it is simple solution, if I have one WAP gateway on host. But once more: I talking about MANY gateways bound to different external interfaces on ONE host. For routing to private network I use only one interface,

Re: Access limitation on wap gateway side.

2003-06-05 Thread Vjacheslav Chekushin
Hi, Angus. Yes, it is simple solution, if I have one WAP gateway on host. But once more: I talking about MANY gateways bound to different external interfaces on ONE host. For routing to private network I use only one interface, so all connection to private network from ALL wap gateways go through t

Re: Access limitation on wap gateway side.

2003-06-05 Thread Vjacheslav Chekushin
Hi, Andreas. Andreas Fink wrote: On Donnerstag, Juni 5, 2003, at 09:50 Uhr, Vjacheslav Chekushin wrote: Hi, list. I have several WAP gateways on one host (bound to different interfaces). One of WAP gateways is allowed to go into private network, but others not. Therefore

Re: Access limitation on wap gateway side.

2003-06-05 Thread Andreas Fink
On Donnerstag, Juni 5, 2003, at 09:50 Uhr, Vjacheslav Chekushin wrote: Hi, list. I have several WAP gateways on one host (bound to different interfaces). One of WAP gateways is allowed to go into private network, but others not. Therefore I must limit access to private network somewhere in WAP g

Access limitation on wap gateway side.

2003-06-05 Thread Vjacheslav Chekushin
Hi, list. I have several WAP gateways on one host (bound to different interfaces). One of WAP gateways is allowed to go into private network, but others not. Therefore I must limit access to private network somewhere in WAP gateway internally. So we go to http connection limitation on WAP gateway s