|
Cant ping Pop or anything
![[ee]](/s/countries/ee.gif) Shadow Hawkins on Monday, 05 July 2010 03:28:59
My IPv6 does not work i have trayd everything.
command i use to get ipv6
ip tunnel add sit1 mode sit local 84.52.10.138 remote 195.222.0.66
ip link set sit1 up
ip link set mtu 1280 dev sit1
ip tunnel change sit1 ttl 64
ip -6 addr add 2001:ad0:900:52::2/64 dev sit1
ip -6 ro add default via 2001:ad0:900:52::1 dev sit1
route -A inet6
Kernel IPv6 routing table
Destination Next Hop Flags Metric Ref Use Iface
2001:ad0:900:52::/64 * U 256 1 0 sit1
fe80::/64 * U 256 0 0 eth0
fe80::/64 * U 256 0 0 eth1
fe80::/64 * U 256 0 0 sit1
*/0 gw-83.tll-01.ee.sixxs.net UG 1024 6068 0 sit1
::1/128 * U 0 26 1 lo
2001:ad0:900:52::/128 * U 0 0 1 lo
cl-83.tll-01.ee.sixxs.net/128 * U 0 0 1 lo
fe80::/128 * U 0 0 1 lo
fe80::/128 * U 0 0 1 lo
fe80::5434:a8a/128 * U 0 0 1 lo
fe80::214:85ff:fe1e:c359/128 * U 0 0 1 lo
fe80::214:d1ff:fe16:4934/128 * U 0 8695 1 lo
ff02::1:ffff:fffe/128 ff02::1:ffff:fffe UC 0 36 0 eth1
ff00::/8 * U 256 0 0 eth0
ff00::/8 * U 256 0 0 eth1
ff00::/8 * U 256 0 0 sit1
Ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:14:85:1E:C3:59
inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::214:85ff:fe1e:c359/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3141031 errors:0 dropped:0 overruns:0 frame:0
TX packets:5244444 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:902954930 (861.1 MiB) TX bytes:458083427 (436.8 MiB)
Interrupt:10
eth1 Link encap:Ethernet HWaddr 00:14:D1:16:49:34
inet addr:172.16.105.239 Bcast:172.16.111.255 Mask:255.255.248.0
inet6 addr: fe80::214:d1ff:fe16:4934/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:44248705 errors:0 dropped:0 overruns:0 frame:0
TX packets:43209206 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3774068493 (3.5 GiB) TX bytes:3670066173 (3.4 GiB)
Interrupt:12 Base address:0x8000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:452989 errors:0 dropped:0 overruns:0 frame:0
TX packets:452989 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:71042255 (67.7 MiB) TX bytes:71042255 (67.7 MiB)
ppp0 Link encap:Point-to-Point Protocol
inet addr:84.52.10.138 P-t-P:212.7.29.236 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1
RX packets:8237206 errors:0 dropped:0 overruns:0 frame:0
TX packets:6805353 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:3
RX bytes:3846271837 (3.5 GiB) TX bytes:1396778336 (1.3 GiB)
sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1280 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:5478 errors:696 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:411226 (401.5 KiB)
sit1 Link encap:IPv6-in-IPv4
inet6 addr: 2001:ad0:900:52::2/64 Scope:Global
inet6 addr: fe80::5434:a8a/128 Scope:Link
UP POINTOPOINT RUNNING NOARP MTU:1280 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:6518 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:507628 (495.7 KiB)
tun0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:10.8.0.1 P-t-P:10.8.0.2 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:15975 errors:0 dropped:0 overruns:0 frame:0
TX packets:28481 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:1094579 (1.0 MiB) TX bytes:39691667 (37.8 MiB)
eth0 = LAN
eth1 = ISP LAN
ppp0 = INTERNET
tun0 = OPENVPN
sit1 = Sixxs
sit0 = ?
Any questions ?
Cant ping Pop or anything
Shadow Hawkins on Monday, 05 July 2010 10:29:25
Sorry seems that my ISP is blocking ipv6 tunnels
Cant ping Pop or anything
Shadow Hawkins on Tuesday, 13 July 2010 18:11:47
Seems that my ISP is NOT blocking ipv6 tunnels in PPPoE tunnel only in LAN.
I Forget to say that my Os is CentOS 5.5 Kernel 2.6.32
Cant ping Pop or anything
![[de]](/s/countries/de.gif) Shadow Hawkins on Monday, 05 July 2010 23:10:22
have you used ping6 instead of ping? that was my mistake *g*
Cant ping Pop or anything
Shadow Hawkins on Thursday, 15 July 2010 17:45:27
not so stupid yet. problem is in pppoe tunnel and some mistake in config but i dont know where.
Cant ping Pop or anything
Shadow Hawkins on Monday, 26 July 2010 17:32:26
somebody some ideas?
Cant ping Pop or anything
Did you check your firewall, tcpdump etc? See the reporting problems list on the contact page for more hints where you should look at.
Cant ping Pop or anything
Shadow Hawkins on Monday, 26 July 2010 18:33:20
what interface i should monitor if i am monitoring. ppp0 sit1 eth1
if i monitor sit1 ( tcpdump -i sit1 icmp6 )
19:29:41.378030 IP6 cl-83.tll-01.ee.sixxs.net > gw-83.tll-01.ee.sixxs.net: ICMP6, echo request, seq 30, length 64
if i monitor ppp0 or any other interface there is no ipv6 activity.
what info you need more ?
Cant ping Pop or anything
How does your IPv4 routing table look like (ip ro sho) and what does "ip ro get 195.222.0.66" result in?
Also, again, check your firewall rules.
Cant ping Pop or anything
Shadow Hawkins on Monday, 26 July 2010 23:16:57
Firewall ipv4 & 6 allow everything!!!
-bash-3.2# ip ro sho
212.7.29.236 dev ppp0 proto kernel scope link src 84.52.10.138
10.8.0.2 dev tun0 proto kernel scope link src 10.8.0.1
10.8.0.0/24 via 10.8.0.2 dev tun0
192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.1
172.16.104.0/21 dev eth1 proto kernel scope link src 172.16.105.239
169.254.0.0/16 dev eth1 scope link
84.0.0.0/8 dev sit0 proto kernel scope link src 84.52.10.138
-bash-3.2# ip ro get 195.222.0.66
195.222.0.66 dev ppp0 src 84.52.10.138
cache mtu 1492 advmss 1452 hoplimit 64
Cant ping Pop or anything
Firewall ipv4 & 6 allow everything!!!
Does that mean there are no rules at all or that you open up the wrong things?
Can you just show them, only way to see what goes wrong.
84.0.0.0/8 dev sit0 proto kernel scope link src 84.52.10.138
What is that doing there? I would think that could break a lot of things, especially as your addresses are in that prefix.
Can you traceroute to the PoP?
Cant ping Pop or anything
Shadow Hawkins on Tuesday, 27 July 2010 01:08:28
i allow ipv6 icmp in and out. yes i can tracert pop and ping ipv4! but ipv6 tunnel does't work that means that i cant ping or tracert ipv6
-bash-3.2# tracert -6 2001:ad0:900:52::1
traceroute to 2001:ad0:900:52::1 (2001:ad0:900:52::1), 30 hops max, 40 byte packets
1 cl-83.tll-01.ee.sixxs.net (2001:ad0:900:52::2) 0.065 ms !H 0.061 ms !H 0.034 ms !H
ipv6 firewall settings
# Generated by ip6tables-save v1.3.5 on Sun Jul 4 17:13:24 2010
*mangle
:PREROUTING ACCEPT [10:719]
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [10:719]
:OUTPUT ACCEPT [0:0]
:POSTROUTING ACCEPT [10:719]
COMMIT
# Completed on Sun Jul 4 17:13:24 2010
# Generated by ip6tables-save v1.3.5 on Sun Jul 4 17:13:24 2010
*filter
:INPUT DROP [0:0]
:FORWARD DROP [10:719]
:OUTPUT DROP [0:0]
-A INPUT -i ppp0 -p ipv6-icmp -j ACCEPT
-A OUTPUT -o ppp0 -p ipv6-icmp -j ACCEPT
-A INPUT -i sit1 -p ipv6-icmp -j ACCEPT
-A OUTPUT -o sit1 -p ipv6-icmp -j ACCEPT
-A INPUT -i lo -p ipv6-icmp -j ACCEPT
-A OUTPUT -o lo -p ipv6-icmp -j ACCEPT
COMMIT
# Completed on Sun Jul 4 17:13:24 2010
Cant ping Pop or anything
Ehmmm you are ONLY allowing ICMP to go outbound? :)
The Internet consists of various nice protocols: IP, TCP, UDP and ICMP.
(And also SCTP, but almost nobody uses that) You might want to allow at least TCP and UDP too.
The better questions though are:
- As you don't have IPv6 on ppp0 why do you allow IPv6 ICMP there?
- Why are you blocking the rest?
Please just FLUSH your firewall rules, as they don't make sense. Also don't forget to set your policy properly (aka ACCEPT).
Next to that, you might want to check the same for the IPv4 firewalls. I assume you make the same mistakes there. Remember that as you have a static tunnel you need to accept protocol 41 inbound and outbound.
Just starting with an empty firewall ruleset is a good idea though, or otherwise, add LOG rules before you drop things.
Cant ping Pop or anything
Shadow Hawkins on Tuesday, 27 July 2010 09:55:56
now i am pretty sure that i allow all connections in and out firewall should not stop any packet both ipv6 and ipv4
*mangle
:PREROUTING ACCEPT [10:719]
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [10:719]
:OUTPUT ACCEPT [0:0]
:POSTROUTING ACCEPT [10:719]
COMMIT
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [10:719]
:OUTPUT ACCEPT [0:0]
COMMIT
but now i see wierd thing i cant add ipv6 addr to sit1
-bash-3.2# ifconfig sit1
sit1 Link encap:IPv6-in-IPv4
UP POINTOPOINT RUNNING NOARP MTU:1280 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:7 dropped:0 overruns:0 carrier:7
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Cant ping Pop or anything
Shadow Hawkins on Tuesday, 27 July 2010 10:25:25
oke this problem went a way after restart
"" but now i see wierd thing i cant add ipv6 addr to sit1 ""
Cant ping Pop or anything
Shadow Hawkins on Tuesday, 27 July 2010 01:11:08
and how can i fix that then "84.0.0.0/8 dev sit0 proto kernel scope link src 84.52.10.138" i am not very good with tcp/ip networking!
Cant ping Pop or anything
either just:
ip ro del 84.0.0.0/8
or:
ip ro del 84.0.0.0/8 dev sit0
should do the trick.
Cant ping Pop or anything
Shadow Hawkins on Tuesday, 27 July 2010 10:33:36
now i ping something i get new reults :)
From 2001:ad0:900:52::2 icmp_seq=568 Destination unreachable: Address unreachable
Cant ping Pop or anything
2001:ad0:900:52::2 is your end of the tunnel, that means that you have no proper IPv6 routing tables setup, check 'ip -6 ro sho' and make sure that you have a route for the tunnel itself and one default to the other side of the tunnel (and optionally a 2000::/3 in case you have a very old or broken kernel)
Cant ping Pop or anything
Shadow Hawkins on Tuesday, 27 July 2010 10:50:06
-bash-3.2# ip -6 ro sho
2001:ad0:900:52::/64 via :: dev sit1 proto kernel metric 256 mtu 1280 advmss 1220 hoplimit 4294967295
fe80::/64 dev eth0 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295
fe80::/64 dev eth1 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295
default via 2001:ad0:900:52::1 dev sit1 metric 1024 mtu 1280 advmss 1220 hoplimit 4294967295
my kernel is 2.6.32.2
Cant ping Pop or anything
Looks fine-ish to me.
What does a "ip -6 ro get 2001:838::/32" do?
And try a "traceroute6 www.sixxs.net"
Cant ping Pop or anything
Shadow Hawkins on Tuesday, 27 July 2010 11:08:21
-bash-3.2# traceroute6 www.sixxs.net
traceroute to www.sixxs.net (2001:838:2:1::30:67), 30 hops max, 40 byte packets
1 cl-83.tll-01.ee.sixxs.net (2001:ad0:900:52::2) 0.051 ms !H 0.062 ms !H 0.029 ms !H
-bash-3.2# ip -6 ro get 2001:838::/32
2001:838:: via 2001:ad0:900:52::1 dev sit1 src 2001:ad0:900:52::2 metric 1024 mtu 1280 advmss 1220 hoplimit 4294967295
Cant ping Pop or anything
-bash-3.2# traceroute6 www.sixxs.net traceroute to www.sixxs.net (2001:838:2:1::30:67), 30 hops max, 40 byte packets 1 cl-83.tll-01.ee.sixxs.net (2001:ad0:900:52::2) 0.051 ms !H 0.062 ms !H 0.029 ms !H
That is definitely your host doing some denying...
What does your IPv4 firewall look like?
Cant ping Pop or anything
Shadow Hawkins on Tuesday, 27 July 2010 11:14:14
my ipv4 firewall
# Generated by iptables-save v1.3.5 on Sun Jul 4 05:53:52 2010
*nat
:OUTPUT ACCEPT [0:0]
:PREROUTING ACCEPT [0:0]
:POSTROUTING ACCEPT [0:0]
-A POSTROUTING -o ppp0 -j MASQUERADE
-A PREROUTING -p udp -m udp --dport 27100 -j DNAT --to-destination 192.168.0.208
-A PREROUTING -p tcp -m tcp --dport 8015 -j DNAT --to-destination 192.168.0.208
-A PREROUTING -p tcp -m tcp --dport 33335 -j DNAT --to-destination 192.168.0.208
-A PREROUTING -p udp -m udp --dport 33334 -j DNAT --to-destination 192.168.0.208
-A PREROUTING -p tcp -m tcp --dport 47624 -j DNAT --to-destination 192.168.0.208
-A PREROUTING -p udp -m udp --dport 47624 -j DNAT --to-destination 192.168.0.208
-A PREROUTING -p tcp -m tcp --dport 2300:2400 -j DNAT --to-destination 192.168.0.208
-A PREROUTING -p udp -m udp --dport 2300:2400 -j DNAT --to-destination 192.168.0.208
COMMIT
# Completed on Sun Jul 4 05:53:52 2010
# Generated by iptables-save v1.3.5 on Sun Jul 4 05:53:52 2010
*mangle
:PREROUTING ACCEPT [0:0]
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
:POSTROUTING ACCEPT [0:0]
COMMIT
# Completed on Sun Jul 4 05:53:52 2010
# Generated by iptables-save v1.3.5 on Sun Jul 4 05:53:52 2010
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
COMMIT
# Completed on Sun Jul 4 05:53:52 2010
Cant ping Pop or anything
Unless your clock is off that seems to be the firewall rules from Sunday, can you just check: "iptables -v --list -n" and "ip6tables -v --list -n" ?
Cant ping Pop or anything
Shadow Hawkins on Tuesday, 27 July 2010 12:44:09
-bash-3.2# iptables -v --list -n
Chain INPUT (policy ACCEPT 691K packets, 76M bytes)
pkts bytes target prot opt in out source destination
Chain FORWARD (policy ACCEPT 3048K packets, 2176M bytes)
pkts bytes target prot opt in out source destination
Chain OUTPUT (policy ACCEPT 565K packets, 145M bytes)
pkts bytes target prot opt in out source destination
----------------------------------------------------------------------------
-bash-3.2# ip6tables -v --list -n
Chain INPUT (policy ACCEPT 1167 packets, 173K bytes)
pkts bytes target prot opt in out source destination
Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination
Chain OUTPUT (policy ACCEPT 2318 packets, 290K bytes)
pkts bytes target prot opt in out source destination
Cant ping Pop or anything
Can you check:
ip -6 link sho
ip -6 addr sho
ip -6 ro sho
ip tunnel sho
ip -6 nei sho
Otherwise the only thing left will be to do some tcpdumps or just blame it on a broken kernel...
Cant ping Pop or anything
Shadow Hawkins on Tuesday, 27 July 2010 12:56:11
-bash-3.2# ip -6 link sho
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:14:85:1e:c3:59 brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:14:d1:16:49:34 brd ff:ff:ff:ff:ff:ff
4: ppp0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1492 qdisc pfifo_fast qlen 3
link/ppp
5: sit0: <NOARP> mtu 1480 qdisc noop
link/sit 0.0.0.0 brd 0.0.0.0
6: sit1: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1280 qdisc noqueue
link/sit 84.52.10.183 peer 195.222.0.66
----------------------------------------------------------------------------
-bash-3.2# ip -6 addr sho
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qlen 1000
inet6 fe80::214:85ff:fe1e:c359/64 scope link
valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qlen 1000
inet6 fe80::214:d1ff:fe16:4934/64 scope link
valid_lft forever preferred_lft forever
6: sit1: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1280
inet6 2001:ad0:900:52::2/64 scope global
valid_lft forever preferred_lft forever
----------------------------------------------------------------------------
-bash-3.2# ip -6 ro sho
2001:ad0:900:52::/64 via :: dev sit1 proto kernel metric 256 mtu 1280 advmss 1220 hoplimit 4294967295
fe80::/64 dev eth0 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295
fe80::/64 dev eth1 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295
default via 2001:ad0:900:52::1 dev sit1 metric 1024 mtu 1280 advmss 1220 hoplimit 4294967295
----------------------------------------------------------------------------
-bash-3.2# ip tunnel sho
sit0: ipv6/ip remote any local any ttl 64 nopmtudisc
sit1: ipv6/ip remote 195.222.0.66 local 84.52.10.183 ttl 64
----------------------------------------------------------------------------
-bash-3.2# ip -6 nei sho
( no results )
----------------------------------------------------------------------------
Cant ping Pop or anything
I don't see anything trivially wrong there, I would say:
$ ping6 2001:ad0:900:52::2
To check that your side of the tunnel works
$ ping6 2001:ad0:900:52::1
To see if you can reach the PoP
If the latter doesn't work do a "tcpdump -i ppp0 -np" and see if you have proto-41 packets flowing over the link and maybe ICMP coming back.
Cant ping Pop or anything
Shadow Hawkins on Tuesday, 27 July 2010 13:20:40
-bash-3.2# ping6 2001:ad0:900:52::2
PING 2001:ad0:900:52::2(2001:ad0:900:52::2) 56 data bytes
64 bytes from 2001:ad0:900:52::2: icmp_seq=0 ttl=64 time=0.638 ms
64 bytes from 2001:ad0:900:52::2: icmp_seq=1 ttl=64 time=0.052 ms
64 bytes from 2001:ad0:900:52::2: icmp_seq=2 ttl=64 time=0.064 ms
64 bytes from 2001:ad0:900:52::2: icmp_seq=3 ttl=64 time=0.055 ms
----------------------------------------------------------------------
-bash-3.2# ping6 2001:ad0:900:52::1
PING 2001:ad0:900:52::1(2001:ad0:900:52::1) 56 data bytes
From 2001:ad0:900:52::2 icmp_seq=0 Destination unreachable: Address unreachable
From 2001:ad0:900:52::2 icmp_seq=1 Destination unreachable: Address unreachable
From 2001:ad0:900:52::2 icmp_seq=2 Destination unreachable: Address unreachable
From 2001:ad0:900:52::2 icmp_seq=3 Destination unreachable: Address unreachable
----------------------------------------------------------------------
tcpdump contains do much gameserver data.
Cant ping Pop or anything
From 2001:ad0:900:52::2 icmp_seq=0 Destination unreachable: Address unreachable
This is really weird, as that is YOUR host telling that the address is unreachable, this while the routing tables make sense....
Could you force it maybe with: "ip -6 ro add 2001:ad0:900:52::1 dev sit1" and try again?
Cant ping Pop or anything
Shadow Hawkins on Tuesday, 27 July 2010 13:35:23
I know its weird its so weird. i think i should tray older kernel 2.6.18 an official centos kernel.
-bash-3.2# ip -6 ro add 2001:ad0:900:52::1 dev sit1
-bash-3.2# ping6 2001:ad0:900:52::1
PING 2001:ad0:900:52::1(2001:ad0:900:52::1) 56 data bytes
From 2001:ad0:900:52::2 icmp_seq=0 Destination unreachable: Address unreachable
From 2001:ad0:900:52::2 icmp_seq=1 Destination unreachable: Address unreachable
Cant ping Pop or anything
Shadow Hawkins on Tuesday, 27 July 2010 13:53:19
i think i will never get it to work or allow some pro ssh access to my pc.
Cant ping Pop or anything
For the fun of it: "ip link set name ipv6 dev sit1"
this as 'sit0' is a special control device, and sitX might be handled specially too, especially as a long time ago one had sit0/sit1 as a pair.
Cant ping Pop or anything
Shadow Hawkins on Tuesday, 27 July 2010 14:12:05
same nothing. ill tray clean centos 5 install
Cant ping Pop or anything
Debian is what works for the rest of the world. It all depends on what you like and need though.
Cant ping Pop or anything
Shadow Hawkins on Tuesday, 27 July 2010 16:27:06
i trayd on Ubuntu 9+ nothing same reulst can ping myself but no pop or any other host
Cant ping Pop or anything
Only thing I can come up with is that there must be something in your network that is blocking packets, or, more likely, that you are configuring it quite wrong...
Cant ping Pop or anything
Shadow Hawkins on Tuesday, 27 July 2010 19:51:39
yeah i realy dont know what to do i used sixxs configuration.
Cant ping Pop or anything
Shadow Hawkins on Tuesday, 27 July 2010 19:55:36
i am happy to allow you to my pc through ssh!
Cant ping Pop or anything
Shadow Hawkins on Tuesday, 27 July 2010 19:59:15
i must say that i am not only one who have that problem with sixxs with my isp.
Cant ping Pop or anything
Shadow Hawkins on Tuesday, 27 July 2010 20:00:09
and that other isp like "Elisa" sixxs works fine and "Elion"
Cant ping Pop or anything
![[ch]](/s/countries/ch.gif) Shadow Hawkins on Thursday, 29 July 2010 18:00:43
I'm trying to setup also my tunnel.
I've exactly the same phenomena i can ping mysql :2 but adress :1 is unreachable.
I'm on 2.6.31 kernel !
It's seems very strange ...
Cant ping Pop or anything
See all the hints above in this thread, and definitely check your routing table.
Cant ping Pop or anything
Shadow Hawkins on Monday, 02 August 2010 10:58:42
on my case i think its isp related problem
|
on Monday, 26 July 2010 18:00:08
Posting is only allowed when you are