RE: connecting laptop to my desktop

2000-01-11 Thread Ward William E PHDN
esday, January 11, 2000 12:30 AM To: [EMAIL PROTECTED] Cc: recipient.list.not.shown; @nswcphdn.navy.mil Subject: RE: connecting laptop to my desktop I hadn't thought of using traceroute...but I tried it and it failed to give me my IP. It starts the trace at... 10.0.0.1. Crap (I wou

RE: connecting laptop to my desktop

2000-01-11 Thread Patrick O Neil
: recipient.list.not.shown Subject: RE: connecting laptop to my desktop On Mon, 10 Jan 2000, Patrick O Neil wrote: > I hadn't thought of using traceroute...but I tried it and > it failed to give me my IP. It starts the trace at... > 10.0.0.1. Crap (I would like to sometimes know what my > I

Re: connecting laptop to my desktop

2000-01-11 Thread Philippe Moutarlier
I didn't think of this ... he might be lucky the cisco is already masquerading the whole 10.0.0.0/24 network .. Philippe Kelley Lingerfelt <[EMAIL PROTECTED]> writes: > This should tell you your address simple enough. > > Send some mail to [EMAIL PROTECTED] > > It should bounce immedi

RE: connecting laptop to my desktop

2000-01-10 Thread Kelley Lingerfelt
This should tell you your address simple enough. Send some mail to [EMAIL PROTECTED] It should bounce immediately. It should tell you in the first line of the bounced message, where the message originated from, which in your case should be the ip address of the cisco. If you want to see if

RE: connecting laptop to my desktop

2000-01-10 Thread EWU
> To: [EMAIL PROTECTED] > Cc: recipient.list.not.shown > Subject: RE: connecting laptop to my desktop > > > On Mon, 10 Jan 2000, Patrick O Neil wrote: > You should not have any problem to setup your laptop to use any IP address > in your private network address range (as you said, 10

RE: connecting laptop to my desktop

2000-01-10 Thread Hossein S. Zadeh
On Mon, 10 Jan 2000, Patrick O Neil wrote: > I hadn't thought of using traceroute...but I tried it and > it failed to give me my IP. It starts the trace at... > 10.0.0.1. Crap (I would like to sometimes know what my > IP is so I can try to access my system from remote sites). Of course it sta

RE: connecting laptop to my desktop

2000-01-10 Thread Patrick O Neil
EMAIL PROTECTED]] Sent: Monday, January 10, 2000 10:06 PM To: [EMAIL PROTECTED] Cc: recipient.list.not.shown Subject: RE: connecting laptop to my desktop On Mon, 10 Jan 2000, Patrick O Neil wrote: You should not have any problem to setup your laptop to use any IP address in your private network ad

RE: connecting laptop to my desktop

2000-01-10 Thread Patrick O Neil
op). There are enough subtle differences from RH that it is just a little confusing. -Original Message- From: Eric Cifreo [mailto:[EMAIL PROTECTED]] Sent: Monday, January 10, 2000 10:13 PM To: [EMAIL PROTECTED] Cc: recipient.list.not.shown Subject: RE: connecting laptop to my desktop Oh b

Re: connecting laptop to my desktop

2000-01-10 Thread Philippe Moutarlier
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

RE: connecting laptop to my desktop

2000-01-10 Thread Hossein S. Zadeh
On Mon, 10 Jan 2000, Patrick O Neil wrote: > I have a dynamic IP account for my DSL from uswest.net. > Everyone who gets such an account receives a Cisco 675 > router (this may have changed to a later version recently). > Everyone with such an account will have an "internal" This is essentiall

RE: connecting laptop to my desktop

2000-01-10 Thread Eric Cifreo
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 BROA

Re: connecting laptop to my desktop

2000-01-10 Thread Philippe Moutarlier
st pb is to get your second eth card running .. Philippe > -Original Message- > From: Philippe Moutarlier [mailto:[EMAIL PROTECTED]] > Sent: Monday, January 10, 2000 10:23 PM > To: [EMAIL PROTECTED] > Cc: recipient.list.not.shown > Subject: Re: connecting laptop to my de

RE: connecting laptop to my desktop

2000-01-10 Thread Patrick O Neil
m going to have to setup, what, IP aliasing or something? -Original Message- From: Philippe Moutarlier [mailto:[EMAIL PROTECTED]] Sent: Monday, January 10, 2000 10:23 PM To: [EMAIL PROTECTED] Cc: recipient.list.not.shown Subject: Re: connecting laptop to my desktop Patrick O Ne

Re: connecting laptop to my desktop

2000-01-10 Thread Philippe Moutarlier
aybe an alias ?) or it will never work. Philippe > What the outer world sees as my > IP I don't know. > > patrick > > -Original Message- > From: Philippe Moutarlier [mailto:[EMAIL PROTECTED]] > Sent: Monday, January 10, 2000 9:37 PM > To: [EMAIL PROTECTED

RE: connecting laptop to my desktop

2000-01-10 Thread Patrick O Neil
patrick -Original Message- From: Philippe Moutarlier [mailto:[EMAIL PROTECTED]] Sent: Monday, January 10, 2000 9:37 PM To: [EMAIL PROTECTED] Cc: recipient.list.not.shown Subject: Re: connecting laptop to my desktop Well, I am not sure how to set 2 eth devices but I know it is possible. poss

Re: connecting laptop to my desktop

2000-01-10 Thread Philippe Moutarlier
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. Make sure the second card is NOT using dhcp : your server might not like having 2 requests from the same client :=) What you might try : - move away any /e