Sorry , I have to correct some things in your answers :=)

First, an explanation: when I answered this, I didn't know there was a (mandatory) 
cisco in the picture. So yes, an interface with external IP is needed ... but it is 
provided by the Cisco router, which I didn't know .

otherwise I must say that ipchains DOES masquerading (this is why I advised it). It 
actually does it pretty well.

Beside this, I aggree with your remarks. 

Philippe

Eric Cifreo <[EMAIL PROTECTED]> writes:

> Oh boy.  Let's make some sense of all this.....
> 
> On Mon, 10 Jan 2000, Patrick O Neil wrote:
> 
> >[patrick@Tempus patrick]$ /sbin/ifconfig
> >eth0          Link encap:Ethernet  HWaddr 00:50:04:6C:DE:AE
> >                  inet addr:10.0.0.2  Bcast:10.0.0.255  Mask:255.255.255.0
> >                  UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500  Metric:1
> >                  RX packets:21185 errors:0 dropped:0 overruns:0 frame:0
> >                  TX packets:21843 errors:0 dropped:0 overruns:0 carrier:0
> >                  collisions:20 txqueuelen:100
> >                  Interrupt:7 Base address:0xe400
> >
> >If I want to connect to my router and alter any settings, I telnet 
> >into it and the address I telnet to is 10.0.0.1 (I can also setup
> >minicom under linux or hyperterminal under windoze to directly 
> >connect to the router for configuring).  If I run ping 10.0.0.2, it
> >is the same as pinging localhost or 127.0.0.1.  If I ping 10.0.0.1
> >I am pinging my router.
> >
> >My thought was to assign something like 10.0.0.3 to my laptop, if
> >that will work.  Otherwise I am going to have to setup, what, 
> >IP aliasing or something?
> 
> OK.  Your Cisco is routing traffic from your working desktop out to the world. 
> Its interface that you can see (10.0.0.1) and your machine (10.0.0.2) are on
> the same Class-C subnet (255.255.255.0).
> 
> You want to network your laptop to your desktop and get out to the net right?
> 
> First thing you must do is get that second network card working.  Can you see
> it during boot-up?  Does 'dmesg | more' show you anything for eth1?
> 
> Have a look at 'cat /proc/pci' and 'cat /proc/interrupts'.  Hopefully both
> cards are visible in some fashion here.  Otherwise we're gonna be up late. ;0)
> 
> Now.  Unless your Cisco has multiple ports, you're going to have to run the
> wire from your laptop to your desktop's second NIC.  And your desktop is
> going to have to be a "router".  This is going to create a separate SUBNET. 
> Like so:
> 
>  Internet
>     |
>     |
>  Cisco
>       [10.0.0.1 (255.255.255.0)]
>     |
>     |
>       [10.0.0.2 (255.255.255.0)]  <-- 1st NIC that works
>  Desktop
>       [192.168.1.1 (255.255.255.0)] <-- 2nd NIC that works (maybe)
>     |
>     |
>     |
>       [192.168.1.2 (255.255.255.0)]
>  Laptop
> 
> 
> >Patrick O Neil <[EMAIL PROTECTED]> writes:
> >
> >> A bit more info... I have my 3c590 driver compiled into
> >> my 2.2.14 kernel but the tulip driver for my netgear
> >> is a module.  My 3com card is eth0 and the netgear would
> >> be/was (I removed the card and rebooted to be able to
> >> reconnect to the net and post) eth1. 
> 
> IRQ conflict maybe?
>  
> >> I have a dynamic IP from uswest on my DSL but my box
> >> is 10.0.0.2 and the DSL router is 10.0.0.1 internally -
> >> to the world, my _router_ has whatever IP uswest assigns.
> >>
> >I guess 10.0.0.1 is the address you assigned to your removed-card ?
> >Not the 3com ?
> 
> Huh?
>  
> >> I do not really know where to start here.  Not that it 
> >> matters but my desktop runs 24/7 - my IP probably remains
> >> the same most of the time though I don't know for sure (I can 
> >> never determine what my DSL router's IP address actually is.  
> >> Everything I've tried to determine it always gives me back
> >> the "internal" network IP of 10.0.0.1 for the router and
> >> 10.0.0.2 for my desktop). 
> >
> >WHAT ????
> 
> Yeah!  in which language are you guys speaking?
> 
> >what does /sbin/ifconfig 
> >says (please report the whole output).
> >You MUST have an interface configured with your external IP (maybe an alias
> >?)
> >or it will never work. 
> 
> Not true.  If his desktop can get out, then his Cisco is smart enough to route
> and masquerade for him.  And he'll have to teach his desktop to do the same for
> his laptop.
> 
> >> 
> >> Well, I am not sure how to set 2 eth devices but I know it is possible.
> >> possibly :
> >> 
> >> alias eth1 ethmodule.o 
> >> 
> >> with the right options there.
> 
> Right-O!  Now make sure your hardware is recognized and you're there....
> 
> 
> >> After that, and if it works, you will have to use "ipchains" 
> >> to masquerade your private ips .
>  
> Um, no.  ipchains does packet filtering, preventing those protocols you specify
> from leaving or entering.  He needs to masquerade first.  Once that's working,
> then he can filter.
>  
> >> If it doesn't work, look at what ifconfig says about IRQS and IOs for both
> >> cards
> 
> Yes, good advice here.  What does it report with both cards in the machine? 
> What does /var/log/messages say when both are present?
> 
> Keep trying.  This will work.
> 
> Eric Cifreo
> Austin. TX
> 
> 
> 
> -- 
> To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
> as the Subject.


-- 
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.

Reply via email to