I'm using a tunnel broker for tunneling IPv6 traffic, as my ISP does not support it natively. As of recent i switched from Hurricane Electrics tunnel broker to Sixxs.
Whenever my IP address changes, i have to manually log in and change it. This is a bit cumbersome so i was thinking of devising a Perl script for this.
With my old tunnel broker ( The one from HE), logins were made over basic Http, this made this a lot easier as you could actually see what was being sent. For example, firing up Wireshark showed.
With the tunnel broker from Sixxs logins are made over SSL, so you have no idea of what is being sent. Is there a way to figure out what to pass to POST?
Issue observed: I have configured ng.my-site.com using widlcard ssl cert. When I hit https://www.my-site.com it loads ng.my-site.com website!
please advise if I missed any concept / configs... Thank you!
httpd.conf
<VirtualHost *:80>
ServerName www.my-site.com
ServerAdmin... (0 Replies)
I'm currently using OpenBSD current as of yesterday. Both curl and wget aren't not part of the OpenBSD base and I would rather attempt to reboot my cable modem (SB6183) using perl HTTP:Tiny if possible. The following 2 commands work and both will reboot my modem:
curl -d Rebooting=1... (3 Replies)
Hi,
I am trying to write a shell script to parse the post request data that it received to a xml file. Below is the post request data that script is receiving.
-----------------------------7dd2339190c8e
Content-Disposition: form-data; name="param1"
1... (2 Replies)
Hello folks,
I need a piece of code in perl which can read the file having multiple ssl certificates in text format one after the other as shown below. I need to parse this file and find out the common names of each of ssl certs it contains.
E.g.
-----BEGIN CERTIFICATE-----... (4 Replies)
Hi
am using a variable in my http post message which is getting data from the select query as follows. if i use some values assigned to that variable , http post works fine but if i use the data of select query its not working...what could be issue?
#!/bin/bash
export... (3 Replies)
Hi,
I am using curl to hit a url using http in solaris 10 using commandline, I want to transfer an attachment(using multipart curl -F) also as a part of the request. If anyone has used kindly help me with the syntax. I am using below command:
Code:
/usr/local/bin/curl -v... (1 Reply)
Hello,
I have 2 solaris 10 systems which are behind a load balancer serving 50% requests each. Both systems are installed with an application which run apache http server on port 80 and 443. both systems use the same virtual hostname like (app.domain.com). So when users hit http://app.domain.com... (1 Reply)
this may be very basic to some but all new to me
I have an application running on SCO Unix server which issues an HTTP Post request to a server with the results being returned in I.E browser window in XML format
I need to import these results into my customers application and dont know how to... (1 Reply)
NOS-TUN(8) BSD System Manager's Manual NOS-TUN(8)NAME
nos-tun -- implement ``nos'' or ``ka9q'' style IP over IP tunnel
SYNOPSIS
nos-tun -t tunnel -s source -d destination -p protocol_number [source] target
DESCRIPTION
The nos-tun utility is used to establish an nos style tunnel, (also known as ka9q or IP-IP tunnel) using a tun(4) kernel interface.
Tunnel is the name of the tunnel device /dev/tun0 for example.
Source and destination are the addresses used on the tunnel device. If you configure the tunnel against a cisco router, use a netmask of
``255.255.255.252'' on the cisco. This is because the tunnel is a point-to-point interface in the FreeBSD end, a concept cisco does not
really implement.
Protocol number sets tunnel mode. Original KA9Q NOS uses 94 but many people use 4 on the worldwide backbone of ampr.org.
Target is the address of the remote tunnel device, this must match the source address set on the remote end.
EXAMPLES
This end, a FreeBSD box on address 192.168.59.34:
nos-tun -t /dev/tun0 -s 192.168.61.1 -d 192.168.61.2 192.168.56.45
Remote cisco on address 192.168.56.45:
interface tunnel 0
ip address 192.168.61.2 255.255.255.252
tunnel mode nos
tunnel destination 192.168.59.34
tunnel source 192.168.56.45
AUTHORS
Nickolay N. Dudorov <nnd@itfs.nsk.su> wrote the program, Poul-Henning Kamp <phk@FreeBSD.org> wrote the man-page. Isao SEKI
<iseki@gongon.com> added a new flag, IP protocol number.
BUGS
We do not allow for setting our source address for multihomed machines.
BSD April 11, 1998 BSD