does the default gateway have to have the same network part as the ip of the adapter ?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Assuming I am configuring my network adapter manually,
does the default gateway have to have the same network
part as the ip of the adapter ?

Also, if I have two adapters, and I know the default gareway
of one, can I use it for the other?

Finally, do I need to use the 'route' command for it to work,
or will it be enough to simply assign the correct default
gateway.

And lastly, if I have Internet Connection Sharing (ICS) enabled,
do I need to know anything else when I am doing the above?

Tia.
 
wireless said:
Assuming I am configuring my network adapter manually,
does the default gateway have to have the same network
part as the ip of the adapter ?
Click to expand...

Not necessarily to that adapter. The default gateway
have to be in the same network which is reachable through
one of your computer's interface.
Also, if I have two adapters, and I know the default gareway
of one, can I use it for the other?
Click to expand...

Know the default gateway? You dont have to know the default
gateway, its not a hidden thing. You set the default gateway
to reach machines which are outside your network.
Finally, do I need to use the 'route' command for it to work,
or will it be enough to simply assign the correct default
gateway.
Click to expand...

You dont need the route command for it to work. However you can
set the default gateway using route command as:

route add 0.0.0.0 mask 0.0.0.0 x.x.x.x
And lastly, if I have Internet Connection Sharing (ICS) enabled,
do I need to know anything else when I am doing the above?
Click to expand...

Not sure what you are asking here! If you have ICS enabled, you set
the default gateway in client computer to that of computer with
internet.
See
http://madhur.netfirms.com/cgi-bin/articles.cgi
 
Madhur Ahuja said:
Not necessarily to that adapter. The default gateway
have to be in the same network which is reachable through
one of your computer's interface.


Know the default gateway? You dont have to know the default
gateway, its not a hidden thing. You set the default gateway
to reach machines which are outside your network.


You dont need the route command for it to work. However you can
set the default gateway using route command as:

route add 0.0.0.0 mask 0.0.0.0 x.x.x.x


Not sure what you are asking here! If you have ICS enabled, you set
the default gateway in client computer to that of computer with
internet.
Click to expand...

Hi Madhur,
I am not sure you realise, but I have 2 internal networks, one is
the usual ICS between two Windows 2000 computers, the other
is a bluetooth network, which is between a pocket pc and the
desktop which is not 192.168.0.1. That machine has the following
'ipconfig' configuration:

Ethernet adapter Bluetooth Network:

Connection-specific DNS Suffix . :
Autoconfiguration IP Address. . . : 169.254.235.193
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 192.168.0.121
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1

As you can see, the Bluetooth network has not got a default
gateway, and this is my problem. Do I just stick 192.168.0.1
there, or do I need to do something else, or , perhaps, it can't
be done, I really don't know if and how I can have Internet
access for my pocket pc (Bluetooth network)
See
http://madhur.netfirms.com/cgi-bin/articles.cgi
Tia.
Click to expand...

--
Madhur Ahuja [madhur<underscore>ahuja<at>yahoo<dot>com]

Homepage
http://madhur.netfirms.com
Click to expand...
 
wireless said:
Hi Madhur,
I am not sure you realise, but I have 2 internal networks, one is
the usual ICS between two Windows 2000 computers, the other
is a bluetooth network, which is between a pocket pc and the
desktop which is not 192.168.0.1. That machine has the following
'ipconfig' configuration:

Ethernet adapter Bluetooth Network:

Connection-specific DNS Suffix . :
Autoconfiguration IP Address. . . : 169.254.235.193
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 192.168.0.121
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1

As you can see, the Bluetooth network has not got a default
gateway, and this is my problem. Do I just stick 192.168.0.1
there, or do I need to do something else, or , perhaps, it can't
be done, I really don't know if and how I can have Internet
access for my pocket pc (Bluetooth network)
Click to expand...

I dont have any experience with Bluetooth. Although you can
try putting the default gateway their. Also assign it a static
IP.
If that doesnt work you may use external NAT or proxy solutions
for Internet Sharing.
 
Madhur Ahuja said:
I dont have any experience with Bluetooth. Although you can
try putting the default gateway their. Also assign it a static
IP.
Click to expand...

This is what I am trying to find out, how do I add the default
gateway to the bluetooth adapter. Also, if it is of any help,
just treat the bluetooth subnet as a second subnet, I don't
believe it behaves any differently to ethernet, so basically
what you have is that one of the computers on the ICS
subnet (192.168.0.x) has another subnet, and the task is
to extend the internet access to that subnet. I don't need
an automatic solution, i.e. if I can do it by manually issuing
a 'route' command this would be fine.
If that doesnt work you may use external NAT or proxy solutions
for Internet Sharing.


--
Madhur Ahuja [madhur<underscore>ahuja<at>yahoo<dot>com]

Homepage
http://madhur.netfirms.com
Click to expand...
 
I am not sure you realise, but I have 2 internal networks, one is
the usual ICS between two Windows 2000 computers, the other
is a bluetooth network, which is between a pocket pc and the
desktop which is not 192.168.0.1. That machine has the following
'ipconfig' configuration:

Ethernet adapter Bluetooth Network:

Connection-specific DNS Suffix . :
Autoconfiguration IP Address. . . : 169.254.235.193
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 192.168.0.121
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1

As you can see, the Bluetooth network has not got a default
gateway, and this is my problem. Do I just stick 192.168.0.1
there, or do I need to do something else, or , perhaps, it can't
be done, I really don't know if and how I can have Internet
access for my pocket pc (Bluetooth network)
Click to expand...

