Configuring DHCP on my laptop is not working. I tried the below two approaches.

[1] Configured my laptop for DHCP access using inetmenu. I can ping to the 
modem but net access is not available.
[2] Deconfigured via inetmenu and tried manual configuration (create empty 
files /etc/hostname.rtls0 and /etc/dhcp.rtls0). Reboot. Again same result - 
modem pings, can connect to modem via its http interface for administration but 
cannot connect to the internet.

Also when configured with the inetmenu, the information doesn't seem to be 
persistent. It needs to be configured again on reboots. While manual 
configuration as in [2] is persistent.

The entries for DNS servers of the service provider are in the modem. The 
laptop only needs the IP address(192.168.1.2 for system and 192.168.1.1 for 
modem) and the netmask(FFFFFF00).

Are there any additional steps required?

Output of some of the commands after configuring is given below
$ ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 
index 1
        inet 127.0.0.1 netmask ff000000 
rtls0: flags=201004843<UP,BROADCAST,RUNNING,MULTICAST,DHCP,IPv4,CoS> mtu 1500 
index 2
        inet 192.168.1.2 netmask ffffff00 broadcast 192.168.1.255
        ether 0:a:e4:e4:b5:fe 

$ ifconfig rtls0 dhcp status
Interface  State         Sent  Recv  Declined  Flags
rtls0      BOUND            1     1         0  [PRIMARY] 
(Began, Expires, Renew) = (12/11/2006 21:23, 12/14/2006 21:23, 12/13/2006 10:37)

$ netstat -i
Name  Mtu  Net/Dest      Address        Ipkts  Ierrs Opkts  Oerrs Collis Queue 
lo0   8232 loopback      localhost      222    0     222    0     0      0     
rtls0 1500 arya-rtls0    arya-rtls0     25     0     94     0     0      0     

configuration file used for inetmenu
-------------------------------------------
IPADDR=192.168.1.2

NETMASK=255.255.255.0
START_SCRIPTS=""
STOP_SCRIPTS=""

thanks and regards
gns
 
 
This message posted from opensolaris.org
_______________________________________________
networking-discuss mailing list
[email protected]

Reply via email to