Re: T43 Networking fix question.

Thanks WIll ..

William L. Hartzell wrote:
Sir:


Can we assume that the LANTRANS.LOG says everything is ok? Try a static route to the router. That would eliminate the DHCP program from the mix. Then try ping.

The LANTRANS.LOG reports everything the same as two other test units in my fixed site boxes, with the exception that the 802 wireless data is in one more line in the T43's report. I shifted the LAN0 operation to fixed addressing. I added a DEFAULT route to the ZyXel router's 192.168.1.1 address with the 'expected' mask of 255.255.255.0. I set the 'expected' metric count to 1. I rebooted.


I can PING the ZyXel router on 192.168.1.1 just fine that way. Netstat -r shows the expected route to the router as well. But then, no matter what combination of HOST or NET route addressing I create in the fixed address tables in the TCP/IP configuration panels, I can never ping anything other than the 192.168.1.1 private address side of the ZyXel router.


I'm wondering about something else I see. No matter what I do about configuring the NIC parameters in the MPTN setup, to me something strange is present. Yes, OS/2 finds and binds the Broadcom NIC. But it ALWAYS identifies it as a 'level 10' speed connection! Shoudn't that be a 'level 100' connection? More interesting. When you go to look at the documents in the supplied Broadcom driver package, in their 'PROTOCOL.INI' sample, they provide for additional 'fields' at the bottom of it in the driver section. Here is what they list:


;[B57_n]
; DriverName = "B57n$"
; BusNum =
; DevNum =
; PortNum =
; FuncNum =
; LineSpeed =
; Duplex =
; NodeAddress =
; FixCheckSumOff


As well, if you look at the 'configuration' for this Broadcom driver in the MPTN configuration operation, you can see that there are 'options' in a pane for setting these 'fields'. If you do not do anything with this, then the Device Driver loads with an automated 'level 10' cable speed selection, the found slot and so on. OK, per the documentation, you can manually set up these 'fields' in the PROTOCOL.INI file. You can then add the 'expected' data into these above fields in the MPTN setup. But no matter what you try, for the as-documented manual 'LineSpeed = 100' and needed 'Duplex = half' parameters, all comes to grief.


During the boot run, when you hit the LAN enablement operations, you'll see the traffic blinker light on the HUB go NUTS with solid rapid flashing where it tries to connect to whatever. If you leave the LAN cable plugged into the T43, you'll eventually see the HUB go RED light jammed for that port. And the only way you can get that back to GREEN and cleared up is to go back to the 'level 10' default found setting and restart.


How am I being approached wrongly by a Level 100 troll here, chuckle? Every other 10/100 NIC I use with this LAN seems to work just fine...


Suggestions?


--


--> Sleep well; OS2's still awake! ;)

Mike Luther
.

Relevant Pages

  • Re: T43 Networking fix question.
    ... Try a static route to the router. ... I can PING the ZyXel router on 192.168.1.1 just fine that way. ... But then, no matter what combination of HOST or NET route addressing I create in the fixed address tables in the TCP/IP configuration panels, I can never ping anything other than the 192.168.1.1 private address side of the ZyXel router. ... When you go to look at the documents in the supplied Broadcom driver package, in their 'PROTOCOL.INI' sample, they provide for additional 'fields' at the bottom of it in the driver section. ...
    (comp.os.os2.misc)
  • Re: Internet isnt accessible after update
    ... > then passes it on to the router. ... > Here is the configuration of the SHARED network connection ... You don't have a DEFAULT route in your routing table. ...
    (Fedora)
  • Re: Bridging interfaces
    ... The handbook section on routing is pretty basic and it seems ... to come down to setting net.inet.ip.forwarding to 1 if you want to route ... both subnets from the router and my routing table looks like: ... your default router and skip the static route configuration all ...
    (freebsd-questions)
  • Re: DHCP and IP routing
    ... > configuration lives in dhclient.conf, so, checking man dhclient.conf: ... This causes another router to be used for the default route. ... a subnet route using the router from the DHCP reply. ...
    (Debian-User)
  • Re: SBS 2003 Misconfigured?
    ... Netgear router because it has 8 ports, utilizes UPNP (at least it did it ONCE ... You mentioned that you assigned the ISP IP to netopia AND the netgear. ... You *can* configure the netopia to operate in bridged mode, but in this configuration, it is literally acting as modem, converting DSL/ATM traffic to ethernet and would not hold a public IP of its own. ... Quickbooks on my server (I know, I shouldn't but I HAVE to because another ...
    (microsoft.public.windows.server.sbs)