Since I hate finding unanswered questions in the archive, I'm posting the
resolution. The previous answers that suggested subnetting the internal
network and setting up additional port diversions for the webserver in the
firewall rules didn't do it, certainly not in combination. However,
settin
Cool, thanks. Yes, there's now two subnets on the internal network. I
changed the IP on the backend here's the config details:
# /etc/rc.conf excerpt
ifconfig_ed0="inet 206.169.18.10 netmask 255.255.255.0"
ifconfig_ep0="inet 10.0.0.1 netmask 255.255.255.128"
ifconfig_ep0_alias0="inet 10.0.0.1
On Fri, 19 Jan 2001, Ian Kallen wrote:
> Well, I've been fiddling with the ipfw syntax, I thought this would do it
> /sbin/ipfw add divert 80 all from 10.0.0.128/25 to 206.169.18.10 via ep0
> but that ain't it.
>
> 10.0.0.128/25 has servers, 10.0.0.0/25 has clients, both gateways
> 10.0.0.1 and
On Fri, 19 Jan 2001, Ian Kallen wrote:
> Well, I've been fiddling with the ipfw syntax, I thought this would do it
> /sbin/ipfw add divert 80 all from 10.0.0.128/25 to 206.169.18.10 via ep0
> but that ain't it.
>
> 10.0.0.128/25 has servers, 10.0.0.0/25 has clients, both gateways
> 10.0.0.1 and
On Fri, 19 Jan 2001, Ian Kallen wrote:
> Well, I've been fiddling with the ipfw syntax, I thought this would do it
> /sbin/ipfw add divert 80 all from 10.0.0.128/25 to 206.169.18.10 via ep0
> but that ain't it.
>
> 10.0.0.128/25 has servers, 10.0.0.0/25 has clients, both gateways
> 10.0.0.1 and
Well, I've been fiddling with the ipfw syntax, I thought this would do it
/sbin/ipfw add divert 80 all from 10.0.0.128/25 to 206.169.18.10 via ep0
but that ain't it.
10.0.0.128/25 has servers, 10.0.0.0/25 has clients, both gateways
10.0.0.1 and 10.0.0.129 run off ep0... yes, I've been reading th
On Fri, 19 Jan 2001, Ian Kallen wrote:
>
> I'd like a hand figuring out how to access resources on the internal side
> of a NAT net from within it without doing something kludgey with DNS.
> i.e. suppose I run natd with a configuration like this:
>
> # begin /etc/natd.conf
> use_sockets
> same_
Hmm, I tried that now. I can ping from one subnet to the other, the
redirect_port directive appears to be working (at least outside machines
can access the internal IP/port combination correctly). But the client
subnet still cannot reach the server subnet via the public IP. The servers
and clie
On Fri, 19 Jan 2001, Ian Kallen wrote:
> Now if the DNS for the web server www.foo.com running on 10.0.0.128
> directs a browser on the 10.0.0.0 net to 206.169.18.10, it doesn't get
> routed back to 10.0.0.128; it just hangs (I'm acutally not sure what's
> happening there, the connction never suc
I'd like a hand figuring out how to access resources on the internal side
of a NAT net from within it without doing something kludgey with DNS.
i.e. suppose I run natd with a configuration like this:
# begin /etc/natd.conf
use_sockets
same_ports
port 8668
deny_incoming no
log
redirect_port tcp 1
10 matches
Mail list logo