This is a discussion on What IP address do I have within the Linux Networking forums, part of the Linux Forums category; Hi All, I have installed Suse 10,1. I am using a wireless internet service from AT&T. Everything ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
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 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 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. 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. Again, I am running Suse 10.1. What can I do to allow my colleague to see my web server? TIA. |
|
|||
|
NiteRider <d0mufasa@googlemail.com> wrote:
>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 >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 > 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. > >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. > >Again, I am running Suse 10.1. What can I do to allow my colleague to >see my web server? > >TIA. It appears that you are connected through a router. So, in this case you have to connect to the routers configuration page and configure port forwarding from the WAN port 80 to port 80 on your LAN (Ububtu) computer. A couple of "gotchas" here: 1) Make sure that your Ubunto LAN IP doesn't change on each re-boot. What I do is put the "Ubunto" computers MAC address in the routers DHCP config so that it gets the same IP address every time. 2) Make sure that the Ubuntu firewall configuration doesn't block port 80 (or whichever port # you decide to use) on the LAN IP address. You may also want to look into a dynamic IP host name (such as dyndns.org) so that you don't have to keep looking up your WAN IP address. Good luck! (I have reduced the number of groups, my host didn't like the original number.) -- ------------------------------------------------ http://www3.sympatico.ca/dmitton SPAM Reduction: Remove "x." from my domain. ------------------------------------------------ |
|
|||
|
On Sep 16, 7:27 pm, NiteRider <d0muf...@googlemail.com> wrote:
> 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 > 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 > 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. > > 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. > > Again, I am running Suse 10.1. What can I do to allow my colleague to > see my web server? > > TIA. Hi, if you perform on a terminal "iptables -L" what is the output? Obviously there is an appropriate entry missing. Regards. T. Kontogiannis |
|
|||
|
NiteRider wrote:
> 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 > 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 > 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. > > 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. > > Again, I am running Suse 10.1. What can I do to allow my colleague to > see my web server? > > TIA. > 192.168.1.67 is a "private" IP address. Between you and the internet there is a firewall that translates IP addresses on the way. If you want your web server to be visible from outside your private network, then you must configure your firewall to forward port 8080 to your machine (192.168.1.67). You web server will then respond to, say, http://76.240.78.202:8080/ Robert |
|
|||
|
On Sun, 16 Sep 2007 09:27:01 -0700, NiteRider wrote:
> 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 > 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 > 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. That would be the address of your modem/router. You'll need to set up port forwarding to forward requests for the appropriate port to your particular local machine. You may get more help from comp.os.linux.networking. > > 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. > > Again, I am running Suse 10.1. What can I do to allow my colleague to > see my web server? > > TIA. |
|
|||
|
On Sep 16, 11:56 am, tko...@gmail.com wrote:
> Hi, > > if you perform on a terminal "iptables -L" what is the output? > Obviously there is an appropriate entry missing. > > Regards. > T. Kontogiannis Here is the output from "iptables -L" INext-DROP-DEFLT ' DROP all -- anywhere anywhere PKTTYPE = multicast LOG tcp -- anywhere anywhere limit: avg 3/min burst 5 tcp flags:FIN,SYN,RST,ACK/SYN LOG level warning tcp- options ip-options prefix `SFW2-INext-DROP-DEFLT ' LOG icmp -- anywhere anywhere limit: avg 3/min burst 5 LOG level warning tcp-options ip-options prefix `SFW2-INext-DROP-DEFLT ' LOG udp -- anywhere anywhere limit: avg 3/min burst 5 LOG level warning tcp-options ip-options prefix `SFW2-INext-DROP-DEFLT ' LOG all -- anywhere anywhere limit: avg 3/min burst 5 state INVALID LOG level warning tcp-options ip- options prefix `SFW2-INext-DROP-DEFLT-INV ' DROP all -- anywhere anywhere Chain reject_func (1 references) target prot opt source destination REJECT tcp -- anywhere anywhere reject- with tcp-reset REJECT udp -- anywhere anywhere reject- with icmp-port-unreachable REJECT all -- anywhere anywhere reject- with icmp-proto-unreachable Cheers, NR |
|
|||
|
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, 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? TIA, KR |
|
|||
|
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....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 |
|
|||
|
NiteRider wrote:
> 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 > 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 > 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. > > 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. > > Again, I am running Suse 10.1. What can I do to allow my colleague to > see my web server? In FC since it was Redhat there has been a user usable program ip in /sbin It will tell you more than you want to know. -- Hodie decimo quinto Kalendas Novembres MMVII est -- The Ferric Webceasar nizkor http://www.giwersworld.org/nizkook/nizkook.phtml http://www.giwersworld.org |
![]() |
| Thread Tools | |
| Display Modes | |
|
|