Re: Unable to get ip6 address
Following is the output of cat /etc/hostanme.mtw0 nwid network Wpakey passwd inet autoconf inet6 autoconf On 15 March 2024 23:08:14 GMT+05:30, "Peter N. M. Hansteen" wrote: >Please keep this on the list unless you want me to start writing invoices. > >On Fri, Mar 15, 2024 at 05:02:27PM +, Pencilgon wrote: >> Sorry for earlier email, I left you some details. >> >> First of all I don't think ip6 work at all, well in theory inet6 autoconf >> should >> work and grant me internet access but it doesn't, I don't get a ip6 address >> at >> all. >> >> Second I am unable to get ip4 address even on wifi. > >This sounds like your wifi interface is not in fact properly configured. > >For this to produce anything even resembling useful results, we need to see at >least the content of your configuration files -- /etc/hostmhame.* and the >output >of ifconfig for the relevant interfaces (if need be with stuff like IP >addresses >and passwords masked). > >-- >Peter N. M. Hansteen, member of the first RFC 1149 implementation team >https://bsdly.blogspot.com/ https://www.bsdly.net/ https://www.nuug.no/ >"Remember to set the evil bit on all malicious network traffic" >delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds. >
Re: Unable to get ip6 address
I have uses mtw wifi firmware. I don't know what do you mean by multicast. I works perfectly fine with linux. On 15 March 2024 23:10:52 GMT+05:30, Stuart Henderson wrote: >On 2024-03-15, Hari wrote: >> >> Well I read and tried to this as stated in faq=2E But it doesn't work, well= >> ip6 does work if I trt ethernet but not with wifi=2E > >At least send a dmesg so readers have some idea of the hardware involved. > >One possible problem: IPv6 requires multicast for address resolution >which might not be working properly. > >
Re: Unable to get ip6 address
Well I read and tried to this as stated in faq. But it doesn't work, well ip6 does work if I trt ethernet but not with wifi. On 15 March 2024 21:20:35 GMT+05:30, "Peter N. M. Hansteen" wrote: >On Fri, Mar 15, 2024 at 03:32:48PM +, Pencilgon wrote: >> I recently installed openbsd got everything working wifi etc. The problem >> arises >> when I tried to connect ip6 network to it using wifi. I connected sucessfully >> but was unable to get ip6 address. My wifi worked fine with ip4 address. > >If your network offers IPv6 connectivity and you have IPv4 working, simply >adding > >inet6 autoconf > >to the hostname.$if file for the interface and running /etc/netstart $if >*should* take care of things. > >There are any number of other possible variations, but you do need some >'inet6' settings in there. > >- Peter > >-- >Peter N. M. Hansteen, member of the first RFC 1149 implementation team >https://bsdly.blogspot.com/ https://www.bsdly.net/ https://www.nuug.no/ >"Remember to set the evil bit on all malicious network traffic" >delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds. >
No internet even wifi is active
There is no internet connection with mobile hotspot even though ifconfig shows that eifi is active. There is in destination or gateway in netstate -rn. I suspect sonething is wrong with dhcp but I can't think of any solution. Please look into this issue. Thanks
Re:
I am not sure what you mean by if am able to connect other host to it, if you
mean wether I am able to connect other wifi then no. Same problem occures while
connecting to other wifi. Also even though ifconfig status is active my lc
doesn't appears in list lo connected device in android
On 10 March 2024 21:28:05 GMT+05:30, "Zé Loff" wrote:
>
>On Sun, Mar 10, 2024 at 02:43:02PM +, Hari wrote:
>> Here is the requested output:
>>
>> lo0: flags=2008049 mtu 32768
>> index 2 priority 0 llprio 3
>> groups: lo
>> inet6 ::1 prefixlen 128
>> inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2
>> inet 127.0.0.1 netmask 0xff00
>> enc0: flags=0<>
>> index 1 priority 0 llprio 3
>> groups: enc
>> status: active
>> mtw0:
>> flags=a48843
>> mtu 1500
>> lladdr 00:e0:2d:4c:73:7f
>> index 4 priority 4 llprio 3
>> groups: wlan
>> media: IEEE802.11 autoselect (DS1 mode 11g)
>> status: active
>> ieee80211: nwid net chan 2 bssid 2e:d1:fa:8e:62:51 -27dBm wpakey
>> wpaprotos wpa2 wpaakms psk wpaciphers ccmp wpagroupcipher ccmp
>> inet6 fe80::2e0:2dff:fe4c:737f%mtw0 prefixlen 64 scopeid 0x4
>> pflog0: flags=141 mtu 33136
>> index 5 priority 0 llprio 3
>> groups: pflog
>> nwid net
>> wpakey connect2net
>> inet autoconf
>> inet6 autoconf
>> Routing tables
>>
>> Internet:
>> Destination Gateway Flags Refs Use Mtu Prio Iface
>> 224/4 127.0.0.1 URS 0 0 32768 8 lo0
>> 127/8 127.0.0.1 UGRS 0 0 32768 8 lo0
>> 127.0.0.1 127.0.0.1 UHhl 1 2 32768 1 lo0
>>
>> Internet6:
>> Destination
>> Gateway Flags Refs Use Mtu Prio
>> Iface
>> ::/96
>> ::1 UGRS 0 0 32768 8 lo0
>> ::1
>> ::1 UHhl 10 100 32768 1 lo0
>> :::0.0.0.0/96
>> ::1 UGRS 0 0 32768 8 lo0
>> 2002::/24
>> ::1 UGRS 0 0 32768 8 lo0
>> 2002:7f00::/24
>> ::1 UGRS 0 0 32768 8 lo0
>> 2002:e000::/20
>> ::1 UGRS 0 0 32768 8 lo0
>> 2002:ff00::/24
>> ::1 UGRS 0 0 32768 8 lo0
>> fe80::/10
>> ::1 UGRS 0 2 32768 8 lo0
>> fec0::/10
>> ::1 UGRS 0 0 32768 8 lo0
>> fe80::1%lo0
>> fe80::1%lo0 UHl 0 0 32768 1 lo0
>> fe80::%mtw0/64
>> fe80::2e0:2dff:fe4c:737f%mtw0 UCn 0 0 - 8
>> mtw0
>> fe80::2e0:2dff:fe4c:737f%mtw0
>> 00:e0:2d:4c:73:7f UHLl 0 0 - 1
>> mtw0
>> ff01::/16
>> ::1 UGRS 0 12 32768 8 lo0
>> ff01::%lo0/32
>> fe80::1%lo0 Um 0 1 32768 4 lo0
>> ff01::%mtw0/32
>> fe80::2e0:2dff:fe4c:737f%mtw0 Um 0 0 - 4
>> mtw0
>> ff02::/16
>> ::1 UGRS 0 12 32768 8 lo0
>> ff02::%lo0/32
>> fe80::1%lo0 Um 0 1 32768 4 lo0
>> ff02::%mtw0/32
>> fe80::2e0:2dff:fe4c:737f%mtw0 Um 0 1 - 4
>> mtw0
>>
>>
>>
>>
>>
>>
>>
>>
>> Sorry for delayed reply
>
>Your mrt0 interface is connected to the access point ("status: active")
>but has no IP address. Since its set for autoconf, this means it's not
>getting an address from a DHCP server.
>
>Are you sure you have one listening on the wifi network? Are you able
>to connect other hosts to it (e.g. a mobile phone, or another machine)?
>If so, does the access point or the host running the DHCP server have
>any kind of MAC filtering?
>
>--
>
>
[no subject]
Here is the requested output: lo0: flags=2008049 mtu 32768 index 2 priority 0 llprio 3 groups: lo inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 inet 127.0.0.1 netmask 0xff00 enc0: flags=0<> index 1 priority 0 llprio 3 groups: enc status: active mtw0: flags=a48843 mtu 1500 lladdr 00:e0:2d:4c:73:7f index 4 priority 4 llprio 3 groups: wlan media: IEEE802.11 autoselect (DS1 mode 11g) status: active ieee80211: nwid net chan 2 bssid 2e:d1:fa:8e:62:51 -27dBm wpakey wpaprotos wpa2 wpaakms psk wpaciphers ccmp wpagroupcipher ccmp inet6 fe80::2e0:2dff:fe4c:737f%mtw0 prefixlen 64 scopeid 0x4 pflog0: flags=141 mtu 33136 index 5 priority 0 llprio 3 groups: pflog nwid net wpakey connect2net inet autoconf inet6 autoconf Routing tables Internet: Destination Gateway Flags Refs Use Mtu Prio Iface 224/4 127.0.0.1 URS 0 0 32768 8 lo0 127/8 127.0.0.1 UGRS 0 0 32768 8 lo0 127.0.0.1 127.0.0.1 UHhl 1 2 32768 1 lo0 Internet6: Destination Gateway Flags Refs Use Mtu Prio Iface ::/96 ::1 UGRS 0 0 32768 8 lo0 ::1 ::1 UHhl 10 100 32768 1 lo0 :::0.0.0.0/96 ::1 UGRS 0 0 32768 8 lo0 2002::/24 ::1 UGRS 0 0 32768 8 lo0 2002:7f00::/24 ::1 UGRS 0 0 32768 8 lo0 2002:e000::/20 ::1 UGRS 0 0 32768 8 lo0 2002:ff00::/24 ::1 UGRS 0 0 32768 8 lo0 fe80::/10 ::1 UGRS 0 2 32768 8 lo0 fec0::/10 ::1 UGRS 0 0 32768 8 lo0 fe80::1%lo0 fe80::1%lo0 UHl 0 0 32768 1 lo0 fe80::%mtw0/64 fe80::2e0:2dff:fe4c:737f%mtw0 UCn 0 0 - 8 mtw0 fe80::2e0:2dff:fe4c:737f%mtw0 00:e0:2d:4c:73:7f UHLl 0 0 - 1 mtw0 ff01::/16 ::1 UGRS 0 12 32768 8 lo0 ff01::%lo0/32 fe80::1%lo0 Um 0 1 32768 4 lo0 ff01::%mtw0/32 fe80::2e0:2dff:fe4c:737f%mtw0 Um 0 0 - 4 mtw0 ff02::/16 ::1 UGRS 0 12 32768 8 lo0 ff02::%lo0/32 fe80::1%lo0 Um 0 1 32768 4 lo0 ff02::%mtw0/32 fe80::2e0:2dff:fe4c:737f%mtw0 Um 0 1 - 4 mtw0 Sorry for delayed reply
No internet while using wifi
Hello, I wanted to connect my openbsd system to wifi. So I downloaded and installed the the necessary wifi firmware using wired connetion. As stated in openbsd wireless networking faq I edited the /etc/hostname.mtw0 file and added the necessary details according to the format. Then I started the /etc/netstart and ifconfig showed the status to be active. But I had no internet connection. I tried using dhcp via ifconfig mtw0 inet autoconf and tried dhclient but noone work there was no ip in netstat -rn.
Re: OpenBSD 4.4 released, Nov 1. Enjoy!
On Wed, Nov 12, 2008 at 6:26 AM, new_guy [EMAIL PROTECTED] wrote: David Schulz-5 wrote: yes, its awesome this time ! That's like telling your wife, You look beautiful... today. It's better to leave off the last part. It's awesome will suffice. I _think_ the reference was to the song. I have listened to all of the release songs (fairly recently). They all rock. I strongly recommend a listen if one hasn't done so already. If you are a Pink Floyd fan, you might appreciate The Wizard of OS. Hari
Re: Patching a SSH 'Weakness'
On Thu, Sep 11, 2008 at 4:58 AM, Kevin Neff [EMAIL PROTECTED] wrote: Hi, Some secure protocols like SSH send encrypted keystrokes as they're typed. By doing timing analysis you can figure out which keys the user probably typed (keys that are physically close together on a keyboard can be typed faster). A careful analysis can reveal the length of passwords and probably some of password itself. The paper: http://portal.acm.org/citation.cfm? id=1267612.1267637coll=Portaldl=GUIDECFID=1943417C FTOKEN=28290455 The paper itself is not accessible. Prima facie, this looked like a technology-in-search-of-a-problem kinda thing to me. For now, it sounds like bull. However, there are atleast 10 references to keystoke timing/characteristics. That this 'weakness' holds water is a judgement call. Of course, one can make any kind of conclusion only after studying the paper/references. Hari
Re: DHCP question
On Fri, Jul 25, 2008 at 6:07 PM, Henning Brauer [EMAIL PROTECTED] wrote: if that still doesn't work... after install, at the boot prompt, do boot -c, and the the upcoming UKC prompt do a disable acpi followed by quit once the system is running send dmesgs with and without acpi and acpidump output (forgot exact instructions, ask list archives) to marco@ and jordan@ openbsd.org Henning Brauer Hello. Apologies for the relatively late reply. I was kinda hoping that OpenBSD would run OOTB on this. However, from the looks of it, might take sometime to get it working. Since our team is on a clock, I got 4.3 CD working on another computer without any problems. Everything works OOTB and we have set that up for our needs. As and when time permits, I shall try and follow up on this network problem. As an aside, would a different NIC solve this problem? Hari
DHCP question
Hello. I just finished installing OpenBSD 4.3. The dhcp setup during network configuration was fine, meaning, IP address was properly assigned. I went ahead with the default values provided. However, after rebooting post installation, I am getting the following messages that seems to point to a network problem (and of course, no IP address is assigned): messages fxp0: warning: SCB timed out (x 3) fxp0: config command timeout DHCPDISCOVER on fxp0 to 255.255.255.255 port 67 interval 1 send_packet: Network is down No DHCPOFFERS received. No working leases in persistent database - sleeping. /messages Several `intervals` are tried. Dump of some relevant(?) files: #ifconfig lo0: flags-8049UP,LOOPBACK,RUNNING,MULTICAST mtu 33208 groups: lo inet 127.0.0.1 netmask 0xff00 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 fxp0: flags-8049UP,LOOPBACK,RUNNING,MULTICAST mtu 33208 lladdr 00:16:76:13:ad:54 media: Ethernet autoselect (100baseTX full-duplex) status: active inet6 fe80::216::76ff::fe13::ad54%fxp0 prefixlen 64 tentative scopeid 0x1 enc0: flags=0 mtu 1536 #cat /etc/hosts: ::1 localhost.WORKGROUP locahost 127.0.0.1 localhost.WORKGROUP localhost ::1 mercury.WORKGROUP mercury 127.0.0.1 mercury.WORKGROUP mercury #cat /etc/hostname.fxp0: dhcp NONE NONE NONE #cat /etc/resolv.conf lookup file bind # hostname mercury.my.domain #domainname (none) For my internet connection, I have a router that acts as a DHCP server assigning IPs as 192.168.11.x. Why is the OpenBSD box not assigned an IP by this router? Can anyone please let me know how I can get the network up and running on the OpenBSD box? Please let me know in case I have missed out on listing any config files. Thanks. Hari
Re: DHCP question
On Wed, Jul 23, 2008 at 4:53 PM, Tomas Bodzar [EMAIL PROTECTED] wrote: $man fxp timed out - problem with network from your post : send_packet: Network is down The network is good and working and this OpenBSD box is able to grab an IP address during the initial network configuration during installation*. I have checked the cables, etceverything is fine. Its only when I reboot post install, the network is not found and consequently no IP is assigned. * To verify this, I have reinstalled OpenBSD 4.3 multiple times (on the same computer, same location). _Everytime_, an IP address is assigned properly during the initial configuration. Hari
Re: DHCP question
On Wed, Jul 23, 2008 at 5:05 PM, Tomas Bodzar [EMAIL PROTECTED] wrote: Ok.So next step. $sudo ifconfig fxp0 dhcp up gives what? $sudo ifconfig fxp0 dhcp up ifconfig: dhcp: bad value $ :-(
Re: DHCP question
On Wed, Jul 23, 2008 at 5:11 PM, Tomas Bodzar [EMAIL PROTECTED] wrote: Eh,I missed something.Look at /etc/hosts and $hostname Why is localhost.WORKGROUP localhost in /etc/hosts and mercury.my.domain in $hostname I have long suspected that this is the problem. I am a novice at this and I have little understanding. I have gone through the man pages for /etc/hosts but I could not figure out what exactly I was doing wrong. What should /etc/hosts read as? And what should the $hostname be? The machine is to be named mercury. $sudo ifconfig fxp0 up fxp0: warning: SCB timed out (x3) fxp0: config command timeout Hari
Re: DHCP question
On Wed, Jul 23, 2008 at 5:36 PM, Tony Abernethy [EMAIL PROTECTED] wrote: Silly question, but WHAT IP is actually assigned during install? I think something like ifconfig before the halt might work I assume you are installing from CD, not from network It might be as simple as a cable not completely plugged in. IIRC, it was 192.168.11.8. The DNS was properly identified as the router (192.168.11.1). I dont think there is a problem with the cabling. (I double checked this with a laptop). Hari
Re: DHCP question
On Wed, Jul 23, 2008 at 5:48 PM, Almir Karic [EMAIL PROTECTED] wrote: #ifconfig lo0: flags-8049UP,LOOPBACK,RUNNING,MULTICAST mtu 33208 groups: lo inet 127.0.0.1 netmask 0xff00 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 fxp0: flags-8049UP,LOOPBACK,RUNNING,MULTICAST mtu 33208 isn't having LOOPBACK flag and mtu 33208 on a 'real' interface strange? Apologies. This is my fault. I copied the text incorrectly. #ifconfig lo0: flags-8049UP,LOOPBACK,RUNNING,MULTICAST mtu 33208 groups: lo inet 127.0.0.1 netmask 0xff00 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 fxp0: flags-8803UP,BROADCAST,SIMPLEX,MULTICAST mtu 1500 Rest is OK. Apologies once again. Hari
Re: DHCP question
On Wed, Jul 23, 2008 at 5:57 PM, Tony Abernethy [EMAIL PROTECTED] wrote: My (not so) humble opinion. /etc/hosts is the poor man's DNS -- what name to what IP ::1 localhost.foo.bar localhost 127.0.0.1 localhost.foo.bar localhost ::1 gw.foo.bar gw this-box 192.168.10.1gw this-box gw.foo.bar 192.168.10.22 that-box Actually the local box can have a lot of names, all for the same IP. Looks like your hostname goes into /etc/myname I just popped the CD in and the installation is on now. This is what am getting during network configuration: System hostname? mercury Configure the network? [Yes] Available interfaces are: fxp0 Which one do you want to initialize? (or 'done') [fxp0] Symbolic (host) name for fxp0? [mercury] The media options for fxp0 are currently media: Ethernet autoselect (qoobaseTX full-duplex) Do you want to change the media options? [no] IPv4 address for fxp0? (or 'none' or 'dhcp') dhcp Issuing hostname-associated DHCP request for fxp0. DHCPDISCOVER on fxp0 to 255.255.255.255 port 67 interval 2 DHCPOFFER from 192.168.11.1 DHCPREQUEST on fxp0 to 255.255.255.255 port 67 DHCPACK from 192.168.11.1 bound to 192.168.11.8 -- renewal in 86400 seconds IPv6 address for fxp0? (or rtsol or none) [none] No more interfaces to initialize. DNS domain name? (e.g. 'bar.com') [my.domain] DNS nameserver? (IP address or 'none') [192.168.11.1] none Default IPv4 route? (IPv4 address, 'dhcp' or 'none') [dhcp] Edit hosts with ed? [no] Do you want to do any manual network configuration? [no] After this, ifconfig on the system gives: $ifconfig lo: flags=8008LOOPBACK,MULTICAST mtu 33208 groups: lo fxp0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 lladdr 00:16:76:13:ad:54 groups: dhcp egress media: Ethernet autoselect (100baseTX full-duplex) status: active inet6 fe80:216:76ff:fe13:ad54%fxp0 prefixlen 64 scopeid 0x1 inet 192.168.11.8 netmask 0xff00 broadcast 192.168.11.255 After rebooting, the network is not up. Getting the error messages I posted initially. Hari
Re: DHCP question
On Wed, Jul 23, 2008 at 6:16 PM, Robert Blacquiere [EMAIL PROTECTED] wrote: I thing here is the real problem. It seems the fxp0 interface fails to do some initializing. This probably results in the interface not being fully enabled/up. I'me not sure what SCB is but i think is related to signaling / irq ? Do you see this also with the bsd.rd kernel? Please look if there are differences between the to in dmesg and ifconfig fxp0 ? I checked dmesg and the output of 'ifconfig fxp0 up'. There is no difference. The only time out messages listed in dmesg are from fxp0 (dmesg | grep -i time). How do I check the SCB thing with the bsd.rd kernel? Hari
Re: DHCP question
On Wed, Jul 23, 2008 at 9:28 PM, Henning Brauer [EMAIL PROTECTED] wrote: ..., so please grab 4.4-beta fron the snapshots dir on ftp and try that. if that still doesn't work, get us full dmesgs as stuart already outlined. I tried with OpenBSD4.4 beta (July 22, 2008) install. Still facing the same network problem. Attached are the dmesgs for bsd.rd and bsd for OpenBSD4.4-latest. Hari [demime 1.01d removed an attachment of type application/octet-stream which had a name of dmesg.44.bsd.out] [demime 1.01d removed an attachment of type application/octet-stream which had a name of dmesg.44.bsd.rd.out]
