gif tunnel ipv4 over ipv4 don't work
Hi All! I found next issue with gif tunnels. gif3 work look's like mpd without tcpmssfix - google opened, but another sites waiting read forever gif4 work fine. all connection to internet in Box2,3 similar I changed gif3 tunnel to vtun ethernet tunnel (tap) - it solve problem and all sites loaded good. Configuration MainBox FreeBSD 10.0-CURRENT #45 r228164M amd64 gif3: flags=8051 metric 0 mtu 1500 tunnel inet 172.17.1.200 --> 172.17.1.222 inet6 fe80::21b:21ff:fe7b:3800%gif3 prefixlen 64 scopeid 0x19 inet 192.168.254.69 --> 192.168.254.70 netmask 0xfffc nd6 options=21 options=1 gif4: flags=8051 metric 0 mtu 1500 tunnel inet 172.17.1.200 --> 172.17.1.150 inet6 fe80::21b:21ff:fe7b:3800%gif4 prefixlen 64 scopeid 0x1a inet 192.168.254.73 --> 192.168.254.74 netmask 0xfffc nd6 options=21 options=1 Box2 9.0-CURRENT FreeBSD 9.0-CURRENT #44: Tue Mar 2 2010 gif4: flags=8051 metric 0 mtu 1500 tunnel inet 172.17.1.150 --> 172.17.1.200 inet6 fe80::215:e9ff:fef1:d04d%gif4 prefixlen 64 scopeid 0x9 inet 192.168.254.74 --> 192.168.254.73 netmask 0xfffc nd6 options=21 options=1 Box3 FreeBSD 10.0-CURRENT #0 r228504M i386 gif3: flags=8051 metric 0 mtu 1500 tunnel inet 172.17.1.222 --> 172.17.1.200 inet 192.168.254.70 --> 192.168.254.69 netmask 0xfffc inet6 fe80::215:e9ff:fe42:1ee5%gif3 prefixlen 64 scopeid 0x8 nd6 options=21 options=1 ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re[2]: gif tunnel ipv4 over ipv4 don't work
15 декабря 2011, 05:08 от "Bjoern A. Zeeb" : > > On 14. Dec 2011, at 23:11 , Andrey Smagin wrote: > > > Hi All! I found next issue with gif tunnels. > > gif3 work look's like mpd without tcpmssfix - google opened, but another > > sites waiting read forever > > Given it's RFC1918 addresses, this normally sounds like a firewall/NAT with > ICMP filter breaking PMTU issue. Issue is: I only updated system from old 9current to 10current and gif3 don't work correctly after that. If I use ports/net/vtun to organize absolutely identical tunnel - all work good. I don't change firewall rules or NAT, only type of tunnel. ifaces with vtun MainBox tap3: flags=8843 metric 0 mtu 1500 options=8 ether 00:bd:b3:b5:3a:03 inet 192.168.254.69 netmask 0xfffc broadcast 192.168.254.71 inet6 fe80::2bd:b3ff:feb5:3a03%tap3 prefixlen 64 scopeid 0x19 nd6 options=21 Opened by PID 68549 Box3 tap3: flags=8843 metric 0 mtu 1500 options=8 ether 00:bd:2f:5e:33:01 inet6 fe80::2bd:2fff:fe5e:3301%tap1 prefixlen 64 scopeid 0xa inet 192.168.254.70 netmask 0xfffc broadcast 192.168.254.71 nd6 options=21 Opened by PID 9319 > > -- > Bjoern A. Zeeb You have to have visions! > Stop bit received. Insert coin for new address family. > > ___ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org" > ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
kern/155585: [tcp] [panic] tcp_output tcp_mtudisc loop until kernel panic
Hi ! Fresh current without patch from PR don't work. Can anybody commit patch from this PR in source tree or resolve problem by another way ? ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re[2]: problem analysys (Re: [Panic] Dummynet/IPFW related recurring crash.)
I think problem may be like there http://lists.freebsd.org/pipermail/freebsd-net/2010-April/025156.html what type of IFace for your FWD rules ? I have crash only for ng IF. over gif fwd work without problem. But it only for my case. Mon, 21 Feb 2011 00:13:12 +0100 письмо от Pawel Tyll : > > understood. I am just saying that for instance the vlan presence and > > changes is quite significant in this context. > > You say vlans are "pretty much static" but can you tell us who adds/remove > > them, assign addresses ? > It's not that much work and changes are simple and far between. I do > that personally. IP addresses don't change, however I sometimes > (rarely) destroy and recreate vlans. Panics don't happen immediately > after this operation, or while it happens, and there were times from > panic to panic that I didn't touch a thing. > > > Also the ruleset must have something more than those two rules. > > From the stack trace, the panic seems to occur in a call to the > > "antispoof" option which presumably is somewhere in your ruleset. > > If not, then the stack is corrupt. > Full ruleset with IP addresses removed: > 00010 1691128516 deny ip from any to any not antispoof in > 00020 874400106826835332 fwd [removed] ip from table(60) to table(61) > 00050 3246156244 allow tcp from any to [removed] dst-port 53 // > DNS Rules 50-59 > 000512463493 260607132 allow udp from any to [removed] // DNS Rules > 50-59 > 00059 23891 1091822 deny ip from any to [removed] // DNS Rules > 50-59 > 00100 32 2176 allow ip from any to any via lo0 > 00100 929493 48342523 deny ip from any to table(10) dst-port > 131-139,445 > 00102 56574 2779124 fwd [removed] tcp from table(1) to not table(5) > dst-port 80 > 00103 0 0 fwd [removed] tcp from table(2) to not table(5) > dst-port 80 > 00104427 17244 fwd [removed] tcp from table(3) to not table(5) > 00105 6 808 deny ip from table(3) to not table(5) > 00200 0 0 deny ip from any to 127.0.0.0/8 > 00300 0 0 deny ip from 127.0.0.0/8 to any > 00400 0 0 deny ip from any to ::1 > 00500 0 0 deny ip from ::1 to any > 00600 0 0 allow ipv6-icmp from :: to ff02::/16 > 00700 0 0 allow ipv6-icmp from fe80::/10 to fe80::/10 > 00800 0 0 allow ipv6-icmp from fe80::/10 to ff02::/16 > 00900 0 0 allow ipv6-icmp from any to any ip6 icmp6types > 1 > 01000 0 0 allow ipv6-icmp from any to any ip6 icmp6types > 2,135,136 > 3 462392089 204487140826 pipe tablearg ip from table(100) to any in > 30001 535282183 461888428313 pipe tablearg ip from any to table(101) out > 34900 116507831216622001 skipto 35001 ip from table(10) to table(10) > 35000 597825867 244960831012 fwd [removed] ip from 192.168.0.0/16 to not > 192.168.0.0/16 > 65534 1595697378 1254723485778 allow ip from any to any > 65535 0 0 allow ip from any to any > > 12:07AM up 1 day, 21 mins, 1 user, load averages: 0.08, 0.06, 0.01 > > Should IP addresses be required, I'll gladly send "uncensored" ruleset > to you privately. > > > ___ > freebsd-i...@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ipfw > To unsubscribe, send any mail to "freebsd-ipfw-unsubscr...@freebsd.org" ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: kern/155585: [tcp] [panic] tcp_output tcp_mtudisc loop until kernel panic
The following reply was made to PR kern/155585; it has been noted by GNATS. From: Andrey Smagin To: bug-follo...@freebsd.org, samsp...@mail.ru Cc: Subject: Re: kern/155585: [tcp] [panic] tcp_output tcp_mtudisc loop until kernel panic Date: Fri, 18 Mar 2011 12:08:24 +0300 this patch solve my problem Index: sys/netinet/tcp_var.h === --- sys/netinet/tcp_var.h (revision 219727) +++ sys/netinet/tcp_var.h (working copy) @@ -239,6 +239,7 @@ #defineTF_ECN_SND_ECE 0x1000 /* ECN ECE in queue */ #defineTF_CONGRECOVERY 0x2000 /* congestion recovery mode */ #defineTF_WASCRECOVERY 0x4000 /* was in congestion recovery */ +#defineTF_WASMTUDISC 0x8000 /* was in mtudiscovery */ #defineIN_FASTRECOVERY(t_flags)(t_flags & TF_FASTRECOVERY) #defineENTER_FASTRECOVERY(t_flags) t_flags |= TF_FASTRECOVERY Index: sys/netinet/tcp_output.c === --- sys/netinet/tcp_output.c(revision 219727) +++ sys/netinet/tcp_output.c(working copy) @@ -1288,8 +1288,15 @@ */ if (tso) tp->t_flags &= ~TF_TSO; + + if ( tp->t_flags & TF_WASMTUDISC ) // if EMSGSIZE after call tcp_mtudisc then return EHOSTUNREACH + return (EHOSTUNREACH); + + tp->t_flags |= TF_WASMTUDISC tcp_mtudisc(tp->t_inpcb, 0); + tp->t_flags &= ~TF_WASMTUDISC; return (0); + case EHOSTDOWN: case EHOSTUNREACH: case ENETDOWN: ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
PCI-E VT6130 NIC (if_vge) hang system with gigabit link
Hi ALL ! If I connect gigabit switch to my card - system hang until I unplug patchcord from device. With 100Mbit switch card work good. System: Current - r226163 ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re[2]: PCI-E VT6130 NIC (if_vge) hang system with gigabit link
Hi ! vge0@pci0:2:0:0:class=0x02 card=0x01101106 chip=0x31191106 rev=0x82 hdr=0x00 vendor = 'VIA Technologies, Inc.' device = 'VT6120/VT6121/VT6122 Gigabit Ethernet Adapter' class = network subclass = ethernet bar [10] = type I/O Port, range 32, base 0x8000, size 256, enabled bar [14] = type Memory, range 64, base 0xd410, size 256, enabled cap 01[50] = powerspec 3 supports D0 D1 D2 D3 current D0 cap 10[90] = PCI-Express 1 endpoint max data 128(128) link x1(x1) cap 05[c0] = MSI supports 1 message, 64 bit, vector masks enabled with 1 message ecap 0001[100] = AER 1 0 fatal 1 non-fatal 6 corrected ecap 0003[130] = Serial 1 1106 vge1@pci0:1:0:0:class=0x02 card=0x01101106 chip=0x31191106 rev=0x82 hdr=0x00 vendor = 'VIA Technologies, Inc.' device = 'VT6120/VT6121/VT6122 Gigabit Ethernet Adapter' class = network subclass = ethernet bar [10] = type I/O Port, range 32, base 0x7000, size 256, enabled bar [14] = type Memory, range 64, base 0xd400, size 256, enabled cap 01[50] = powerspec 3 supports D0 D1 D2 D3 current D0 cap 10[90] = PCI-Express 1 endpoint max data 128(128) link x1(x1) cap 05[c0] = MSI supports 1 message, 64 bit, vector masks enabled with 1 message ecap 0001[100] = AER 1 1 fatal 1 non-fatal 6 corrected ecap 0003[130] = Serial 1 1106 dmesg is empty 26 октября 2011, 00:11 от YongHyeon PYUN : > On Tue, Oct 25, 2011 at 10:44:48AM +0400, Andrey Smagin wrote: > > Hi ALL ! If I connect gigabit switch to my card - system hang until I > > unplug patchcord from device. > > With 100Mbit switch card work good. > > Show me the output of dmesg and 'pciconf -lcbv'. > > > System: Current - r226163 > > > ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re[2]: PCI-E VT6130 NIC (if_vge) hang system with gigabit link
26 октября 2011, 20:49 от YongHyeon PYUN : > On Wed, Oct 26, 2011 at 01:49:14PM +0400, Andrey Smagin wrote: > > Hi ! > > vge0@pci0:2:0:0:class=0x02 card=0x01101106 chip=0x31191106 > > rev=0x82 hdr=0x00 > > vendor = 'VIA Technologies, Inc.' > > device = 'VT6120/VT6121/VT6122 Gigabit Ethernet Adapter' > > class = network > > subclass = ethernet > > bar [10] = type I/O Port, range 32, base 0x8000, size 256, enabled > > bar [14] = type Memory, range 64, base 0xd410, size 256, enabled > > cap 01[50] = powerspec 3 supports D0 D1 D2 D3 current D0 > > cap 10[90] = PCI-Express 1 endpoint max data 128(128) link x1(x1) > > cap 05[c0] = MSI supports 1 message, 64 bit, vector masks enabled with > > 1 message > > ecap 0001[100] = AER 1 0 fatal 1 non-fatal 6 corrected > > ecap 0003[130] = Serial 1 1106 > > vge1@pci0:1:0:0:class=0x02 card=0x01101106 chip=0x31191106 > > rev=0x82 hdr=0x00 > > vendor = 'VIA Technologies, Inc.' > > device = 'VT6120/VT6121/VT6122 Gigabit Ethernet Adapter' > > class = network > > subclass = ethernet > > bar [10] = type I/O Port, range 32, base 0x7000, size 256, enabled > > bar [14] = type Memory, range 64, base 0xd400, size 256, enabled > > cap 01[50] = powerspec 3 supports D0 D1 D2 D3 current D0 > > cap 10[90] = PCI-Express 1 endpoint max data 128(128) link x1(x1) > > cap 05[c0] = MSI supports 1 message, 64 bit, vector masks enabled with > > 1 message > > ecap 0001[100] = AER 1 1 fatal 1 non-fatal 6 corrected > > ecap 0003[130] = Serial 1 1106 > > > > dmesg is empty > Hmm, check whether you have old dmesg file in /var/log directory. > At least, I need output of 'devinfo -rv' to know which PHY you have. pcib4 pnpinfo vendor=0x10de device=0x005d subvendor=0x subdevice=0x class=0x060400 at slot=13 function=0 handle=\_SB_.PCI0.XVR1 I/O ports: 0x8000-0x8fff I/O memory addresses: 0xd410-0xd41f pci2 vge0 pnpinfo vendor=0x1106 device=0x3119 subvendor=0x1106 subdevice=0x0110 class=0x02 at slot=0 function=0 Interrupt request lines: 256 pcib4 I/O port window: 0x8000-0x80ff pcib4 memory window: 0xd410-0xd41000ff miibus1 ip1000phy0 pnpinfo oui=0x9c3 model=0x19 rev=0x0 at phyno=1 pcib5 pnpinfo vendor=0x10de device=0x005d subvendor=0x subdevice=0x class=0x060400 at slot=14 function=0 handle=\_SB_.PCI0.XVR0 I/O ports: 0x7000-0x7fff I/O memory addresses: 0xd400-0xd40f pci1 vge1 pnpinfo vendor=0x1106 device=0x3119 subvendor=0x1106 subdevice=0x0110 class=0x02 at slot=0 function=0 Interrupt request lines: 257 pcib5 I/O port window: 0x7000-0x70ff pcib5 memory window: 0xd400-0xd4ff miibus2 ip1000phy1 pnpinfo oui=0x9c3 model=0x19 rev=0x0 at phyno=1 > By chance, are you using manual link configuration instead of > relying on auto-negotiation? I tried manual link and auto-negotiation. Now I not remember which mode hang system. I will try and write result. > > > > > 26 октября 2011, 00:11 от YongHyeon PYUN : > > > On Tue, Oct 25, 2011 at 10:44:48AM +0400, Andrey Smagin wrote: > > > > Hi ALL ! If I connect gigabit switch to my card - system hang until I > > > > unplug patchcord from device. > > > > With 100Mbit switch card work good. > > > > > > Show me the output of dmesg and 'pciconf -lcbv'. > > > > > > > System: Current - r226163 > > > > > > > > > > ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: PCI-E VT6130 NIC (if_vge) hang system with gigabit link
! vge0: watchdog timeout vge0: MIB counter dump timed out! vge0: MIB clear timed out! vge0: soft reset timed out vge0: MIB clear timed out! vge0: MII write timed out vge0: failed to start MII autopoll vge0: MII read timed out vge0: failed to start MII autopoll vge0: MII read timed out vge0: failed to start MII autopoll vge0: MII read timed out vge0: failed to start MII autopoll vge0: MII write timed out vge0: failed to start MII autopoll vge0: MII write timed out vge0: failed to start MII autopoll vge0: MII write timed out vge0: failed to start MII autopoll vge0: MII read timed out vge0: failed to start MII autopoll vge0: MII read timed out vge0: failed to start MII autopoll vge0: MII read timed out vge0: failed to start MII autopoll vge0: MII read timed out vge0: failed to start MII autopoll vge0: flags=8943 metric 0 mtu 1500 options=389b ether 00:a1:b0:00:01:3e inet 192.168.4.1 netmask 0xfffc broadcast 192.168.4.3 nd6 options=29 media: Ethernet 1000baseT (10baseT/UTP ) status: no carrier > > > > 26 октября 2011, 00:11 от YongHyeon PYUN : > > > On Tue, Oct 25, 2011 at 10:44:48AM +0400, Andrey Smagin wrote: > > > > Hi ALL ! If I connect gigabit switch to my card - system hang until I > > > > unplug patchcord from device. > > > > With 100Mbit switch card work good. > > > > > > Show me the output of dmesg and 'pciconf -lcbv'. > > > > > > > System: Current - r226163 > > > > > > > > > > ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re[2]: PCI-E VT6130 NIC (if_vge) hang system with gigabit link
31 октября 2011, 04:56 от YongHyeon PYUN : > On Sat, Oct 29, 2011 at 09:57:30AM +0400, Andrey Smagin wrote: > > > > Ok. With autonegotiation ifconfig show speed 100MBit. > > And vge(4) work without problems with the resolved speed/duplex > of auto-negotiation? > > > with manual 1000baseT full-duplex settings in dmesg: > > vge0: failed to start MII autopoll > > vge0: MII read timed out > > vge0: failed to start MII autopoll > > vge0: link state changed to UP > > vge0: MII read timed out > > [...] > > Did vge(4) ever work with 1000baseT on your box? Hm... I never seen 1000baseT with vge on this box because it have only FreeBSD. > And why you have to manually configure 1000baseT link? With autonegatiation link stand on 100Mbit full-duplex > Does link partner(switch) also use auto-negotiation? In box also present Intel if_em gigabit and if_nfe gigabit card wich work with same cable and partner(switch) at gigabit speed. I only switch connector to if_vge socket. > ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re[2]: PCI-E VT6130 NIC (if_vge) hang system with gigabit link
31 октября 2011, 04:57 от YongHyeon PYUN : > On Sat, Oct 29, 2011 at 09:57:30AM +0400, Andrey Smagin wrote: > > > > Ok. With autonegotiation ifconfig show speed 100MBit. > > And vge(4) work without problems with the resolved speed/duplex > of auto-negotiation? With auto-negotiation vge connect at 100baseTX and work good. > > > with manual 1000baseT full-duplex settings in dmesg: > > vge0: failed to start MII autopoll > > vge0: MII read timed out > > vge0: failed to start MII autopoll > > vge0: link state changed to UP > > vge0: MII read timed out ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re[2]: PCI-E VT6130 NIC (if_vge) hang system with gigabit link
01 ноября 2011, 22:03 от YongHyeon PYUN : > On Mon, Oct 31, 2011 at 12:58:29PM +0400, Andrey Smagin wrote: > > > > > > > > 31 октября 2011, 04:56 от YongHyeon PYUN : > > > On Sat, Oct 29, 2011 at 09:57:30AM +0400, Andrey Smagin wrote: > > > > > > > > Ok. With autonegotiation ifconfig show speed 100MBit. > > > > > > And vge(4) work without problems with the resolved speed/duplex > > > of auto-negotiation? > > > > > > > with manual 1000baseT full-duplex settings in dmesg: > > > > vge0: failed to start MII autopoll > > > > vge0: MII read timed out > > > > vge0: failed to start MII autopoll > > > > vge0: link state changed to UP > > > > vge0: MII read timed out > > > > > > [...] > > > > > > Did vge(4) ever work with 1000baseT on your box? > > Hm... I never seen 1000baseT with vge on this box because > > it have only FreeBSD. > > > And why you have to manually configure 1000baseT link? > > With autonegatiation link stand on 100Mbit full-duplex > > > Does link partner(switch) also use auto-negotiation? > > In box also present Intel if_em gigabit and if_nfe gigabit card wich work > > with > > same cable and partner(switch) at gigabit speed. I only switch connector to > > if_vge socket. > > > > > > > I should have been more clearer. I wanted to know which previous > FreeBSD release was able to establish a 1000baseT link. I upgrade FreeBSD, after some time put 2 PCI-E vge cards in box to replace 2 PCI stge cards. > Downshifting feature of IC Plus IP1001 PHY is automatically enabled > which will downshift to 100TX link when 1000baseT link > establishment fails in auto-negotiation process. So can you confirm > there is no cabling issues there? Cable and switch 100% good. Any another NIC(em,stge,nfe) in box succesfully connected at 1Gb and speed of transfer more than 500mbit/s in any direction, always. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re[2]: kern/155585: [tcp] [panic] tcp_output tcp_mtudisc loop until kernel panic
Hi. I updated system to r227141:227142M and tried patch. 6 hours uptime right now. Bug looks fixed. 02 ноября 2011, 21:01 от Andrey Zonov : > The following reply was made to PR kern/155585; it has been noted by GNATS. > > From: Andrey Zonov > To: bug-follo...@freebsd.org, samsp...@mail.ru > Cc: > Subject: Re: kern/155585: [tcp] [panic] tcp_output tcp_mtudisc loop until > kernel panic > Date: Wed, 02 Nov 2011 20:54:15 +0400 > > This is a multi-part message in MIME format. > --040501090905060606010708 > Content-Type: text/plain; charset=UTF-8; format=flowed > Content-Transfer-Encoding: 7bit > > Hi Andrey, > > Please try attached patch. > > I think the same problem was resolved here [1]. > > [1] http://svnweb.freebsd.org/base?view=revision&revision=178029 > > -- > Andrey Zonov > > --040501090905060606010708 > Content-Type: text/plain; > name="patch-tcp_output.c.txt" > Content-Transfer-Encoding: base64 > Content-Disposition: attachment; > filename="patch-tcp_output.c.txt" > > SW5kZXg6IHN5cy9uZXRpbmV0L3RjcF9vdXRwdXQuYwo9PT09PT09PT09PT09PT09PT09PT09 > PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09Ci0tLSBzeXMv > bmV0aW5ldC90Y3Bfb3V0cHV0LmMJKHJldmlzaW9uIDIyNzAyMCkKKysrIHN5cy9uZXRpbmV0 > L3RjcF9vdXRwdXQuYwkod29ya2luZyBjb3B5KQpAQCAtMTc3LDggKzE3Nyw5IEBACiAJaW50 > IGlkbGUsIHNlbmRhbG90OwogCWludCBzYWNrX3J4bWl0LCBzYWNrX2J5dGVzX3J4bXQ7CiAJ > c3RydWN0IHNhY2tob2xlICpwOwotCWludCB0c287CisJaW50IHRzbywgbXR1LCBvZmZlcjsK > IAlzdHJ1Y3QgdGNwb3B0IHRvOworCXN0cnVjdCByb3V0ZSBybzsKICNpZiAwCiAJaW50IG1h > eGJ1cnN0ID0gVENQX01BWEJVUlNUOwogI2VuZGlmCkBAIC0yMTgsNiArMjE5LDcgQEAKIAkJ > dGNwX3NhY2tfYWRqdXN0KHRwKTsKIAlzZW5kYWxvdCA9IDA7CiAJdHNvID0gMDsKKwltdHUg > PSAwOwogCW9mZiA9IHRwLT5zbmRfbnh0IC0gdHAtPnNuZF91bmE7CiAJc2VuZHdpbiA9IG1p > bih0cC0+c25kX3duZCwgdHAtPnNuZF9jd25kKTsKIApAQCAtMTIzMSw5ICsxMjMzLDE2IEBA > CiAJaWYgKFZfcGF0aF9tdHVfZGlzY292ZXJ5ICYmIHRwLT50X21heG9wZCA+IFZfdGNwX21p > bm1zcykKIAkJaXAtPmlwX29mZiB8PSBJUF9ERjsKIAotCWVycm9yID0gaXBfb3V0cHV0KG0s > IHRwLT50X2lucGNiLT5pbnBfb3B0aW9ucywgTlVMTCwKKwliemVybygmcm8sIHNpemVvZihy > bykpOworCisJZXJyb3IgPSBpcF9vdXRwdXQobSwgdHAtPnRfaW5wY2ItPmlucF9vcHRpb25z > LCAmcm8sCiAJICAgICgoc28tPnNvX29wdGlvbnMgJiBTT19ET05UUk9VVEUpID8gSVBfUk9V > VEVUT0lGIDogMCksIDAsCiAJICAgIHRwLT50X2lucGNiKTsKKworCWlmIChlcnJvciA9PSBF > TVNHU0laRSAmJiByby5yb19ydCkKKwkJbXR1ID0gcm8ucm9fcnQtPnJ0X3JteC5ybXhfbXR1 > OworCWlmIChyby5yb19ydCkKKwkJUlRGUkVFKHJvLnJvX3J0KTsKICAgICB9CiAjZW5kaWYg > LyogSU5FVCAqLwogCWlmIChlcnJvcikgewpAQCAtMTI3OSwyMiArMTI4OCwyMCBAQAogCQkJ > LyoKIAkJCSAqIEZvciBzb21lIHJlYXNvbiB0aGUgaW50ZXJmYWNlIHdlIHVzZWQgaW5pdGlh > bGx5CiAJCQkgKiB0byBzZW5kIHNlZ21lbnRzIGNoYW5nZWQgdG8gYW5vdGhlciBvciBsb3dl > cmVkCi0JCQkgKiBpdHMgTVRVLgotCQkJICoKLQkJCSAqIHRjcF9tdHVkaXNjKCkgd2lsbCBm > aW5kIG91dCB0aGUgbmV3IE1UVSBhbmQgYXMKLQkJCSAqIGl0cyBsYXN0IGFjdGlvbiwgaW5p > dGlhdGUgcmV0cmFuc21pc3Npb24sIHNvIGl0Ci0JCQkgKiBpcyBpbXBvcnRhbnQgdG8gbm90 > IGRvIHNvIGhlcmUuCi0JCQkgKgotCQkJICogSWYgVFNPIHdhcyBhY3RpdmUgd2UgZWl0aGVy > IGdvdCBhbiBpbnRlcmZhY2UKLQkJCSAqIHdpdGhvdXQgVFNPIGNhcGFiaWxpdHMgb3IgVFNP > IHdhcyB0dXJuZWQgb2ZmLgotCQkJICogRGlzYWJsZSBpdCBmb3IgdGhpcyBjb25uZWN0aW9u > IGFzIHRvbyBhbmQKLQkJCSAqIGltbWVkaWF0bHkgcmV0cnkgd2l0aCBNU1Mgc2l6ZWQgc2Vn > bWVudHMgZ2VuZXJhdGVkCi0JCQkgKiBieSB0aGlzIGZ1bmN0aW9uLgorCQkJICogaXRzIE1U > VS4gVXBkYXRlIHRfbWF4b3BkIGFuZCB0X21heHNlZyB0aHJvdWdoCisJCQkgKiB0Y3BfbXNz > X3VwZGF0ZSgpIGFuZCB0cnkgdG8gc2VuZCBkYXRhIGFnYWluLgogCQkJICovCi0JCQlpZiAo > dHNvKQotCQkJCXRwLT50X2ZsYWdzICY9IH5URl9UU087Ci0JCQl0Y3BfbXR1ZGlzYyh0cC0+ > dF9pbnBjYiwgMCk7Ci0JCQlyZXR1cm4gKDApOworCQkJaWYgKG10dSAhPSAwKSB7CisJCQkJ > b2ZmZXIgPSBtdHUgLSBoZHJsZW47CisJCQkJaWYgKCh0cC0+dF9mbGFncyAmIFRGX1JDVkRf > VFNUTVApID09IFRGX1JDVkRfVFNUTVApCisJCQkJCW9mZmVyICs9IFRDUE9MRU5fVFNUQU1Q > X0FQUEE7CisJCQkJdGNwX21zc191cGRhdGUodHAsIG9mZmVyLCBOVUxMLCBOVUxMKTsKKwkJ > CQlnb3RvIGFnYWluOworCQkJfQorCQkJLyoKKwkJCSAqIFRoaXMgaXMgdGhlIGJlc3Qgd2Ug > Y2FuIGRvIGhlcmUuCisJCQkgKi8KKwkJCXJldHVybiAoZXJyb3IpOwogCQljYXNlIEVIT1NU > RE9XTjoKIAkJY2FzZSBFSE9TVFVOUkVBQ0g6CiAJCWNhc2UgRU5FVERPV046Cg== > --040501090905060606010708-- > ___ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org" > ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re[2]: PCI-E VT6130 NIC (if_vge) hang system with gigabit link
02 ноября 2011, 06:07 от YongHyeon PYUN : > If there is no cabling issue there, please try attached patch and > let me know whether the patch makes any difference on you. > > Thanks. > I tried patch. Now automatic connection can't established. In dmesg vge0: MII read timed out ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re[2]: PCI-E VT6130 NIC (if_vge) hang system with gigabit link
Hi! Some days back I put card in Win7 machine.
Win7 hang own network subsystem if connected to gigabit switch.
I tried last night your patches. Now when put in gigabit switch no hangs or
errors,
but link (autodetect) 100mbit/s and work good.
I think I bought buggy network cards :((.
Index: sys/dev/mii/ip1000phy.c
===
--- sys/dev/mii/ip1000phy.c (revision 227501)
+++ sys/dev/mii/ip1000phy.c (working copy)
@@ -324,7 +324,6 @@
PHY_WRITE(sc, IP1000PHY_MII_ANAR, reg | IP1000PHY_ANAR_CSMA);
reg = IP1000PHY_1000CR_1000T | IP1000PHY_1000CR_1000T_FDX;
- reg |= IP1000PHY_1000CR_MASTER;
PHY_WRITE(sc, IP1000PHY_MII_1000CR, reg);
PHY_WRITE(sc, IP1000PHY_MII_BMCR, (IP1000PHY_BMCR_FDX |
IP1000PHY_BMCR_AUTOEN | IP1000PHY_BMCR_STARTNEG));
Index: sys/dev/vge/if_vge.c
===
--- sys/dev/vge/if_vge.c(revision 227501)
+++ sys/dev/vge/if_vge.c(working copy)
@@ -173,6 +173,7 @@
static voidvge_freebufs(struct vge_softc *);
static voidvge_ifmedia_sts(struct ifnet *, struct ifmediareq *);
static int vge_ifmedia_upd(struct ifnet *);
+static int vge_ifmedia_upd_locked(struct vge_softc *);
static voidvge_init(void *);
static voidvge_init_locked(struct vge_softc *);
static voidvge_intr(void *);
@@ -180,7 +181,6 @@
static int vge_ioctl(struct ifnet *, u_long, caddr_t);
static voidvge_link_statchg(void *);
static int vge_miibus_readreg(device_t, int, int);
-static voidvge_miibus_statchg(device_t);
static int vge_miibus_writereg(device_t, int, int, int);
static voidvge_miipoll_start(struct vge_softc *);
static voidvge_miipoll_stop(struct vge_softc *);
@@ -190,6 +190,7 @@
static int vge_rx_list_init(struct vge_softc *);
static int vge_rxeof(struct vge_softc *, int);
static voidvge_rxfilter(struct vge_softc *);
+static voidvge_setmedia(struct vge_softc *);
static voidvge_setvlan(struct vge_softc *);
static voidvge_setwol(struct vge_softc *);
static voidvge_start(struct ifnet *);
@@ -218,7 +219,6 @@
/* MII interface */
DEVMETHOD(miibus_readreg, vge_miibus_readreg),
DEVMETHOD(miibus_writereg, vge_miibus_writereg),
- DEVMETHOD(miibus_statchg, vge_miibus_statchg),
{ 0, 0 }
};
@@ -1099,10 +1099,11 @@
goto fail;
}
+ vge_miipoll_start(sc);
/* Do MII setup */
error = mii_attach(dev, &sc->vge_miibus, ifp, vge_ifmedia_upd,
vge_ifmedia_sts, BMSR_DEFCAPMASK, sc->vge_phyaddr, MII_OFFSET_ANY,
- 0);
+ MIIF_DOPAUSE);
if (error != 0) {
device_printf(dev, "attaching PHYs failed\n");
goto fail;
@@ -1660,30 +1661,41 @@
{
struct vge_softc *sc;
struct ifnet *ifp;
- struct mii_data *mii;
+ uint8_t physts;
sc = xsc;
ifp = sc->vge_ifp;
VGE_LOCK_ASSERT(sc);
- mii = device_get_softc(sc->vge_miibus);
- mii_pollstat(mii);
- if ((sc->vge_flags & VGE_FLAG_LINK) != 0) {
- if (!(mii->mii_media_status & IFM_ACTIVE)) {
+ physts = CSR_READ_1(sc, VGE_PHYSTS0);
+ if ((physts & VGE_PHYSTS_RESETSTS) == 0) {
+ if ((physts & VGE_PHYSTS_LINK) == 0) {
sc->vge_flags &= ~VGE_FLAG_LINK;
if_link_state_change(sc->vge_ifp,
LINK_STATE_DOWN);
- }
- } else {
- if (mii->mii_media_status & IFM_ACTIVE &&
- IFM_SUBTYPE(mii->mii_media_active) != IFM_NONE) {
+ } else {
sc->vge_flags |= VGE_FLAG_LINK;
if_link_state_change(sc->vge_ifp,
LINK_STATE_UP);
+ CSR_WRITE_1(sc, VGE_CRC2, VGE_CR2_FDX_TXFLOWCTL_ENABLE |
+ VGE_CR2_FDX_RXFLOWCTL_ENABLE);
+ if ((physts & VGE_PHYSTS_FDX) != 0) {
+ if ((physts & VGE_PHYSTS_TXFLOWCAP) != 0)
+ CSR_WRITE_1(sc, VGE_CRS2,
+ VGE_CR2_FDX_TXFLOWCTL_ENABLE);
+ if ((physts & VGE_PHYSTS_RXFLOWCAP) != 0)
+ CSR_WRITE_1(sc, VGE_CRS2,
+ VGE_CR2_FDX_RXFLOWCTL_ENABLE);
+ }
if (!IFQ_DRV_IS_EMPTY(&ifp->if_snd))
vge_start_locked(ifp);
}
}
+ /*
+* Restart MII auto-polling because link state change interrupt
+* will disable it.
+*/
+ vge_miipoll_start(sc);
}
#ifdef DEVICE_POLLING
@@ -2028,6 +2040,7 @@
*/
vge_stop(sc);
vge_reset(sc)
Bridge on WiFi cards strange work
Hello ALL 192.168.1.4 can ping only 192.168.1.200. All another PC(exclude 192.168.1.200) can't ping only 192.168.1.4. Firewall in allow ip from any to any. Switching cable and ssid for acx0 and ath0 have no effect - 192.168.1.4 not pinging outside server 1 anyway. NAT(with PPP) on Server1 work fine for 192.168.1.4 as and for all another. acx0 ath0 fxp0 in promisc mode, viewed in log. I have server with 3NIC in Server1(FBSD-6.0-CUR-1week): Intel PILA PRO DWL-G520 DWL-520+ and 2NIC in Server2(FBSD-6.0-CUR-1week): Intel PILA PRO DWL-G520 in sysctl.conf on Sever1 bridge.config=fxp0:1,ath0:1,acx0:1 bridge.enable=1 in sysctl.conf on Sever2 bridge.config=fxp0:1,ath0:1 bridge.enable=1 net topology 192.168.3.200192.168.1.200 192.168.1.4(DWL-520+) ~~~ (DWL-520+ acx0)Server1(fxp0)===192.168.1.2(rl0) (DWL-G520 ath0 192.168.2.200) ~ ~ (DWL-G520 ath0 192.168.2.100) Server2 (fxp0 192.168.1.100) || || 192.168.1.5 = Switch(Acorp 5Port)= 192.168.1.1 -- Best regards, Andrey mailto:[EMAIL PROTECTED] ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Bridge on WiFi cards strange work
MK> What does sysctl net.inet.ip.check_interface say? Does switching it MK> off helps? net.inet.ip.check_interface was 0 Switch it to 1 have no effect. I think WiFi devices can hear each other through antenna. But devices have different SSID and IMHO can't have loop. -- Best regards, Andreymailto:[EMAIL PROTECTED] ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
connect 2 subnet by WiFi
Hi all! Need to connect 2 ethernet subnet. Now for it used D-Link DI-624 Wireless Router and DWL-G520. Problem that Server can ping any another PC in net, subnet A can ping Server but can't ping subnet B, subnet B also can ping Server but can't ping subnet A. topology and configs: 192.168.1.3 |by wire subnet A | 192.168.1.6 \ | Air 192.168.1.100 192.168.1.7 > (Switch) --- DI-624 ~~ (ath0)Server(fxp0) 192.168.1.8 / by wire | (Switch) | subnet B | 192.168.1.5 192.168.1.1 rc.conf ... ifconfig_ath0="inet up ssid my_net" ifconfig_fxp0="inet 192.168.1.100 netmask 255.255.255.0" ... sysctl.conf ... sysctl net.link.ether.bridge_cfg="ath0:1,fxp0:1" sysctl net.link.ether.bridge=1 sysctl net.inet.ip.check_interface=0 ... -- Best regards, Andreymailto:[EMAIL PROTECTED] ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
vr0 kernel panic
Hi ALL, panic: vr0f0: BUG: if_attach called without if_alloc'd input() Kernel panic after load, since about week in current. Bad but solution: load if_vr module and configure interface after all (in rc.d/ script). -- Best regards, Andreymailto:[EMAIL PROTECTED] ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: vr0 kernel panic
Hello Brooks, Thursday, June 16, 2005, 8:51:14 PM, you wrote: BD> [DO NOT reply to random messages to post on new topics. I nearly missed BD> this message.] BD> On Thu, Jun 16, 2005 at 10:06:01AM +0400, Andrey Smagin wrote: >> Hi ALL, >> >>panic: vr0f0: BUG: if_attach called without if_alloc'd input() >> >> Kernel panic after load, since about week in current. >> Bad but solution: >> load if_vr module and configure interface after all (in rc.d/ script). BD> Please read /usr/src/UPDATING. It looks like you updated your kernel, BD> but not modules. vr(4)'s attach routing looks correct by inspection and BD> the interface works here. Ok. I am will check it all more complex. But about year i live on current. By cron every day at 2:30(Moscow) cvsup new sources and automaticaly build and install it. And i not touched configs last few month. Today new build also panic reboots at vr0. Bad news for me that i updated my server, and it also hang's on boot. Server have no vr at all, then because i think that problem not in vr driver. Server have no monitor i can't look point of crash now. Now i use kernel.old. Present some incompatibles with world, but system work anyway. BD> -- Brooks -- Best regards, Andreymailto:[EMAIL PROTECTED] ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Satellite internet connenction
Hi. Please help. Need to create connection with internet via satellite for in and modem for out, anybody have success stories about it ? Please tell me you hardware and software configuration. -- Best regards, Andreymailto:[EMAIL PROTECTED] ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
How connect 2 PC with ath in hostap mode ?
Hi All. Now bridge between net segments work in adhoc mode, but it very slow ~40KB/s. If set one in client another in hostap then speed 2.5MB/s. Devices is D-Link DWL-G520, system FreeBSD 7.0-CURRENT (week ago). If both devices in hostap mode, then no packets transmitted. -- Best regards, Andreymailto:[EMAIL PROTECTED] ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How connect 2 PC with ath in hostap mode ?
Hi ALL, People please say it possible under FreeBSD ? Any body have sucess stories about it ? What manual I must read to do it ? :) -- Best regards, Andreymailto:[EMAIL PROTECTED] ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How connect 2 PC with ath in hostap mode ?
Hello Marcin, MJ> man ifconfig should be the place to start. :) re read it 2 year, for information about MJ> Anyway, you can connect two PCs when one of them runs in MJ> hostap and the other one in ad-hoc mode. MJ> This will set up one of them as AP: MJ> ifconfig_ath0="inet 12.23.34.1 netmask 255.255.255.0 ssid Andrey mode MJ> 11g mediaopt hostap" MJ> And one in adhoc: MJ> ifconfig_ath0="inet 12.23.34.1 netmask 255.255.255.0 ssid Andrey MJ> channel 6 mode 11g mediaopt adhoc" MJ> You can also run both atheros nics in ad-hoc mode and bridge their MJ> interfaces with wired nics. My most qestion - how increase speed for ad-hoc<=>ad-hoc connection. It mode have very small speed(40KBy/s) . For me important bridge on both sides for connect 2 wired LAN segments through air. When i connect client<=>hostup bridging not work (but speed 2MBy/s between this hosts). I am will try ad-hoc<=>hostap. MJ> And you can set up your atheros access point as apbridge which will MJ> pass packets between wireless clients directly. For me not enough for connect another WiFi clients, now configured -apbridge. MJ> You cannot connect two APs in hostap mode as they will never associate MJ> to one another. Thank you. -- Best regards, Andreymailto:[EMAIL PROTECTED] ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How connect 2 PC with ath in hostap mode ?
Hello Marcin, Tuesday, October 4, 2005, 11:35:17 AM, you wrote: MJ> How are you bridging the interfaces? What kind of bridging mechanism MJ> are you using? In FreeBSD: kldload ath, ath_hal, bridge, fxp On both host: ifconfig_ath0="inet ssid 1234 channel 6 mode 11g mediaopt adhoc" in sysctl.conf hwbridge.config=ath0:1,fxp0:1 hwbridge.enable=1 ipfw allow ip from any to any in this mode speed about 8KBy/s ifconfig_ath0="inet ssid 1234 channel 6 media OFDM54 mode 11g mediaopt adhoc" increase speed up to 45-50 KBy/s Bridging work fine and uptime for both host more wheek under full load :) (40KBy/s over wireless) Some strange - ping report low average delay about 0.700ms for any host in another net segment. MJ> Anyway, the difference in speed is indeed strange. MJ> Try to set following: MJ> sysctl dev.ath.0.tpscale=1 MJ> sysctl dev.ath.0.tpc=1 MJ> sysctl dev.ath.0.diversity=0 MJ> ifconfig ath0 protmode off MJ> ifconfig ath0 mtu 2290 MJ> You could also use device tap (virtual ethernet) and connect two lan's MJ> that way running one link in hostap and the other bss mode. Check out MJ> the vtun port. Thanks i will try it. MJ> I am not sure why you have such a speed loss running in adhoc mode. MJ> What I noticed on NetBSD (where the ath driver is not yet fully ported) MJ> was I got pretty decent speed with the same setup as yours (2xath in MJ> adhoc bridged with wired nics) but my embedded devices allways crashed MJ> when I sent over many small packets. I think this is a driver problem, two ap sucessfully connect with each other, why hostap can't do this ? I tested D-Link 624 WiFi router, D-Link 2100AP, DWL-520+, DWL-G520. On DWL-520+ - acx chipset, it speed not more 8KBy/s with adhoc<=>adhoc connection(but under W2K it have fullspeed 800KBy/s in this mode). I bought DWL-G520 on ath chipset, upgraded hosts hardware up 850MHz processor, new MB, more RAM, but it not resolve the problem, with 54MBit/s connection, speed is too small. D-Link AP, with WiFi router have good connection and speed 38MBit/s(2MBy/s). -- Best regards, Andreymailto:[EMAIL PROTECTED] ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ioctl(SIOCAIFADDR, 85.195.153.121 -> 82.198.6.19): File exists
Hello All. I have a strange problem with VPN connection. PPP can't set IP address for interface. I use pptpclient by commands: #route add 82.198.6.19 192.168.1.200 #pptpclient 82.198.6.19 vpn If I route to 82.198.6.19 by #route add 80.82.6.0/24 192.168.1.200 connection successfuly esteblish, but after some seconds drop. Because GRE traffic became out via tun0 interface and after recursion overfiow connection terminated(ppp.log.1). Please help, I have no more ideas now. ppp.conf: vpn: set authname myname set authkey mypassword set timeout 0 set ifaddr 0 0 set mtu 1500 add default HISADDR ppp.log: Jul 30 12:22:27 sputnik ppp[1120]: Phase: Using interface: tun0 Jul 30 12:22:27 sputnik ppp[1120]: Phase: deflink: Created in closed state Jul 30 12:22:27 sputnik ppp[1120]: Phase: PPP Started (direct mode). Jul 30 12:22:27 sputnik ppp[1120]: Phase: bundle: Establish Jul 30 12:22:27 sputnik ppp[1120]: Phase: deflink: closed -> opening Jul 30 12:22:27 sputnik ppp[1120]: Phase: deflink: Connected! Jul 30 12:22:27 sputnik ppp[1120]: Phase: deflink: opening -> carrier Jul 30 12:22:28 sputnik ppp[1120]: Phase: deflink: carrier -> lcp Jul 30 12:22:29 sputnik ppp[1120]: Phase: bundle: Authenticate Jul 30 12:22:29 sputnik ppp[1120]: Phase: deflink: his = CHAP 0x05, mine = none Jul 30 12:22:29 sputnik ppp[1120]: Phase: Chap Input: CHALLENGE (19 bytes from satgate) Jul 30 12:22:29 sputnik ppp[1120]: Phase: Chap Output: RESPONSE (myname) Jul 30 12:22:35 sputnik ppp[1120]: Phase: Chap Input: SUCCESS (^E) Jul 30 12:22:35 sputnik ppp[1120]: Phase: deflink: lcp -> open Jul 30 12:22:35 sputnik ppp[1120]: Phase: bundle: Network Jul 30 12:22:35 sputnik ppp[1120]: Phase: deflink: IPV6CP protocol reject closes IPV6CP ! Jul 30 12:22:35 sputnik ppp[1120]: Phase: deflink: IPV6CP protocol reject closes IPV6CP ! Jul 30 12:22:38 sputnik ppp[1120]: Warning: iface add: ioctl(SIOCAIFADDR, 85.195.153.121 -> 82.198.6.19): File exists Jul 30 12:22:38 sputnik ppp[1120]: Error: ipcp_InterfaceUp: unable to set ip address Jul 30 12:22:42 sputnik ppp[1120]: Phase: deflink: IPV6CP protocol reject closes IPV6CP ! Jul 30 12:22:44 sputnik ppp[1120]: Phase: deflink: IPV6CP protocol reject closes IPV6CP ! Jul 30 12:22:45 sputnik ppp[1120]: Phase: deflink: open -> lcp Jul 30 12:22:45 sputnik ppp[1120]: Phase: bundle: Terminate Jul 30 12:22:45 sputnik ppp[1120]: Phase: Signal 15, terminate. Jul 30 12:22:48 sputnik ppp[1120]: Phase: deflink: Disconnected! Jul 30 12:22:48 sputnik ppp[1120]: Phase: deflink: Connect time: 21 secs: 664 octets in, 534 octets out Jul 30 12:22:48 sputnik ppp[1120]: Phase: deflink: 22 packets in, 28 packets out Jul 30 12:22:48 sputnik ppp[1120]: Phase: total 57 bytes/sec, peak 119 bytes/sec on Sun Jul 30 12:22:30 2006 Jul 30 12:22:48 sputnik ppp[1120]: Phase: deflink: lcp -> closed Jul 30 12:22:48 sputnik ppp[1120]: Phase: bundle: Dead Jul 30 12:22:48 sputnik ppp[1120]: Phase: PPP Terminated (normal). ppp.log.1: Jul 31 17:55:05 sputnik ppp[5536]: Phase: Using interface: tun0 Jul 31 17:55:05 sputnik ppp[5536]: Phase: deflink: Created in closed state Jul 31 17:55:05 sputnik ppp[5536]: Phase: PPP Started (direct mode). Jul 31 17:55:05 sputnik ppp[5536]: Phase: bundle: Establish Jul 31 17:55:05 sputnik ppp[5536]: Phase: deflink: closed -> opening Jul 31 17:55:05 sputnik ppp[5536]: Phase: deflink: Connected! Jul 31 17:55:05 sputnik ppp[5536]: Phase: deflink: opening -> carrier Jul 31 17:55:06 sputnik ppp[5536]: Phase: deflink: carrier -> lcp Jul 31 17:55:07 sputnik ppp[5536]: Phase: bundle: Authenticate Jul 31 17:55:07 sputnik ppp[5536]: Phase: deflink: his = CHAP 0x05, mine = none Jul 31 17:55:07 sputnik ppp[5536]: Phase: Chap Input: CHALLENGE (23 bytes from satgate) Jul 31 17:55:07 sputnik ppp[5536]: Phase: Chap Output: RESPONSE (myname) Jul 31 17:55:13 sputnik ppp[5536]: Phase: Chap Input: SUCCESS (^E) Jul 31 17:55:13 sputnik ppp[5536]: Phase: deflink: lcp -> open Jul 31 17:55:13 sputnik ppp[5536]: Phase: bundle: Network Jul 31 17:55:13 sputnik ppp[5536]: Phase: deflink: IPV6CP protocol reject closes IPV6CP ! Jul 31 17:55:13 sputnik ppp[5536]: Phase: deflink: IPV6CP protocol reject closes IPV6CP ! Jul 31 17:55:14 sputnik ppp[5536]: Phase: Signal 15, terminate. Jul 31 17:55:14 sputnik ppp[5536]: Phase: Signal 15, terminate. Jul 31 17:55:14 sputnik ppp[5536]: Phase: deflink: read (0): Got zero bytes Jul 31 17:55:14 sputnik ppp[5536]: Phase: deflink: open -> lcp Jul 31 17:55:14 sputnik ppp[5536]: Phase: bundle: Terminate Jul 31 17:55:14 sputnik ppp[5536]: Phase: deflink: Disconnected! !!! Jul 31 17:55:14 sputnik ppp[5536]: Phase: deflink: Connect time: 9 secs: 490 octets in, 872018 octets out !!! Jul 31 17:55:14 sputnik ppp[5536]: Phase: deflink: 15 packets in, 1431 packets out Jul 31 17:55:14 sputnik ppp[5536]: Phase: total 96945 bytes/sec, peak 126 bytes/sec on Mon Jul 31 17:55:08 2006 Jul 31 17:55:14 sputnik ppp[5536]: Phase: deflink: lcp -> closed Jul 3
