NiteRider <d0mufasa@googlemail.com> writes:

>Hi All,

>Thanks for all the responses :-) I did some search on the net and
>found a thread (the link is listed below) of someone in a similar
>situation: 2Wire gateway, Linux OS,

Ah. Look into the 2Wire manual and set up the router to do bridging or half
bridging. Or tell it to port forward, and make sure it gives your computer
the same address each time.
It is that 2wire modem/router that is assigned that routable address and is
supplying your machine with its address.


>Basically, more information is as follows:

>gandolf:~ # route -n
>Kernel IP routing table
>Destination Gateway Genmask Flags
>Metric Ref Use Iface
>192.168.1.0 0.0.0.0 255.255.255.0 U
>0 0 0 eth0
>127.0.0.0 0.0.0.0 255.0.0.0
>U 0 0 0 lo
>0.0.0.0 192.168.1.254 0.0.0.0 UG
>0 0 0 eth0


>According to the thread below,
>http://groups.google.com/group/comp....f1f16992c5a7f4

>The line:

>0.0.0.0 192.168.1.254 0.0.0.0 UG
>0 0 0 eth0

>Should allow for my colleague to connect to my web server on my Linux
>box but this is not working. Is there something else that needs to be
>done? Is the table correct?

No it should not. That simply says that your default route is through
192.168.1.254 ( which is the router). It says nothing about packets getting
back to you. There is NOTHING you can do on your computer which can get
others to be able to send stuff to you. You MUST go into the router/modem (
use your web browser and go to
192.168.1.254 and you will get the setup pages for the router.)

Then either tell the router to do bridging or to do port forwarding.



>TIA,
>KR