Darren Ewaniuk
|
Netmask problems for 192.168 network - can't seem to get bigger than
|
Darren Ewaniuk
05/26/2008 4:35 PM
post8443
|
Netmask problems for 192.168 network - can't seem to get bigger than
This is with Qnx 4.25 (Socket 4.25C)
I am trying to assign a 16 bit node address space within the 192.168 network but ifconfig does not seem to allow
anything larger than 8 bits for any network starting with 192.
Using a 192.168.0.1/24 network works fine:
ifconfig en1 192.168.0.1 netmask 255.255.255.0 up
ifconfig en1
returns
en1: flags=8863<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST>
inet 192.168.0.1 netmask ffffff00 broadcast 192.168.0.255
but using 192.168.0.1/16 network forces it back to a /24 network:
ifconfig en1 192.168.0.1 netmask 255.255.0.0 up
ifconfig en1
returns
en1: flags=8863<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST>
inet 192.168.0.1 netmask ffffff00 broadcast 192.168.0.255
However it will allow to subnet to finer than a /24 network
I.E. 192.168.0.1/25
ifconfig en1 192.168.0.1 netmask 255.255.255.128 up
ifconfig en1
returns
en1:
flags=8863<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST>
inet 192.168.0.1 netmask ffffff80 broadcast 192.168.0.127
Using any other network the netmask I ask for is used: (10.1.0.1/16, for example, also works with 193.0.0.1/16)
ifconfig en1 10.1.0.1 netmask 255.255.0.0 up
ifconfig en1
returns
en1:
flags=8863<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST>
inet 10.1.0.0 netmask ffff0000 broadcast 10.255.255.255
This also works for 193.168.0.1/16 which should also technically be a class C network (but is a real address so was
restricted to a private network for testing)
---
So the Qnx 4.25 networking seems to force any 192.X.X.X network to using a 8 bit class C network space even though the
192.X.X.X network is 256 /24 class C networks that should be able to subnet to up to a /16 network.
Is there any work around to use more than 8 bits of node space with the 192.X.X.X network in QNX?
|
|
|
Sean Boudreau(deleted)
|
Re: Netmask problems for 192.168 network - can't seem to get bigger than
|
Sean Boudreau(deleted)
05/26/2008 4:49 PM
post8444
|
Re: Netmask problems for 192.168 network - can't seem to get bigger than
On Mon, May 26, 2008 at 04:35:30PM -0400, Darren Ewaniuk wrote:
> This is with Qnx 4.25 (Socket 4.25C)
>
> I am trying to assign a 16 bit node address space within the 192.168 network but ifconfig does not seem to allow
anything larger than 8 bits for any network starting with 192.
>
> Using a 192.168.0.1/24 network works fine:
> ifconfig en1 192.168.0.1 netmask 255.255.255.0 up
> ifconfig en1
> returns
> en1: flags=8863<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST>
> inet 192.168.0.1 netmask ffffff00 broadcast 192.168.0.255
>
> but using 192.168.0.1/16 network forces it back to a /24 network:
> ifconfig en1 192.168.0.1 netmask 255.255.0.0 up
> ifconfig en1
> returns
> en1: flags=8863<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST>
> inet 192.168.0.1 netmask ffffff00 broadcast 192.168.0.255
>
> However it will allow to subnet to finer than a /24 network
> I.E. 192.168.0.1/25
> ifconfig en1 192.168.0.1 netmask 255.255.255.128 up
> ifconfig en1
> returns
> en1:
> flags=8863<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST>
> inet 192.168.0.1 netmask ffffff80 broadcast 192.168.0.127
>
> Using any other network the netmask I ask for is used: (10.1.0.1/16, for example, also works with 193.0.0.1/16)
> ifconfig en1 10.1.0.1 netmask 255.255.0.0 up
> ifconfig en1
> returns
> en1:
> flags=8863<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST>
> inet 10.1.0.0 netmask ffff0000 broadcast 10.255.255.255
>
> This also works for 193.168.0.1/16 which should also technically be a class C network (but is a real address so was
restricted to a private network for testing)
>
> ---
>
> So the Qnx 4.25 networking seems to force any 192.X.X.X network to using a 8 bit class C network space even though the
192.X.X.X network is 256 /24 class C networks that should be able to subnet to up to a /16 network.
>
> Is there any work around to use more than 8 bits of node space with the 192.X.X.X network in QNX?
>
You can use a later stack. Earlier versions didn't support
'supernetting', only 'subnetting'. I think the Tcpip manager
supported supernetting as opposed to Socket.
-seanb
|
|
|
Dave Brown
|
RE: Netmask problems for 192.168 network - can't seem to get bigg
er than
|
Dave Brown
05/26/2008 4:53 PM
post8445
|
RE: Netmask problems for 192.168 network - can't seem to get bigg
er than
> -----Original Message-----
> From: Sean Boudreau [mailto:seanb@qnx.com]
> Sent: Monday, May 26, 2008 4:49 PM
> To: qnx4-community
> Subject: Re: Netmask problems for 192.168 network - can't seem to get
> bigger than
>
> On Mon, May 26, 2008 at 04:35:30PM -0400, Darren Ewaniuk wrote:
> > This is with Qnx 4.25 (Socket 4.25C)
> >
> > I am trying to assign a 16 bit node address space within the 192.168
> network but ifconfig does not seem to allow anything larger than 8 bits
> for any network starting with 192.
> >
> > Using a 192.168.0.1/24 network works fine:
> > ifconfig en1 192.168.0.1 netmask 255.255.255.0 up
> > ifconfig en1
> > returns
> > en1: flags=8863<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST>
> > inet 192.168.0.1 netmask ffffff00 broadcast 192.168.0.255
> >
> > but using 192.168.0.1/16 network forces it back to a /24 network:
> > ifconfig en1 192.168.0.1 netmask 255.255.0.0 up
> > ifconfig en1
> > returns
> > en1: flags=8863<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST>
> > inet 192.168.0.1 netmask ffffff00 broadcast 192.168.0.255
> >
> > However it will allow to subnet to finer than a /24 network
> > I.E. 192.168.0.1/25
> > ifconfig en1 192.168.0.1 netmask 255.255.255.128 up
> > ifconfig en1
> > returns
> > en1:
> > flags=8863<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST>
> > inet 192.168.0.1 netmask ffffff80 broadcast 192.168.0.127
> >
> > Using any other network the netmask I ask for is used: (10.1.0.1/16, for
> example, also works with 193.0.0.1/16)
> > ifconfig en1 10.1.0.1 netmask 255.255.0.0 up
> > ifconfig en1
> > returns
> > en1:
> > flags=8863<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST>
> > inet 10.1.0.0 netmask ffff0000 broadcast 10.255.255.255
> >
> > This also works for 193.168.0.1/16 which should also technically be a
> class C network (but is a real address so was restricted to a private
> network for testing)
> >
> > ---
> >
> > So the Qnx 4.25 networking seems to force any 192.X.X.X network to using
> a 8 bit class C network space even though the 192.X.X.X network is 256 /24
> class C networks that should be able to subnet to up to a /16 network.
> >
> > Is there any work around to use more than 8 bits of node space with the
> 192.X.X.X network in QNX?
> >
>
> You can use a later stack. Earlier versions didn't support
> 'supernetting', only 'subnetting'. I think the Tcpip manager
> supported supernetting as opposed to Socket.
>
> -seanb
>
'Tcpip' manager is part of TCPRT 5.0. This is a separate package from TCPRT
4.25.
Dave
> _______________________________________________
> QNX4 Community Support
> http://community.qnx.com/sf/go/post8444
|
|
|
|