On 06/10/2007, a.padilla <[EMAIL PROTECTED]> wrote:
> this is a small private I'm doing between to computers for
> educational purposes.  the server is also connected to a dhcp
> network.  that's why the internal interface has a private IP.

I'm not surprised your internal NIC has a private IP.
I'm surprised your external NIC has one too.

> I'm trying to work with what's available to me.
> On Oct 5, 2007, at 3:10 PM, ropers wrote:
>
> > On 05/10/2007, a.padilla <[EMAIL PROTECTED]> wrote:
> >> ifconfig:
> >>
> >> (...)
> >> rl0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
> >>         lladdr 00:18:4d:ea:33:0a
> >>         groups: egress
> >>         media: Ethernet autoselect (100baseTX full-duplex)
> >>         status: active
> >>         inet6 fe80::218:4dff:feea:330a%rl0 prefixlen 64 scopeid 0x1
> >>         inet 192.168.0.111 netmask 0xffffff00 broadcast 192.168.0.255
> >> dc0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
> >>         lladdr 00:14:bf:53:1e:fe
> >>         media: Ethernet autoselect (100baseTX full-duplex)
> >>         status: active
> >>         inet6 fe80::214:bfff:fe53:1efe%dc0 prefixlen 64 scopeid 0x2
> >>         inet 10.0.0.0 netmask 0xff000000 broadcast 255.255.255.0
> >
> > I need to do a double-take on the above: Why do both of your NICs have
> > private IPs? Is your ISP doing NAT as well and do they only give you
> > private IPs or what's the story?
>
>


-- 
www.ropersonline.com

Reply via email to