Beiträge von bibib

  • [GUIDE] Sickbeard+SABnzbd+Couchpotato+Headphones+Others

    As it's not listed on the first page.


    Can I upgrade from v0.4 to v0.5 with this script? What additional steps might I have to do? Would be great if this detail could be added to the first post. Been holding off upgrading as i'm worried about my previous installs (sabnzbd, coachpotato and sickbeard) breaking.
    Thanks

  • [Resolved twice] Lost OMV on my network

    Zitat von "tekkbebe"

    I think old settings from the DHCP server were feeding info to the nic. I don't think the problem was your OMV.


    The DHCP server was swapped (gateway router changed) which had a different subnet. The slave router (switch) didn't have dhcp enabled but probably had a static IP assigned for that MAC address. The slave router was then swapped for another router which didn't fix the problem.


    Anyway, i'm just glad it's working now.

  • [Resolved twice] Lost OMV on my network

    Had server off all night and this morning, both files stated the name server as the gateway router.


    I'll try disconnecting it from the network later, just to be 100% it's sticking. Was it a bug that the nameserver didn't update properly initially?

  • [Resolved twice] Lost OMV on my network

    Zitat von "tekkbebe"

    Got a feeling the resolv.conf file is pulling from this file.


    /etc/resolvconf/run/interfaces/eth0.inet


    Have you rebooted to verify setting will hold?


    Not yet, will do tomorrow (late) . I'll probably just check the file you've mentioned first.

  • [Resolved twice] Lost OMV on my network

    Zitat von "tekkbebe"

    Glad it fixed but you should use fixed ip for a server.


    C-ya


    Yeah I will and I always have. I just made that change whilst trying to get things to work. I don't think that was the problem though, as I had set the IP to be static several times whilst trying to get this to work.


    I was getting fed up of loosing connection to the nasbox and having to re-hookup a monitor.



    Still wondering why the nameserver would remain as that after all the other changes.

  • [Resolved twice] Lost OMV on my network

    Zitat von "tekkbebe"

    should be 192.168.1.1


    Finally!!! Yup that worked. After all of that, it was down to 1 number. As far as I know that setting wasn't exposed through the GUI or changed when I ran firstaid.


    Bet the router would still work now... switch only arrived today.


    Thanks for all your help with this!! You've all been really patient!

  • [Resolved twice] Lost OMV on my network

    And I think we have a winner for what is wrong?
    /etc/resolv.conf

    Code
    search local
nameserver 192.168.0.1


    Not sure what you mean about not being dynamic? I'm obtaining an IP via dhcp. It's not set up statically, as far as I know.

  • [Resolved twice] Lost OMV on my network

    Zitat von "tekkbebe"

    You cannot remove the mac address. Where did you edit?


    I just meant I edited it out of my posts. I've not actually touched it on the nasbox.
    This is the full unedited output. appologies for any confusion. I've been updating my post from 3 posts back with the other details


  • [Resolved twice] Lost OMV on my network

    Zitat von "tekkbebe"

    All this other stuff is nonsense til you get this resolved.


    Code
    eth0      Link encap:Ethernet  HWaddr -----------
          inet addr:192.168.1.111  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:935 errors:0 dropped:0 overruns:0 frame:0
          TX packets:347 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:130927 (127.8 KiB)  TX bytes:75669 (73.8 KiB)
          Interrupt:18


    No mac address and your showing the ip address as the address of your router?


    I removed the MAC address.. dunno why, thought it was for security. My routers IP is 192.168.1.1, my nasbox is 192.168.1.111

  • [Resolved twice] Lost OMV on my network

    Thanks. I removed my mac address, so assume that part was normal.


    Traceroute on Googles DNS, goes nasbox - > gateway router, external IP's and carries on for a while I can also ping my nasbox 192.168.1.111


    nslookup doesn't seem to get anywhere

    Code
    nslookup 8.8.8.8
;; connection timed out; no servers could be reached



    /etc/network/interfaces

    Code
    # The loopback network interface
auto lo
iface lo inet loopback


# eth0 network interface
auto eth0
allow-hotplug eth0
iface eth0 inet dhcp
    pre-down ethtool -s $IFACE wol g


    /etc/hosts

    Code
    127.0.0.1       localhost
127.0.1.1       openmediavault.local    openmediavault


