2 NICS-correct IP

2 NICS-correct IP

Post by guita » Tue, 04 Jan 2000 04:00:00



I have 2 NICs in one of my PC running BeOS and FreeBSD. I want to test it
using FreeBSD by pinging or telneting to my OpenBSD box(firewall). I just
need a correct IP on both of these NICs, inclusing netmasks. My OpenBSD's
NIC has an IP of 192.168.0.1, netmask 255.255.255.0.
TIA

Leon

 
 
 

2 NICS-correct IP

Post by Brett Wilso » Wed, 05 Jan 2000 04:00:00


I'm not sure what you're asking. Why do you have 2 NICs in your PC
inside the firewall? The firewall should have 2 of course...

Is your problem setting up the firewall or the inside computer? You can
make up the IP addresses youself as long as the firewall has the correct
routing. The only place you need the IP is in the OS of the computer
whose IP you want to set.

Brett


> I have 2 NICs in one of my PC running BeOS and FreeBSD. I want to test it
> using FreeBSD by pinging or telneting to my OpenBSD box(firewall). I just
> need a correct IP on both of these NICs, inclusing netmasks. My OpenBSD's
> NIC has an IP of 192.168.0.1, netmask 255.255.255.0.
> TIA

> Leon


 
 
 

2 NICS-correct IP

Post by guita » Wed, 05 Jan 2000 04:00:00


I just want to test if the new NIC(the one that isn't working) works by
putting it in my PC inside the firewall. In the future I will be be using
the inside PC as a firewall because I'm planning to get a DSL which in this
case should need 2 NICS. My other PC which acts as a firewall right now has
only one NIC and a dial-up connection to the 'net.
    But, basically all I want to know are correct IP addresses for my two
NICs in the inside PC. Let's say I don't have any IPs on both NICs in my
inside PC and my other PC has an IP of 192.168.0.1. Can I just assign any IP
other thatn 192.168.0.1 on both NICS?


> I'm not sure what you're asking. Why do you have 2 NICs in your PC
> inside the firewall? The firewall should have 2 of course...

> Is your problem setting up the firewall or the inside computer? You can
> make up the IP addresses youself as long as the firewall has the correct
> routing. The only place you need the IP is in the OS of the computer
> whose IP you want to set.

> Brett


> > I have 2 NICs in one of my PC running BeOS and FreeBSD. I want to test
it
> > using FreeBSD by pinging or telneting to my OpenBSD box(firewall). I
just
> > need a correct IP on both of these NICs, inclusing netmasks. My
OpenBSD's
> > NIC has an IP of 192.168.0.1, netmask 255.255.255.0.
> > TIA

> > Leon

 
 
 

1. Correct IP configuration for machine with dynamically-assigned IP address?

Hi,

I am using Linux 2.0.33 with ppp-2.3.5, and I am trying to unravel my
nightmarish network configuration. I used to have my hostname aliased to
the loopback address and everything seemed to work OK. Then I learnt
that this was a "bad thing" and so I tried to correct the issue - anyway
I'd like to resolve my hostname to my REAL IP addres when such a thing
is available. The problem now is that some of the network-aware daemons
such as lpd and pppd are now giving me errors.

lpd is flatly refusing to run - it reads my hostname, can't find an IP
address in the /etc/hosts file to match it and then quits. pppd is
working, but it is also adding strange messages to the syslog such as

Cannot determine ethernet address for proxy ARP

whatever that means - I don't HAVE any ethernet hardware so I don't see
why it is looking for anything remotely ethernet-related.  Sendmail is
also trying to resolve my hostname into an IP address.

There has to be a tidy solution to this - there must be lots of Linux
boxes out there that only network though ppp.
Can anyone help, please?

Cheers,
Chris.

2. Odd behaviour of DNS?

3. IP Multipathing - Etherchannel - Solaris 2.7 - Dual NIC - SIngle IP

4. POVRAY 3.0 Install -- X-povray wont run, at all

5. via-rhine.c to support new VIA's nic chip VT6105, V6105M (correct).

6. Installing 2.5.1 on an Ultra5?

7. 2 NICs: Can't set correct routing

8. PPP connect - pppd: bad local IP address 127.0.0.1

9. Newbie: How do I change NIC from a static IP to recieve a DHCP IP

10. via-rhine.c to support new VIA's nic chip VT 6105, V6105M(corrected)

11. IP aliasing? (many IP's, one NIC)

12. Correct way to control alias of a NIC interface from application running as non-root

13. via-rhine.c to support new VIA's nic chip VT6 105, V6105M (correct).