NiteRider <d0mufasa@googlemail.com> writes: >Hi All, >I have installed Suse 10,1. I am using a wireless internet service >from AT&T. Everything is working - but - I have made a web server and >I want a colleague of mine to be able to access it. >I do 'ifconfig' and get an IP address and send it to him. He then told >me that the address was for a WAN and not a LAN - oops! (I sent him Other way around. Lan is Local Area Network, while Wan is Wide area network. The numbers 192.168.x.x and 10.x.x.x are unroutable address on the world wide net. Any packet with those as destination are simply thrown away by routers on the internet. Ie, noone except on your local network can use them to communicate with your machine. >192.168.1.67) - see below >eth0 Link encap:Ethernet HWaddr 00:19:21:1F:EF:8C > inet addr:192.168.1.67 Bcast:192.168.1.255 Mask: >255.255.255.0 You probably got this via dhcp from your adsl/cable/... modem > inet6 addr: fe80::219:21ff:fe1f:ef8c/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:181912 errors:0 dropped:0 overruns:0 frame:0 > TX packets:103699 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:155933054 (148.7 Mb) TX bytes:13910295 (13.2 Mb) > Interrupt:177 >Then, I use a website "no-ip.com" to see that the IP address that they >think I am broadcasting from is: 76.240.78.202. Yup that is the address assigned to your router. >Of course, when trying to use it (http://76.240.78.202:8080/), it >stalls. Leaving me to believe that this is some kind of firewall or >proxy address. It is a router/modem which is not designed to pass on packets. You can do one of three things. a) forget coming in from outside. b) set up a vpn between your machine and his machine. c) set up your router to do port forwarding ( where if the router gets a packet for port 80 say it automatically sends it to port80 on your machine-- but this means that your local IP address must be stable-- ie not dhcp, or with the dhcp address tied to your mac address d) set up your router to do bridging so that your computer is also given the address 76.240.78.202 with all packets immediately forwarded to your machine. (And yes that is four points not three). >Again, I am running Suse 10.1. What can I do to allow my colleague to >see my web server? Is your address supplied by a router under your command ( eg from an adsl modem) or is it supplied from some organisation out of your command. In the latter case you are SOL. >TIA.

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.os.linux.networking/browse_thread/thread/5113db9a961d9968/5bf1f16992c5a7f4?lnk=gst&q=forwarding+ip+address+2Wire&rnum=1#5bf1f16992c5a7f4 >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

Andy Ruddock <andy.ruddock@gmail.com> writes: >On Sep 17, 5:48 am, Bill Unruh <un...@physics.ubc.ca> wrote: >> NiteRider <d0muf...@googlemail.com> writes: >> >Hi All, >> >I have installed Suse 10,1. I am using a wireless internet service >> >from AT&T. Everything is working - but - I have made a web server and >> >I want a colleague of mine to be able to access it. >> >I do 'ifconfig' and get an IP address and send it to him. He then told >> >me that the address was for a WAN and not a LAN - oops! (I sent him >> >> Other way around. Lan is Local Area Network, while Wan is Wide area >> network. >> The numbers 192.168.x.x and 10.x.x.x are unroutable address on the world >> wide net. Any packet with those as destination are simply thrown away by >> routers on the internet. Ie, noone except on your local network can use >> them to communicate with your machine. >> >> >192.168.1.67) - see below >> >eth0 Link encap:Ethernet HWaddr 00:19:21:1F:EF:8C >> > inet addr:192.168.1.67 Bcast:192.168.1.255 Mask: >> >255.255.255.0 >> >> You probably got this via dhcp from your adsl/cable/... modem >> >> > inet6 addr: fe80::219:21ff:fe1f:ef8c/64 Scope:Link >> > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >> > RX packets:181912 errors:0 dropped:0 overruns:0 frame:0 >> > TX packets:103699 errors:0 dropped:0 overruns:0 carrier:0 >> > collisions:0 txqueuelen:1000 >> > RX bytes:155933054 (148.7 Mb) TX bytes:13910295 (13.2 Mb) >> > Interrupt:177 >> >Then, I use a website "no-ip.com" to see that the IP address that they >> >think I am broadcasting from is: 76.240.78.202. >> >> Yup that is the address assigned to your router. >> >> >Of course, when trying to use it (http://76.240.78.202:8080/), it >> >stalls. Leaving me to believe that this is some kind of firewall or >> >proxy address. >> >> It is a router/modem which is not designed to pass on packets. You can do >> one of three things. >> a) forget coming in from outside. >> b) set up a vpn between your machine and his machine. >> c) set up your router to do port forwarding ( where if the router gets a >> packet for port 80 say it automatically sends it to port80 on your >> machine-- but this means that your local IP address must be stable-- ie not >> dhcp, or with the dhcp address tied to your mac address >> d) set up your router to do bridging so that your computer is also given >> the address 76.240.78.202 with all packets immediately forwarded to your >> machine. >> >> (And yes that is four points not three). >> >> >Again, I am running Suse 10.1. What can I do to allow my colleague to >> >see my web server? >> >> Is your address supplied by a router under your command ( eg from an adsl >> modem) or is it supplied from some organisation out of your command. In the >> latter case you are SOL. >> >> >TIA. >If the external address is supplied by the ISP he can still use one of >the dynamic-dns services (I use dyndns.org) together with port- >forwarding to make the web-site publicly available. Sure, but first he must use port forwarding, if he can actually get at the router to set that. If the router is out of his control (it sounds like it is not-- it is a 2wire I assume dsl modem/router), then he is SOL. If it is in his control, he may be able ( after negotiating the user manual of the modem) to enable port forwarding. That is the hard part.