network problems after new IP

[toukie]

I got a new IP-address from my ISP (ownit.se) after a very curious mistake they made by giving my IP-address to some other person. I changed to the new IP-address in B3 user interface and since then I can't reach anything on my B3. Command-line connection to B3 remains. How can i put the new IP-address to easyfind and how do I get the connection by browser back so that I can see the admin page?

[Gordon]

Exactly what did you change? Because the B3 will take its outside IP (eth0) from DHCP and this does not require you to make any changes. Also: is your B3 directly connected to the internet or behind another (ISP) router?

[toukie]

I changed my IP-address in the admin pages network/WAN settings to the new IP I got from my ISP after that they had given my original IP-address to some other person by a curious mistake. My easyfind name points to my old IP-address. How do I make it point to the new IP-address?

My B3 is connected directly to internet and serves as router server and firewall. I use static IP address settings. My connection works only with those. The "Obtain IP-address automatically (DHCP)"- settings don't work for me.

[Gordon]

Okay, so the issue is that easyfind was not updated. I guess that means that you're not on the latest software? In the older software updates of easyfind are triggered by DHCP client, but you can of course also manually execute the script.

This should do it:

Code: Select all

/usr/lib/web-admin/easyfind.pl

[toukie]

/usr/lib/web-admin/easyfind.pl
gives: Failed to connect to database serverUpdating IP on file.
Wrote config to file
{"msg":"Failed to connect to database server","record":{},"error":"true"}

I can ping and get the new IP-number related to the easyfind-name, but with a browser i get the old one ( I have done ip neigh flush all and dscacheutil -flushcache)

arp gives my old IP-number.

It was my ISP-provider that put me in this mess.

I have bubba.version 2.5.1.2.

[Gordon]

I don't know what that error message means, but if you're on the latest software version I think the straightforward method is to start the easyfind service. AFAIK the only thing you need for easyfind to function is the right name and bubba-key (a unique ID assigned to your box), but new software might store these parameters differently. I suspect you could probably also reset your subscription by disabling easyfind and then re-enable it on the same name.

[toukie]

Trying to disable easyfind by the user interface gives an error: "Following errors where encountered when trying to apply the changes: Easyfind failed with following error: No opcode available in the response. Server responded: Failed to connect to database server"

I don't know the command-line options for handling the same thing.

[Gordon]

My guess is that you have a DNS issue on your B3

[toukie]

That much is clear. I have access to internet but nothing that has to do with Excito works, neither easyfind nor aptitude from command-line, it gives: Could not resolve 'b3.update.excito.org' etc.

Easyfind doesn't get rid of the old IP-number. Aptitude and the rest I have no idea of why they have stopped working.

I got aptitude back by putting two nameservers to /etc/resolv.conf, 127.0.0.1 was not enough or whatever. Still no easyfind.

01:15 I got easyfind back by refreshing it.

( I did the dnsmasq / 127.0.0.1 as your DNS server-thing before. Maybe I made some mistake somewhere. Why didn't it work with only 127.0.0.1 in /etc/resolv.conf?)

[Gordon]

Hard to say. At least this would indicate that something was/is wrong with DNSmasq. It may not have been running, have incorrect forwarders specified in the privatised resolvconf file (did your ISP specify other DNS servers to use with your new IP?) or possibly have had a bind to the old IP address or routing table.

[toukie]

I had only: domain excito, search excito, and nameserver 127.0.0.1 in /etc/resolv.conf from the beginning. With them I got nowhere. When I added two nameservers there everything started working. I don't use DNS servers from my ISP. I had bind to the old number, arp-command showed the old number all the time. I didn't know how to get rid of it. Now it's gone, I installed resolvconf and bind9 with these instructions:

https://www.awxcnx.de/handbuch_21g2.htm

It's up and running.

This is a nice tool for checking out nameservers: https://code.google.com/p/namebench/

[Gordon]

I had only: domain excito, search excito, and nameserver 127.0.0.1 in /etc/resolv.conf

I realize that. The thing is that if you point 127.0.0.1, i.e. localhost, then you must have a DNS server there and to query addresses outside this servers own pool it must have forwarders defined. With DNSmasq that requires specifying an alternate location for resolv.conf (a privatized one) that specifies the DNS servers that DNSmasq can query for unknown addresses. It seems likely that this part, which you now did in Bind, was incorrectly defined.

[toukie]

With bind9 and resolvconf /etc/resolv.conf looks like this:

# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 127.0.0.1

works like a charm as a caching nameserver listening on 127.0.0.1

There is a thing called Unbound which might be better.

[Gordon]

I have that same content in /etc/resolv.conf using DNSmasq

The issue here is that DNSmasq is configured by default to look at that same file (i.e. /etc/resolv.conf) to find addresses that aren't locally defined (what Bind calls "forwarders"). Obviously you cannot have DNSmasq refer to itself to get anything sensible out of this, so to use this particular content in /etc/resolv.conf you need to instruct DNSmasq to use a different file to reference these forwarders.

So your DNS issue may have been caused by either one of these two problems:
1) the "resolv-file=" directive went missing from your DNSmasq configuration
2) the file that the directive from #1 points to is missing or has invalid content