View Single Post

   
  #5 (permalink)  
Old 01-16-2008, 10:19 AM
James Carlson
 
Posts: n/a
Default Re: Moving IP address information from bge0 to bge1: Solaris 8

"Raqueeb Hassan" <wideangle@gmail.com> writes:
> > # ifconfig bge1 plumb 10.1.1.2 netmask 255.255.0.0 \
> > broadcast 10.1.255.255 up

[...]
> bge1: flags=1000842<BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 3
> inet 10.1.1.2 netmask ff000000 broadcast 10.255.255.255
> ether x:x:xx:xx:xx:xx


So, now you're using a /8 netmask on that network. What's the *right*
netmask?

Note that this interface isn't marked "up." What exactly do you have
in /etc/hostname.bge1?

It's almost certainly not going to run correctly if the netmask issue
isn't resolved and the interface isn't enabled (marked "up").

> bge2: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500
> index 2
> inet 192.168.100.3 netmask ffffff00 broadcast 192.168.100.255
> ether x:x:xx:xx:xx:xx
>
> Here I configured annex to be connected to bge2. You are right. The
> broadcast seems to be a issue here. How do I change that? What should
> be the value of /etc/netmasks for network 10.1.1.0?


I can't answer that question. This is something that has to come from
*you* or your local network administrator. Netmasks are a property of
the local network configuration. They're not something that can be
deduced from an IP address -- even one that's called a "network."

Plausible masks corresponding to network 10.1.1.0 are /24 through /30,
which correspond to these:

255.255.255.0
255.255.255.128
255.255.255.192
255.255.255.224
255.255.255.240
255.255.255.248
255.255.255.252

> # netstat -nr
>
> Routing Table: IPv4
> Destination Gateway Flags Ref Use Interface
> -------------------- -------------------- ----- ----- ------ ---------
> 192.168.100.0 192.168.100.3 U 1 0 bge2
> 127.0.0.1 127.0.0.1 UH 3 6 lo0
>
> Here is a problem. It doesn't say anything about network 10.1.1.0 and
> how that should be routed. How do I fix that?


It's not there because bge1 has been marked "down" administratively.

Most likely, it's due to a bad entry in /etc/hostname.bge1. Probably,
you have multiple lines in that file rather than a single line.

--
James Carlson, Solaris Networking <james.d.carlson@sun.com>
Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
Reply With Quote