The Bluetooth network shows an Automatic Private IP Address (APIPA) (because
it starts with 169...) which usually means you've connected two things
together and have set the interfaces on both to "Obtain an IP address
automatically". In that case, you don't identify a Gateway.

It's not clear what your network configuration is. You also didn't say what
you're trying to accomplish. Here's a wild guess:

Computer #1 has two interfaces: one to the internet and one to the LAN which
only goes to Computer #2. Computer #1 has ICS enabled so Computer #2 can
reach the internet.

Computer #2 has two interfaces: the one mentioned above to Computer #1 and
the Bluetooth interface.

Assuming you want to set up so the Bluetooth device can reach Computer #1
and, therefore/also the internet, you would set up ICS on Computer #2. The
hierarchy would look something like this:

Internet IP address>
(modem / router / dialup....?)
Computer #1 interface #1 gets the internet IP address or a translated
private address from the modem/router - but not usually from a dialup).
Computer #1 ICS bridges interfaces 1 and 2 - providing address translation.
Computer #1 interface #2 with IP address of 192.168.1.1 has no gateway named
... it *is* the intended gateway for the range 192.168.1.xxx.

Computer #2 interface A with IP address of 192.168.1.2 and gateway
192.168.1.1
Computer #2 ICS bridges interfaces A and B - providing address translation.
Computer #2 interface B (to the 3rd device)) with IP address of 10.0.0.1 has
no gateway named .. it *is* the intended gateway for the range 10.0.0.xxx.

A 3rd device with IP address of 10.0.0.2 and gateway of 10.0.0.1 connected
to Computer #2 inteface B.

I like to think of the "gateway" in Yogi Berra-ese "the place to go when you
don't know where to go".

So, if the 3rd device wants to reach 209.206.166.140 - well that address is
clearly not on on the 3rd device's subnet so the request goes to the
gateway - in this case computer #2.
And, since it's not on computer#2's "outside" subnet either, it goes to
computer #1.

If the 3rd device only needs to ever to reach computer #2, then it only
needs to use the IP address of computer #2 and doesn't need a gateway to
forward things further. In that case, it doesn't hurt to name computer #2
as a gateway on the 3rd device

In the hierarchy above:
- the 3rd device uses Computer #2 as a gateway.
- Computer #2 uses Computer #1 as a gateway.

If you don't want to connect the 3rd device to computer #1, then turn off
ICS on Computer #2.
If you do this, you still don't need to have a gateway in computer #2,
interface #2 because presumably all addresses being communicated are on the
same subnet.

If, for some reason, you have to use APIPA on the 3rd device, then it might
look like this:

Computer #2 interface A with IP address of 192.168.1.2 and gateway
192.168.1.1
Computer #2 has no ICS
Computer #2 interface B (to the 3rd device)) with APIPA address of
....whatever ...169.xxx.xxx.xxx

A 3rd device with IP address of 169.xxx.xxx.xxx and no gateway, connected to
Computer #2 inteface B.

If you need the 3rd device to connect to computer #1 via computer #2, then I
don't think you can use APIPA and need to have a gateway identified. I
could be wrong about this - I've not tried it.

Note: If you see an APIPA address on an interface as you do, it could simply
mean that it's not connected to anything - if you have "Obtain an IP address
automatically" enabled.

Fred
 
Fred Marshall said:
<wireless> wrote in message news:[email protected]...

The Bluetooth network shows an Automatic Private IP Address (APIPA) (because
it starts with 169...) which usually means you've connected two things
together and have set the interfaces on both to "Obtain an IP address
automatically". In that case, you don't identify a Gateway.

It's not clear what your network configuration is. You also didn't say what
you're trying to accomplish. Here's a wild guess:

Computer #1 has two interfaces: one to the internet and one to the LAN which
only goes to Computer #2. Computer #1 has ICS enabled so Computer #2 can
reach the internet.

Computer #2 has two interfaces: the one mentioned above to Computer #1 and
the Bluetooth interface.

Assuming you want to set up so the Bluetooth device can reach Computer #1
and, therefore/also the internet, you would set up ICS on Computer #2. The
hierarchy would look something like this:
Click to expand...

No! ICS is setup on computer #1 which is also connected to the internet.

Computer #1 has one internet ip plus 192.168.0.1 which is the ICS subnet

Computer #2 has one ethernet adapter, which is on the ICS subnet, i.e.
192.168.0.x (x>1, but random)
Computer #2 also has a bluetooth adapter with ip 169.254.y.z

Computer #3 has only a bluetooth adapter and ip 169.254.y1.z1

And the problem is that computer #3 cannot access computer #1 hence
cannot access the internet.

??
 
No! ICS is setup on computer #1 which is also connected to the internet.

Computer #1 has one internet ip plus 192.168.0.1 which is the ICS subnet

Computer #2 has one ethernet adapter, which is on the ICS subnet, i.e.
192.168.0.x (x>1, but random)
Computer #2 also has a bluetooth adapter with ip 169.254.y.z

Computer #3 has only a bluetooth adapter and ip 169.254.y1.z1

And the problem is that computer #3 cannot access computer #1 hence
cannot access the internet.
Click to expand...

Then go back and read my last message.
Computer #2 needs ICS to bridge between the interfaces for computer #3 to
get to computer #1.
It may be called "Internet Connection Sharing" but it is really a network
address translating (NAT)router sort of capability.

Fred
 
Back
Top