New User

vlok stone vlokstone at yahoo.com
Sun Jun 29 16:24:21 EDT 2003


Terayon tj210 cable  modem connected thru usb. all
these modem also have an eth port
it's recommend to get a NIC install it and use that.
but try the steps given.
I don't know if there are any permissions needed for
usb devices. Anyone out there know? 

--- vlok stone <vlokstone at yahoo.com> wrote:
> I see iptables are still running. 
> Did you try shutting them down?
> #/sbin/service iptables stop 
> Generally, even in windows ( I worked for adelphia) 
> they recommend not using usb. It does work BUT..
> Hardware is always prefered over software .
> It seems that the driver for CDC usb works 'cause
> you're able to ping etc..
> in your /etc/modules.conf the CDC is the alias 
> for your kernel to load the usb drivers.
> Usually most browsers by defalult have a direct 
> connecton set. 
> I think it's your firewall that's causing the
> problem
> you could also try this
> telnet www.yahoo.com 80
> that tells telnet to connect on port 80 (web)
> [ivlok at GOLEM ivlok]$ telnet www.yahoo.com 80
> Trying 216.109.125.77...
> Connected to w4.www.dcn.yahoo.com (216.109.125.77).
> Escape character is '^]'.
>  Trying 216.109.125.77...
> Connected to w4.www.dcn.yahoo.com (216.109.125.77).
> 
> is what you should see. just press enter to
> disconnect
> if not your firewall is blocking port 80
> hope this helps
> 
> 
> 
> 
> --- Joe Isom <jsi at adelphia.net> wrote:
> > My ethernet is obviously working to some degree
> > because this system is
> > what I am using to comunnicate with NFLUG.  But,
> as
> > I mentioned earlier,
> > something's not quite right as evidenced by my
> > inability to get rid of
> > these various error and warning messages, and by
> the
> > response I get when
> > I type dmesg at the root.  Nonetheless, here's
> what
> > I get when I run
> > ifconfig:
> > 
> > [root at localhostlocaldomain root]# ifconfig
> > eth0      Link encap:Ethernet  HWaddr
> > 00:E0:6F:05:xx:xx
> >           inet addr:24.51.30.xxx 
> > Bcast:255.255.255.255 
> > Mask:255.255.254.0
> >           UP BROADCAST RUNNING MULTICAST  MTU:1500
> 
> > Metric:1
> >           RX packets:343070 errors:0 dropped:0
> > overruns:0 frame:0
> >           TX packets:26572 errors:6832728
> dropped:0
> > overruns:6832728
> > carrier:6832728
> >           collisions:0 txqueuelen:100
> >           RX bytes:30989795 (29.5 Mb)  TX
> > bytes:2158264 (2.0 Mb)
> > 
> > lo        Link encap:Local Loopback
> >           inet addr:127.0.0.1  Mask:255.0.0.0
> >           UP LOOPBACK RUNNING  MTU:16436  Metric:1
> >           RX packets:414210 errors:0 dropped:0
> > overruns:0 frame:0
> >           TX packets:414210 errors:0 dropped:0
> > overruns:0 carrier:0
> >           collisions:0 txqueuelen:0
> >           RX bytes:28263360 (26.9 Mb)  TX
> > bytes:28263360 (26.9 Mb)
> > 
> > [root at localhostlocaldomain root]#
> > 
> > Also, here's what I get when I run route at the
> > root:
> > 
> > [root at localhostlocaldomain root]# route
> > Kernel IP routing table
> > Destination  Gateway       Genmask        Flags
> > Metric Ref    Use  Iface
> > 24.51.30.0   *             255.255.254.0  U     0 
>  
> >   0        0  eth0
> > 169.254.0.0  *             255.255.0.0    U     0 
>  
> >   0        0  eth0
> > 127.0.0.0    *             255.0.0.0      U     0 
>  
> >   0        0  lo
> > default      ny-amherst7a-ga 0.0.0.0      UG    0 
>  
> >   0        0  eth0
> > 
> > I keep thinking there is some setting in my
> browser
> > security that is
> > causing this because of the way I can go to a site
> > whose link is
> > presented to me in an EMAIL.  But if I try
> manually
> > typing in a domain
> > name in the search field at the top, using the
> full
> > address, i.e.,
> > http://www.ebay.com/
> > I'll get, "Connect refused when contacting
> > www.ebay.com" or "Connection
> > timed out . . . "
> > 
> > Joe
> > 
> > On Sun, 2003-06-29 at 00:06, John Seth wrote: 
> > > as root, run "ifconfig".  You should see all
> > available network
> > > interfaces. 127.0.0.1, Ethernet (Eth0, Eth1,
> > and/or any others) as well
> > > as any PPP interfaces. If all you see is a
> > reference to 127.0.0.1, then
> > > only localhost (or localhost.localdomain) is
> > active.  Also Look for "UP"
> > > on the interface under the line that starts with
> > "inet addr". If any
> > > says "DOWN" then the IP is not active on that
> > device/interface.
> > > 
> > > I'm not sure if this will do you any good.  But
> at
> > least it'll let you
> > > know if your ethernet is up and running and with
> > an actual IP or not. 
> > > Without it, no matter what you type, you won't
> get
> > out.
> > > 
> > > Example of my system:
> > > 
> > > eth0      Link encap:Ethernet  HWaddr
> > 00:04:5A:74:4D:55
> > >           inet addr:192.168.1.61 
> > Bcast:192.168.1.255  Mask:255.255.255.0
> > >           UP BROADCAST RUNNING MULTICAST 
> MTU:1500
> >  Metric:1
> > >           RX packets:7154 errors:0 dropped:0
> > overruns:0 frame:0
> > >           TX packets:0 errors:5724 dropped:0
> > overruns:0 carrier:11448
> > >           collisions:0 txqueuelen:100
> > >           RX bytes:656372 (640.9 Kb)  TX bytes:0
> > (0.0 b)
> > >           Interrupt:10 Base address:0xe800
> > > 
> > > eth1      Link encap:Ethernet  HWaddr
> > 00:A0:CC:28:50:76
> > >           inet addr:2x.2x.2x.2x 
> Bcast:2x.2x.2x.2x
> >  ask:255.255.255.128
> > >           UP BROADCAST RUNNING MULTICAST 
> MTU:1500
> >  Metric:1
> > >           RX packets:147846 errors:1 dropped:0
> > overruns:0 frame:0
> > >           TX packets:112206 errors:951 dropped:0
> > overruns:4 carrier:947
> > >           collisions:90 txqueuelen:100
> > >           RX bytes:22583161 (21.5 Mb)  TX
> > bytes:90833983 (86.6 Mb)
> > >           Interrupt:12 Base address:0xec00
> > > 
> > > lo        Link encap:Local Loopback
> > >           inet addr:127.0.0.1  Mask:255.0.0.0
> > >           UP LOOPBACK RUNNING  MTU:16436 
> Metric:1
> > >           RX packets:18237 errors:0 dropped:0
> > overruns:0 frame:0
> > >           TX packets:18237 errors:0 dropped:0
> > overruns:0 carrier:0
> > >           collisions:0 txqueuelen:0
> > >           RX bytes:2269375 (2.1 Mb)  TX
> > bytes:2269375 (2.1 Mb)
> > > 
> > > Another idea, make sure "named" is not running.
> An
> > inability to resolve
> > > hostnames, comes from bad DNS servers being
> listed
> > in /etc/resolv.conf
> > > or named (BIND) running with an invalid
> > configuration, as well as a lack
> > > of a connection to the internet.
> > > 
> > > I understand you may have a few issues, so my
> > suggestions are for dns
> > > resolution at this point.  First, verify you
> have
> 
=== message truncated ===


=====
Free Good
Fire Bad

__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com



More information about the nflug mailing list