Re: Problem connecting to internet through DSL

2007-03-12 Thread sac
   can't ping the dsl router from the bce0 machine, or from
   a lan host behind the bce0 machine?


I have only one machine through with I'm trying to connect to the internet
via the ADSL2 router.


   if the former, what does 'ifconfig bce0' look like, check
   to see if you're getting any ARP replies for the enet addr
   of 192.168.1.1, and perhaps watch tcpdump on bce0 after
   deleting any (incomplete) entries for 192.168.1.1 and
   then trying to ping 192.168.1.1

 This is my ifconfig output:

bce0: flags=8a43UP,BROADCAST,RUNNING,ALLMULTI,SIMPLEX,MULTICAST mtu 1500
lladdr 00:0f:b0:bd:4a:51
groups: egress
media: Ethernet autoselect (100baseTX full-duplex)
status: active
inet 192.168.1.3 netmask 0xff00 broadcast 192.168.1.255
inet6 fe80::20f:b0ff:febd:4a51%bce0 prefixlen 64 scopeid 0x1

And my netstat -rn output:

Internet:
DestinationGatewayFlagsRefs  UseMtu
Interface
default192.168.1.1UGS 00  -   bce0
127/8  127.0.0.1  UGRS00  33224   lo0
127.0.0.1  127.0.0.1  UH  00  33224   lo0
192.168.1/24   link#1 UC  10  -   bce0
192.168.1.1link#1 UHLc10  -   bce0
224/4  127.0.0.1  URS 00  33224   lo0

I followed the instructions in:
http://www.openbsd.com/faq/faq6.html

But somehow I'm not able to ping my gateway.
Is there anything I missed out?

The ADSL information is:
Product: ADSL2+ CPE
Model: beetel 220BX

Regards,
sac.



Re: Problem connecting to internet through DSL

2007-03-12 Thread Kyle George

On Mon, 12 Mar 2007, sac wrote:


I have only one machine through with I'm trying to connect to the internet
via the ADSL2 router.

bce0: flags=8a43UP,BROADCAST,RUNNING,ALLMULTI,SIMPLEX,MULTICAST mtu 1500
   lladdr 00:0f:b0:bd:4a:51
   groups: egress
   media: Ethernet autoselect (100baseTX full-duplex)
   status: active
   inet 192.168.1.3 netmask 0xff00 broadcast 192.168.1.255
   inet6 fe80::20f:b0ff:febd:4a51%bce0 prefixlen 64 scopeid 0x1

I followed the instructions in:
http://www.openbsd.com/faq/faq6.html

But somehow I'm not able to ping my gateway.
Is there anything I missed out?


Are you sure your gateway (dsl modem) is 192.168.1.1?  A lot of dsl modems 
are configured to act as bridges and require PPPoE, etc. running on the 
host (in this case, your OpenBSD machine).


--
Kyle George



Re: Problem connecting to internet through DSL

2007-03-12 Thread sac
 Are you sure your gateway (dsl modem) is 192.168.1.1?  A lot of dsl modems
 are configured to act as bridges and require PPPoE, etc. running on the
 host (in this case, your OpenBSD machine).



I'm pretty sure about the gateway,  right now  I'm  connecting through the
same with Linux.
But somehow this is not working with my OpenBSD4.0 installation.


regards,
sac



Problem connecting to internet through DSL

2007-03-11 Thread sac
Hi,

I'm having a DSL router through which I connect to the internet.
I have my default gateway specified in /etc/mygate,

# cat /etc/mygate
192.168.1.1

I have specified the DNS in /etc/resolv.conf

#cat /etc/resolv.conf
search intra.informedia.in
nameserver 125.22.47.125
nameserver 202.56.250.5
lookup file bind

The interface:

#cat /etc/hostname.bce0
inet 192.168.1.3 255.255.255.0 NONE

The routing tables do not show any problems.
But I'm not able to connect or ping my DSL router. Have I missed out
anything or is there anything else that has to be done?

Thanks,
sac.



Re: Problem connecting to internet through DSL

2007-03-11 Thread jared r r spiegel
On Mon, Mar 12, 2007 at 12:36:22AM +0530, sac wrote:
 
 The interface:
 
 #cat /etc/hostname.bce0
 inet 192.168.1.3 255.255.255.0 NONE
 
 The routing tables do not show any problems.
 But I'm not able to connect or ping my DSL router. Have I missed out
 anything or is there anything else that has to be done?

  can't ping the dsl router from the bce0 machine, or from
  a lan host behind the bce0 machine?

  if the latter, maybe you forgot net.inet.ip.forwarding=1, or
  don't have a nat rule in pf.conf correctly?

  if the former, what does 'ifconfig bce0' look like, check
  to see if you're getting any ARP replies for the enet addr
  of 192.168.1.1, and perhaps watch tcpdump on bce0 after
  deleting any (incomplete) entries for 192.168.1.1 and
  then trying to ping 192.168.1.1

-- 

  jared