# The following lines are desirable for IPv6 capable hosts
::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters


    And I think we have a winner for what is wrong?
    /etc/resolv.conf

    Code
    search local
nameserver 192.168.0.1

  • [Resolved twice] Lost OMV on my network

    I should probably laugh....... but it's not really funny.


    Switch has arrived. nas box still won't resolve domains.....
    Switch is connected to main router(gateway), nas box is connected to switch. Nas box obtains IP via DHCP. Nasbox doesn't have dns set and obtains everything automatically.


    ifconfig output. Don't really know if/what the loopback is right.


    Would a re-install help at this stage? Or could the EE BrightBox (router) be blocking me in some way? I'm testing the dns resolution by doing traceroutes of domains via telnet on OMV from the nasbox.


  • [Resolved twice] Lost OMV on my network

    Took me a while to find out how to find my share directory....


    Code
    traceroute 192.168.1.1
traceroute to 192.168.1.1 (192.168.1.1), 30 hops max, 60 byte packets
 1  192.168.1.1 (192.168.1.1)  25.493 ms  25.514 ms  25.508 ms


    Code
    traceroute 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
 1  192.168.1.1 (192.168.1.1)  21.576 ms  21.562 ms  21.551 ms
 2  213.1.112.169 (213.1.112.169)  34.442 ms  35.821 ms  37.006 ms


    It then proceeded to come up with loads of different IP's maybe because I tried copying from PUTTY and it re entered what I copied.


    A little test with a domain


    Finally, maybe a silly question but i'm just using lan port to lan port on the routers. There is a wan port on the primary router though but not on the slave.

  • [Resolved twice] Lost OMV on my network

    Thought you might say I needed to install it :D since the domains aren't resolving it can't get the app.


    From Windows cmd I get (same from both 2ndry routers i've tried) Both have dhcp turned off and the dns set to the gateways + googles:
    C:\Users\Thomas>tracert 192.168.1.1

    Code
    Tracing route to BRIGHTBOX [192.168.1.1]
over a maximum of 30 hops:


  1     3 ms     3 ms     3 ms  BRIGHTBOX [192.168.1.1]


Trace complete.


    One thing I don't understand is, if the router and nasbox can't resolve domains. Then why can my desktop, laptop, mobiles etc ?

  • [Resolved twice] Lost OMV on my network

    I'm probably doing this wrong but I get: -bash: traceroute: command not found
    whilst telneting into OMV...


    tried the same cmd through windows just in-case. Also doesn't work there. Assume that I don't know the steps to running these commands as i'm learning a lot still with Linux.

  • [Resolved twice] Lost OMV on my network

    At this point, i'm ready to accept defeat and buy a gigabit switch.... (wanted one anyway) Just not happy about still having to use a potentially usable wifi router in addition to the switch and the cost of doing this. Wasted too much time on this.


    Thanks for your help tekkbebe, you've been very patient! I've learnt loads!


    ---EDIT


    Switch ordered.... I'll put this one down as a learning experience. at least now I know how to turn off my routers leds via cmd line :lol:

  • [Resolved twice] Lost OMV on my network

    Trying out the old 1st router inplace of the 2nd.


    It's a DGN1000. Initial quick setup and I get the same issue. I will play around with this routers settings some more but on the face of it it doesn't look like this is going to work either.


    There is a ping feature from this router and it can't resolve domains.


    Done the usual, setting subnet, gateway, dns etc.

  • [Resolved twice] Lost OMV on my network

    Yup, that's how i've got it setup. At this stage i'm fairly sure I know what the settings I need are. I've been telneting into my 2nd router and making sure it has the right dns entries (1st router + google). + DHCP disabled


    I have noticed that the dhcp lease pool on my 2nd router starts and ends at: 192.168.1.253
    For some reason I can't change this but I don't think this would be an issue since DHCP is disabled.


    Unfortunately the 2nd router isn't support by DD-WRT.


    It's a frustrating problem as my only way of debugging it is by trying to resolve a domain....


    btw my 2nd router specifically is a tg587n v2

  • [Resolved twice] Lost OMV on my network

    Zitat von "tekkbebe"

    I don't even know if the 2nd router can be setup properly. Like I said before a switch, in place of the 2nd router, would be the simplest option.


    The thing is, it has worked before.


    It's the new first router and a change of subnet that has triggered this issue. Yeah a switch would be a lot easier and I might do that. It's just not an ideal solution.