Re: Changing IP address
Doug Thistlethwaite wrote: > > > IPADDR .103 > NETMASK 255.255.255.240 > NETWORK=.96 > BROADCAST= .111 > GATEWAY= .101 > > on my linux system. The thought was that I could use 4 bits to define > my network (FF.FF.FF.F0) and with the number 101, 102, 103, it would > define the block between .96 and .111 > > Unfortunately, after I changed each system to these settings, the > network still behaved in the same way. > > Can I know the pipeline 50 has filters, DHCP, NAT, and other fancy > features. Unfortunately, I do not have a manual for the device. > Maybe I can help you on that, anyway, since I have a Pipeline 75. You *can* telnet to your router to set it up, right? How does the router know when something is outside his subnet and he needs to dial out? Look at Configure/MyAddr. You'd set that up as 204.178.54.101/29, so now the router knows what his address and subnet is. Also, set Configure/RemAddr to 204.178.54.253/29, and set the appropriate phone number (which I imagine you've already done). I'm actually not sure if you have to do the following if you only have one connection profile, but you should give it a look. Probably the Lan Addrs on the connection profile has already been done automatically, and the Default/Gateway stuff *is* necessary. Look at Ethernet/Connections//IP options/Lan Addrs=x.x.x.x for your connection profile to the ISP. I believe for what you're wanting to do, Lan Addrs should be 204.178.54.253/29, since it's *his* subnet that you'd be dialing out to. Even more importantly, look at Ethernet/Static Rtes/Default/Gateway. Set that value to 204.178.54.253. That makes it so that any IP address the router sees that is outside his subnet needs to go through a gateway of 204.178.54.253, which is in the subnet that you just set up the connection profile for. If you can get this router config stuff straight, you should at least be able to inhibit the unnecessary outgoing calls. If you're still getting outgoing calls, then you probably need to do things like look at the output of tcpdump -ttn to see what addresses are causing the callouts, and getting debug output from named, to see what's making him do stupid lookups (this is where NetBIOS stuff from Win95 comes in). Just as a clue here, make sure your domain name on your Windows machine is set to be the same as your Linux server. A mismatch there often causes stupid DNS lookups. Now on your Linux machine, you'll need 204.178.54.101 (your router address) as the gateway, but I think you already know that. > Thanks for the help, > > Doug > Your welcome. :-)
Re: Changing IP address
Doug Thistlethwaite wrote: > > Dan Willard wrote: > > > You are correct that your ISP is clueless. Going by the numbers that you > > sent, your home network and theirs are one network with the same network > > number and broadcast number. And why your router calls out whenever a > > broadcast packet is sent. > > Dan, Thanks for the information. I was kind of thinking that they had a > problem with > what they gave me. (see below). > > > > > Now, provided that the numbers for your range are correct, your linux box > > is trying to take the broadcast number for your home network. And yes, the > > first number in a range is the network number (even) and the last is the > > broadcast number (odd), your reasoning looks good to me. Gonna take a > > little work to straighten it out. > > You should call your ISP and varify your home network numbers. Yell at > > 'em if they give you a wrong subnet, its a major security hole for both you > > and them. (Unless you are using your office's network, then different rules > > apply). > > Both your win95 and linux boxes need the same subnetmask number. You'll > > need to change you linux box's ip to something other than 103 (100 looks > > good). You should also change your router's subnet to match > > (204.178.54.101/29 if the router doen't like it try /21, some routers drop > > the first 8 bits) and change its network and broadcast numbers. You will > > also probably have to change the route in the router to point to the new > > network. > > I hope I haven't forgoten anything. Now, don't you just love computers > > and networks? > > Humm > > Basically, my ISP gave me three IP addresses (I had to twist his arm as > normally he changes A LOT more for static IP addresses. I have .101, > .102, and .103 on his network with .253 being his system. His > suggestion is to use 255.255.255.0 for the netmask, with .0 for the > network and .255 for the broadcast address. I have asked him a few > question on this issue and I think he is already getting tired of me! :O > > Oh, one more piece of information If I pull the power on my router, my > pc can't connect to the samba on the linux at all! > > I have the feeling that if I push to much, I am going to become a > internet orphan again. In my location, I am having a very hard time > trying to get ISDN service within my local calling area. I am basically > waiting for DSL to arrive later this summer. This said... > > Is there any way for me to use the three IP addresses they assigned to > me? I know the router (pipeline 50) has some fancy features and maybe > they can help. I tried the following this morning after your last > message. > > IPADDR .103 > Can I know the pipeline 50 has filters, DHCP, NAT, and other fancy > features. Unfortunately, I do not have a manual for the device. > This is probably not your real problem, but you can download the Pipeline manuals from www.ascend.com.
RE: Changing IP address
'k you are using a special case :). Normally ISPs like to seperate networks into subnets, guess they think that its too much of a hassle. Pipeline does have a configuration program that makes it easer to play with the router. With only getting three ip addresses you're kinda screwed, and have only two options that I can think of. Option #1 - use the settings that he gave you and live with the router dialing out. Option #2 - drop a second network card in your linux box and use ipmasq for an internal network. Sorry that this has been such a pain. --Dano
Re: Changing IP address
As discussed sounds like that ISP has no ideas about subnetting like all us do :) -Original Message- From: Doug Thistlethwaite <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>; debian-user@lists.debian.org Date: Thursday, 3 June 1999 15:23 Subject: Re: Changing IP address > > >Dan Willard wrote: > >> You are correct that your ISP is clueless. Going by the numbers that you >> sent, your home network and theirs are one network with the same network >> number and broadcast number. And why your router calls out whenever a >> broadcast packet is sent. > >Dan, Thanks for the information. I was kind of thinking that they had a >problem with >what they gave me. (see below). > >> >> Now, provided that the numbers for your range are correct, your linux box >> is trying to take the broadcast number for your home network. And yes, the >> first number in a range is the network number (even) and the last is the >> broadcast number (odd), your reasoning looks good to me. Gonna take a >> little work to straighten it out. >> You should call your ISP and varify your home network numbers. Yell at >> 'em if they give you a wrong subnet, its a major security hole for both you >> and them. (Unless you are using your office's network, then different rules >> apply). >> Both your win95 and linux boxes need the same subnetmask number. You'll >> need to change you linux box's ip to something other than 103 (100 looks >> good). You should also change your router's subnet to match >> (204.178.54.101/29 if the router doen't like it try /21, some routers drop >> the first 8 bits) and change its network and broadcast numbers. You will >> also probably have to change the route in the router to point to the new >> network. >> I hope I haven't forgoten anything. Now, don't you just love computers >> and networks? > >Humm > >Basically, my ISP gave me three IP addresses (I had to twist his arm as >normally he changes A LOT more for static IP addresses. I have .101, >.102, and .103 on his network with .253 being his system. His >suggestion is to use 255.255.255.0 for the netmask, with .0 for the >network and .255 for the broadcast address. I have asked him a few >question on this issue and I think he is already getting tired of me! :O > >Oh, one more piece of information If I pull the power on my router, my >pc can't connect to the samba on the linux at all! > >I have the feeling that if I push to much, I am going to become a >internet orphan again. In my location, I am having a very hard time >trying to get ISDN service within my local calling area. I am basically >waiting for DSL to arrive later this summer. This said... > >Is there any way for me to use the three IP addresses they assigned to >me? I know the router (pipeline 50) has some fancy features and maybe >they can help. I tried the following this morning after your last >message. > >IPADDR .103 >NETMASK 255.255.255.240 >NETWORK=.96 >BROADCAST= .111 >GATEWAY= .101 > >on my linux system. The thought was that I could use 4 bits to define >my network (FF.FF.FF.F0) and with the number 101, 102, 103, it would >define the block between .96 and .111 > >Unfortunately, after I changed each system to these settings, the >network still behaved in the same way. > >Can I know the pipeline 50 has filters, DHCP, NAT, and other fancy >features. Unfortunately, I do not have a manual for the device. > >Thanks for the help, > > >Doug > > >-- >Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null > >
Re: Changing IP address
Dan Willard wrote: > You are correct that your ISP is clueless. Going by the numbers that you > sent, your home network and theirs are one network with the same network > number and broadcast number. And why your router calls out whenever a > broadcast packet is sent. Dan, Thanks for the information. I was kind of thinking that they had a problem with what they gave me. (see below). > > Now, provided that the numbers for your range are correct, your linux box > is trying to take the broadcast number for your home network. And yes, the > first number in a range is the network number (even) and the last is the > broadcast number (odd), your reasoning looks good to me. Gonna take a > little work to straighten it out. > You should call your ISP and varify your home network numbers. Yell at > 'em if they give you a wrong subnet, its a major security hole for both you > and them. (Unless you are using your office's network, then different rules > apply). > Both your win95 and linux boxes need the same subnetmask number. You'll > need to change you linux box's ip to something other than 103 (100 looks > good). You should also change your router's subnet to match > (204.178.54.101/29 if the router doen't like it try /21, some routers drop > the first 8 bits) and change its network and broadcast numbers. You will > also probably have to change the route in the router to point to the new > network. > I hope I haven't forgoten anything. Now, don't you just love computers > and networks? Humm Basically, my ISP gave me three IP addresses (I had to twist his arm as normally he changes A LOT more for static IP addresses. I have .101, .102, and .103 on his network with .253 being his system. His suggestion is to use 255.255.255.0 for the netmask, with .0 for the network and .255 for the broadcast address. I have asked him a few question on this issue and I think he is already getting tired of me! :O Oh, one more piece of information If I pull the power on my router, my pc can't connect to the samba on the linux at all! I have the feeling that if I push to much, I am going to become a internet orphan again. In my location, I am having a very hard time trying to get ISDN service within my local calling area. I am basically waiting for DSL to arrive later this summer. This said... Is there any way for me to use the three IP addresses they assigned to me? I know the router (pipeline 50) has some fancy features and maybe they can help. I tried the following this morning after your last message. IPADDR .103 NETMASK 255.255.255.240 NETWORK=.96 BROADCAST= .111 GATEWAY= .101 on my linux system. The thought was that I could use 4 bits to define my network (FF.FF.FF.F0) and with the number 101, 102, 103, it would define the block between .96 and .111 Unfortunately, after I changed each system to these settings, the network still behaved in the same way. Can I know the pipeline 50 has filters, DHCP, NAT, and other fancy features. Unfortunately, I do not have a manual for the device. Thanks for the help, Doug
RE: Changing IP address
Samba sends out broadcast packets saying what services it has available to the network. If the netmask is set incorrectly the other machines on the network don't get the broadcast and don't see the machine in network neighborhood. Your router is dialing out 'cuse it thinks that the machine is on a different network and is trying to reach it through the net. The only samba setting that needs an ip (I think) is the 'win server'. 255.255.255.248 gives a range of 8 IPs, with six usable IPs (first is network ip, last is broadcast). --Dano > -Original Message- > From: Doug Thistlethwaite [SMTP:[EMAIL PROTECTED] > Sent: Tuesday, June 01, 1999 10:13 AM > To: debian-user@lists.debian.org > Subject: Re: Changing IP address > > Well, > > I have now have the linux system working on my network. I ended up > changing the network > broadcast, and netmask to (XXX.XXX.XXX.0, XXX.XXX.XXX.255, and > 255.255.255.0 > respectively). I do not know why I had to do this as my network mask was > far more > restrictive 255.255.255.248 with my last ISP. I guess I need to do a > little more studying > on what each of these parameters do. > > I do still have a few behavior problems (my network that is :) ! > > 1. My windows 95 system can not see my linux samba server in network > neighborhood (it use > to see it fine). I can type in the link by hand \\linuxsystemid\username > to create the > link. Does anybody know if there is a parameter in samba that relates to > system IP > addresses? > > 2. My router logs into the internet every time my windoze 95 system powers > up and connects > to the samba servers. I think this has to do with the netmask... > > Thanks to everyone who has helped! > > Doug >
Re: Changing IP address
Well,
I have now have the linux system working on my network. I ended up changing
the network
broadcast, and netmask to (XXX.XXX.XXX.0, XXX.XXX.XXX.255, and 255.255.255.0
respectively). I do not know why I had to do this as my network mask was far
more
restrictive 255.255.255.248 with my last ISP. I guess I need to do a little
more studying
on what each of these parameters do.
I do still have a few behavior problems (my network that is :) !
1. My windows 95 system can not see my linux samba server in network
neighborhood (it use
to see it fine). I can type in the link by hand \\linuxsystemid\username to
create the
link. Does anybody know if there is a parameter in samba that relates to
system IP
addresses?
2. My router logs into the internet every time my windoze 95 system powers up
and connects
to the samba servers. I think this has to do with the netmask...
Thanks to everyone who has helped!
Doug
Doug Thistlethwaite wrote:
> I am using a 2.036 kernel I believe.
>
> One thing to note is this system was working perfectly on the network before
> I was
> forced to change my IP addresses. All I want to do is setup the new IP
> addresses in
> the system. I would think the only thing I would need to do is set the
> correct IP and
> netmasks.
>
> Doug
>
> George Bonser wrote:
>
> > On Sun, 30 May 1999, Doug Thistlethwaite wrote:
> >
> > > So far I have had a couple of people help and this is what we have come
> > > up with.
> > >
> > > To change the IP address of a system the following files need to be
> > > modified.
> > >
> > > ifconfig eth0 ${IPADDR} netmask ${NETMASK} broadcast ${BROADCAST}
> > >
> > > executes without any errors.
> > >
> > > route add -net ${NETWORK}
> > >
> > > executes and gives the error SIOCADDR: invalid argument
> >
> > Yeah, if you are using a 2.2.x kernel, comment this line out, the network
> > route is auto-added when you ifconfig the interface.
> >
> > George Bonser
> >
> > Welcome to Wit's End
>
> --
> Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
Re: Changing IP address
I am using a 2.036 kernel I believe.
One thing to note is this system was working perfectly on the network before I
was
forced to change my IP addresses. All I want to do is setup the new IP
addresses in
the system. I would think the only thing I would need to do is set the correct
IP and
netmasks.
Doug
George Bonser wrote:
> On Sun, 30 May 1999, Doug Thistlethwaite wrote:
>
> > So far I have had a couple of people help and this is what we have come up
> > with.
> >
> > To change the IP address of a system the following files need to be
> > modified.
> >
> > ifconfig eth0 ${IPADDR} netmask ${NETMASK} broadcast ${BROADCAST}
> >
> > executes without any errors.
> >
> > route add -net ${NETWORK}
> >
> > executes and gives the error SIOCADDR: invalid argument
>
> Yeah, if you are using a 2.2.x kernel, comment this line out, the network
> route is auto-added when you ifconfig the interface.
>
> George Bonser
>
> Welcome to Wit's End
Re: Changing IP address
Subject: Re: Changing IP address
Date: Sun, May 30, 1999 at 05:35:52PM -
In reply to:Pollywog
Quoting Pollywog([EMAIL PROTECTED]):
>
> On 30-May-99 George Bonser wrote:
> > On Sun, 30 May 1999, Doug Thistlethwaite wrote:
> >
> >> So far I have had a couple of people help and this is what we have come up
> >> with.
> >>
> >> To change the IP address of a system the following files need to be
> >> modified.
> >>
> >> ifconfig eth0 ${IPADDR} netmask ${NETMASK} broadcast ${BROADCAST}
> >>
> >> executes without any errors.
> >>
> >> route add -net ${NETWORK}
> >>
> >> executes and gives the error SIOCADDR: invalid argument
> >
> > Yeah, if you are using a 2.2.x kernel, comment this line out, the network
> > route is auto-added when you ifconfig the interface.
>
> I was having this problem just last night and could not figure out where this
> SIOCADDR error was coming from.
>
> --
> Andrew
>
Then you don't read all the mail, pollywog. This has been given as
the fix at least once or twice a week for the last two months.
Old saying:
People should read twice as much mail as they send.
--
You know you've been spending too much time on the computer when your
friend misdates a check, and you suggest adding a "++" to fix it.
___
Wayne T. Topa <[EMAIL PROTECTED]>
Re: Changing IP address
On 30-May-99 George Bonser wrote:
> On Sun, 30 May 1999, Doug Thistlethwaite wrote:
>
>> So far I have had a couple of people help and this is what we have come up
>> with.
>>
>> To change the IP address of a system the following files need to be
>> modified.
>>
>> ifconfig eth0 ${IPADDR} netmask ${NETMASK} broadcast ${BROADCAST}
>>
>> executes without any errors.
>>
>> route add -net ${NETWORK}
>>
>> executes and gives the error SIOCADDR: invalid argument
>
> Yeah, if you are using a 2.2.x kernel, comment this line out, the network
> route is auto-added when you ifconfig the interface.
I was having this problem just last night and could not figure out where this
SIOCADDR error was coming from.
--
Andrew
Re: Changing IP address
So far I have had a couple of people help and this is what we have come up with.
To change the IP address of a system the following files need to be modified.
/etc/hosts - This was easy to figure out.
/etc/resolv.conf - Just change the DNS servers to the new IP's.
/etc/networks - I am a little confused on this one. My system had a single
line in
this file of:
localnet 204.178.205.224 where the IP address of the linux system was
204.178.205.227
and the pipeline router's IP was 204.178.205.225. How is the number
determined? It
must have been calculated by the install scripts as I do not remember typing it
in.
/etc/init.d/network - Here is where I am having my problems.
I have modified the IPADDR to my new IP address of the linux system.
XXX.XXX.XXX.103
I have left the NETMASK at 255.255.255.248 as it was set before.
I set NETWORK to the IP address of the router minus XXX.XXX.XXX.100 - IS THIS
CORRECT?
I set the BROADCAST to what it was before XXX.XXX.XXX.231 - IS THIS CORRECT?
The GATEWAY is set to XXX.XXX.XXX.101 which is the IP address of my router.
The lines:
ifconfig eth0 ${IPADDR} netmask ${NETMASK} broadcast ${BROADCAST}
executes without any errors.
route add -net ${NETWORK}
executes and gives the error SIOCADDR: invalid argument
The last line also gives an error "SIOCADDR: Network is unreachable" but I
think that
is probably caused by the former error.
Is there anything else we need to change that is not listed above? -or- Does
anyone
have an idea of why this error occurs and what value NETWORK shoud be?
Any ideas on an easier way to get this working? I know during the original
install,
it was much easier to understand and many of these parameters were calculated
by the
script.
Thanks,
Doug
Doug Thistlethwaite wrote:
> Hello,
>
> I just changed my IP and as a result, I now have new IP addresses. How
> do I go about changing the IP address of my machine? I will need to
> change the DNS as well...
>
> Also, I use SAMBA and I can't remember if I had any changes to be done
> there.
>
> If you know what is involved in this, please point me in the right
> direction! :)
>
> Thanks,
>
> Doug
>
> --
> Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
Re: Changing IP address: which config files?
A great many files could possibly be effected. It depends on if you are running DNS, sendmail, samba, etc.. The essential files are /etc/hostname, /etc/hosts, and edit /etc/init.d/network for the ip changes. HTH. -Ian On Thu, 4 Mar 1999, Syrus Nemat-Nasser wrote: > Hi! > > Which files do I neet to edit when changing my hostname and IP address? > My machine had a static IP and a T1 connection, and I need to swap the > address with another. > > Thanks. Syrus. > > -- > > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > Syrus Nemat-Nasser <[EMAIL PROTECTED]>UCSD Physics Dept. > > > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null > __ Ian Setford [EMAIL PROTECTED] PGP = F2 92 50 E3 CD D7 A2 D9 C4 CE 08 A6 98 E0 0F 58
