Article

XOHM modem port forwarding

image I just got a new office in downtown Baltimore and I needed to get my own internet.  I was debating between Verizon DSL or Comcast. I like comcast speed, but not the price. Since I use skype for my office phone I didn’t need anything else but a broadband connection. So I figured why not try XOHM (soon to be Clearwire) which by the way Baltimore is one of the first cities to have coverage. What attracted me was the price, speed and no contract. They have a special right now for $25 a month for six months and then it’s $10 dollars more after that. Setting it up was a breeze. I was online in about 10 minutes. I had a little problem with the signal at start. My office is in a building surrounded with brick walls so I had to move the modem closer to a window. Download speed is around 2mbps and upload is around 0.4mbps. Not as fast as other people have reported (6 down, 2up.) Being a tech guy I wanted to modify the settings on the modem right away so I go to 192.168.100.1 and try all default usernames and passwords that other routers use, but it didn’t work. So I called XOHM support and they gave me a 6 digit random number for my password and username admin. After I got in I wanted to forward few ports, like the port 80 to my linux box. I don’t know why but that never worked. I thought it had to do with remote management of the router which is also set on port 80 so I switched it to 8080 but still no luck. I was surprised to find out that there are some other ports open by default like ftp, telnet and another one. So my only issue with XOHM is the port forwarding, so far. Maybe I am missing something. I will post an update when I figure it out.

4 Comments

  • You can’t forward port 80 on XOHM – was told that by 2 extremely nice and knowledgeable tech support guys tonight.

    What might be tripping you up is double-NAT if you have the XOHM modem plugged into a router.

    I was trying to do very similar things but could not get into my local network, only a single box connected directly to the XOHM modem set up as the DMZ, which quite frankly, I didn’t like.

    So the XOHM modem provides NAT/DHCP to your router, then your router is doing the same thing for your LAN – no inbound traffic is going to hit your LAN in this config. Basically I told the XOHM techs that all I wanted to do was either a) turn off NAT/DHCP on the XOHM modem and pass the external IP to the router, or b) have the XOHM modem provide NAT/DHCP for my entire LAN, not just the router.

    Long story short – all I had to do was plug the XOHM modem in the 1st LAN port on my router instead of the internet port. This basically lets the XOHM modem provide NAT/DHCP for my entire LAN now, as it overrides the NAT/DHCP on my router.I manually set up the router to have an address at the end of the address block that the XOHM modem was providing so I could administer it (even though it says the router isn’t connected to the internet, the clients are fine).

    Once you get it set up so that the XOHM modem is providing NAT/DHCP for your LAN, then port forwarding should work as expected.

    Hope this helps!

    • Yep, that sucks. it’s not the end of the world for me but it would be nice to be able to do that. I was able to forward port 5900 for vnc.

      I have the same setup with a router. I even tried using a switch to make sure the router was not blocking anything but no luck.

  • You can’t forward port 80 on XOHM – was told that by 2 extremely nice and knowledgeable tech support guys tonight.

    What might be tripping you up is double-NAT if you have the XOHM modem plugged into a router.

    I was trying to do very similar things but could not get into my local network, only a single box connected directly to the XOHM modem set up as the DMZ, which quite frankly, I didn’t like.

    So the XOHM modem provides NAT/DHCP to your router, then your router is doing the same thing for your LAN – no inbound traffic is going to hit your LAN in this config. Basically I told the XOHM techs that all I wanted to do was either a) turn off NAT/DHCP on the XOHM modem and pass the external IP to the router, or b) have the XOHM modem provide NAT/DHCP for my entire LAN, not just the router.

    Long story short – all I had to do was plug the XOHM modem in the 1st LAN port on my router instead of the internet port. This basically lets the XOHM modem provide NAT/DHCP for my entire LAN now, as it overrides the NAT/DHCP on my router.I manually set up the router to have an address at the end of the address block that the XOHM modem was providing so I could administer it (even though it says the router isn’t connected to the internet, the clients are fine).

    Once you get it set up so that the XOHM modem is providing NAT/DHCP for your LAN, then port forwarding should work as expected.

    Hope this helps!

    • Yep, that sucks. it’s not the end of the world for me but it would be nice to be able to do that. I was able to forward port 5900 for vnc.

      I have the same setup with a router. I even tried using a switch to make sure the router was not blocking anything but no luck.

Leave a Comment

Your email address will not be published. Required fields are marked *

Subscribe to our newsletter
GoogleSidebar Office365Sidebar DellSidebar MicrosoftSidebar auth