Re: CP2102 UART adapter not attaching

2016-01-12 Thread Hans Petter Selasky
On 01/13/16 07:04, Mark Johnston wrote: On Mon, Jan 11, 2016 at 09:41:01AM +0100, Hans Petter Selasky wrote: On 01/10/16 05:07, Mark Johnston wrote: Hi, I have the module listed here: http://www.amazon.com/KEDSUM%C2%AE-CP2102-Module-Download-Converter/dp/B009T2ZR6W Under Windows 8 it works

Re: CP2102 UART adapter not attaching

2016-01-12 Thread Hans Petter Selasky
On 01/13/16 07:17, Mark Johnston wrote: On Wed, Jan 13, 2016 at 07:17:04AM +0100, Hans Petter Selasky wrote: On 01/13/16 07:04, Mark Johnston wrote: On Mon, Jan 11, 2016 at 09:41:01AM +0100, Hans Petter Selasky wrote: On 01/10/16 05:07, Mark Johnston wrote: Hi, I have the module listed

Re: CP2102 UART adapter not attaching

2016-01-12 Thread Mark Johnston
On Mon, Jan 11, 2016 at 09:41:01AM +0100, Hans Petter Selasky wrote: > On 01/10/16 05:07, Mark Johnston wrote: > > Hi, > > > > I have the module listed here: > > http://www.amazon.com/KEDSUM%C2%AE-CP2102-Module-Download-Converter/dp/B009T2ZR6W > > > > Under Windows 8 it works perfectly, but on

[Bug 206143] DLINK DUB-E100 revision C1 can't reach destination

2016-01-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206143 Hans Petter Selasky changed: What|Removed |Added CC|

[Bug 206143] DLINK DUB-E100 revision C1 can't reach destination

2016-01-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206143 --- Comment #4 from Hans Petter Selasky --- Also, did you try to enable debugging for your driver? sysctl -a hw.usb | grep debug --HPS -- You are receiving this mail because: You are the assignee for the bug.

[Bug 206143] DLINK DUB-E100 revision C1 can't reach destination

2016-01-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206143 --- Comment #2 from Mantas --- (In reply to Hans Petter Selasky from comment #1) Mister, it's nor firewall, nor routing settings, it's something with the drivers specificaly with C1 revision of this device. I'm not the

[Bug 206143] DLINK DUB-E100 revision C1 can't reach destination

2016-01-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206143 --- Comment #3 from Hans Petter Selasky --- Hi, Sorry if you have to repeat yourself. Did you try to make a tcpdump trace showing why traffic is not passing like expected: "tcpdump -i ue0 -pn -w test.pcap" The only

[Bug 206143] DLINK DUB-E100 revision C1 can't reach destination

2016-01-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206143 --- Comment #5 from Hans Petter Selasky --- If the debug knob is not there, you'll have to rebuild the network driver you are using like this: cd /usr/src make -C sys/modules/usb/xxx -m $PWD/share/mk

[Bug 206143] DLINK DUB-E100 revision C1 can't reach destination

2016-01-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206143 --- Comment #17 from Mantas --- (In reply to Hans Petter Selasky from comment #16) #ipfw2 show ipfw2: Command not found. #ipfw show ipfw: Context is mandatory: No such file or directory -- You are receiving this mail

[Bug 206143] DLINK DUB-E100 revision C1 can't reach destination

2016-01-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206143 --- Comment #15 from Hans Petter Selasky --- Hi, I suspect maybe pfsense doesn't recognize the ue0 properly and sets up some firewall rules which block the webpage access. Can you check the statistics for the

[Bug 206143] DLINK DUB-E100 revision C1 can't reach destination

2016-01-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206143 --- Comment #6 from Mantas --- Created attachment 165435 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=165435=edit pcap file -- You are receiving this mail because: You are the assignee for the bug.

[Bug 206143] DLINK DUB-E100 revision C1 can't reach destination

2016-01-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206143 --- Comment #7 from Mantas --- (In reply to Hans Petter Selasky from comment #5) Debug was set to 0, so I have to rebuild it, but there is no directory /usr/src, since it's pfsense, not full freebsd. -- You are

[Bug 206143] DLINK DUB-E100 revision C1 can't reach destination

2016-01-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206143 --- Comment #16 from Hans Petter Selasky --- Is there something like "ipfw2 show" or "ipfw show" in the command list of your pfsense installation? -- You are receiving this mail because: You are the assignee for the

[Bug 206143] DLINK DUB-E100 revision C1 can't reach destination

2016-01-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206143 Anatoly changed: What|Removed |Added CC|

[Bug 206143] DLINK DUB-E100 revision C1 can't reach destination

2016-01-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206143 --- Comment #14 from Mantas --- (In reply to Hans Petter Selasky from comment #11) It just can't be any misconfiguration. All I do is is set ale0 interface as my lan interface. Everything works fine Then I do factory

[Bug 206143] DLINK DUB-E100 revision C1 can't reach destination

2016-01-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206143 --- Comment #8 from Mantas --- (In reply to Hans Petter Selasky from comment #4) systctl hw.usb.debug=1 it changed from 0 to 1, so it means the knob is there, right? -- You are receiving this mail because: You are the

[Bug 206143] DLINK DUB-E100 revision C1 can't reach destination

2016-01-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206143 --- Comment #9 from Hans Petter Selasky --- (In reply to Mantas from comment #8) No, that's the wrong one. You should find one like: hw.usb.axe.debug=16 Or something like that. --HPS -- You are receiving this

[Bug 206143] DLINK DUB-E100 revision C1 can't reach destination

2016-01-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206143 --- Comment #10 from Mantas --- There is no axe.debug, but there also is no /usr/src/ directory in pfsense. How should I procede? -- You are receiving this mail because: You are the assignee for the bug.

[Bug 206143] DLINK DUB-E100 revision C1 can't reach destination

2016-01-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206143 --- Comment #11 from Hans Petter Selasky --- In your test.pcap, there are a lot of destination unreachable messages. It might indicate a misconfiguration of some kind. Traffic seems to be flowing both in and out of

[Bug 206143] DLINK DUB-E100 revision C1 can't reach destination

2016-01-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206143 --- Comment #13 from Mantas --- (In reply to Hans Petter Selasky from comment #12) #ifconfig ath0: flags=8843 metric 0 mtu 2290 ether 00:25:d3:65:ab:ab nd6

[Bug 206143] DLINK DUB-E100 revision C1 can't reach destination

2016-01-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206143 --- Comment #12 from Hans Petter Selasky --- (In reply to Mantas from comment #10) Can you show me the output from: sysctl hw.usb And: ifconfig And: dmesg | grep ugen --HPS -- You are receiving this mail