hm, strange...how many IPv6 adresses are assigned at your ethX? One or two?
I'll investigate this this evening/tomorrow if auto configuration makes a difference...
hm, strange...how many IPv6 adresses are assigned at your ethX? One or two?
I'll investigate this this evening/tomorrow if auto configuration makes a difference...
Hey,
jep, sometimes it is...
Well, on all the windows and other linux hosts, its working nicely with the current configuration. As I run out of options I did a check with a Ubuntu VM today with a simple ssh server and it worked out of the box. So I guess the FB config should be fine, since router-advertisement is also enabled and my other linux machines are completely self-configuring without any manual intervention. The static gateway I configured preliminary to get my other stuff working is a fe80:: right now, and the FB keeps a static postfix unless you explicitly change it manually.
Now, all options are correctly taken vom DHCPv6 in OMV, therefor I still suspect some sort of configuration error, since the default route in v6 is normally provided via router-advertisement. Seems like you have to enable this explicitly and I'm not sure if the current OMV ifconfig does so properly. I found this: https://bugs.launchpad.net/ubu…rce/ifupdown/+bug/1013597
Could it be that the fritzbox is not advertising in regular intervals, and the advertisements to the kernels initial solicitations are ignored?
Maybe some Mod/Dev can comment on the issue? Could the launchpad "bug" apply here?
not quite sure, but shouldn't there be an IPv6 gateway somewhere:
root@StoneStation:~# ping6 -I eth1 www.google.com
connect: Network is unreachable
root@StoneStation:~# netstat -r
Kernel-IP-Routentabelle
Ziel Router Genmask Flags MSS Fenster irtt Iface
default fritz.box 0.0.0.0 UG 0 0 0 eth1
192.168.2.0 * 255.255.255.0 U 0 0 0 eth1
root@StoneStation:~# ip -6 route
2001:a60:1664:1901::/64 dev eth1 proto kernel metric 256
fe80::/64 dev eth1 proto kernel metric 256
root@StoneStation:~# route -A inet6
Kernel-IPv6-Routentabelle
Destination Next Hop Flag Met Ref Use If
2001:a60:1664:1901::/64 :: U 256 0 0 eth1
fe80::a96:d7ff:fe12:3941/128 :: U 1024 0 0 eth1
fe80::/64 :: U 256 0 0 eth1
::/0 :: !n -1 1 4408 lo
::1/128 :: Un 0 1 14 lo
2001:a60:1664:1901:feaa:14ff:fe21:81c5/128 :: Un 0 1 8268 lo
fe80::feaa:14ff:fe21:81c5/128 :: Un 0 1 567 lo
ff00::/8 :: U 256 0 0 eth1
::/0 :: !n -1 1 4408 lo
Display More
Edit: Got it working by manually defining a default route for the IPv6 (seems like this is not properly advertised by dhcp?) with
.
But this won't survive a reboot...any way to make this the config static in such a way that it also survives updates and OMV config changes through the gui??
Jep, I'm aware of that and only using IPv6 for connecting...with my router (fritzbox) however you have to enable the ports in the firewall for IPv6, which I have done properly (it's been working with the old xpenology setup) and there are at least some packets that seem to make it through to omv as in the tcpdump above, but I guess somethings blocking and I just cant figure out whats going on...
Once this is done I'm going to make a pydio-install & setup guide based on the websites and mysql plugin from extras (since it was super easy to install, instance is already running but only internal access since this issue is not resolved, however there's no up-to-date guide or how to) for the forum which pretty much obsoletes a plugin for the future. I'm willing to return something for a little help
Please
tracing the problem down (I'm quite a novice in linux...):
looks to me like tcpdump reveals that the port forwarding is working, so it's not a NAT/FW issue from the router since something from the outside world is arriving:
tcpdump -i eth1 | grep ssh
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth1, link-type EN10MB (Ethernet), capture size 65535 bytes
22:05:36.826243 IP6 OMVMACHINE.ssh > MYLOCALCOMPUTERONWIN8 : Flags [P.], seq 589061796:589062004, ack 1340497466, win 309, length 208
22:05:36.826407 IP6 MYLOCALCOMPUTERONWIN8 > OMVMACHINE.ssh: Flags [.], ack 208, win 252, length 0
22:05:42.944571 IP6 AREMOTEIPV6IHAVEACCESSTO > OMVMACHINE.ssh: Flags [S], seq 4011206678, win 8192, options [mss 1432,nop,wscale 8,nop,nop,sackOK], length 0
70 packets received by filter
13 packets dropped by kernel
What next? Seems like something is blocking...but I can't really figure out what and how to configure this correctly.
What now?
Hi folks,
first of all thanks for all the effort with the forum and omv, great work!
I've been using synology for quite a while and went xpenology with a custom build that I've been updating with new hardware from time to time. I switched to omv for numerous reasons the last days, and its working nicely so far , except:
Local connections are fine, but I can't get access from WAN. I'm on a IPv6 + DS-Lite, but thats usually not the issue. Port forwarding seems ok, I'm currently only testing with port SSH, since i will only use ssh tunnels later on for security reasons and maybe a pydio instance directly available for convenience. When I test the ports with a online port scanner, the result is a access denied on other ports than 22 (I guess my fritzbox sends ICMP replies) and a timeout on port 22.
Am I missing something? The network/firewall/hosts config is stock right now, so could something be blocking?? I'm still no expert on the shell, so could someone help me out on this? Local IPv6/IPv4 access is working, both work with ssh/gui/samba/etc...
Edit (some infos):
================================================================================
= Network interfaces
================================================================================
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
link/ether fc:aa:14:21:81:c7 brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether fc:aa:14:21:81:c5 brd ff:ff:ff:ff:ff:ff
inet 192.168.2.3/24 brd 192.168.2.255 scope global eth1
inet6 2001:a60:16fd:7301:feaa:14ff:fe21:81c5/64 scope global
valid_lft forever preferred_lft forever
inet6 2001:a60:16be:f401:feaa:14ff:fe21:81c5/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::feaa:14ff:fe21:81c5/64 scope link
valid_lft forever preferred_lft forever
--------------------------------------------------------------------------------
Interface information eth0:
===========================
Settings for eth0:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supported pause frame use: No
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Speed: Unknown!
Duplex: Unknown! (255)
Port: Twisted Pair
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
MDI-X: Unknown
Supports Wake-on: pg
Wake-on: pg
Current message level: 0x00000000 (0)
Link detected: no
--------------------------------------------------------------------------------
Driver information eth0:
========================
driver: alx
version:
firmware-version: alx
bus-info: 0000:02:00.0
supports-statistics: no
supports-test: no
supports-eeprom-access: no
supports-register-dump: yes
supports-priv-flags: no
--------------------------------------------------------------------------------
Interface information eth1:
===========================
Settings for eth1:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supported pause frame use: No
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Speed: 1000Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 2
Transceiver: internal
Auto-negotiation: on
MDI-X: on
Supports Wake-on: pumbg
Wake-on: g
Current message level: 0x00000007 (7)
drv probe link
Link detected: yes
--------------------------------------------------------------------------------
Driver information eth1:
========================
driver: e1000e
version: 2.3.2-k
firmware-version: 0.13-4
bus-info: 0000:00:19.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: no
================================================================================
= IP packet filter
================================================================================
IPv4:
=====
Chain INPUT (policy ACCEPT)
target prot opt source destination
ACCEPT all -- anywhere anywhere
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
ACCEPT all -- anywhere anywhere
--------------------------------------------------------------------------------
IPv6:
=====
Chain INPUT (policy ACCEPT)
target prot opt source destination
ACCEPT all anywhere anywhere
ACCEPT all anywhere anywhere
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
ACCEPT all anywhere anywhere
tcp6 0 0 :::22 :::* LISTEN 2821/sshd
So long,
Stoney