Thanks !

"SatSpy" <vkwireless@hi.t-com.hr> wrote in news:dmt1do$co2$1@ss405.t-
com.hr:

> Thanks !
>
>
>

Why would you want to? What's the actual problem you're trying to solve?

Netbios, games, etc....

For example , if I create game on 192.168.1.x subnet, I want that game to be
visible in ingame lan browser on the other subnets too ( 192.168.2.x, etc ).
That's the case when game does not have option to connect to IP address
directly ( Battlefield2 for example in offline mode ).

Thanks !


"Andre Kostur" <nntpspam@kostur.net> wrote in message
news:Xns97227E2356FE8nntpspamkosturnet@207.35.177. 134...
> "SatSpy" <vkwireless@hi.t-com.hr> wrote in news:dmt1do$co2$1@ss405.t-
> com.hr:
>
>> Thanks !
>>
>>
>>
>
> Why would you want to? What's the actual problem you're trying to solve?

SatSpy <vkwireless@hi.t-com.hr> wrote:
> Netbios, games, etc....

> For example , if I create game on 192.168.1.x subnet, I want that game to be
> visible in ingame lan browser on the other subnets too ( 192.168.2.x, etc ).
> That's the case when game does not have option to connect to IP address
> directly ( Battlefield2 for example in offline mode ).

Err .. and what stops you bridging those two subnets? Are you saying
that the game does not route? That it does some kind of broadcast?
Well, change the subnet broadcast mask ...

Peter

In message <dmvqfp$46k$1@ss405.t-com.hr>
"SatSpy" <vkwireless@hi.t-com.hr> wrote:

> Netbios, games, etc....
>
> For example , if I create game on 192.168.1.x subnet, I want that game to be
> visible in ingame lan browser on the other subnets too ( 192.168.2.x, etc ).
> That's the case when game does not have option to connect to IP address
> directly ( Battlefield2 for example in offline mode ).

If you have control over the subnets, make them into one.

192.168.1.0 and 192.168.2.0 are only different networks if the subnet mask
is 255.255.0.0.

If you make the mask 255.255.255.0 they become part of one network. The
broadcasts them pass between all systems.

You do have to alter the mask on every connected interface. (Or if you know
exactly what you are doing, it is possible to use different masks in
different places, but debugging problems gets VERY interesting. For example
some routing protocols ca cope, some can't.)

>
> Thanks !
>
>
> "Andre Kostur" <nntpspam@kostur.net> wrote in message
> news:Xns97227E2356FE8nntpspamkosturnet@207.35.177. 134...
> > "SatSpy" <vkwireless@hi.t-com.hr> wrote in news:dmt1do$co2$1@ss405.t-
> > com.hr:
> >
> >> Thanks !
> >>
> >>
> >>
> >
> > Why would you want to? What's the actual problem you're trying to solve?
>
>

--
Alan Adams
alan.adams@orchard-way.freeserve.co.uk
http://www.nckc.org.uk/

Alan Adams <alan.adams@orchard-way.freeserve.co.uk> wrote in
news:e6ac32d44d.Alan.Adams@orchard-way.freeserve.co.uk:

> In message <dmvqfp$46k$1@ss405.t-com.hr>
> "SatSpy" <vkwireless@hi.t-com.hr> wrote:
>
>> Netbios, games, etc....
>>
>> For example , if I create game on 192.168.1.x subnet, I want that
>> game to be visible in ingame lan browser on the other subnets too (
>> 192.168.2.x, etc ). That's the case when game does not have option to
>> connect to IP address directly ( Battlefield2 for example in offline
>> mode ).
>
> If you have control over the subnets, make them into one.
>
> 192.168.1.0 and 192.168.2.0 are only different networks if the subnet
> mask is 255.255.0.0.

Uh, don't you mean 255.255.255.0?

> If you make the mask 255.255.255.0 they become part of one network.
> The broadcasts them pass between all systems.

Er... 255.255.0.0 .... I think you got them reversed...

> You do have to alter the mask on every connected interface. (Or if you
> know exactly what you are doing, it is possible to use different masks
> in different places, but debugging problems gets VERY interesting. For
> example some routing protocols ca cope, some can't.)

Andre Kostur <nntpspam@kostur.net> writes:

>> 192.168.1.0 and 192.168.2.0 are only different networks if the subnet
>> mask is 255.255.0.0.
>
> Uh, don't you mean 255.255.255.0?

I think he did mean 255.255.255.0

>
>> If you make the mask 255.255.255.0 they become part of one network.
>> The broadcasts them pass between all systems.
>
> Er... 255.255.0.0 .... I think you got them reversed...

That would work, but isn't 255.255.252.0 enough to bridge x.x.2.0 and
x.x.1.0?

-- HASM

HASM <not_really@comcast.net> wrote in news:m3hd9oh0px.fsf@127.0.0.1:

> Andre Kostur <nntpspam@kostur.net> writes:
>>> If you make the mask 255.255.255.0 they become part of one network.
>>> The broadcasts them pass between all systems.
>>
>> Er... 255.255.0.0 .... I think you got them reversed...
>
> That would work, but isn't 255.255.252.0 enough to bridge x.x.2.0 and
> x.x.1.0?

Yep... I just didn't want to get into the complexity of CIDR subnet
masks... figured it would be easier to stick to class C vs. class B
addressing.

In message <m3hd9oh0px.fsf@127.0.0.1>
HASM <not_really@comcast.net> wrote:

> Andre Kostur <nntpspam@kostur.net> writes:
>
> >> 192.168.1.0 and 192.168.2.0 are only different networks if the subnet
> >> mask is 255.255.0.0.
> >
> > Uh, don't you mean 255.255.255.0?
>
> I think he did mean 255.255.255.0

So I did.

>
> >
> >> If you make the mask 255.255.255.0 they become part of one network.
> >> The broadcasts them pass between all systems.
> >
> > Er... 255.255.0.0 .... I think you got them reversed...
>
> That would work, but isn't 255.255.252.0 enough to bridge x.x.2.0 and
> x.x.1.0?

It is, for the same reason I got it wrong above.

I can only be sure I've got netmasks right if I write them and the addresses
down in binary, and I didn't take the time.

The requirement is that all the bits of the addresses which are different
must be on the host part of the address, which is where the netmask has
0's. In that case, when all the network bits match, the networks are the
same, i.e. one network.

192 168 1 x
11000000 10110000 00000001 xxxxxxxx

192 168 2 x
11000000 10110000 00000010 xxxxxxxx

255 255 252 0
11111111 11111111 11111100 00000000

This shows that the third byte of 252 is enough. The resulting network has
1022 legal addresses - 192.168.3.255 is the broadcast address, and
192.168.0.0 is the network number, both reserved.

Let's hope I got it right this time!

Alan

--
Alan Adams
alan.adams@orchard-way.freeserve.co.uk
http://www.nckc.org.uk/