Results 1 to 3 of 3

Thread: Incomplete routing in OpenSUSE 13.1 using bridged DSL

  1. #1

    Default Incomplete routing in OpenSUSE 13.1 using bridged DSL

    OK, I think I'm going to need a little help on this one.

    The problems started with I tried to upgrade from 11.3 to a newer version (12.3 at that time) and the upgrade had problems because there was not enough room in my boot partition for both versions of Linux. I was upgrading primarily to add all the newer software packages I wanted to switch to. The upgrade did not go smoothly as there wasn't enough room in the boot partition for both versions and the upgrade process crashed and the computer wouldn't boot. I eventually figured it out, but wiped out my old configuration in the process. I wound up with a new, fresh installation of OpenSUSE 13.1.

    The initial release of 13.1 had problems with the DSL configuration, but an update I installed today seemed to resolve that problem. Initially it would not set up the DSL configuration and I could not run my DSL modem in bridged mode. Now I am able to log in to my modem and connect to the Internet.

    The problem I am having, however, is I cannot get to every web site, only certain ones. I can ping any IP address on the network and do an nslookup on any URL and get the IP address back. I can get to Google and search for anything on google, but I can't bring up any of the web pages it finds. I can get to Home - Welcome to CenturyLink just fine, but not any links on their page.

    Web pages I had open and not closed before switching the DSL to bridged mode still work, hence I am able to post this because I was already logged in to the forum. MS Outlook cannot get new messages from my Earthlink account, but I had the web interface open to my Earthlink account and can still read new messages there. I'm running postfix on my server and can send and receive emails when the modem is in bridged mode but not when the modem is in routed mode.

    The setup is fairly straight forward. eth0 (192.168.0.2) is connected to dsl0, eth1 is the internal network. The default route is through 192.168.0.1, which is the dsl modem. Here is the routing table

    Kernel IP routing table
    Destination Gateway Genmask Flags Metric Ref Use Iface
    default * 0.0.0.0 U 0 0 0 dsl0
    10.1.1.0 * 255.255.255.0 U 0 0 0 eth1
    loopback * 255.0.0.0 U 0 0 0 lo
    link-local * 255.255.0.0 U 0 0 0 eth0
    184.99.0.12 * 255.255.255.255 UH 0 0 0 dsl0
    192.168.0.0 * 255.255.255.0 U 0 0 0 eth0

    I'm not sure where to look next. Is this something with the firewall? Any suggestions?

  2. #2

    Default Re: Incomplete routing in OpenSUSE 13.1 using bridged DSL

    It appears that you have cached a certain amount of DNS entries. But I wonder if you are reflecting the DNS service of your ISP through the firewall to your system.

    Example: I am running a F/W appliance. It expects to be the gateway, DHCP and DNS. So any computer that asks the DHCP server for an address gets back, as an example, 192.168.1.1 gateway, 192.168.1.1. DHCP, 192.168.1.1 DNS, etc.

    So, it sounds like you have a similar problem, except, you have certain things cached so they will resolve. You may need to open a hole in your firewall to allow DNS service. And you would want to make sure that you get the correct DNS server address on your side of the firewall.

    I hope this isn't confusing you.

    Regards,
    Wylbur

  3. #3
    Join Date
    Jun 2008
    Location
    San Diego, Ca, USA
    Posts
    13,295
    Blog Entries
    2

    Default Re: Incomplete routing in OpenSUSE 13.1 using bridged DSL

    Flush your local DNS cache so that any incorrect or stale entries are removed.
    One way is
    Code:
    /etc/init.d/nscd restart
    If that doesn't work, somewhere I've got the two-step command that I've been using since "forever"...

    As wylbur suggests,
    A firewall configuration may be blocking. If it only happens when your modem is in "routing" mode, then you'll need to inspect it. When you installed new, your "new" machine has a different MAC address so things like MAC filtering may need to be re-configured. Any IP address filtering may need to be re-configured. Ports may need to be opened.

    TSU

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •